HeaderSIS.jpg

IS480 Team wiki: 2018T2 BOSS Unit/Finals Wiki

From IS480
Jump to navigation Jump to search
BOSSUnit Logo.PNG


Nav home active.png
1 nav aboutus.png
1 nav projoverview.png
1 nav projmgmt.png
1 nav doc.png

 


 

Project Progress Summary

Project Highlights


Finalcurrentstatus boss.PNG
Bosshighlights.PNG


Final Slides Wed Deployed Site Eventually Facebook Page
File:Final Slide V1.pptx Partnerry Deployed Website Partnerry Domain Page



Project Management

Project Status


Planned Project Scope
BOSSUnit PLAN SCOPE.PNG
Actual Project Scope: Re-Scoped after talking to real business users and sponsor
Partnerryscopefinal.PNG


Project Schedule


Planned Project Timeline BOSSUnit INITIAL 1.PNG BOSSUnit INITIAL 2.PNG


Actual Project Timeline BOSSUnit actual 1.PNG BOSSUnit actual 2.PNG


Project Metrics


Taskmetricsboss.PNG


Bugmetricsboss.PNG


Challenges


Challengesginalboss.PNG



Technical Complexity


Technicalcoplecityboss1.PNG
Complexityboss2.PNG
Complexityboss3.PNG


Quality of product


Intermediate Deliverables


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
Testing


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:

Hatchid UT1.png Hatchid UAT1.png Hatchid UT2.png Hatchid UAT2.png Ut3pic.png

 


Reflections

Team Reflections


Yjreflectionpic.PNG
Refelction2.PNG
Reflection23.PNG