COS420-Fall23 / Team-D

This is Team D's project repository. Shall be tackling the problem of helping graduates/students find a reliable job by cutting down the search method or type that other sites use.
3 stars 2 forks source link

Update Use case descriptions #164

Closed DracoDrakthen closed 11 months ago

DracoDrakthen commented 11 months ago

The comments from Deliverable 5 must be addressed.

For any comment that was not addressed, deduct -2 points.

If the number of UCD were below 10 or the models/diagrams were below 2 in Deliverable 5 and they did not change in Deliverable 5, deduct -5 points for each.

If the models/diagrams are missing entirely, an additional -5 points

If the quality of the UCD or models varies substantially, deduct -5 for the team not internally reviewing/quality checking their work before submission

Use this use case description template. Here is an example of Use Case Diagrams and Descriptions.

Use case diagrams/models should be correct and have the correct links.

If they have unnecessary arrows, deduct -2 points per each mistake.

If they are complicated, deduct -5 points per each diagram/model.

Use cases should start from the actor. If not, deduct -2 points for each mistake.

Only have include, extend and generalize links between the use cases.

If the links are not correct or they do not have a type, deduct -2 points for each mistake.

Use case descriptions should follow the templates/guidelines from slides or the given template.

If they do not match, deduct -5 points for each mistake.

The name of the UC Descriptions should match with the use cases in the diagram.

If they do not match, deduct -1 point per each mistake.

The related use cases should be shown correctly

If they do not shown correctly, deduct -1 point per each mistake.

For every other mistake, deduct -1 points for each.