Project Deliverable 4
Due: November 8

Note: there are both team deliverables and individual deliverables
Team deliverables are worth 10 points - all team members will receive the same grade.
Individual reflections are worth 5 points.

In this deliverable, teams will perform design engineering activities on the project assigned to them. In addition to the design engineering tasks the team will need to update the project management plan. Turnover in the industry has been unusually high, presenting additional challenges. Fortunately, the highly trained professional software engineers making up the teams will rally to the challenge, applying their considerable skills to adapt to these changes and keep their projects on the road to success.

• select a new team leader - - notify Dr. Challinger before the end of class on 10/20 who your team leader is
• perform design engineering activities
  • your goal is to describe the data structures, system architecture, interfaces, and components
  • all design engineering work products should be traceable back to the requirements
  • many UML diagrams used in the design model are refinements of diagrams created in the analysis model
  • here is a potential set of tasks for design engineering
    • select an architectural pattern appropriate to the software based on the analysis model
    • partition the analysis model into design subsystems, design interfaces, and allocate analysis functions (classes) to each subsystem
    • examine information domain model and design appropriate data structures for data objects and their attributes
    • create a set of design classes
      • translate each analysis class into one or more design classes
      • check each class against design criteria and consider inheritance issues
      • define methods and messages for each design class
      • select design patterns for each design class or subsystem after considering alternatives
      • review design classes and revise as needed
    • design user interface
      • review task analyses
      • specify action sequences based on user scenarios
      • define interface objects and control mechanisms
      • review interface design and revise as needed
    • conduct component level design
      • specify algorithms at low level of detail
      • refine interface of each component
      • define component level data structures
      • review components and correct all errors uncovered
    • develop deployment model
      
• update the project management plan
  • refine the project management plan, including a schedule, in accordance with the selected process model
  • all scheduled tasks should refer back to the requirements
• remember, do your best work - everything you do will be handed off to another team for the next process activity

Team Deliverables:

• Be sure that the names of all team members are on each document.
• review - in one document
  • discussion of quality and completeness of D3 work products
    
  • any revisions to D3 work products
• design engineering work products - in one document
  • architecture
  • data structures
  • interface design
  • component design
  • consider using this Software Design Specification template from R.S. Pressman & Associates, Inc
• project management plan - in one document
  • the process model and discussion of whether it still seems appropriate
  • any updates to decomposition and/or estimates
  • updated project schedule (detailed for first increment only if using an incremental process model)
  • updated dependency network
• team plan for completion of deliverables above - meetings, writing, etc.

Individual Deliverable:

• reflection - one page, maximum, answer the following
  • How well did your team work together?
    • Give a rating between 1 and 5
      • 1 = extremely poorly
      • 5 = extremely well
    • What do you base your rating on?
  • How did the team decide how to divide up the team responsibilities?
  • Describe what each specific team member contributed to the completion of the deliverables
  • What would have improved team productivity?

Turn-in Procedure:

• In WebCT, click on the Assignments icon, upload your file and submit
  • The team leader is responsible for turning in the team deliverables plus his/her reflection - zip all these documents up and submit one file
  • Each student is responsible for turning in their individual deliverables
    
    
• In addition, the team must add to the binder for this project
  • print all of the review, design, and planning documents
  • put these in the binder
  • bring this binder to class on 11/10