<< Chapter < Page | Chapter >> Page > |
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 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.
Content&Criteria | Points Possible | Points Obtained | Comments | |
Feasibility and Planning | 10 | |||
What is the scope of the proposed project? | 2 | |||
Is the project technically feasible? | 2 | |||
What are the projected benefits? | 2 | |||
What are the costs, timetable? | 2 | |||
Project Risk Identification? | 2 | |||
Requirements | 10 | |||
Requirements identification | 2 | |||
Requirements analysis | 2 | |||
Requirements definition | 2 | |||
Requirements specification | 2 | |||
Requirements report | 2 | |||
System and Software Design | 20 | |||
Design describes the system from the software developers' viewpoint | 5 | |||
System design: Match the requirements to hardware or software systems. Establishes an overall system architecture | 5 | |||
Program design: Represent the software system functions in a form that can be transformed into one or more executable programs | 5 | |||
Tools: apply tools for designing | 5 | |||
Implementation and Testing | 10 | |||
Is the level of language that the program offers clearly indicated? | 1 | |||
Is it easy to start the program? | 1 | |||
Is the user interface easy to understand? (For example, is the screen layout clear and easy to interpret?) | 2 | |||
Does the program include scoring? | 2 | |||
Individual components are tested against specifications. | 2 | |||
The individual program units are integrated and tested against the design by the students as a complete system. | 1 | |||
The complete system is tested against the requirements by the client. | 1 | |||
Maintenance | 10 | |||
Operation: The system is put into practical use. | 2.5 | |||
Maintenance: Errors and problems are identified and fixed. | 2.5 | |||
Evolution: The system evolves over time as requirements change, to add new functions or adapt the technical environment. | 2.5 | |||
Phase out: The system is withdrawn from service. | 2.5 | |||
Quality of software | 10 | |||
Maintainability- easy to maintain to meet changing needs | 2.5 | |||
Dependability- reliability, security, safety | 2.5 | |||
Efficiency- not wasting system resources | 2.5 | |||
Usability- user friendly, good documentation | 2.5 | |||
Performance of each student’s effort in the project | 10 | |||
Student had a major role in the success of the project | 2 | |||
Student always showed up on time for project meetings | 2 | |||
Student completed his/her part of the project. | 2 | |||
Student showed a lot of interest in the project | 2 | |||
Student played a major role in the project design, implementation and validation | 2 | |||
Report | 10 | |||
Overview/introduction | 2 | |||
Organization of body | 2 | |||
Quality of result | 2 | |||
Effective data presentation | 2 | |||
Conclusion | 2 | |||
Oral presentation | 10 | |||
Organization (presentation refined and clearly explained, information logically introduced and explained, the area of study's connection to the broad topic and the group's work is clearly explained) | 2 | |||
Content (presentation reveals good use of sources, provides pertinent information) | 2 | |||
Presentation (speaks clearly, uses appropriate language, uses appropriate body language, meets time specifications) | 2 | |||
Questions | 4 |
Notification Switch
Would you like to follow the 'Software engineering' conversation and receive update notifications?