1 / 16

Domain Model:

Domain Model:. Larman Chapter 9, Sections 16 and 17 Adding Attributes Prepared by: Sachin Verma. OBJECTIVES. Learn how to identify and specify attributes in a domain model Learn to distinguish attributes correctly. ATTRIBUTES.

jin-flowers
Download Presentation

Domain Model:

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Domain Model: Larman Chapter 9, Sections 16 and 17 Adding Attributes Prepared by: Sachin Verma

  2. OBJECTIVES • Learn how to identify and specify attributes in a domain model • Learn to distinguish attributes correctly

  3. ATTRIBUTES • After establishing classes based on the concepts of use case scenarios, the scenarios are examined to discover attributes • Attributes are logical data values of an object

  4. UML Attribute Notation

  5. Valid Attribute Types • Keep attributes simple • Distinguish between conceptual and implementation perspectives • Identify data types

  6. Relate with associations, not attributes

  7. Avoid Representing Complex Domain Concepts as Attributes

  8. Non Primitive Data Type Represent what may be considered a primitive data type (such as a number or string) as a non primitive class if: • It is composed of separate sections. phone number, name of person • There are operations usually associated with it, such as parsing or validation. social security number • It has other attributes promotional price could have a start date and end date

  9. Non Primitive Data Type • It has a quantity with a unit. payment amount has a unit of currency • It has abstraction of one or more types with some of these qualities. item identifier in the sales domain is a generalization of types such as Universal product code(UPC) or European Article Number(EAN)

  10. Non primitive data Types Applying these guidelines to the POS domain model yields the following analysis: • The item identifier is an abstraction of various common coding codes schemes, including UPC-A, UPC-E, and the family of EAN schemes. These numeric coding schemes have subparts identifying the manufacturer, product and EAN

  11. (continued) • The price and the amount attribute should be non primitive Quantity or Money classes because they are quantities in a unit of currency • The address attribute should be a non primitive Address class because it has separate sections

  12. If the attribute class is a data type, it may be shown in the attributebox

  13. No attributes as Foreign Key

  14. Modelling Attribute Quantites and Units

  15. Domain Model Conclusion • A relatively useful model has been created for the domain of the POS application. • A good domain model captures the essential abstractions and information required to understand the domain in context of current requirements, and aids people in understanding the domain – its concepts , terminology, and the relationships.

More Related