... | ... | @@ -5,11 +5,11 @@ |
|
|
|
|
|
|
|
|
## 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.
|
|
|
* 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*****
|
|
|
## Scope (FURPS+)
|
|
|
* Functionality (functional requirements)
|
|
|
* Users should be able to log in to their account (in the app)
|
|
|
* The user/member should be able to search for leagues and teams
|
... | ... | @@ -30,7 +30,7 @@ |
|
|
* Our app should also load within 3 seconds max. if we compare this time to a website, it will be faster than 50% of the web and corresponds with the time that the average user leaves a website if it has not loaded yet (https://www.bluecorona.com/blog/how-fast-should-website-be/). We will aim for 1-2 seconds load time, but 3 seconds will be our max.
|
|
|
* Supportability
|
|
|
* Our product (the app) will be published on the Google Play Store. Releasing updates/revisions will also be published on the Google Play Store, which is how our users will be able to update the app.
|
|
|
* Our system is very maintainable, since we own (or have access to) all aspects of the app: Android Studio (which is where our app can be modified and features can be added), and Google firebase. Both of these things will be available and used by us even after the class is done this semester.
|
|
|
* Our system is very maintainable since we own (or have access to) all aspects of the app: Android Studio (which is where our app can be modified and features can be added), and Google firebase. Both of these things will be available and used by us even after the class is done this semester.
|
|
|
* Testing for this system will occur locally through Android Studio (unit tests by testing individual classes, and systems tests by using the Android emulator). Through the emulator, we will be able to test our app on a variety of phones and Android OS versions.
|
|
|
* Our app can also be easily modified (and features can be added), since all the source code can be edited on android Studio.
|
|
|
* "+" (design, implementation, interface, and physical constraints)
|
... | ... | @@ -42,22 +42,25 @@ |
|
|
## 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.
|
|
|
* Markers are able to set up and run the application with the use of the instructions inside the README file.
|
|
|
|
|
|
|
|
|
## Roles and Responsibilities of Team Members
|
|
|
* 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.
|
|
|
* Will ensure the theme is consistent throughout the application and each page is laid-out cleanly.
|
|
|
* Lee
|
|
|
* Back End
|
|
|
* Responsible for java classes, interfaces and assisting in database operations.
|
|
|
* Will ensure back end code is efficient and of sufficient quality.
|
|
|
* 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.
|
|
|
* Jay:
|
|
|
* Front End
|
|
|
* Responsible for the complete sidebar navigation menu, icons, header bar, and home page
|
|
|
* Will ensure that user navigation is intuitive & smooth and that the respective GUI components work as expected.
|
|
|
* Shantanu
|
|
|
* Back End
|
|
|
* Responsible for Database and application integration with database for running query and login.
|
|
|
* Responsible for Database and application integration with database for running query and log-in.
|
|
|
* Will ensure back end code is efficient and of sufficient quality, Also will take care for further API integration.
|
|
|
|
|
|
|
... | ... | @@ -88,7 +91,7 @@ |
|
|
* 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: Refactor League, Team and Member classes to facilitate reading and writing to database; create Info interface and objects to do this.
|
|
|
* 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.
|
|
|
* Jay: Will update the homepage to show user-specific teams from the database (once we figure out how to do that). I will also work on the profile page for individual users.
|
|
|
* Shantanu: Finish dynamic list for menus and to fetch class at once instead of fetching individual property. Storing the data locally based upon time stamp. So that user can access basic features without network. Also need to work on phone permissions to access user calendar and other apps.
|
|
|
|
|
|
|
... | ... | |