Assignment 1 (Feasibility Study)

The deliverables for Assignment 1 are:

• A written Feasibility Study and Plan (group assignment)
• Survey 1 (individual assignment)

The exact form of the written report on the feasibility study is up to you. It is likely to be about ten pages.  It should include the following:

• The client for whom the work will be done.
• List of team members and email addresses.
• A statement of the task to be undertaken. A preliminary requirements analysis.
• Suggested deliverables.
• Process to be followed, e.g., iterative refinement, agile, modified waterfall model, phased development, etc.
• Outline plan, showing principal activities and milestones.
• Visibility plan. How will you keep in contact with the client and report progress? How will you communicate among your team?
• Discussion of business considerations (see the Projects -> Business page on the Web site).
• Risk analysis. What can go wrong? What is your fallback plan?
• Probable technical requirements

Here are some example of feasibility reports from earlier classes. They are very different in style, but each provides a good example of an effective report. They are placed here with the permission of the student teams.

• Feasibility report 1
• Feasibility report 2

Assignment 2 (Milestone 2)

The purpose of Assignment 2 is to describe to your client and the course team the progress up to Milestone 2. The deliverables for Assignment 2 are:

• Presentation on Milestone 2 (group assignment)
• Report on Milestone 2 (group assignment)
• Survey 2 (individual assignment)

If the team is following an iterative process Milestone 2 is likely to include a first set of requirements, a provisional design, and a prototype that can be used to demonstrate the functionality of the system. If the team is following a modified waterfall development process, Milestone 2 should include completion of the requirements phase and preliminary design work.

Assignment 3 (Milestone 3)

The purpose of Assignment 3 is to describe to your client and the course team the progress up to Milestone 3. The deliverables for Assignment 3 are:

• Presentation on Milestone 3 (group assignment)
• Report on Milestone 3 (group assignment)
• Survey 3 (individual assignment)

If the team is following an iterative process Assignment 3 should mark a major milestone when you can report visible progress to your client. If you are following a modified waterfall process, this milestone will include the completion of the design phase and significant progress in the implementation.

Assignment 4 (Demonstration and Final Delivery)

Assignment 4 consists of a presentation in which you will demonstrate your system in operation followed later by a brief final report and the handover of the completed system and documentation to the client. The deliverables for Assignment 4 are:

Online Presentation

• Presentation and demonstration of the completed system (group assignment)

Final Handover

• Short report (group assignment)
• Delivery of system to the client (group assignment)
• Survey 4 (individual assignment)

The Handover Package

During the semester you will be developing a set of materials that will be the handover package for your project. Because every project is different, the exact content of the package is up to you, but it should be carefully edited and suitable for handover to your client. The final package is likely to include some or all of the following:

• A feasibility study
• Requirements analysis and specification
• System and program design
• User interface design and testing
• Test plan, test examples, and results
• Source and binary code
• Either transfer of the rights in the system to the client or an unrestricted license for the client (see the Projects -> Business page on the Web site)

Enter your handover pacakage into GitHub or another software project system.