Assignment
Summary: This is the assignment for the Software Engineering course.
The four assignments are group assignments. In addition, with each assignment there is an survey to be completed individually. It is important that everybody completes each survey and submits it on time. The course team uses the surveys to monitor the progress of the projects and to understand the contributions made by each member of the team.
Assignment 1. Project Feasibility Study and Plan
Write a short feasibility report that describes the project that you have selected. The exact form of the report is up to you, but it should be well written and suitable to present to an external client. The length is likely to be between five and ten pages.
The report should include the following:
- The client for whom the work will be done.
- Visibility plan. How will you keep in contact with the client and report progress? How will you communicate among your team?
- A statement of the task to be undertaken.
- A preliminary requirements analysis.
- Suggested deliverables.
- Process to be followed, e.g., modified waterfall model, iterative refinement, prototype, phased development, etc.
- Outline plan, showing principal activities and milestones.
- Discussion of business considerations (see Projects page on the Web site).
- Risk analysis. What can go wrong? What is your fallback plan?
- Probable technical requirements
This report is a group assignment. All members of the project team should share in the production of the report.
Assignment 2. Progress Report and Presentation
During the semester each team will give three presentations with associated reports on the work completed. You will make a 45 minute presentation to the client, the Instructor and the Teaching Assistant assigned to your project. Everybody is expected to be a presenter at least once.
The first progress report and presentation should complete one third of the total work from the feasibility study.
If you are following an iterative process the first progress report should mark a major milestone when you can report visible progress to your client. Typically, this will include a first set of requirements, a provisional design and a prototype that can be used to demonstrate the functionality of the system, including user interface design.
If you are following a modified waterfall development process, this progress report should include completion of the requirements phase. Carry out the requirements analysis, definition and specification for your project. Write a requirements document. The exact form of the document is up to you, but it should be well written and suitable to present to your client. In writing a requirements report, pay particular attention to the following:
- The report must be understandable by the client.
- The requirements must be specified in sufficient detail to test against the implementation.
- The requirements must be the client's, not your own concepts.
- Design concepts must be clearly separated from requirements.
- Requirements should be partitioned into those that must be met by the first release and those that are optional.
Assignment 3. Progress Report and Presentation
The second presentation and report will follow the same format as the first. You will make a 45 minute presentation to the client, the Instructor and the Teaching Assistant assigned to your project. Remember that everybody is expected to be a presenter at least once during the semester.
The second progress report and presentation should complete two thirds of the total work from the feasibility study.
If you are following an iterative process this progress report should mark a major milestone when you can report visible progress to your client.
If you are following a modified waterfall process, this progress report will be the completion of the design phase. You should probably have already begun implementation.
The exact form of the report is up to you, but it should be well written and suitable to present to your client. In writing a design report, pay particular attention to the following:
- The report must be understandable by the client.
- The design should include both system and program design.
- Design concepts must be clearly separated from requirements and the implementation.
- Update your schedule to confirm that you will have an operational system by the end of the semester.
Assignment 4. Final Presentation
The final presentation and report will follow the same format as the others. You will make a 45 minute presentation to the client, the Instructor and the Teaching Assistant assigned to your project. Remember that everybody is expected to be a presenter at least once during the semester.
This presentation should describe to the client and the course team what has been accomplished during the semester and should include a demonstration of your system in operation. The documentation should be a complete hand-over package, which has been entered into your project management system, so that the client's staff can put your project into production, extend and maintain it.
Comments, questions, feedback, criticisms?
Send feedback
- E-mail the author of the module, Assignment
Footer
More about this content: Metadata | Version History
This work is licensed by Trung Hung VO under a Creative Commons Attribution License (CC-BY 2.0).
Last edited by Trung Hung VO on Sep 3, 2007 4:40 pm GMT-5.