1. The last 2 parts Informal 374 class Survey Please do this now. On Schedule page Final Construction (today)  User Materials  Exercise 14 – Preliminary Lists for Deliveries 2 & 4 Moving to Production (after today)  Testing  Maintenance  Production

2. Always think about what’s next

3. Apr 18/19 – Red/Yellow/Green exercise – in class Apr 20/21 – Review for exam 2 – OR – client work day Apr 21 – Delivery 2 is due at 2pm Apr 25/26 – Exam 2 (optional – let us know by 15th) Apr 27/28 – No class – client work day May 2/3 – 4-5 presentations (Email prof for preference) May 4/5 – 4-5 presentations (Email prof for preference)

4. Interim Status Report (#2) Checklist  Use your Delivery 2 & 4 Specifications to check that everything is included.  Turn in electronic & physical copies  Please don’t print hardcopy front and back  Interim Status Report—Your document should clearly tell your IT supervisors and your client:  What has been done  What the schedule is for final completion – Be transparent  What is the expected outcome of this project (it may have changed since Delivery 1)  Samples of your final deliveries  Optional – “For Professor’s Eyes only”  Your cover sheet should let us know  when your client will see your report & software-to-date  access information to allow evaluation of your software progress.

5. The Code Review will be for file organization as well as looking at code commenting, naming, etc. Code Review Tip: Code and Interface Review Rubric--checklist for TAs is on Canvas

6. Final Delivery (#4) Checklist  Final Delivery--Note that there should be no planning documents. (Thursday Dec 10 th )  No document labeled “plan” from Delivery #1 or #2 should be included in the Final Delivery. If revised versions of those documents are included, they should be re-named “Guide” rather than “Plan.”  Be sure to change “tense” in your document.  Again…your cover sheet should let us know  when your client will see report & completed software  access information to allow evaluation of your software  Peer evaluations are with the Final Delivery

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

8. Development  Production

9. Change Management is KEY!

10.  Think about:  Who are the users?  What are their roles?  What are the main user events? o (i.e. How will they use the system?)  What is more critical to users?  How does this relate to testing?  What is your users’ experience level?  How does this relate to your training?  Can they manage after you leave?

11. Development  Production Where do the user testing activities fit on the Gantt Chart ?

12. Zach Scott Theatre – Client Project There were 5 semesters a year. A volunteer handled all typing & data entry. Sandie had a shoe box of notes about people who called her about classes. She wanted these on a computer for easy label printing.

13. Change Management is  Ensuring your client will be successful in using and supporting the system after you are gone.  Covers: training, reference materials, change control process, communication, and more  So what are ways your clients will need help managing change?

14. Considerations to Manage Change  How accepting are future users?  How is client advocating for system?  Do we need to send out an announcement email?  Will we train future users or future trainers?  How much detail is needed?  Slide show or PowerPoint  User Manual, Dev Guide (with or without pictures?)  Step by Step Tutorials (using Snag-it, Jing, QuickTime)  Other ideas?  Other things to consider  Online help (i.e. help built into app)  How will bugs/ideas get reported?

17. Installation Guide w/ pictures Team Alief Lisa Chow Joseph Lam James Le Tam Le Sanju Patel Fall 2004

19. Do you need a QRG (Quick Reference Guide) Are there common repeat tasks in the system?

20. Quick Reference Guide – for common tasks

21. Quick Reference Guide – experienced user

22. Quick Reference Guide – one page reference & training

23. Online help

24. Plan to help manage future change  How will users report issues? Is feedback loop built into your application?  Who will modify system after delivery to correct faults, improve performance, or adapt the product to a changed environment?  Are you commenting code properly for future developer?  In Delivery 4 you will leave a list of Future Recs  Developer Guide will instruct on how to:  Follow standards for coding  How to backup system or restore/reinstall  How to do upgrades and maintenance

25. Maintenance Issues

26. Do you need a test environment

27. Environments: Dev  Production Environments Development Staging (2,3) Production

28. System Testing and User Acceptance Testing Occur in the Last Software Staging Environment

29. Testing & timing Users (& Operations staff) take over Unit test Integrated test Systems test of all components, incl. volume testing User acceptance test

30. System Testing and User Acceptance Testing Occur in the Last Software Staging Environment

31. From Fundamentals of Software Integration, by Kay Hammer and Tina Timmerman, 2007 Environments & why layers of code are so important

32. Graphic overview of layers

33. Murphy was an optimist Murphy’s “Law’ say “what can go wrong, will” What could go wrong with your project? Your code doesn’t work Your client(s) quit/move away suddenly One of your teammates doesn’t do his / her work on time And … any of a million other things. What if something does go wrong?

34. WHAT IF THIS HAPPENS? “ 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 November 20 th 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 gone for Thanksgiving. ” 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?

35. Exercise 14 – User Materials  Who are your internal users?  Who are your external users?  To whom will you turn over your system at the Go Live point?  Who are the developers who will replace you at the Go Live point ?

36. Go back to your Organizational Impact & Non- functional Requirements System requirements for enhancements and fixes that require custom development and future upgrades. Maintainability System requirements for cross-platform, multi-user agent access, etc. Portability System requirements for growth of organization and system usage. Scalability System requirements for secure environment and processing--hardware, software, application and user security. Security How will the proposed system (or system enhancement) help the organization improve their competitive advantage? Strategic How will the proposed system (or system enhancement) help managers make better decisions? Management How will the proposed system (or system enhancement) improve transaction processing? Operations Who are your users? What matters most ? Operations ? Or reaching new clients? Who will troubleshoot and maintain your system? Who will enhance your system?