Software Engineering
Project 4-blockers
Course Map
Agenda
- Course Map
- Course Project
- What is a 4-blocker
- Team Member Roles
- Project 4-blockers
Course Project
Develop one of the the following systems:
-
Voting System
(see the detailed requirements and the code examples in the textbook
(requirements based on
Section 1.8 in
the textbook))
-
Web-based course registration system
- Student Dashboard oriented
-
Web-based banking system (multiple
accounts types)
-
Web-based ATM system (a web-based
cash machine software system)
-
Online book sale system
- A 4-blocker is a concise one-page project proposal focused on business
requirements.
A 4-blocker
concisely and clearly defines (each not critical word should be removed):
- Project description - state the problem statement (difficulty that needs
to be resolved) and the problem
conclusions
- Project objective and approach - how you can reach the project main goal
(objective)
- Requirements (Functional/Non-functional) - requirements definition and the relevance of the project - why you are not wasting your
and my time
- Resources/Schedule - a realistic step-by-step timeline with required
resources
- Extended 4-blocker contains all
related
user
stories,
non-functional requirements
- All 4-blockers will be posted (linked to your project website) in this page
below.
- Use the provided 4-blocker template (JPG PL) (PPT PL) (JPG EN) (PPT EN)
- Examples of SORCER
lab 4-blockers
- Team Leader - responsible for planning team activities, website, CVS, scheduling review meetings, demos and
final presentation/demo (bug tracking system, email archive)
- Architect - architectural analysis, design, concurrency, distribution
- Use Case Designer - use case analysis, design
- Designer - object analysis, design
- Design Reviewer (team leader) - QA, review analysis, design,
architecture
- Coders - all, need to specify who implemented what in your class model description.
Team 1:
- Workspace: /sp/d1, group: spd1
- Samba folder:
\\spring.cs.ttu.edu\spd1, Unix login/request your password
-
Project Website:
http://spd1.cs.ttu.edu from /sp/d1/public_html
-
4-blocker
- Team Members:
- Eric Rowell
Roles: team leader, design reviewer
Login: erowell
Email: eric.rowell@ttu.edu
Phone: 806-773-8107
- Matt Roth
Roles: architect
Login: mroth
Email: matthew.roth@ttu.edu
Phone: 806-679-2742
- Brady Ellison
Roles: designer
Login: brelliso
Email: brady.ellison@gmail.com
Phone: 432-288-4070
- Kevin Kreutz
Roles: use case designer
Login: kkreutz
Email: dennis.kreutz@ttu.edu
Phone: 817-807-7827
Team 2:
-
Workspace: /sp/d2, group: spd2
- Samba folder: \\spring.cs.ttu.edu\spd2,
Unix login/request your password
- Project Website:
http://spd2.cs.ttu.edu from /sp/d2/public_html
- 4-blocker
- Team Members:
- Michael Easterling
Roles: team leader & design reviewer
Login: measterl
Email: Michael.Easterling@ttu.edu
- Noah Berlow
Roles: architect
Login: nberlow
Email: Noah.Berlow@ttu.edu
- Christopher W. Carter
Roles: use case designer
Login: christoc
Email:
Christopher.w.Carter@ttu.edu
- Matthew Phelps
Roles: designer
Login: mphelps
Email: Matthew.Phelps@ttu.edu
Team 3:
-
Workspace: /sp/d3, group: spd3
- Samba folder: \\spring.cs.ttu.edu\spd3,
Unix login/request your password
- Project Website:
http://spd3.cs.ttu.edu from /sp/d3/public_html
- 4-blocker
- Team Members:
- Michael Moore
Roles: team leader, design reviewer
Login: mimoore
Email: michael.a.moore@ttu.edu
- Adam Fidel
Roles: Architect
Login: afidel
Email: adam.fidel@ttu.edu
- Darryl Odero
Roles: Designer
Login: dodero
Email: darrylfly@gmail.com
- Ryan Pickens
Roles: Use Case Designer
Login: rypicken
Email: pickens.ryan@gmail.com
Team 4:
Team 5:
Team 6:
Team 7:
Unix Groups
spd1::1090
spd2::1091
spd3::1092
spd4::1093
spd5::1094
spd6::1095
spd7::1096
spd8::1097