Class 5 – SDLC & Project Planning

1. Class 5 – SDLC & Project Planning Group Planning Exercise: End-of-year party Development Methodologies (SDLC) System Life Cycle as a sequence (Fig. 3.2a, p.171) Phased Development Process Model (Fig. 3.6, p.178 ) Producing a Phased Project Schedule: Milestone Lists Gantt charts Network Diagrams

2. Reminders for next 8 days: • Due Friday February 6th at 4pm: • Group Project #1 report to CBA 5.202 or CBA 3.416 CBA 3.416 • Peer Evaluation for Group Project #1: • Go to Fri. Feb. 6th, on Schedule page on class web site • Click on Peer Evaluation form • Complete evaluation • Click on submit • Also due Friday --Select client project team on project portal • Due for Monday class – Download Group Project 2 Instructions & find your team on Blackboard & sit with GP 2 team • Friday, February 13th: Bid for client project • bidding opens 8am • team admin must bid

3. 2 Development Methodologies • Waterfall aka SDLC – System Development Life Cycle 2. Phased development

4. Why build the system? (Goals, work plan, feasibility) A waterfall SDLC is a sequence of stages Planning Stage How will the system work? Analysis Stage Do it. Design Stage Implementation Stage What is required? Who will use it? When? Production(aka Go Live) This model rarely works well, because it is too difficult to specify requirements completely at the beginning of a project. Once you are downstream in implementation and realize there are analysis and design problems, it is difficult to swim up stream. p. 171, Fig. 3.2a

5. A waterfall SDLC is a sequence of stages Planning Stage Analysis Stage Design Stage Implementation Stage Production Neverplan a 1-pass, do- it-right-the-first-time-from- Beginning-to-End SDLC. p. 171, Fig. 3.2a

6. Phased Development Figure 3.6, p. 178 Preliminary investigation P A Analysis User Review Design D C Preliminary construction Finalconstruction System testand installation Why build the system? (Goals, work plan, feasibility) What? Who? When ? How ? Create & test Cut over /deploy/migrate to production system

7. Phased Development Figure 3.6, p. 178Advantage 1 Preliminary investigation P A Analysis User Review Design D C Preliminary construction Finalconstruction System testand installation Cut Over: Put system in production Each A – D – C – R loop is a phase. Phased delivery avoids the waterfall model’s problem of no part of the system being done until all of it’s done.

8. A–D–C-R loop may be called an iteration. Iterative Development Preliminary investigation P A Analysis User Review Design D C Preliminary construction In agile methods the iterations are called sprints. Finalconstruction System testand installation Cut Over / Deploy / Publish: Put system in production

9. Phased Development Figure 3.6, p. 178Advantage 2 & 3 Preliminary investigation P A Analysis User Review Design D C Preliminary construction Finalconstruction System testand installation Cut Over: Put system in production 2. Users will give better feedback to system views. 3. Developers learn best by creating functional components in incremental steps.

10. Phased Development Advantages 1.Phased delivery avoids the waterfall model’s problem of no part of the system being done until all of it’s done. 2. Users will give better feedback to system views—so phases need to be meaningful deliveries for users. 3. Developers learn best by creating functional components in incremental steps. 4. Phases reduce the problem of deadline behavior by users and developers.

11. Functionality Elapsed Time In Months 1 2 3 4 The waterfall SDLC and workload risk Planning Stage Analysis Stage Design Stage Implementation Stage Production The risk with the waterfall method is that the real work doesn’t start until into the implementation stage as the deadline for production approaches.

12. MIS 374 Planning Requirement For Group Project #2 and the Client Project you must use 1. a Phased Development Model and 2. MS Project

13. Example of Phased Planning: Library Control System • MIS 374 project --- Delivery 1 report pages • Illustrates use of • Milestone Summaries (AKA phase list) * • Gantt Charts * • Network Diagram * * Required for Group Project 2 and Client Project

14. Proposed Library Control System:Major Milestone Summary Phases and MilestonesWeek Ending Date Phase 1: Preliminary Investigation Weeks 1-4 March 23 Phase 2: Design System Database Week 5 March 30 Phase 3: Administration Module Week 6 April 10 Phase 4: Resource Tracking /Search Module Week 6 April 10 Phase 5: Check-in/Check-out Module Week 7 April 18 Phase 6: Report Generation Module Week 7 April 18 Phase 7: On-line Help Module Week 8 April 27 Phase 8: Additional Functionality Module Week 8 April 27 Phase 9: Installation and System Testing Week 9 May 8 Phase 10: Documentation and Training Week 10 May 15 All 4 team members

15. Gantt Chart View of MS Project

16. Proposed Library Control System:Major Milestone Summary Phases and MilestonesWeek Ending Date Phase 1: Preliminary Investigation Weeks 1-4 March 23 Phase 2: Design System Database Week 5 March 30 Phase 3: Administration Module Week 6 April 10 Phase 4: Resource Tracking /Search Module Week 6 April 10 Phase 5: Check-in/Check-out Module Week 7 April 18 Phase 6: Report Generation Module Week 7 April 18 Phase 7: On-line Help Module Week 8 April 27 Phase 8: Additional Functionality Module Week 8 April 27 Phase 9: Installation and System Testing Week 9 May 8 Phase 10: Documentation and Training Week 10 May 15

17. Gantt Chart View of MS Project

18. Data includes the Phase Label, Task #, Length, Start & Finish, & “Resource” Names You can switch between the Gantt Chart view and Network Diagram views in MS Project. This is a Network Diagram with the details collapsed so only the Phases are shown.

19. Week 7 Week 6 Week 6 Week 6 Week 8 The Network Diagram view shows simultaneous work more clearly than the Gantt chart view.

20. Download MS Project free Tutorial

21. Note task guide w/ MS Project

22. Step 1: Select File  New For this task guide, click on Tasks