Project Phase 3

M&IS 44048 Software Integration

Development, Installation, Testing, User Documentation

Now you develop the application. Do not deviate from the design provided you from the end of Phase 2 with out a written sign-off from the user (things do change - but you may not deviate unless your client approves). The work will be evaluated on several criteria:
  1. Adherence to design (no extra features - none missing)
  2. Quality of implementation (how well did you use the technologies that you selected and how well are they integrated)
  3. How modular is your application - in effect, how well did you set it up for future maintenance
  4. Is your work of professional quality (no sloppiness will be tolerated)
  5. How smoothly did you work with the server team
Basically you build the system - all of it. As it is built pieces (units) are tested and certified (fixed if needed). At the end of this phase the system is ready to be stress-tested.

Test Plan Development and Unit Testing

Develop and document your plan for testing. This becomes a checklist for unit and system testing. Be very clear about responsibilities, due dates and test criteria. Spell out in list form what you are going to test, when and by whom. Include a place to record the outcome and action plan for resolution (fixing) parts/features that do not work.

Unit testing (individual components) is done by the developer responsible for the specific unit. System testing is done by other than the developers. Decide who is in charge of overall testing - this person keeps the records which become part of your project book.

Make this more thorough than you have ever done before. Assume a zero tolerance for bugs of any kind: program failure, logic errors, invalid data validation, etc. Get totally absorbed in this. No room for error. No tolerance on the instructor's part either.

All testing work, results and actions is to be documented and reported in your Phase 3 submission. - ask the instructor for a discussion of how to do this - it is your responsibility to ask - failure to do so will probably result in your group doing an inadequate job!

Warning: Inadequate testing is where most projects fail!

Installation

Get your work installed on the server as it will be when used by your clients. This means moving from development to production mode. In this phase all directories, backup/restore routines, etc. will be in place. All installation work is to be documented and the documentation included in your Phase 3 report.

Usability Testing

How does the system feel. Better go back to the syakeholders and see how they feel. Have them try your work. Encourage them to be brutal. Document it all! Better get the client's approval before you go to user training in Phase 4.

User Documentation

Prepare the user documentation because you will need it for user training in Phase 4 (ask instructor at a staff meeting for details).

Schedule/Responsibilities

Same as prior phases.

  • Phase Report Table of Contents

    1. Executive Summary

    2. Finished programs - printed listings of all - indexed for easy navigation

    3. Test Plan

    4. Unit Test Results

    5. Installation Documentation

    6. Usability Test Report

    7. User Documentation

    8. Technology Architecture

    9. Schedule & Responsibilities

    10. Resource Allocation (show that your team resources are balanced)