230 likes | 530 Views
03/01/2004. (2). Agenda . Project Overview AMCi Objectives Spring 2004 Goals Revisit fall 2003 Postmortem Solutions to Postmortem Issues Review Questions. 03/01/2004. (3). Project Overview . New product (AMCi) will be built on top of Team Synergy's product (AMC) AMC Automated Model Compiler Build on top of Acme Studio.
E N D
1. 03/01/2004 (1) Team Mission Possible Junjie Lu
Ming Zhao
Namrata Malik
Kasil Hariharan
Jaime Rodrigo Oviedo Silva
2. 03/01/2004 (2) Agenda
3. 03/01/2004 (3)
4. 03/01/2004 (4)
5. 03/01/2004 (5) Spring 2004 Goals
6. 03/01/2004 (6) Fall 2003 Postmortem (1)
7. 03/01/2004 (7) Fall 2003 Postmortem (2)
8. 03/01/2004 (8) Fall 2003 Postmortem (3)
9. 03/01/2004 (9) Understand AMC (Areas = Experts)
Acme Studio = Jack
Acme = Jaime
XML/SynchroMod = Kasil
AMC APIs = Ming Matrix with names
Matrix with names
10. 03/01/2004 (10) Analyze Requirements
Develop Use Cases (160 Reqs vs 30 Use Cases)
Validate with the client
Identify areas already implemented
Effort/time estimation
Develop user manual and test cases
Reverse engineering of AMC code base
Insufficient AMC related documentation
Matrix with names
Matrix with names
11. 03/01/2004 (11) Fall 2003 Postmortem (4)
12. 03/01/2004 (12) Matrix with names
Cycle oriented planning/tracking
Brainstorm before planning
WBS based task assignment
Earned Value tracking
Matrix with names
Cycle oriented planning/tracking
Brainstorm before planning
WBS based task assignment
Earned Value tracking
13. 03/01/2004 (13) Matrix with names
Cycle oriented planning/tracking
Brainstorm before planning
WBS based task assignment
Earned Value tracking
Matrix with names
Cycle oriented planning/tracking
Brainstorm before planning
WBS based task assignment
Earned Value tracking
14. 03/01/2004 (14)
15. 03/01/2004 (15) Fall 2003 Postmortem (5)
16. 03/01/2004 (16) Matrix with names
Cycle oriented planning/tracking
Brainstorm before planning
WBS based task assignment
Earned Value tracking
Matrix with names
Cycle oriented planning/tracking
Brainstorm before planning
WBS based task assignment
Earned Value tracking
17. 03/01/2004 (17) Review
18. 03/01/2004 (18) Questions to mentors
19. 03/01/2004 (19) Questions
22. Team Process Handbook
Meta Process; Decision Making; Meetings;
Communication; Risk Management;
Document reviews; Planning
Configuration Mangement Plan
Identification; Control; CCB;
Counting; Audits; Release; Storage;
Document reviews;
Approvals; Naming; Revision numbering
Centralized repository – CVS
All documents; AMC Code Base
Backup to Slide 14 (process)
23. The requirements elicitation process cannot help us to
explicitly and completely define the requirements; we
might have to re-estimate time or have to do rework.
Our experience tells us that as we decompose the
requirements we will identify gaps in them that may
lengthen the analysis & design phases beyond the
plan.
The team will not have a technical writer during the
summer semester; might create unsatisfactory
documentation.
We have not yet defined our internal interfaces; might result in
coding difficulties in the summer semester.
Our project is dependent on Bill being there throughout the studio;
something could happen to him and we’d have nothing to show for
our work.
Backup to Slide 14 (process) Top 5 risks