Requirement Specification Domain Model

1. Requirement SpecificationDomain Model Domain Model Classes and Objects Association Structure

2. Information Need in the IT System • Information need are found by analysing the problem-domain for the IT system • Ask the question: What information should be registered by the IT system ? • The building blocks are objects • binds requirements, design and program together • Result: A model showing the problem-domain – we call it Domain Model • ” The most important model in OO analysis”

3. Objects binds requirements, design and programming together Implementation Writing the code public class Customer { private int id, private String name; private String address; public Customer(int id) { this.id = id; } public String getName() { return name; } ….. Test Requirement Functional Use case: find customer A sales person wants to find information about customer The sales person types the customers id The system returns information about the customer Non functional The system has to be user friendly Clarify information Customer: id, name, address Design Design of architecture Design of GUI Design of classes Design database Domain object of class Customer 3

4. Class, objects, attributes and values Customer is candidate Object of class ”Customer” for a class A class describes a collection of objects of the same attributes, structure, and behaviour pattern

5. Domain model • A domain model is the visual representation of conceptual classes • We illustrate it by drawing a UML class diagram: • Domain objects or conceptual classes • Associations between the objects • Each objects attributes • A conceptual class is described by: • name (symbol) • Definition – the purpose in problem domain (intension) • Examples given on objects created from class (extension)

6. Example of a conceptual class Customer • Class: • Definition: The customer class is used to describe the company's customers. • An example: • Hans Andersen, Eventyrvej 2, 5000 Odense, phone 75 45 67 89, e-mail: ha@eventyr.dk • …… • Attributes: Name, adress, phone, e-mail Customer Name Adress Phone E-mail

7. A Domain Model • The classes are connected - here by an association • drawn as the line between the concepts. Nameable of a verb phrase. Start with Capital • Add the multiplicity • defines how many instances(objects) of a class that can be associated with an instance (object) of another classEx: a student can be enrolled in none or 1 team • Result: A UML class diagram

8. Requirement specification . Try to create this one in UMLet

9. "Multiplicity" - Diversity or cardinality

10. Association • Relation between a number of objects. Association • A customer can have more orders at once – an order belongs to one customer only. • Drawn as a simple line like this: UML class UML Association with multiplicity

11. Generalisation • Used when there are some common attributes shared by several classes (it is implemented as inheritance)

12. Aggregation • Used when there is a stronger relation between two classes than association can express

13. Patterns • A pattern is defined as a generic solution to a problem often encountered in the real world • Not a theoretical solution • Based on empirical data and what works • When we construct a domain model then we will often use patterns • Next time we will look at several patterns