Analysis pattern

Analysis patterns ( English analysis pattern ) describe practically proven and reusable templates to solve problems in an application domain . They model complex relationships from practice and use the language of the domain expert. Analysis patterns are defined by the presentation of the problem , the context and the solution .

use

Analysis patterns offer the system analyst the opportunity for standard components of business processes , such as Role Object or Party , to present the domain expert with a model that has already proven itself in practice . This enables the system analyst, together with the domain expert, to deal more quickly with the specific problems in the specific application domain and the process of the requirements analysis is accelerated.

Analysis sample from Martin Fowler

The following analysis samples were published by Martin Fowler. They are based on his experience from discussions with the respective domain experts (e.g. doctor or accountant).

Accountability

• party
• Organization hierarchy
• Organization Structure
• Accountability
• Accountability Knowledge Level
• Party type generalization
• Hierarchic accountability
• Operating scope
• post Office

Observations and Measurements

• Quantity ( Quantity )
• Conversion ratio
• Compound unit
• Measurement
• Observation
• Protocol
• Dual time record
• Rejected observation
• Active Observation, Hypothesis, and Projection
• Associated Observation
• Process of observation
• Event sourcing

Observations for Corporate Finance

• Enterprise segment
• Measurement Protocol
• Range

Referring to Objects

• Surname
• Identification Scheme
• Object merge
• Object equivalence

Inventory and Accounting

• Account
• Transaction
• Summary account
• Memo account
• Posting rule
• Individual Instance Method
• Posting rule execution
• Posting Rules for Many Accounts
• Balance Sheet and Income Statement
• Corresponding Account
• Specialized Account Model
• Booking Entries to Multiple Accounts

Planning

• Proposend and Implemented Action
• Completed and Abandoned Actions
• suspension
• plan
• Protocol
• Resource allocation
• Outcome or start function

Trading

• Contract
• Portfolio
• Quota
• Scenario

Derivative contracts

• Forward Contract
• Options
• Product
• State machine subtype
• Parallel Application and Domain Hierarchy

Trading Packages

• Multiple Access Levels to a Package
• Mutual Visibility
• Subtyping packages

Further

• Accounting Entry
• Accounting transaction
• Application Facade ( Application Facade )
• Event
• Fixed property
• Flexible dynamic property
• Knowledge level
• Posting rule
• Role Object
• Typed Relationship
• Money

Analysis sample from Peter Coad

• Item-Item Description

Analysis sample from Heide Balzert

• coordinator

See also

• Requirements analysis

literature

• Martin Fowler : Analysis Patterns: Reusable Object Models . Addison-Wesley, 1996, ISBN 0-201-89542-0 (English).
• Peter Coad : Object Models: Strategies, Patterns, and Applications . Prentice Hall, 1996, ISBN 0-13-840117-9 (English).

Web links

• Martin Fowler : Analysis Patterns. Retrieved on April 9, 2013 (English, articles on Martin Fowler's homepage, which are marked as analysis samples). 

swell

1. ↑ ^{a b c d e f g h i j k l m n o p q r s t u v w x y z aa ab ac ad ae af ag ah ai aj ak al am an ao ap aq ar as at au av aw ax ay az ba bb bc bd be bf} Martin Fowler: Analysis Patterns: Reusable Object Models . Addison-Wesley, 1996, ISBN 0-201-89542-0 (English).
2. ↑ Martin Fowler: Event Sourcing. December 12, 2005, accessed July 13, 2014 . 
3. ↑ ^{a b c d e f g h i j} Martin Fowler : Analysis Patterns. Retrieved on April 9, 2013 (English, articles on Martin Fowler's homepage, which are marked as analysis samples).  
4. ^ Martin Fowler: Patterns of Enterprise Application Architecture . Addison-Wesley-Longman, Amsterdam 2002, ISBN 0-321-12742-0 .