Reference no: EM131844844
Assignment
• I especially need user documentation that is complete enough that non-team users can operate the system and a progress report including issues encountered, what was done to overcome them, a comparison schedule with specific items completed and by whom.
• Provide a summary document of the work that was completed, issues encountered, progress against schedule, and updated risk analysis
o Include specific work completed by individuals in the summary.
• Test plan (from original project plan) and summary of test results
o Include an evaluation of the results and the implications for further required development and testing. Major defects (those that prohibit release of the application) should be clearly noted.
• Beta candidate project application
o The beta candidate should include all of the required functionality and should have passed the group's testing successfully. The group should be ready to have this candidate tested by members outside of the group.
o The group should also include sufficient user documentation to allow nongroup members to successfully operate the application.
• Zip file of well-documented project code
Your application should be fully functional at this point, and your remaining time should be spent on building quality. Quality is not just about making sure there are no serious defects in the software but also ensuring that the requirements have been met.
For this assignment, your group will finalize the code in your application and work on the quality issues. You will provide another summary document of the work completed according to the instructions below. You will also prepare a comprehensive test plan and execute the plan.
The project deliverables are the following:
• 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 that was completed by each individual on the team. This summary should address the technical coding progress to assist in the review of the code.
o Discuss any issues that you have encountered in the work and how your team has decided to address those issues. These could be technical coding and implementation issues or other issues that impeded progress.
o Summarize progress against the schedule, and discuss how the team has decided to work through delays (if any) so that the project will remain on-track for timely completion.
o Challenge Topic: Include a summary of how the team has been monitoring and controlling risks that were encountered thus far in the project.
• Test Plan:
o Define specific tests that will be performed to ensure that the application meets all of the requirements.
o Include an evaluation of the results and the implications for further required development and testing.
o Major defects (those that prohibit release of the applications) should be clearly noted.
• Beta Candidate:
o Prepare a build of your application following execution of the test plan and include modifications based on the results of the testing. This will be the beta candidate of the application.
o The beta candidate should include all of the required functionality and should have passed the group's testing successfully.
o The group should be ready to have this candidate tested by members outside of the group.
o The group should also include sufficient user documentation to allow nongroup members to successfully operate the application.