COS420-Fall24 / Team-F

Team Firetruck's COS 420 working repository
Creative Commons Zero v1.0 Universal
1 stars 0 forks source link

Use Case Descriptions: Complete 2 to 3 Descriptions #73

Closed bryansturdivant closed 1 month ago

bryansturdivant commented 1 month ago

Use Case Diagrams/Models and Descriptions ( /30)

Use this use case description template.

Examples: UMaine Connect Team C 2022 Team F 2022 (some errors in arrows but overall good)

Make the use case diagrams first, then assign individual people to making each use case’s description.

About 10 - 20 use case descriptions and 2-4 use case diagrams/models each including 3 - 5 use cases.

If the number of use case descriptions (UCD) is below 10, deduct -3 points for any one missing. For example, if there are only 8 UCD, then deduct -6 points.

If the number of use case diagrams/models is less than 2, deduct -10 points.

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 UCD 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 in the UCD

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

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

If the quality of the UCD or diagrams varies substantially, deduct -10 for the team not internally reviewing/quality checking their work before submission. Not recoverable with regrade.