Reference no: EM133772858
Capstone Project
Assignment - Project Report
Project - GadgetZone Website
The final project report should be prepared according to the instructions below:
Using similar format as the project proposal, your end of semester report should be at least 30 pages long (at most 12pt font with reasonable margins and spacing), excluding the title page and references pages, and be in Word or PDF formats.
Title page similar to the one in the project proposal, with the project report submission date.
Table of contents and page numbers.
Include list of references and use either APA or Harvard referencing style.
The proposal should include, at least, the following:
Final User Stories and Sprints
Final product backlog with screenshots showing it in Jira.
Final start and end dates for the five sprints planned for both MIT651 Project Capstone 1 and MIT652 Project Capstone 2.
Final description of how all project objectives are satisfied by the defined user stories.
Final description of how some of the defined user stories provide novel functionality compared to existing systems.
Design and architecture Overview
Includes a professional presentation of the final design and architecture.
Functionalities
Description of the functionalities developed by the team and how they map/address project objectives.
Third-Party Functionalities
Proper references and brief description of third-party functionalities (such as APIs and libraries) used by the team with discussion and justification for their use.
Implementation Challenges
Description of any tricks, non-trivial algorithms, and special architecture/design while implementing the system.
User Documentation/Manual
How to build, setup, configure, and use your system and functionalities.
Final Project Planning
Includes a Work Breakdown Structure (WBS) for your final project planning.
Includes a Gantt chart for your final project planning.
Final Storyboards
Final storyboards (that is, screenshots) showing the developed system functionalities.
Report Formatting
Report conforms to the formatting requirements specified above and is easy to read.
The submission for this assessment should also include your entire and complete code that your team has developed for the project. This will be mainly assessed for the scale and technical depth of the delivered implementation, its correctness, its value, its novelty, its performance (e.g., is it too slow for its intended usages), clarity of your code, its design (including interface design), its structure and organization, and ease of use.