cos-301 / graduates Goto Github PK

Investigate and formulate testing plan for the project. Textbook has additional information.

Due: 20/03/22

Task: BA must create the documentation listing the functional requirements needed for the storage feature. This must be in either Overleaf or Google docs

Deadline: 15/03/2022

I already created the api and data-access lib, the service lib should still be created.

Wireframe the front-end and design some mockups

Due: 19/03/2022

Compile a miniature feasibility study to add to the SRS.

Due: 20/03/2022

To be done by: Sunday 28 March

Due Date: 21/03/2022

** Description:**
* Must design and implement the database schema for the the feature. Must be able to store:
1. Company Representative name, surname, company and role in company.
2. Description about company rep
3. Username and Password.

-Module & Sub-module planning
-Angular Material Theme creation

Task: Must determine at 3 functional and 3 non functional requirements for the Company Representative Profile. All of these must be in an Overleaf document
Deadline: 15/03/2022

• Verify roles with Authentication and other teams
• Design of repo layer for the service layer to interface with data https://stackoverflow.com/a/52579478 (maybe this would help)
• push your Mock entities to the repo under our feature's shared library
• Write tests for your code

Something to consider :
https://docs.oracle.com/en/cloud/get-started/subscriptions-cloud/csimg/authorization-error.html#:~:text=If%20the%20access%20code%20request,Copy

work with designer to come up with use cases for accessing data and when unauthorized user accesses data, admin giving permission, and errors being shown

Define the acceptance criteria for the feature to be accepted

Due: 22/03/22

Due Date: 21/03/2022

Task: Create the UI with mock data[name, surname, company, description and etc.]

Due date: 14/03/2022 09:00

Investigate into whether a class (or design pattern) wrapped around the API interactions/GraphQL could be beneficial. A class which interacts on the backend which the backend engineer can use to generate valid queries and similarly on the frontend. The class then abstracts the API details from other members which may need to use it.

If it could be beneficial, please make a UML diagram to begin modelling it

To be done by Sunday 20 March
New due date: Thursday 24 March (as per BA WhatsApp group)
See: #72

A test on making cards

Now that UI Kit has been given to us I need to complete designing the register and login pages.

• [ ]Test plan
• [ ]

Diagrams which show the process flow of the backend.

1. Activity diagrams outlining receiving API calls to storing the request DB.
2. Sequence diagram of object call interactions (makeup the names for now as none are finalized)

Essentially an outline of how the backend will operate.

Due: 19/03/22

Due: 19/03/22

System needs to be decomposed into subsystems hierarchly ordered in terms of importance and functional requirements need to be assigned to them

Assigned to: Gerard

Create ER diagram of backend DB schema.

Possibly automate this using prisma.

Due: 19/03/22

Add to the wiki the different roles the system will have

Due: 19/03/22

You two should discuss a class (design pattern or a single class) to interact with the database on the backend through PRISMA.
Investigate whether PRISMA directly should be fine but a class which does the inserting/updating etc. (interface wrapping ontop of PRISMA) and which scrubs the data to check it is safe for the DB would be a good idea.

Please look into making a UML diagram which could be used as reference.

• Design how the api layer will communicate with the service layer, how data will be accessed
• Mock code for requesting data from the database (receiving requests from service and requesting that data from the database)

Due Date: 21/03/2022

1. Abstract & high-level use cases. and use case diagrams.
2. Perform behavioural modelling of the system.

Creation of the database schema for the following relations and data structures:

• user_permissions
• permissions
• roles
• role_permissions
• user_role

Go through the roles I sent to you and check if we have all the functional requirements

See group recording for additional information.
Document the planned endpoints

Due: 19/03/22

To be done by: Sunday 20 March

Task: Create wireframe Ideas and post the link to the document

• Work on the business logic for authorization https://softwareengineering.stackexchange.com/a/234254 (maybe this would help)
• Service layer Mock https://stackoverflow.com/a/52579478 : service layer (maybe this would help)
• Have mock code for the other teams to work with, push it to the library
• Write tests for your code

To be started by: Sunday 20 March
To be done by: Sunday 28 March

• create mock code for the front end after designs have been made

• Add it to the feature library

• Write tests for your code

• Note it doesn't have to be a full fledged ui just something that other teams can work with e.g. code for the 404 error message popup

• Create Designs for error messages (how they will be shown, suggested: notification eg popup)
• Mockups of the designs created (wireframes and stories)
• Add designs to github

Retype the functional requirements, non-func, and acceptance criteria in brief on requirements wiki and define completely in BA documentation

Contribute a wiki page to help people with git flow and contributing code to upsteam.

As per: #15 (reply in thread)

Task: Design the wireframe for the Company Representative Profile Page
Due Date: 14/03/2022

Design a provisional activity diagram for front-end interactions for Request of access

Due: 19/03/22

Compile the docs related to the initial work.

Look at all our issues related to docs

Due: 20/03/22