Analysis Patterns-Patterns in Software Engineering-Lecture 18 Slides-Computer Engineering, Slides of Software Engineering

Download Analysis Patterns-Patterns in Software Engineering-Lecture 18 Slides-Computer Engineering and more Slides Software Engineering in PDF only on Docsity! Patterns in Software Engineering Lecturer: Raman Ramsin Lecture 18 Analysis Patterns Part 1 Department of Computer Engineering 1 Sharif University of Technology Patterns in Software Engineering – Lecture 18 Analysis Patterns First introduced by Fowler in 1997. “Analysis patterns are groups of concepts that represent a common construction in business modeling.“ An analysis pattern may be relevant to only one domain or it may span , many domains. Department of Computer Engineering 2 Sharif University of Technology Patterns in Software Engineering – Lecture 18 Analysis Patterns: Accountability - Party Problem: People and organizational units have similar responsibilities. Solution: Create a type party as a supertype of person and organization. Department of Computer Engineering 5 Sharif University of Technology Patterns in Software Engineering – Lecture 18 Analysis Patterns: Accountability - Party Department of Computer Engineering 6 Sharif University of Technology Patterns in Software Engineering – Lecture 18 Analysis Patterns: Accountability - Accountability Problem: Representing organization structures employment , , management, professional registration, and contracts with a similar structure. Solution: Create accountability as a directed relationship between two parties. Give it an accountability type to represent the kind of relationship. Department of Computer Engineering 7 Sharif University of Technology Patterns in Software Engineering – Lecture 18 Analysis Patterns: Observations and Measurements - Quantity Department of Computer Engineering 10 Sharif University of Technology Patterns in Software Engineering – Lecture 18 Analysis Patterns: Observations and Measurements - Measurement Problem: An object has a large number of quantity attributes . Recording information about an individual measurement of an attribute. Tracking changes in a value to an attribute over time. Solution: Create an object to represent the individual measurement. This is linked to the object being measured and to a phenomenon type that describes the kind of measurement being made. Department of Computer Engineering 11 Sharif University of Technology Patterns in Software Engineering – Lecture 18 Analysis Patterns: Observations and Measurements - Measurement Department of Computer Engineering 12 Sharif University of Technology Patterns in Software Engineering – Lecture 18 Analysis Patterns: Referring to Objects - Identification Scheme Problem: Ensuring an identification refers to only one object but different parties can refer to the object differently. Solution: Create identification schemes that contain identifiers, where each identifier refers to only one unit . A party can use any identification scheme. Department of Computer Engineering 15 Sharif University of Technology Patterns in Software Engineering – Lecture 18 Analysis Patterns: Referring to Objects - Identification Scheme Department of Computer Engineering 16 Sharif University of Technology Patterns in Software Engineering – Lecture 18 Analysis Patterns: Inventory and Accounting - Account Problem: Recording a history of changes to some quantity. Solution: Create an account. Each change is recorded as an entry against the account. The balance of the account gives its current value. Department of Computer Engineering 17 Sharif University of Technology Patterns in Software Engineering – Lecture 18 Analysis Patterns: Inventory and Accounting - Transaction Department of Computer Engineering 20 Sharif University of Technology Patterns in Software Engineering – Lecture 18 Analysis Patterns: Planning - Proposed and Implemented Action P bl R ti b th h t i t d d t d d h tro em: epresen ng o w a you n en e o o an w a you did. Solution: Use separate objects for the proposed and implemented actions . Department of Computer Engineering 21 Sharif University of Technology Patterns in Software Engineering – Lecture 18 Analysis Patterns: Planning - Proposed and Implemented Action Department of Computer Engineering 22 Sharif University of Technology Patterns in Software Engineering – Lecture 18 Analysis Patterns: Trading - Contract Problem: Recording deals from the perspective of both the buyer and the seller. Solution: Use a contractor with both buying and selling parties. Department of Computer Engineering 25 Sharif University of Technology Patterns in Software Engineering – Lecture 18 Analysis Patterns: Trading - Contract Department of Computer Engineering 26 Sharif University of Technology Patterns in Software Engineering – Lecture 18 R fe erence Fowler, M., Analysis Patterns: Reusable Object Models, Addison- Wesley, 1997. Department of Computer Engineering 27 Sharif University of Technology