* Shantanu: Shantanu finished integrating the user account to the user/member Java Class (so that one user account corresponds to member info - including stats, teams joined, etc). (6 hours)
* Brayden:
* Brayden: Began working on the Leagues page, now displaying list of leagues with a search bar. (6 hours)
* Lee:
* Lee: (6 hours)
* Jay: Previously, clicking on a sidebar navigation menu item opened a "fragment", which replaced a portion of the screen of the main screen. Over the last week, I have been making brand new activities (which consists of a Java file and a corresponding XML file) and linking the menu options to open a new activity. Now the code for each activity includes the menu button and the top bar (which previously wasn't needed when making a fragment).
* Jay: Previously, clicking on a sidebar navigation menu item opened a "fragment", which replaced a portion of the screen of the main screen. Over the last week, I have been making brand new activities (which consists of a Java file and a corresponding XML file) and linking the menu options to open a new activity. Now the code for each activity includes the menu button and the top bar (which previously wasn't needed when making a fragment). (6 hours)
* Work to do in the next week
* Work to do in the next week
* Shantanu:
* Shantanu: Will begin the process of fetching from the database for updating the app information.
* Brayden:
* Brayden: Will start work on the Home page.
* Lee:
* Lee:
* Jay: I will finish making the remaining Activities (Java and XML classes for each of League, Team, About Us, etc). I will add a functional menu button (and sidebar navigation bar) and a top bar for each activity.
* Jay: I will finish making the remaining Activities (Java and XML classes for each of League, Team, About Us, etc). I will add a functional menu button (and sidebar navigation bar) and a top bar for each activity.
\ No newline at end of file
# Requirements
- Action Plan
- who did what and who will do what
- provide time actuals and time estimates per person
- Design storyboards
- Low-fidelity sketches of principle user stories
- System architecture
- Use a UML component diagram
- key components identified (tiers)
- packages and nested components identified if necessary
- required and provided interfaces of components are identified
- associations between components
- deployment nodes (devices or execution environments)
