Software analysis patterns or analysis patterns in software engineering 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."[1]
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". An example:
Figure 1: Event analysis pattern
Martin Fowler describes this pattern as one that "captures the memory of something interesting which affects the domain".[3]
Describing an analysis patternedit
While doing Analysis we are trying to understand the problem. Fowler does not detail in his book[2] 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 Erich Gamma, Frank Buschmann and Christopher Alexander on patterns (in architecture or computer science). One of them, proposed by Hahsler,[4] 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"[5]
Forces and context: "Discussion of forces and tensions which should be resolved by the analysis pattern"[6]
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."[4]
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.
^Purao, Sandeep; Storey, Veda C.; Han, Taedong (September 2003). (PDF). Information Systems Research. 14 (3): 169–290. ISSN 1526-5536. Archived from the original (PDF) on 2006-09-08. Retrieved 2007-01-31.
^ abFowler, Martin (1996-11-27). Analysis Patterns: Reusable Object Models. Addison-Wesley. ISBN0-201-89542-0. A pattern is an idea that has been useful in one practical context and will probably be useful in others.
^Alexander, Christopher (1979). The Timeless Way of Building, volume 1 of Center for Environmental Structure Series. New York: Oxford University Press. ISBN0-19-502402-8.
Further readingedit
Haitham, Hamza & Fayad, Mohamed E. (2002). A Pattern Language for Building Stable Analysis Patterns(PDF). 9th Conference on Pattern Languages of Programs. Computer Science and Engineering Dept., University of Nebraska-Lincoln. Retrieved 2007-01-31. This paper on pattern language for analysis pattern was presented at PLoP 2002.
Buschmann, Frank; Regine Meunier; Hans Rohnert; Peter Sommerlad; Michael Stal (1996). Pattern-oriented Software Architecture, Volume 1: A System of Patterns. John Wiley & Sons. ISBN0-471-95869-7.
January 01, 1970
software, analysis, pattern, analysis, patterns, software, engineering, conceptual, models, which, capture, abstraction, situation, that, often, encountered, modelling, analysis, pattern, represented, group, related, generic, objects, meta, classes, with, ster. Software analysis patterns or analysis patterns in software engineering 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 1 Contents 1 Overview 2 Describing an analysis pattern 3 See also 4 References 5 Further readingOverview editMartin 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 An example nbsp Figure 1 Event analysis pattern Martin Fowler describes this pattern as one that captures the memory of something interesting which affects the domain 3 Describing an analysis pattern editWhile doing Analysis we are trying to understand the problem Fowler does not detail in his book 2 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 Erich Gamma Frank Buschmann and Christopher Alexander on patterns in architecture or computer science One of them proposed by Hahsler 4 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 5 Forces and context Discussion of forces and tensions which should be resolved by the analysis pattern 6 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 4 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 editDesign pattern computer science Object oriented analysis and design Problem frames approach is another approach to software requirements analysis Role class model an example of analysis pattern applied to the role concept Requirements analysisReferences edit Purao Sandeep Storey Veda C Han Taedong September 2003 Improving Analysis Pattern Reuse PDF Information Systems Research 14 3 169 290 ISSN 1526 5536 Archived from the original PDF on 2006 09 08 Retrieved 2007 01 31 a b Fowler Martin 1996 11 27 Analysis Patterns Reusable Object Models Addison Wesley ISBN 0 201 89542 0 A pattern is an idea that has been useful in one practical context and will probably be useful in others Fowler Martin Accounting Patterns PDF Analysis Pattern Retrieved 2007 01 31 a b Hahsler Michael Geyer Schulz Andreas November 2001 Software Engineering with Analysis Patterns CiteSeerX 10 1 1 70 8415 Retrieved August 26 2023 Gamma Erich Richard Helm Ralph Johnson John Vlissides 1995 Design Patterns Elements of Reusable Object Oriented Software hardcover 395 pages Addison Wesley ISBN 0 201 63361 2 Alexander Christopher 1979 The Timeless Way of Building volume 1 of Center for Environmental Structure Series New York Oxford University Press ISBN 0 19 502402 8 Further reading editHaitham Hamza amp Fayad Mohamed E 2002 A Pattern Language for Building Stable Analysis Patterns PDF 9th Conference on Pattern Languages of Programs Computer Science and Engineering Dept University of Nebraska Lincoln Retrieved 2007 01 31 This paper on pattern language for analysis pattern was presented at PLoP 2002 Buschmann Frank Regine Meunier Hans Rohnert Peter Sommerlad Michael Stal 1996 Pattern oriented Software Architecture Volume 1 A System of Patterns John Wiley amp Sons ISBN 0 471 95869 7 Retrieved from https en wikipedia org w index php title Software analysis pattern amp oldid 1172393335, wikipedia, wiki, book, books, library,
