Client Project Deliveries

1. Client Project Deliveries Delivery 1 – Project Charter P Delivery 2 – Interim Stage Report Delivery 3 – 15- to 20-minute presentation to class Nov. 28 or 30 Final Delivery–What you leave for your client (Delivery #4)

2. Overview of Delivery 2 The first report section includes plans for completion. User Interaction Software, Pages, Test data, Environ- ments Revised Planning Status Memo Executive Summary Quick Reference Guide(s) These 3 sections are an early draft of your final delivery. Sample Pages Table of Contents Table of Contents Introductory Pages including Planning Sample Pages Test Specs Table of Contents User Materials * (to Date) Test Plan 1 Developers’ Materials * (to Date) Test Materials * (to Date) 2 * The table of contents of the user and developer materials will be graded for completeness. The sample pages and the table of contents must be reviewed by the appropriate clients (end-user, user-sponsor, or systems staff). 3 4

3. Overview of Final Delivery User Interaction X Software, Pages, Test data, Environ- ments Revised Planning Status Memo Executive Summary Quick Reference Guide(s) Final Pages Table of Contents Test ResultDetails Table of Contents Introductory Pages Final Pages Test Summary Table of Contents User Materials * (Final) 1 Developers’ Materials * (Final) Test Materials * (Results) 2 3 4

4. The Build Phase Looking ahead to Production Construction as part of methodology Construction Iterations (akaA-D-C-R Loops ) Final Construction Environments for A-D-C-R Loops & Final Construction 1st Environment: Developers’ sandbox Staging Environments 2, 3, & 4

5. Development  Production

6. Production • Goals: • Keep the system running • Help users use it • High Level tasks: • Operate the system • Support the system • Identify defects and enhancements •  that leads to development work for errors, quick fixes, and enhancements that are termed “maintenance” or may be considered work on “next release”

7. Industry Perspective of Maintenance – high cost Forrester Research • In 2004, 73% of I.T. budgets were spent on maintenance and 27% on new investments • In 2005, survey respondents expect to spend 76% on maintenance, leaving just 24% for new investments 73 % on maintenance 76 % on maintenance

8. Why does maintenance cost so much

9. Cost of Change Curve for Traditional SDLC Scott Ambler’s Figure 1 in http://www.agilemodeling.com/essays/costOfChange.htm Maintenance: Changes in Production

10. How can maintenance costs be reduced

11. SDLC Perspective How can maintenance costs be reduced ? Fixing defects and making enhancements = Maintenance

12. Maintenance Issues Inception

13. The Build Phase Looking ahead to Production Construction as part of methodology Preliminary Construction Iterations Final Construction Environments for A-D-C-R Loops & Final Construction 1st Environment: Developers’ sandbox Staging Environments 2, 3, & 4

14. Build Iterations Construct / create / test – web pagesConstruct / create / test – reports Construct / create / test – code (copy max & edit) Construct / create / test – On-line help & other help Construct / create / test – training Construct / create / test – database Acquire/ arrange / test hardware capacityTest conversion / migration

15. Test Specification for MIS 374 – Can opt for variation on 333k spreadsheet

16. Client Project Team Q’s – Data Focus How good is your test data? How will your users test your work(software, training, on-line help, etc ) ? Who will create your production data to be ready for the go live point ?

17. Final Construction • Integrated Testing, Acceptance Testing • Final Documents for Stakeholders • (Final) Training • Deploy / Migrate / Transition to new system

18. Release (End Game) Figure 4 and Section 5 in “The Agile SDLC,” Scott Amblerhttp://www.ambysoft.com/essays/agileLifecycle.html • Goal: Transition the system into production • High Level tasks: • Final testing of the system • Rework • Complete documentation for all stakeholders (system and user docs) • Deploy the system • Note: this can take several iterations.

19. Delivery 2 is a user test of your materials User Interaction Software, Pages, Test data, Environ- ments Revised Planning Status Memo Executive Summary Quick Reference Guide(s) These 3 sections are an early draft of your final delivery. Sample Pages Table of Contents Table of Contents Introductory Pages including Planning Sample Pages Test Specs Table of Contents Test Plan User Materials (to Date) 1 Developers’ Materials * (to Date) Test Materials * (to Date) 2 * Put as much help material as you can directly into your system. 3 4

20. SoftwareStagingEnvironmentsforMIS374 For 374 you will migrate your code from your sandbox to a host site, unless you are already on the host site. Preliminary Construction occurs in “sandbox”– coding and testing in the A – D – C loops

21. Do you need to integrate modules before migration? For 374 you will migrate your code from your sandbox to a host site, unless you are already on the host site. Build Phase Reading, p. 3

22. USAA has a 5th Staging environment Test system with interfaces with other systems. Test complete system

23. Graphic overview of layers

24. Basic organization of code shows separation of layers for .vb files The code review at the Interim Status Report time (i.e. Delivery 2) will be for file organization as well as looking at code commenting, naming, etc.

25. Late in the development cycle . . “We’re strapped for time,” says Lou, the nervous one on the team. Looking at the Gantt chart he says “we can’t possibly make the April 20 deadline for testing with live data. We’re already three weeks behind.” As you have better planning skills than Lou, you say “if we push the testing off, the users will be on vacation.” Lou is upset. Lou suggests “something’s got to go. Let’s see…maybe we can skip unit testing….and do it at system test time.” What should the team do? What is realistic?