1. Use Case Model (40 marks)
Analyse the case study to determine the high level functional requirements for the new system. Express your understanding of those requirements with:
a. A use case diagram capturing at least all critical and significant use cases that the system will have to support
b. A document containing short use case descriptions for the use cases identified in the use case diagram.
2. Domain Model (40 marks)
Analyse the case study to determine the classes required to express the problem domains structure and operation. Express your understanding of the problem domain in:
a. A domain model.
3. State Machine (20 marks)
Analyse the lifecycle and behaviour of the most complex stateful object* identified in your domain model and express its behaviour in:
a. A state machine diagram
*Note: a list of appropriate domain objects will be made available during semester. Please contact the lecturer to confirm your selection if you wish to complete this task before that list is available.
Rationale
This assignment relates to the following:
- be able to analyse and verify system requirements;
- be able to produce and verify analysis and design models for a system
Marking criteria
Use Case Model
| Criteria | Fail (Bad) | Pass (OK) | Credit (Good) | Distinction (Very Good) | High Distinction (Excellent) |
| How well does the Use Case Model address its intended purpose? |
Incorrect concept of use cases demonstrated. Short use case descriptions missing, largely incomplete, or generally wrong. Presentation poor, bad spelling and poor grammar in use case descriptions. |
Correct concept of ‘end-goal’ use cases demonstrated. Some critical or significant use cases identified, many missing. Some use cases inappropriately named. Some important/obvious external actors identified, many missing or misidentified. incomplete, or poorly described, some missing. Short use case descriptions generally consistent with use case diagram. |
Correct concept of ‘end-goal’ use cases demonstrated. Most critical and significant use cases identified. Use cases correctly named with short imperative action statements. Most important external actors identified Generally correct UML syntax. Short use case descriptions provided for all critical and significant use cases. Short use case descriptions consistent with use case diagram. |
All Credit requirements plus All critical and significant use cases identified Other necessary but minor use cases identified. All external actors identified, including external systems and events. Common elements of end-goal use cases factored out into ‘sub-function’ uses cases. Generally correct use of <<includes>> and <<extends>> relationships. Short use case descriptions provided for all identified use cases. |
All Distinction requirements plus Fully correct UML syntax. Fully correct use of <<includes>> and <<extends>> relationships. Use cases consistent with needs and features as expressed in Vision Well-presented use case diagram. Short use case descriptions correctly spelled, with correct grammar. |
Domain Model
| Criteria | Fail (Bad) | Pass (OK) | Credit (Good) | Distinction (Very Good) | High Distinction (Excellent) |
| How well does the Domain Model address its intended purpose? |
Incorrect concept of domain object demonstrated. Domain model includes application concepts such as databases and user interfaces. Domain model largely incomplete. |
Correct concept of domain objects demonstrated. No application concepts such as databases or user interfaces present in domain model. Some critical or significant domain objects identified, many missing. Some relationships between domain object shown, many incorrect. |
All Pass requirements plus Most critical or significant domain objects identified, some missing. Relationships between domain objects generally correct. Generally correct UML syntax. |
All Credit requirements plus All critical and significant domain objects identified Correct concept of inheritance shown (if appropriate) |
All Distinction requirements plus Necessary but minor domain objects shown. Correct concept of aggregation/composition shown (if appropriate) Fully correct UML syntax. Well-presented domain class diagram. |
State Machine Diagram
| Criteria | Fail (Bad) | Pass (OK) | Credit (Good) | Distinction (Very Good) | High Distinction (Excellent) |
| How well does the State Machine Diagram address its intended purpose? |
Incorrect concept of states and transitions demonstrated. State machine largely incomplete. |
Generally correct concept of states and transitions demonstrated. |
All Pass requirements plus Generally correct representation of required states and transitions for selected domain object. |
All Credit requirements plus Fully correct representation of required states and transitions. States and transitions correctly labelled. |
All Distinction requirements plus Correct understanding of guard conditions demonstrated (if appropriate) Correct UML syntax. Well-presented state machine diagram. |
0 comments