Reference no: EM131824449
Assignment
You will be expected to produce some type of prototype for the application. Prototypes help demonstrate progress to the stakeholders, and they also help you measure your team's progress against the design and the project plan. Although a lot of coding work must be done on these projects that is not visible to anyone outside of the project, it is also important to be able to show something visual to less technical people because that is how they view the application.
For this assignment, the group will continue its work on the project and provide a progress report. Your group will also demonstrate your progress on the coding efforts with a prototype and code.
Assignment Details:
• Project Status Report: Prepare a summary document that includes the following:
o Summary of work completed
- This summary should identify specific tasks in the project plan.
- Include identification of specific work completed by each individual on the team.
- This summary should address technical coding progress to assist in the review of the code.
o Discuss issues encountered in the work and how your team has decided to address the issues. These could be technical coding and implementation issues or other issues that impeded progress.
o Summarize progress against the schedule and how the team has decided to work through delays (if any) so that the project would remain on track for timely completion.
o Challenge Topic: Prepare a planned-versus-actual view of the project time line, and discuss the primary problems that caused the variance.
• Functional Prototype: Prepare a functional prototype of your application that meets the following requirements:
o The prototype should demonstrate the overall design of the project from a user interface (UI) perspective. The major functionality of the application should be apparent in the prototype. Functionality is not required at this point, but the UI should have a sufficient level of design completed to support the functionality in the design document.
o The prototype should demonstrate the overall design from a code perspective. Class definitions, including properties, constructors, accessors, and methods should be defined and either implemented or stubbed. Navigation through the application should be functional. Code should be well-commented and notes should identify areas that still need to be completed.