-
Notifications
You must be signed in to change notification settings - Fork 2
Deliverable 1 Report
Max Brodeur-Urbas edited this page Feb 11, 2019
·
6 revisions
Also see Domain Model
- We tried doing the player-role pattern on UML and it did not generate a correct code, so we decided to simplify our model for the sake of debugging and code simplicity.
- We decided that each term instructor can grade a document pass or fail. If all documents are passed, the coop position itself will be completed. Otherwise, it will be failed.
- Decided to implement a method that would sort the courses by popularity rather than include cover functionality in the domain model.
- Unit 3
- Our group is doing Program Manager and Term Instructor
- Start writing down use cases
- Create issues on github
- List of questions for TA:
- Do we have multiple disciplines?
- Do we need to account for all actors in use case diagram?
- Is it the employer or the student that submit the evaluation form.
For next meeting:
- Continue writing use cases
- Think about class diagram
- Work on class modeling
- Decisions for model (See Domain Model Version 1)
For next meeting:
- Backend should be set up
- Start writing everything on wiki
- Our generated code from UML Lab does not work.
- Simplify model, no more player-role pattern, use association instead of composition (See Domain Model Current Version).
TODO: Test Cases
- Fixed Heroku deployment
- Model and persistence layer works
- 3 Working test cases
For submission:
- More test cases
- Determine if there are any last changes to the model
Group 19 BRODEUR Max, DENG Sophie, ELKHOURY Carl, KABA Andre, ZHOU Mia