Project Deliverable 3
Due: Before class October 20

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 third deliverable, teams will perform analysis modeling activities on the project assigned to them. Due to the current high level of turnover in the software engineering field, each team lost a member that had to be replaced with a new hire. The team will need to devote some time to bringing their new hire up to speed. In addition to the analysis modeling tasks the team will need to produce estimates in order to solidify the project management plan. Upper management has requested estimates be made of both total LOC based on a functional decomposition, and total number of key and support classes based on the analysis model and multipliers.

• select a new team leader - someone who has not been a team leader prior to this - notify Dr. Challinger before the end of class on 9/29 who your team leader is
• perform analysis modeling activities
  • your goal is to represent the informational, functional, and behavioral requirements
  • all analysis work products should refer back to the requirements
  • make extensive use of graphics and diagrams
  • here is a potential set of tasks for analysis modeling
    • review requirements and constraints
    • expand and refine user scenarios
    • model information domain
    • define analysis classes using information objects as a guide
    • represent responsibilities and collaborations of each analysis class
    • group related classes into packages
    • model functional domain
    • model behavioral domain
    • analyze and model the user interface
• update the project management plan
  • utilizing the analysis model and functional decomposition as needed, generate estimates of both total LOC and total key and support classes
  • consider the proposed process model from D2, and then select a process model
  • 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 completeness (or lack thereof) of elicitation & elaboration documents from D2
    (Please review links above to work products to see variation in completeness!!)
  • revisions to D2 requirements and/or use cases
    • number each requirement if they are not already numbered
    • ensure that the list of requirements is complete
• analysis work products - in one document
  • information domain model
  • analysis classes, CRC, packages
  • functional domain model
  • behavioral domain model
  • user interface model
• project management plan - in one document
  • selected process model and why
  • decomposition for estimation and derivation of estimates
  • project schedule (detailed for first increment only if using an incremental process model)
  • 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, analysis, and planning documents
  • put these in the binder
  • bring this binder to class on 10/20