... | ... | @@ -5,7 +5,8 @@ |
|
|
|
|
|
|
|
|
## Introduction
|
|
|
*
|
|
|
* The quality assurance goals we are focused on meeting are easy to set up to run, quickly understood how to use, and can be used without encountering bugs or crashes.
|
|
|
* To meet these goals set we are using unit testing to weed out bugs that may be introduced by new code and comparing the user experience to the acceptance tests from our user stories.
|
|
|
|
|
|
|
|
|
## Scope (FURPS+) *****Need to add features & requirements that will NOT be checked*****
|
... | ... | @@ -39,11 +40,16 @@ |
|
|
* Physical Constraint: One of our largest constraints is the size of a phone. We need to make an app that is usable in a relatively small format (and the various different sizes available for Android phones, which means our design/layout has to be adaptable). We also need to take into account the different shapes for Android phones available (i.e. notch vs no-notch, camera cutout, different aspect ratio, etc.).
|
|
|
|
|
|
## Quality Objective
|
|
|
*
|
|
|
* Markers will be able to visit every page and use any interaction element, buttons or text entry, without the application crashing.
|
|
|
* Markers can intuitively understand how to use the application once launched without the assistance of external resources.
|
|
|
* Markers are able to set up and run the application with use of the instructions inside the README file.
|
|
|
|
|
|
|
|
|
## Roles and Responsibilities of Team Members
|
|
|
* Brayden:
|
|
|
* Brayden
|
|
|
* Front End
|
|
|
* Responsible for All Leagues, League, Team and Member pages, pop-up pages, and the design theme for the application.
|
|
|
* Will ensure the theme is consistent throughout the application and each page is layed out cleanly.
|
|
|
* Lee:
|
|
|
* Jay: Responsible for the complete sidebar navigation menu and home page. Will ensure that user navigation is intuitive & smooth, and that the respective GUI components work as expected.
|
|
|
* Shantanu:
|
... | ... | @@ -59,12 +65,19 @@ |
|
|
|
|
|
## Action Plan
|
|
|
* Work done over the past week:
|
|
|
* Brayden:
|
|
|
* Brayden
|
|
|
* Finished the All Leagues page. Includes a search bar, list of leagues, floating action button to call a pop-up for the addition of a new league.
|
|
|
* Created a League page which is the same as the All League page but instead shows teams and a pop-up for adding a new team.
|
|
|
* Created a Team page which shows the record for the team, next scheduled game, and a list of the current members.
|
|
|
* Created the two pop-ups mentioned before for adding either a new League or Team.
|
|
|
* Lee:
|
|
|
* Jay: Added scrollable teams list to the homepage, showing all individual teams that the user is part of. Currently, it shows hard-coded teams (for testing). This will be modified later to get the teams from the firebase database for the user. When a team is clicked, it goes to the individual team info page (which also has hard-coded info, for now). I wrote the scope for this milestone.
|
|
|
* Shantanu:
|
|
|
* Work to be completed next week:
|
|
|
* Brayden:
|
|
|
* Brayden
|
|
|
* Create a Member page for displaying the information about a user.
|
|
|
* Add a floating action button for adding a new member to the team. This will be visible only to the owner of a team.
|
|
|
* Add a seperated owner field above the member list in the Team page.
|
|
|
* Lee:
|
|
|
* Jay: Will update the homepage to show user specific teams from the database (once we figure out how to do that). Will also work on the profile page for individual users.
|
|
|
* Shantanu:
|
... | ... | @@ -72,10 +85,10 @@ |
|
|
|
|
|
|
|
|
|
|
|
TODO:
|
|
|
* Introduction - brief description of quality assurance strategies we are using
|
|
|
* Scope – The features and requirements (functional and non-functional)that will be checked and those that will not be checked. (Refer to FURPS+)
|
|
|
* Quality Objective – e.g., markers are able to run without it crashing and markers are able to use it by only referring to the Readme file
|
|
|
#TODO:
|
|
|
* ***DONE*** Introduction - brief description of quality assurance strategies we are using
|
|
|
* ***DONE*** Scope – The features and requirements (functional and non-functional)that will be checked and those that will not be checked. (Refer to FURPS+)
|
|
|
* ***DONE*** Quality Objective – e.g., markers are able to run without it crashing and markers are able to use it by only referring to the Readme file
|
|
|
* Roles and responsibilities of team members
|
|
|
* Test methodology – deliverables, strategies/approach (unit, regression, system/integration, acceptance), bug reporting, test tools
|
|
|
* Inspection methodology – deliverables, strategies/approach |
|
|
\ No newline at end of file |