1. lecture 13-17, chitkara university

3.  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. lecture 13-17, chitkara university

5. The following features enable us to express time invariant static business rules for a domain:- o Domain classes – each domain class denotes a type of object. o 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. o 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. o Additional rules – complex rules that cannot be shown with symbology can be shown with attached notes. lecture 13-17, chitkara university

6. Perform the following in very short iterations: o Make a list of candidate domain classes. o Draw these classes in a UML class diagram. o If possible, add brief descriptions for the classes. o Identify any associations that are necessary. o Decide if some domain classes are really just attributes. o Where helpful, identify role names and multiplicity for associations. o Add any additional static rules as UML notes that cannot be conveyed with UML symbols. o Group diagrams/domain classes by category into packages. Concentrate more on just identifying domain classes in early iterations ! lecture 13-17, chitkara university

7. Three Strategies to Find Conceptual Classes? 1. Reuse or modify existing models. 2. Use a category list. 3. Identify noun phrases. lecture 13-17, chitkara university

8. We can create a domain model by making a list of candidate conceptual classes which contains many common categories with an emphasis on business information system needs. lecture 13-17, chitkara university

9. Case Study: Airline Reservation Domain Conceptual Class CategoryExamples product or service related to a transaction or transaction line item Item, Flight, Seat, Meal where is the transaction recorded?Register, Ledger, Flight Manifest roles of people or organizations related to the transaction; actors in the use case Cashier, Customer, Passenger, Airline place of transaction; place of serviceStore, Airport, Plane, Seat physical objectsItem, Register Board, Piece, Die Airplane descriptions of thingsProduct Description, Flight Description lecture 13-17, chitkara university

10. Another useful technique (because of its simplicity) suggested is linguistic analysis: Identify the nouns and noun phrases in textual descriptions of a domain, and consider them as candidate conceptual classes or attributes. lecture 13-17, chitkara university

11. Case Study: POS Domain 1. Customer arrives at a POS checkout with goods and/or service s to purchase. 2. Cashier starts a new sale. 3. Cashier enters item identifier. 4. System records sale line item and presents item description, price, and running total. Price calculated from a set of price rules. lecture 13-17, chitkara university

12. The domain model illustrates conceptual classes or vocabulary in the domain. Informally, a conceptual class is an idea, thing, or object. More formally, a conceptual class may be considered in terms of its symbol, intension, and extension 1. Symbol words or images representing a conceptual class. 2. Intension the definition of a conceptual class. 3. Extension the set of examples to which the conceptual class applies. lecture 13-17, chitkara university

14.  Case Study: POS Domain  From the category list and noun phrase analysis, a list is generated of candidate conceptual classes for the domain. On the basis of category list guidelines that emphasize business transactions and their relationship with other things. The list is constrained to the requirements which is under consideration for scenario of Process of Sale. lecture 13-17, chitkara university

15.  Sale  Cashier  CashPayment  Customer  SalesLineItem  Store  Item  ProductDescription  Register  ProductCatalog  Ledger lecture 13-17, chitkara university

17.  Some software systems are for domains that find very little analogy in natural or business domains; › software for telecommunications is an example.  It is still possible to create a domain model in these domains, but it requires a high degree of abstraction and stepping back from familiar designs.  For example, here are some candidate conceptual classes related to a telecommunication switch: › Message, Connection, Port, Dialog, Route, Protocol. lecture 13-17, chitkara university

18. The most common mistake when creating a domain model is to represent something as an attribute when it should have been a conceptual class.  Guideline If we do not think of some conceptual class X as a number or text in the real world, X is probably a conceptual class, not an attribute. lecture 13-17, chitkara university

19. In the real world, a store is not considered a number or text the term suggests a legal entity, an organization, and something that occupies space. Therefore, Store should be a conceptual class. As another example, consider the domain of airline reservations. Should destination be an attribute of Flight, or a separate conceptual class Airport? In the real world, a destination airport is not considered a number or text it is a massive thing that occupies space. Therefore, Airport should be a concept. lecture 13-17, chitkara university

20. A description class contains information that describes something else. For example, a ProductDescription that records the price, picture, and text description of an Item. lecture 13-17, chitkara university

21. 1. An Item instance represents a physical item in a store; as such, it may even have a serial number. 2. An Item has a description, price, and itemID, which are not recorded anywhere else. 3. Everyone working in the store has amnesia. 4. Every time a real physical item is sold, a corresponding software instance of Item is deleted from "software land." lecture 13-17, chitkara university

22. The * means a multiplicity of "many." It indicates that one Product Description may describe many (*) Items. lecture 13-17, chitkara university

24. Bounded by the current iteration requirements under design: 1. Find the conceptual classes (see a following guideline). 2. Draw them as classes in a UML class diagram. 3. Add associations and attributes.associationsattributes lecture 13-17, chitkara university

25. An attribute is a logical data value of an object. It is useful to identify those attributes of conceptual classes that are needed to satisfy the information requirements of the current scenarios under development. attribute lecture 13-17, chitkara university

26. A domain class sounds like an attribute if: - o It relies on an associated class for it’s identity – e.g. ‘order number’ class associated to an ‘order’ class. The ‘order number’ sounds suspiciously like an attribute of ‘order’. o It is a simple data type – e.g. ‘order number’ is a simple integer. Now it really sounds like an attribute! lecture 13-17, chitkara university

27.  An association is a relationship between classes (more precisely, instances of those classes) that indicates some meaningful and interesting connection. association lecture 13-17, chitkara university

30.  Multiplicity defines how many instances of a class A can be associated with one instance of a class B. Multiplicity on association lecture 13-17, chitkara university