Software analysis pattern

Analysis pattern ( engl. pattern analysis ) describe practically proven and reusable templates for problem solving in an application domain. They form complex relationships in practice as models, and use the language of the domain experts. Analysis patterns are defined by the representation of the problem, its context and the solution.

Use

Analysis patterns provide the system analyst the possibility for standard components of business processes, such as Role Object or party, the domain experts to provide an already proven in practice modeling. This allows the systems analyst respond faster together with the domain experts on the specific problems in your specific application domain and the process of requirements analysis is accelerated.

Analysis pattern by Martin Fowler

The following analysis patterns were published by Martin Fowler. They are based on his experience of the discussions with the respective domain experts (eg, doctor or accountant ).

  • Party
  • Organization Hierachy
  • Organization Structure
  • Accountability
  • Accountability Knowledge Level
  • Party Type generalization
  • Hierarchic Accountability
  • Operating Scope
  • Post
  • Quantity ( Quantity)
  • Conversion ratio
  • Compound Unit
  • Measurement
  • Surveillance
  • Protocol
  • Dual Time Record
  • Rejected Observation
  • Active Observation, Hypothesis, and Projection
  • Associated Observation
  • Process of Observation
  • Event sourcing
  • Enterprise segment
  • Measurement Protocol
  • Range
  • Name
  • Identification Scheme
  • Object Merge
  • Object Equivalence
  • 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
  • Proposend and Implemented Action
  • Completed and Abandoned Actions
  • Suspension
  • Plan
  • Protocol
  • Resource Allocation
  • Outcome or Start Function
  • Contract
  • Portfolio
  • Rate
  • Scenario
  • Forward Contract
  • Options
  • Product
  • Subtype State Machine
  • Parallel Application and Domain Hierarchy
  • Multiple Access Levels to a Package
  • Mutual Visibility
  • Subtyping Packages
  • Accounting Entry
  • Accounting Transaction
  • Application Facade (Application Facade )
  • Event
  • Fixed Property
  • Flexible Dynamic Property
  • Knowledge level
  • Posting Rule
  • Role Object
  • Typed Relationship
  • Money

Analysis by Peter Coad pattern

  • Item Item Description

Analysis of patterns of heath Balzert

  • Coordinator
59958
de