Reference no: EM133517145 , Length: word count:1900
Software Design and Development Project
Assessment: In-class Project Demonstration and Report
Task Description:
This is a group assessment, however, individuals may receive different scores based on their contributions. This assessment has two components - Part 1: In-class Presentation and Demonstration, and Part 2: Report. Part1 and Part 2 submissions are due in Week 10 and Week 12 respectively.
Part 1: In-class Presentation and Demonstration
In this part, you are required to present all aspects of your enterprise application including the project background, objective, user stories, major data structures, database design, software architecture, sequence diagram, platforms/tools/frameworks, test results (including user acceptance test), and lessons learnt. This presentation should form the basis of your public presentation (Assessment 5).
Moreover, you will run the current prototype of your enterprise application in a lab computer/your personal computer/your mobile device to demonstrate the user stories/interfaces/features/business logic that have been fully or partially implemented during the current progress period. You are also required to show evidence of tracking the progress of your project using a project tracking tool (e.g., Jira).
For this part, you must submit a presentation file to Moodle by the end of Week 10.
Part 2: Report
In this part, you are required to develop a final report containing a final project summary, user stories, major data structures, database design, software architecture, sequence diagram, platforms/tools/frameworks, test results (including user acceptance test), user manual and a project reflection. In Appendix of the report, you will have to provide implementation details of the various components of your latest prototype. That means you will provide screenshots of various components of your source code and explain the role of each component, how it works, and what input it takes or what output it delivers.
A copy of the prototype source code must be maintained in a GitHub repository and the link to the repository must be included in the report.