1 / 28

The Last 2 Phases

The Last 2 Phases. Final Construction (today) User Materials Exercise 14 – Preliminary Lists for Deliveries 2 & 4 Moving to Production (after today) Testing Maintenance Production Return Project Charters. Always think about what’s next. TODAY. THURSDAY.

mingan
Download Presentation

The Last 2 Phases

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Last 2 Phases Final Construction (today) User Materials Exercise 14 – Preliminary Lists for Deliveries 2 & 4 Moving to Production (after today) Testing Maintenance Production Return Project Charters

  2. Always think about what’s next TODAY THURSDAY

  3. Always think about what’s next • Tuesday April 15 – Red / Yellow / Green exercise – in class • Thursday April 17 – Client work day • Tuesday April 22 – Review for exam 2 – OR – client work day • Thursday April 24 – Exam 2 (optional – let us know) • Tuesday April 29th – 3-5 presentations (which teams?) • Thursday May 1st – 3-5 presentations (which teams?)

  4. Development  Production

  5. Interim Status Report (#2) Checklist • Use your Delivery 2 & 4 Specifications to check that everything is included. (Client Delivery 2 – Thursday 17th – 2:00 p.m. ) • 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.

  6. Code Review Tip: Code and Interface Review Rubric--checklist for TAs is on April 11th

  7. Final Delivery (#4) Checklist • Final Delivery--Note that there should be no planning documents. (Thursday May 8th) • 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 due with the Final Delivery

  8. Delivery 2 is a user testof 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

  9. Client Project Final Delivery • Think about: • Who are the users? • What are the main user events? (i.e. How will they use the system?) • What are the most critical parts to users? • How does this relate to testing? • What is your users’ experience level? • How does this relate to your training?

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

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

  12. Best Materials? User or Developer Manual Online help Video Tutorial -- Snag-it, Jing Announcement email or mailing to users Slide show for staff training Other ideas?

  13. Installation Guide Team Alief Lisa Chow Joseph Lam James Le Tam Le Sanju Patel Fall 2004

  14. Do you need a QRG (Quick Reference Guide)

  15. Quick Reference Guide – for non-technical users

  16. Quick Reference Guide – experienced user

  17. Quick Reference Guide – one page reference & training

  18. Online help

  19. Ongoing Training and User Support • User support covers training and user assistance that occurs after installation • On-line documentation and troubleshooting • Resident experts • Help desk • Technical support

  20. Maintenance and System Enhancement • Modification of software after delivery to correct faults, improve performance, or adapt the product to a changed environment • Tracking modification requests and changes. • Do this even if clients don’t continue! • ARE YOU COMMENTING? • Implementing changes • Monitoring system performance • Upgrading hardware/software • Updating documentation

  21. Maintenance Issues

  22. 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 ?

  23. Go back to your Organizational Impact & Non-functional Requirements Who are your users? What matters most ? Operations ? Or reaching new clients? Who will troubleshoot and maintain your system? Who will enhance your system?

  24. 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) die / 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?

  25. Due Date Reminders

More Related