In the BeginningIn the Beginning
Blockhead Ken Kenney Lead Programmer Program Documentation Seth W. Phillips Team Leader Lead Documenter Jay McCullough Lead Tester Web Designer Tim Chamberlain Lead Analysis Web Designer Luke Snell Client Jerry Weinberg Manager\Professor Organizational Chart
Project Lifecycle Modified Waterfall Project Definition Analysis Staged Design Staged Development Testing Training Implementation
Staged Design Paper Prototyping Screen GUI Design Database Design
Design Steps Paper Prototyping Figure out ways of do the things Dr. Snell wants. Database vs. Spreadsheet
Prototyping: Before
Prototyping: After
Staged Development GUI Development Database Development Code and Debug Test Code and Debug Test
Project Plan From Inception to Completion
Project Plan- Milestones From Inception to Completion
Risk Management Include database version (Jet Version) Add constraints to installation of produce (i.e. must have Access 97) Varied OS - Database Version Keep all members informed on what the other members are doing. Redistribute workload. Adjust Contract and Deliverables Loss of Team Member Adjust Contract Add more concentration to underdeveloped area Slate more work hours Re-achieve Deadlines Missed Deadline Project for Fun of It Loss of Client Analyze the Creep Practical: time allows rework deliverable schedule Impractical: tell the client. (If client insists rework deliverables) Feature Creep RisksResolution
Tentative Testing Plan IntragroupTesting Testing of functionality Code Review Client Testing Dr. Snell will be guinea pig Will test live simulations Will review “feel” of program External Small Test Group Dr. Snell will provide outside testers to provide feedback on completed subtasks of the system External Large Test Group Dr. Snell will provide outside testers to provide feedback on completed system
Tentative Documentation Plan Extensive Help Files Cut initial documentation while program is being developed. Refine Documentation with feedback from Lead Tester-Lead Analysis-Client