Data Dictionary
Actor Description
TEMPLATE
Name
Alternate Names
Input Data
Name of Use Case
Inputs to the System
Name of Use Case
Outputs from the System
Output Data
Description
Comments
Data Dictionary
Actor Description
INSTRUCTIONS
Name -
Name of the actor EXACTLY as it appears on the use case diagram. It must be a noun or
noun phrase with the first letter of the name capitalized.
Alternate Name(s) – Alternative names this actor may be referred to in the application domain.
Providing these names helps the readers to understand this document.
Input Data - List of the inputs to the system that this actor provides. This section must contain a list of
the use cases with which this actor interacts (has a line on the use case diagram) and
provides input. For each use case, list the inputs this actor provides.
Output Data - List of the outputs from the system that this actor receives. This section must contain a list
of the use cases with which this actor interacts (has a line on the use case diagram) and
receives output. For each use case, list the outputs this actor receives.
Description - Brief description of the general purpose or role of this actor.
Comments -
Any additional information that aid in the understanding of this actor.
Grading Criteria
Data Dictionary – ACTOR and USE CASE Descriptions
1. Lateness of deliverable:
1 day late 20 points
2 days late 40 points
3 days late 80 points
After 3 days late a zero grade is recorded.
2. Correctness (80 points total):
a. Actor (20 points total)
i. Name does not match use case diagram
ii. Actors missing or incorrect
iii. Obvious alternate names missing
iv. Input/Output data missing
v. Input/Output data incorrect
vi. Description missing, incomplete, incorrect, or ambiguous.
b. Use Case (60 points total)
i. Name does not match use case diagram
ii. ID does not match use case diagram
iii. Requirement number does not match functional requirement in Section III of the
SRS.
iv. Description missing, incomplete, incorrect, or ambiguous.
v. Pre-condition missing, incomplete, incorrect, or ambiguous.
vi. Post-condition - missing, incomplete, incorrect, or ambiguous.
vii. Trigger - missing, incomplete, incorrect, or ambiguous.
viii. Normal scenario - missing, incomplete, incorrect, or ambiguous.
1. Scenario steps out of order
2. An extension included in the normal scenario.
3. Not underlying reused use cases.
4. Steps written too granular (keystroke level)
5. Steps written too broad (for example, rent video)
6. Use of proper phrasing (for example, check whether vs. validate)
ix. Extensions – missing, incomplete, incorrect, or ambiguous.
1. Extension steps out of order
2. Extension numbering incorrect
3. A normal scenario step included in the extension.
4. Not underlying reused use cases.
5. Extension written too granular (keystroke level)
6. Extension written too broad (for example, rent video)
3. Format(20 points total):
a. Not written in required format as provided in instructions – 1 point per occurrence
i. Not in the table format provided.
ii. Normal scenario steps not written in the specified format (for example, subjectverb-direct object)
iii. Extensions not written in the specified format (for example, missing colon)
b. Misspelled words – ½ point for each occurrence