Software Analysis Pattern Article Index for
Software 		Website Links For
Software 		 

Information About

Software Analysis Pattern
  CATEGORIES ABOUT SOFTWARE ANALYSIS PATTERN
   
software analysis patterns
   
software engineering
   
software architecture
   
software development
   
unified modeling language
   
APPAREL
BABY
BEAUTY
BOOKS
CAR TOYS
CELL PHONES
DVD'S
ELECTRONICS
GOURMET FOOD
GROCERIES
HEALTH & PERSONAL
HOME & GARDEN
JEWELRY
MUSIC
MUSIC INSTRUMENTS
OFFICE PRODUCTS
SOFTWARE
SPORTING GOODS
TOOLS & HARDWARE
TOYS
VIDEO GAMES
SHOPPING HOME
MORE SHOPPING...



Software analysis patterns or simply analysis patterns are Conceptual Models , which capture an abstraction of a situation that can often be encountered in Modelling . An analysis pattern can be represented as "a group of related, generic objects ( Meta-classes ) with stereotypical attributes (data definitions), behaviors (method signatures), and expected interactions defined in a domain-neutral manner" say Purao, Storey and Han1.

Martin Fowler defines a pattern as an "idea that has been useful in one practical context and will probably be useful in others"2. He further on explains the analysis pattern, which is a pattern "that reflects conceptual structures of Business Processes rather than actual software implementations".


HISTORY

''Section to be completed''


USAGE AND RATIONALE

''Section to be completed''


DESCRIBING AN ANALYSIS PATTERN

Fowler does not detail in his book a formal way to write or to describe analysis patterns. Suggestions have been raised since to have a consistent and uniform format for describing them. Most of them are based on the work from Gamma , Buschmann and Alexander on patterns (in architecture or computer science). One of them, proposed by Hahsler3, has the following structure:
  • Pattern name: a pattern name should really reflect the meaning of what it is abstracting. It should be simple so that one can refer to it during analysis.

  • Intent: the intent aims to describe the goal the pattern is trying to achieve. It should also describe the problem it tries to solve.

  • Motivation: "A scenario that illustrates the problem and how the analysis pattern contributes to the solution in the concrete scenario"4

  • Forces and context: "Discussion of forces and tensions which should be resolved by the analysis pattern"5

  • Solution: "Description of solution and of the balance of forces achieved by the analysis pattern in the scenario in the motivation section. Includes all relevant structural and behavioural aspects of the analysis pattern."

  • Consequences: this should emphasise how the goal is achieved by the analysis pattern with its limitation.

  • Design: Suggestions of design implementations of this pattern.

  • Known uses: Real world examples of this pattern usage.



See Also: Design pattern (computer science)#Documentation
l1=Describing a design pattern




CRITICISM

''Section to be completed''


EXAMPLES


Event



Martin Fowler describes this pattern as one that "captures the memory of something interesting which affects the domain"6.


SEE ALSO



REFERENCES



FURTHER READING