Software Engeenering

Project Objective Software Engineering is an important discipline and the principles you have learnt during this course will be practically used while you work on software development in the future. The purpose of this assignment is to enable you to use the knowledge you have acquired to critically review what have been implemented in previous Graduation Projects. The detailed specifications of this assignment are detailed in the following section. 1. PROJECT SPECIFICATIONS You have to form a group of 4 members and choose a project for real clients. Based on what you have studied in this course, critically review the report for the following three areas: 1- Software Requirements 2- Design and Implementation 3- Software Testing Your findings should be documented in a report that should be organized into sections each of which addresses one of the areas above. In critical reviews you should express your own opinion in light of what you know (whether that is from what you have learnt from the course textbook or what you have read from other resources). Your review should acknowledge both the strengths and limitations that you find in your chosen Graduation Project report and provide some recommendations on how to improve the work. You are required to submit a report that includes: 1. Cover page with project title, Course number and name, your names and your instructor name. 2. An introduction of the system and describe the problem statement and the proposed system. 3. List of functional and non-functional requirements. 4. A use case model with table description for every use case. 5. The class diagram that model the system data and their relationships. 6. At least two sequence diagram showing the main interactions in the system. 7. Summarize your work and present the lessons learned and the challenges faced and provide possible extensions that could enhance your software solution. 2. PROJECT EXPECTATIONS • You are expected to work ethically and communicate effectively and professionally with your team members. Remember that poor peer evaluation affects your final mark. • You have to use StarUML or any other similar software to create your diagrams. 3. DELIVERABLES 1. Submission will be a word file containing the names and IDs of team members in the cover page and all the seven sections mentioned above. The documents should be submitted through email by team leader only. 2. Weekly minutes (attached) or an evidence of any other means by which you manage your team. Four weekly minutes at least should be used and submitted by team leader. 3. Individual peer-review form in which you ‘individually’ evaluate your team members. This should be submitted through email by all team members. 4. Please note that team leader should submit the document, the weekly minutes and her evaluation form altogether in one submission via email. 5. 5-10 minutes presentation in which you get the chance to share your work with your classmates. You can delay the submission of the presentation until the presentation day (more details will be available soon). 4. GENERAL GUIDELINES 1. An assessment sheet is attached along with this document. Please use it to understand how you will be assessed and work accordingly. Some guidelines can also be found at the same excel file in a separate sheet. 2. Remember that plagiarism will not be tolerated, and a zero mark will be given. 3. Late submission will receive 10% penalty per day.