Software Engineering Project ChecklistSubmission of ProjectIt is your responsibility to ensure that your software runs on any computer. To this end you are advised to test it out on at least 2 different machines. 1. Team report: The report should be at least 30 pages (main content font size is no more than 12). You should use the proposed structure listed follows as a guide, however, you feel free to modify it as you see fit. 2. Individual report: The report should be 3-5 pages in length (main content font size is no more than 12). You should attach your complete set of Personal Log forms to one copy of the report. 3. E-version of the team report: Please use the following convention to name your report file: 2009SpringSWTeamReportName.doc.4. Description: A one page description of the program. 5. Source code - make sure that you use relative pathnames rather than absolute ones, so that the system can run without depending on your login name.Team Report/Presentation Content 1. Requirements(25) You should be able to identify the users and stakeholders and the needs of the users and stakeholders. You need to describe the feature of the system. You should pick up right diagrams for your project requirements.2. Design (25)Overview of design, key component designs, data organization, file/database structure, user-interface design, requirements cross-reference, and summary of any modifications made to design during later stages of project. You should pick up right diagrams for your project requirements.3. Coding & Integration (20)Planning for coding & integration of system components, key implementation decisions, libraries used, use of existing software, algorithms, etc. We do not expect to see large amounts of code in the report; small code fragments may be used to illustrate major decisions, etc.4. Testing (10)Testing strategy, description of test data, use of test harness code, test results.5. Summary (10)Discussion of outcome of project, if original client requirements were not satisfied- explanation of why, possible future changes/additions to the system, lessons learnt.6. Appendices (10)a) Appendix 1 - User ManualIntroductory material on how to run the system.b) Appendix 2 - Maintenance ManualDescription of how to install and compile system, hardware/software dependencies (including libraries), list of source code files (with brief summary of role in system), etc.c) Appendix 3 - Notes from the meetinga. Include member attendance, time of the meeting and topics.d) Appendix 4 – Other activity notesa. Include the copy of email and/or message in the message board, etc.,.Individual Report Format1. IntroductionBrief summary of aims/objectives of the project.2. Personal ContributionIn each of the following sub-sections, you should summarize your personal contribution to the appropriate project phase, initiatives taken, particular problemswhich you solved, difficulties encountered, etc: - Requirements Analysis - Design - Coding/Integration - Testing - Documentation 3. Project Management/Other ResponsibilitiesSummary of any responsibilities which you took on during the project – project manage, librarian, analyst/designer, and programmer etc. You should discuss howyou coped with responsibility, what you achieved, etc. You can find a Team Project Role Assessments form here.4. Team DynamicsSummary of how you feel you contributed to the overall functioning of the team unit. Any problems within team. Also use this section to summarize (and rate) the contributions made by each of the other members of the team; we recommend thatyou do this in the following style: Joe Bloggs summary of contribution made. Rating: +10% Jane Doe summary of contribution made. Rating: -25% and so on for the other team members...The rating here is your recommended delta to be applied to the team-mark for that person, e.g. if a team receives a mark of 80% for the project, a delta of 25% would mean an individual mark of 60%. NB. These are only your personal recommendations - the staff marking the project have the final decision in this matter. (Remember that we will use a number of information sources, including our own experiences of the team, your project log sheets, comments in the individual reports, outstanding warnings, as well as student ratings of their peers).Note that you can rate yourself and the other team members as equal to, above, or below the average. No explicit upper or lower boundaries are defined, however try to be realistic. Ratings such as +100% or -100%, which express a substantial (positive or negative) deviation from the average and thus extreme satisfaction or dissatisfaction, although possible, should be thoroughly and satisfactorily