1. Analysis Pattern Dr. Zhen Jiang West Chester University E-mail: zjiang@wcupa.edu url: www.cs.wcupa.edu/~zjiang

2. Outline Introduction Accountability Observations and Measurements Inventory and Accounting Planning Trading

3. Introduction A Pattern is an idea that has been useful in one practical context and will probably be useful in others Analysis patterns are group of concepts that represent a common construction in business modeling. It may be relevant to only one domain, or it may span many domains.

4. Accountability Party Organization Accountability Operating scopes

5. Party Person E-mail Address Telephone Number Company 0..1 Address Book 0..*

6. Party Party E-mail Address Telephone Number 0..1 0..* Person Organization 0..*

7. Organization Region Sales Office Division 0..* Operating Unit 0..*

8. Organization Region Sales Office Division Operating Unit Organization parent sub no parentOU is parentR is parentD is parent

9. Organization Region Sales Office Division Operating Unit Organization parent sub Structure Time Period Type Rule 0..*

10. Principle 1 Design a model so that the most frequent modification of the model causes changes to the least number of types

11. Accountability PersonOrganization Party commissioner responsible Accountability Time Period Type 0..*

12. Accountability Using a party allows accountability to cover a wide range of inter-party responsibilities, including management, employment, and contracts.

13. Principle 2 Whenever defining features for a type that has a super-type, consider whether placing the features on the super-type makes sense.

14. Operating Scopes Clinical Care Scope Operating Scope Accountability Location 0..*1..* Protocol Scope Resource Scope Sales Territory Product Type Observation Concept Protocol Resource Type

15. Measurements allow us to record quantitative information. Observation extends this pattern to deal with qualitative information. It is also often essential to record the protocol for an observation. Observations and Measurements

16. This model is useful if a large number of possible measurements would make person too complex. Measurement Measurement Type Person Quantity John Smith is 6 feet tall, which can be represented by a measurement whose person is John Smith, type is height, and quantity is 6 feet 11 1

17. This model supports qualitative measurements. For example, ( tall, average, short) and (A,B, AB, O) Observation Observation Type Person Quantity 1 1 Measurement Category Observation 1 Category 1

18. This model represents the context used to identify an object Extensions Identifier Scheme Object String 11 1

19. Extensions Measurement Type Person Quantity

20. Extensions Observation Type Person Quantity Measurement Category 1..*1

21. Inventory and Accounting Entry Amount: Quantity Transaction 0..* Account 21 1 Sum(entries.amount=0) Transactions

22. Inventory and Accounting Transaction Timepoint 0..* Account 1 1 Quantity 0..* 11 amount 0..* 1 withdrawals deposit from to balance

23. Inventory and Accounting Entry Transaction 0..* Account balance:Quantity 1 12 entries Summary Account Detailed 1 0..* A summary account can be composed of both summary and detailed account. The entries of a summary account are derived from the components’ entries in a recursive manner. components

24. Inventory and Accounting Entry Transaction 0..* Account balance:Quantity 1 12 entries Summary Account Detailed

25. Inventory and Accounting Entry amount: Quantity Transaction Account balance:Quantity 12 Holding Inventory Entry 1 Location 0..* Item Type 0..* 11 1 Transfer Sum (entries.amount)=0

26. Inventory and Accounting Inventory Entry amount: Quantity Transaction 1from 1 Location 0..* Item Type Transfer Sum (entries.amount)=0 Account balance:Quantity Summary Account Detailed Holding to1

27. Properties of actions Planning Action Location Time Party 1 1

28. Separate objects record the proposal and the implementation so that differences can be tracked. Planning Proposed Action Status Implemented Action 11 0..*

29. Completed and abandoned Actions Planning Proposed Action Abandoned Action Implemented Action 11 Status

30. Suspension Planning Proposed Action Abandoned Action Implemented Action 11 Status Suspension 0..* Time 0..* 1 1

31. Planning Plan Dependency Action Reference Plan Proposed Action 0..*1 The combination of plan and proposed action is unique dependent consequent 11 10..* dependent and consequent are in the same plan

32. Planning Plan Dependency Plan Proposed Action 0..*1 dependent consequent

33. Planning Plan Dependency Protocol Reference Software Protocol dependent consequent 11 10..* Protocol referred protocol 10..* components step

34. Planning Protocol Reference Software Protocol dependent consequent 11 referred protocol 10..* Compound Protocol Step

35. Contract Party Long Contract amount: Number price: Money 1 1 counterparty 0..* Short Instrument 1 primaryparty 0..*