Domain modelling.pptVIP

What is a domain model? “A domain model captures the most important types of objects in the context of the business. The domain model represents the ‘things’ that exist or events that transpire in the business environment.” – I. Jacobsen Why do a domain model? Gives a conceptual framework of the things in the problem space Helps you think – focus on semantics Provides a glossary of terms – noun based It is a static view - meaning it allows us convey time invariant business rules Foundation for use case/workflow modelling Based on the defined structure, we can describe the state of the problem domain at any time. Simple domain model Features of a domain model The following features enable us to express time invariant static business rules for a domain:- Domain classes – each domain class denotes a type of object. ? Attributes – an attribute is the description of a named slot of a specified type in a domain class; each instance of the class separately holds a value. ? Associations – an association is a relationship between two (or more) domain classes that describes links between their object instances. Associations can have roles, describing the multiplicity and participation of a class in the relationship. Additional rules – complex rules that cannot be shown with symbology can be shown with attached notes. Domain classes? Each domain class denotes a type of object. It is a descriptor for a set of things that share common features. Classes can be:- Business objects - represent things that are manipulated in the business e.g. Order. Real world objects – things that the business keeps track of e.g. Contact, Site. Events that transpire - e.g. sale and payment. A domain class has attributes and associations with other classes (discussed below). It is important that a domain class is given a good description How do I make a domain model? Perform the following in very short iterations: Make a list of candidate domain classes. Draw these classes in a UML class diagr