IS480 Team wiki: 2018T2 BOSS Unit/Midterm Wiki
Project Progress Summary
| Midterm Slides | Web Deployed Site |
|---|---|
| Midterm Slides | Partnerry Deployed AWS |
Project Management
Planned Project Scope: before Acceptance
Actual Project Scope: after Acceptance
Planned Project Timeline
Actual Project Timeline
Quality of product
| Topic of Interest | Link |
|---|---|
| Project Management | Minutes |
| Metrics | |
| Risk Management | |
| Project Schedule | |
| Project Overview | Project Overview |
| Project Scope | |
| Project Documentation | Technical Diagrams |
| Wireframe | |
| Choice of Technologies |
Internal Testing Approach
During each iteration, after developers conduct their unit testing and commit their codes, the quality assurance team will perform comprehensive manual testing testing. Bugs are documented and developers are notified of the issues. Regression testing is also conducted at the end of every iteration to ensure that all previously built functionalities have not been impacted and are still functional.
User Testing Approach
Given that our project is a self-proposed idea, our team understands the need to constantly validate the product being built by performing tests to ensure that it is both functional as well as a desirable product that meets user needs. Two types of user tests will be performed - namely, User Testing and User Acceptance Testing. While they are both similar, they differ slightly in terms of their goals:
User Acceptance Testing
- More focused on finding bugs in the website and its functionalities
- Ensure that the product works according to the requirements and functional specifications
Usability Testing
- More focused on testing if the application is easy to use for the end user
- Feedback on user experience is used to make incremental changes to the website design
For user test details, access here:
| [[Image: |110px|link=IS480 Team wiki: ]] | [[Image: |110px|link=IS480 Team wiki: ]] |
|---|
Reflections
[[image: |center|800px]]
