tailieunhanh - Lecture Enterprise systems development (CSC447) - Lecture 10

The objective of this chapter is to introduce some tools for documenting the task level detail of business processes. The task level in REA modeling is the level at which workflow is documented. | Lecture 10 Enterprise Systems Development ( CSC447) COMSATS Islamabad Muhammad Usman, Assistant Professor College of Statistical and Acturial Science NextGen POS partial domain model. Attributes Attributes A logical data value of an object that needs to be remembered Some attributes are derived from other attributes The usual ‘primitive’ data types Numbers, characters, Booleans Common compound data types Date, time (or dateTime), address, SSN, phoneNumber, bar codes, etc. May become full class objects in design Attributes Include attributes that the requirements (for example, use cases) suggest or imply a need to remember information. Sale needs a dateTime attribute. Store needs a name and address. Cashier needs an ID. Applying UML: Attribute Notation Applying UML: Attribute Notation Showing visibility on domain model is probably overkill. We’ll talk about visibility later in the course. Applying UML: Derived Attribute The total attribute in the Sale can be calculated or derived from the information in the SalesLineItems. Data Types Relate with associations, not attributes. Don’t use an attribute in lieu of an association Attributes Two Ways to Indicate a Data Type Property of an Object Do Not Use Attributes as Foreign Keys Modeling Quantities NextGen POS Partial Domain Model Requirements Document for the Banking System Requirements Document The requirements document is a formal document used to communicate the requirements to customers, engineers and managers It is also known as software requirements specifications or SRS Requirements Document The services and functions which the system should provide The constraints under which the system must operate Overall properties of the system ., constraints on the system’s emergent properties Today’s Topics In this lecture, we’ll discuss the requirements document of the Banking system that we have been talking about in this course Let’s develop a . | Lecture 10 Enterprise Systems Development ( CSC447) COMSATS Islamabad Muhammad Usman, Assistant Professor College of Statistical and Acturial Science NextGen POS partial domain model. Attributes Attributes A logical data value of an object that needs to be remembered Some attributes are derived from other attributes The usual ‘primitive’ data types Numbers, characters, Booleans Common compound data types Date, time (or dateTime), address, SSN, phoneNumber, bar codes, etc. May become full class objects in design Attributes Include attributes that the requirements (for example, use cases) suggest or imply a need to remember information. Sale needs a dateTime attribute. Store needs a name and address. Cashier needs an ID. Applying UML: Attribute Notation Applying UML: Attribute Notation Showing visibility on domain model is probably overkill. We’ll talk about visibility later in the course. Applying UML: Derived Attribute The total attribute in the Sale can be .