1. 1 st 5 minutes: Fill out Exercise #13 Write your team answers to #1 & 2 on your flip chart.

2. Launch Point for Build Phase Inception Phase(s) Launch Point Project Charter Analysis & Requirements Summaries & Planning You are here

3. Development Production You are here

4. Client Project Deliveries Delivery 1 – Project Charter Delivery 2 – Interim Stage Report Final Delivery – What you leave for your client (Delivery #4) Delivery 3 – ~ 12-minute presentation to class 4/29 or 5/1

5. Client Project Deliveries: # 2 #4 Delivery 2 – Interim Stage Report & software & test data Final Delivery – What you leave for your client #2 is an early draft of Final Delivery

6. Focus Shift: across Client Project Deliveries Delivery #1 Charter Delivery #2 Interim Status Report : big shift in focus Delivery #2 Interim Status Report Delivery #4 Final Delivery : NO shift in focus Delivery 2 is an early version of the Final Delivery, plus a planning section. note: Delivery 3 is a ~10-minute presentation to class on Apr 29 or May 1

7. Sample Pages Introductory Pages including Planning Table of Contents Executive Summary Status Memo Revised Planning User Interaction User Materials * ( to Date ) Table of Contents Sample Pages Quick Reference Guide(s) Test Materials * ( to Date ) Test Plan * 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 tech support staff). The first report section includes plans for completion. These 3 sections are an early draft of your final delivery. Test Specs Software, Pages, Test data, Environ- ments 1 2 4 Developers Materials * ( to Date) Table of Contents 3 Overview of Delivery 2

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

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

10. Development Production

11. Production Goals: 1.Keep the system running 2.Help users use it High Level tasks: 1.Operate the system 2.Support the system 3.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

12. 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

13. Why does maintenance cost so much

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

15. Comparison of Power of Bugs to... Steve McConnell, Rapid Development

16. How can maintenance costs be reduced

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

18. Maintenance Issues Inception

19. 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

20. Launch Point for Build Phase Inception Phase(s) Launch Point Project Charter Analysis & Requirements Summaries Build Iterations Focus on Creating Functionality

21. We provide end-to-end services focused on business issues important to our portfolio clients. Our investments and scale are aligned around those issues and industry sectors where we have unique expertise to deliver complete valuable solutions. Deloittes Build Phase Strategy Manage Plan Design Build Sustain Provide executable strategy supporting business and technology objectives. Includes assessments, diagnostics, advice, planning, and strategy articulation. Strategy Establish a programs or projects scoping, timeline definition, resource allocation, and high leveled requirements gathering in tactical, detailed steps. Plan Link business and technology through designing enterprise architecture, technology-enabled business operations, technology infrastructure, IT organizations, Centers of Excellence, and reusable methods and tools. Design Configure, extend, and integrate SAP and Oracle industry solutions. Deliver IT solutions in Finance, HR, Supply Chain, and Customer Management. Custom engineer and integrate software using deep industry and technology platform expertise. Build Deliver application stabilization, maintenance and support, and operations management in areas of deep business expertise. Sustain Lead oversight, program, and integration management of large-scale technology design, configuration, implementation, merger integration, and cost reduction efforts. Manage Build

22. Sense Corp has 4 Inception Phases: > Assessing > Conception > Initiation > Planning

23. MIS 374s Build Phase is Sense Corps 10-step Execution Phase.

24. Build Iterations Construct / create / test – web pages Construct / 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 capacity Test conversion / migration

25. Test Data for Safari Books, 333k Match test data to each functional phase

26. Data Validation Requirements for Safari Books, 333k

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

28. User Testing is key to success Construct / create / test – web pages Construct / 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 capacity Test conversion / migration

29. User Testing in Build Iterations – Client Project Example

30. Provide user materials each function

31. Where do the user testing activities fit on the Gantt Chart

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

33. Final Construction 1. Integrated Testing, Acceptance Testing 2. Final Documents for Stakeholders 3. (Final) Training 4. Deploy / Migrate / Transition to new system

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

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

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

37. 4 Software Staging Environments 1.Development sandbox – hardware where individual software modules or objects are constructed, tested, and debugged. (This is where unit testing occurs.) 2.Development integration environment – hardware for integration testing 3.Production staging environment – hardware for system testing & user acceptance testing occurs 4.Production environment – hardware for user interaction

38. Software Staging Environments for MIS 374 Preliminary Construction occurs in sandbox– coding and testing in the A – D – C loops For 374 you will migrate your code from your sandbox to a host site, unless you are already on the host site.

39. This is the code – test, code – test area. Integration testing combines modules and tests again. This is the 333k experience – test data was used for testing in a McCombs folder. System testing will test the complete system with broader test data. This is the 374 situation. User acceptance testing is after system testing in contractual situations & 374. Finally, the system is deployed (or migrated) and goes live (or control is cut over to the new system.)

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

41. Complexity is a Growing Problem Infrastructure built with no roadmap Architecture policy may not exist Applications built/bought to support line-of- business needs Point-to-point connections made on ad hoc basis MIS 373 - Copyright Edward Doan 200841

42. Production Staging is needed for large public systems – so all 4 environments must be created.

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

44. Graphic overview of layers

45. 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.

46. Late in the development cycle.. Were strapped for time, says Lou, the nervous one on the team. Looking at the Gantt chart he says we cant possibly make the July 1 deadline for testing with live data. Were 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 somethings got to go. Lets see…maybe we can skip unit testing….and do it at system test time. What should the team do? What is realistic?