COS420-Fall23 / Team-H

Team H's Project Repository; Problem: Supporting learning in augmented and virtual reality
0 stars 1 forks source link

Use Case Diagrams/Descriptions - Feedback Update #47

Closed rgiles4 closed 8 months ago

rgiles4 commented 8 months ago

Use Case Diagrams/Models and Descriptions ( /10)

The comments from Deliverable 2 must be addressed.

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

Update Use Case Models and Descriptions document with potential new use cases and based on the feedback given on prior Deliverable(s)

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

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

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

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.