Task-based System Modeling

CO7207 Generative Development

Tasks

Task 1: System Description [10 marks]

Firstly, you must choose a business that you will model. Please describe this business, list its stakeholders (e.g. customers, staff, etc), list the important information about the business entities (e.g. products and services), and informally describe the main use cases and activities of the business. Do Not write this as a list, it should be written in sentences and paragraphs.

Task 2: Behaviour Model [24 marks]

Part a) Use Case Diagram

Create a Use Case diagram for the system supporting your chosen business (as described in Task 1 above). [12 marks]

Part b) Activity Diagram

Create one activity diagram for the system supporting your chosen business (as described in Task 1 above). [12 marks]

Task 3: Structural Model [26 marks]

The following tasks will require the use of Eclipse and the Eclipse Modelling Framework. The previous lab sessions will help you with learning the necessary techniques.

Part a) Class Diagram

Using EMF, design a class diagram for the system of your chosen business. Use role names and multiplicities on all association ends. [17 marks]

Part b) OCL Invariants

Add three meaningful OCL class invariants to the Ecore model that follow your description in Task 1. Do this using the OCLinEcore editor (see here for details). The names of invariants must start with “inv1”, “inv2”, and “inv3” respectively. [9 marks]

Task 4: Instances [20 marks]

You will now continue your use of EMF, this time focusing on instances.

Part a) Instance of Ecore Model (Object Diagram)

Using EMF API (and not the editor), create an instance of the Ecore Model (in other words, an Object Diagram). This should have at least 5 objects and 5 links and should be saved into XMI format. [8 marks]

Part b) Instances of OCL Invariants

Using the Dynamic Instance Editor, create two instances per OCL invariant. One instance must satisfy the OCL invariant, while the other must violate the OCL invariant. All instances must be valid in the Class Diagram when ignoring the OCL invariants. [12 marks]

Get instant help from 5000+ experts for