cos301-se-2022 / team-utilisation-monitor Goto Github PK

DONE

• Added Headings
• Added Team Banner
• Added Project description

TO DO

• add link to demo
• add link to SRS documentation
• add team member profiles and links to LinkedIn

• Create proper navigation, cards and settings for a logged in user

• implement the nav bar as a component to standardize the nav bar across the admin pages

Create a sign-up page for the admin
Create a sign-up page for the user

• Add Utilization history fields in Company table and Person table
• This will be an array of 12 Float values used in timeline utilization graphs

Issue: We need to be able to generate multiples of the same component. meaning that the datalink needs to change in order for each employee to get their own name. currently all the components is linked to the same variable and will have the same name, Cornel does not yet know how to fix this issue

Possible solution:
using an array to and referencing to that to get each employee's name, discussion will follow in weekly scrum.

To show Chris on 10/05

• Create wireframe for login page
• Create wireframe for logged in user
  • dashboard that shows user details. as well as current selected organization, settings, name, status ...
  • current status of the users inside of the organization (owner, admin, contributor/worker)
  • cards that show workers inside the organization as well as their utilization. ability to shift the view to something like a graph, list, less detailed list, and more...
• Create wireframe for an individual worker, when clicked it should display
  • show stats of current user like their utilization
  • current projects
  • current efficiency
  • skill set and more...

• add graph home page
• add current company user page
• add list view of employees and their utilization

Document detailing our project.

add links to the recording of Demo1 and all meetings handled on BB Collaborate to the ReadMe.md file as to comply with Demo1 instructions.

• create components for the owner and company employees, admin and employee.

• the function should be able to allow a user to to register a company
• It should use CQRS(research)
• Should take inputs such as company name and company admins.
• And store that data in the database

Create a Mono-repo
Create a gitflow structure

add Routing to admin Home Page if an admin log in via the Login Page

this nav bar will be replicated on the Admin list view as well as the Admin Company view pages so routing will be required as soon as front end is done for the admin pages.