Reference no: EM13336238

Task

This assignment revolves around the Case Study, which may be found as a separate PDF document in the Resources/Assignment 1 section of the subject Interact site.

The objective of the assignment is to apply and consolidate skills acquired in the requirement and analysis disciplines through analysis of a simple case study, and to express the results through the relevant UML diagrams.

Part A - Vision 

1. Analyse the Case Study documents and produce a Vision document for a software system to meet the needs identified in the Case Study. Make sure your Vision document:

a) Identifies the business case for development of the proposed system, identifying both the problem it is intended to solve, and the benefits to be expected from solving it.
b) Identifies all the stakeholders relevant to the system and their interest in it.
c) Identifies the key features of the proposed system
d) Clearly identifies the scope of the system
e) Identifies key considerations and constraints which affect the technical solution to be developed.

Use the Vision template provided in the Resources section for Assignment 1. 

Part B - High Level Functional Requirements 

2. Analyse the Case Study documents and produce an initial high level functional requirements specification. Document these requirements with:

i. A use case diagram for the functional requirements of the entire system. 
ii. Short use case descriptions for all use cases. 

Part C - Detailed Functional Requirements 

3. Detail the functional requirements for the system's critical core use case. Document these requirements with:

i. A full use case description for the critical core use case. 

ii. An activity diagram that shows the normal and major alternate flows for the critical core use case. 

iii. A system sequence diagram showing the user's inputs and system's responses for the critical core use case's normal flow. 

iv. An operation specification for the most important single interaction between user and system during the critical core use case's normal flow. 

Part D - Object Modelling 

4. Develop a domain model for the Case Study. Document your model with:

i. A domain class diagram showing inheritance and compositional relationships 

5. Analyse the behaviour of the most important stateful object of the system and document this behaviour with:

ii. A state diagram