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

Part^1 Sharif University of Technology

Patterns in Software Engineering – Lecture 18 Analysis PatternsAnalysis

Patterns

„^ First introduced by Fowler in 1997. „^ “Analysis patterns are groups of concepts that represent a„^ Analysis patterns are groups of concepts that represent acommon construction in business modeling.“^ ^

An analysis pattern may be relevant to only one domain

or it may span

^ An analysis pattern may be relevant to only one domain, or it may spanmany domains. Department of Computer Engineering

2

Sharif University of Technology

Patterns in Software Engineering – Lecture 18 Supporting PatternsSupporting

Patterns

„^ Fowler also provides several supporting patterns, which

p^

pp^

g p^

describe how to take analysis patterns and apply them:^ ^ Layered Architecture for Information Systems ^ Layered

Architecture for Information Systems

^ Patterns for Type Model Design Templates ^ Association Patterns Department of Computer Engineering

4

Sharif University of Technology

Patterns in Software Engineering – Lecture 18 Analysis Patterns: Accountability

-^ Party

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

-^ Accountability

Analysis Patterns: Accountability

Accountability

„^ Problem:

Representing organization structures

employment

„^ Problem:

Representing

organization structures, employment,

management, professional registration, and contracts with asimilar structure. „ Solution:

Create accountability as a directed relationship „^ Solution:

Create

accountability as a directed relationship

between two parties.^ ^ Give it an accountability type to represent the kind of relationship.

y^ yp^

p^

p

Department of Computer Engineering

7

Sharif University of Technology

Patterns in Software Engineering – Lecture 18 Analysis Patterns: Accountability

-^ Accountability

Analysis Patterns: Accountability

Accountability

Department of Computer Engineering

8

Sharif University of Technology

Patterns in Software Engineering – Lecture 18 Analysis Patterns:

Observations and Measurements

-^ Quantity

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

Analysis Patterns:

Observations and Measurements

Measurement

„^ Problem:^ ^

An object has a large number of

quantity attributes

^ 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

Solution:

Create

an object to represent the individual

measurement.^ ^ This is linked to the object being measured and to a phenomenon typethat 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

-^ Observation

Analysis Patterns:

Observations and Measurements

Observation

„^ Problem:

Attributes are qualitative and thus

cannot be

„^ Problem:

Attributes

are qualitative and thus cannot be

measured with numbers. „ Solution:

Create an observation type that links the object to a phenomenonphenomenon.^ ^ Each phenomenon is a value for some phenomenon type.Department of Computer Engineering

13

Sharif University of Technology

Patterns in Software Engineering – Lecture 18 Analysis Patterns:

Observations and Measurements

-^ Observation

Analysis Patterns:

Observations and Measurements

Observation

Department of Computer Engineering

14

Sharif University of Technology

Patterns in Software Engineering – Lecture 18 Analysis Patterns:

Referring to Objects -

Identification Scheme

y^

g^

j

Department of Computer Engineering

16

Sharif University of Technology

Patterns in Software Engineering – Lecture 18 Analysis Patterns:

Inventory and Accounting -

Account

y^

y^

g

„^ 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

y^

y^

g

„^ Problem:

Ensuring that nothing gets lost from an account. „^ Solution:

Use transactions to transfer items between accounts. Department of Computer Engineering

19

Sharif University of Technology

Patterns in Software Engineering – Lecture 18 Analysis Patterns:

Inventory and Accounting -

Transaction

y^

y^

g

Department of Computer Engineering

20

Sharif University of Technology