ICT308 IT Project 2
Assessment 1 – Iteration 2 Product Backend Development and Testing Documentation (25%)
1 Overview
Assessment Group/ Weight Due
individual
1. Iteration 2 Product Backend Development and Testing Documentation Group 25% Friday, Week 10
• Please see CIHE Moodle for the exact due date of this assessment.
This is your final iteration and at the end of the iteration your project should be complete and handed over to your client.
THERE ARE THREE COMPONENTS TO THIS ASSESSMENT AS FOLLOWS:
• Component A – Backend Development
• Component B – Acceptance Testing
• Component C – Usability Testing
2 Component A – Backend Development
Component A of this assessment has the following three parts:
• Part 1: Member’s contribution in the backend development
• Part 2:Business user stories to be included in your project
• Part 3:Plug-ins and templates your team used to implement these user stories. You need to describe the purpose and outcome from each plug-in in the backend development.
Note:
A sample of component A is included in assessment 1 iteration 2 folder for your reference.
3 Component B – Acceptance Testing
Write a brief summary of objectives of acceptance testing in your project.
Please note:
• You must have at least one acceptance test for every user story you have completed in the project.
• Depending on how many acceptance tests you have, you could include them all in Acceptance Testing. Alternatively, you may like to group them on different sections, i.e. Frontend Acceptance Testing (for example, a user is able to browse the homepage for the e-commerce website), Backend Acceptance Testing (for example, an admin is able to update item information from the e-commerce website).
• A sample of acceptance testing is included in assessment 1 iteration 2 folder for your reference.
4 Component C – Usability Testing
Write a brief summary of objectives of usability testing in your project.
Please note:
• You must attach the completed usability tests to your Usability Testing section. Alternatively, you may like to group them on different sections, i.e. General Usability Testing, Task-Specific Usability Testing.
• You can choose up to 5 participants in the usability testing. The client or anyone you know of can be the participant in the usability testing. The participants need to sign the usability testing form and you need to include these forms as a part of assessment 1 iteration 2 submission. A sample of usability form is included in the assessment 1 iteration 2 folder for your reference.
ALL teams must also make a video demonstrating your product. If you do not have screen recording software, a good free version is OBS Studio – https://obsproject.com/. You will need to upload the video of your product and attach the link in the assessment 1: iteration 2 submission document.
___________________
Component A – Backend Development
Part 1: Member’s Contribution in the Backend Development
In this part, you need to outline the contributions made by each member of your team in the backend development of the project. Describe the tasks assigned to each member and their role in implementing those tasks.
Part 2: Business User Stories
In this part, you should include the business user stories that have been implemented in your project. User stories describe the functionality or features of the system from the perspective of the end user or customer. Include a description of each user story and how it contributes to the overall project goals.
Part 3: Plug-ins and Templates
Describe the plug-ins and templates used by your team to implement the user stories in the backend development. Explain the purpose of each plug-in and template and how they were utilized in the project. Provide an overview of the outcomes achieved through the use of these plug-ins and templates.
Component B – Acceptance Testing
In this section, provide a brief summary of the objectives of acceptance testing in your project. Acceptance testing aims to ensure that the system meets the specified requirements and is ready for deployment. It involves testing the system’s functionality, usability, and performance against the acceptance criteria defined for each user story. Mention that you must have at least one acceptance test for every user story completed in the project. You can choose to group the acceptance tests into different sections, such as frontend acceptance testing and backend acceptance testing, based on the nature of the tests.
Component C – Usability Testing
In this section, write a brief summary of the objectives of usability testing in your project. Usability testing aims to evaluate how user-friendly and intuitive the system is for the end users. It involves observing users as they interact with the system to identify any usability issues or areas for improvement. Mention that you must attach the completed usability tests to this section. You can choose to group them into different sections, such as general usability testing and task-specific usability testing. Also, mention that you can choose up to 5 participants for the usability testing, and their signed usability testing forms should be included as part of the submission.
Additionally, mention that all teams must create a video demonstrating their product. Provide a link to OBS Studio, a free screen recording software, for teams that need it. Teams should upload the video of their product and include the link in the submission document for Assessment 1: Iteration 2.
