Semantic Analysis Patterns

  • Eduardo B. Fernandez
  • Xiaohong Yuan
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 1920)


The development of object-oriented software starts from requirements expressed commonly as Use Cases. The requirements are then converted into a conceptual or analysis model. Analysis is a fundamental stage because the conceptual model can be shown to satisfy the requirements and becomes the skeleton on which the complete system is built. Most of the use of software patterns until now has been at the design stage and they are applied to provide extensibility and flexibility. However, design patterns don’t help avoid analysis errors or make analysis easier. Analysis patterns can contribute more to reusability and software quality than the other varieties. Also, their use contributes to simplifying the development of the analysis model. In particular, a new type of analysis pattern is proposed, called a Semantic Analysis Pattern (SAP), which is in essence a miniapplication, realizing a few Use Cases or a small set of requirements. Using SAPs, a methodology is developed to build the conceptual model in a systematic way.


Analysis Pattern Design Pattern Class Diagram Sequence Diagram Pattern Language 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Arsanjani, A.: Service provider: A domain pattern and its business framework implementation, Procs. of PloP’99.
  2. 2.
    Booch, G., Rumbaugh, J., Jacobson, I.: The Unified Modeling Language User Guide, Addison-Wesley 1998.Google Scholar
  3. 3.
    Braga, R.T.V., Germano, F.S.R., Masiero, P.C.: A confederation of patterns for resource management, Procs. of PLoP’98,
  4. 4.
    Braga, R.T.V., Germano, F.S.R., Masiero, P.C.: A pattern language for business resource management, Procs. of PloP’99,
  5. 5.
    Coad, P.: Object models — Strategies, patterns, and applications (2nd. Edition), Prentice-Hall 1997Google Scholar
  6. 6.
    Fernandez, E. B.: Good analysis as the basis for good design and implementation, Report TR-CSE-97-45, Dept. of Computer Science and Eng., Florida Atlantic University, September 1997. Presented at OOPSLA’97Google Scholar
  7. 7.
    Fernandez, E.B., Hawkins, J.: Determining role rights from use cases, Procs. 2 nd ACM Workshop on Role-Based Access Control, 1997, 121–125Google Scholar
  8. 8.
    Fernandez, E.B.:Building systems using analysis patterns, Procs. 3 rd Int. Soft. Architecture Workshop (ISAW3), Orlando, FL, November 1998, 37–40Google Scholar
  9. 9.
    Fernandez, E.B, Yuan, X.: An analysis pattern for reservation and use of entities, Procs.of PLoP99,
  10. 10.
    Fernandez, E. B.: Stock manager: An analysis pattern for inventories, to appear in Procs. of PLoP 2000.Google Scholar
  11. 11.
    Fernandez, E. B., Yuan, X., Brey, S.: Analysis Patterns for the Order and Shipment of a Product, to appear in Procs. of PLoP 2000.Google Scholar
  12. 12.
    Fowler, M.: Analysis patterns — Reusable object models, Addison-Wesley, 1997Google Scholar
  13. 13.
    Gamma, E., Helm, R., Johnson, R. and Vlissides, J.: Design patterns — Elements of reusable object-oriented software, Addison-Wesley 1995Google Scholar
  14. 14.
    Gamma, E., Beck, K.: JUnit: A cook’s tour, Java Report, May 1999, 27–38Google Scholar
  15. 15.
    Hay, D.: Data model patterns— Conventions of thought, Dorset House Publ., 1996Google Scholar
  16. 16.
    Hays, V., Loutrel, M., Fernandez, E.B.: The Object Filter and Access Control Framework, to appear in Procs. of PLoP 2000 Google Scholar
  17. 17.
    Jacobson, I., Booch, G., Rumbaugh, J.: The Unified Software Development Process, Addison-Wesley 1999Google Scholar
  18. 18.
    Johnson, R., Woolf, B.: Type Object, Chapter 4 in Pattern Languages of Program Design 3, Addison-Wesley, 1998Google Scholar
  19. 20.
    McGregor, J. D.: Validating domain models, JOOP, July-August 1999, 12–17Google Scholar
  20. 21.
    Mellor, S.J.: Graphical analysis patterns, Procs. Software Development West98, February 1998.
  21. 22.
  22. 23.
    Purao, S. and Storey, V.: A methodology for building a repository of object-oriented design fragments. Procs. of 18th International Conference on Conceptual Modeling (ER’99), 203–217.Google Scholar
  23. 24.
    Rechtin, E.: The synthesis of complex systems, IEEE Spectrum, July 1997, 51–55Google Scholar
  24. 25.
    Riehle, D.: Composite design patterns, Procs. of OOPSLA’97, 218–228.Google Scholar
  25. 26.
    Wanner, J., Kloppe, A.: The OCL: Precise modeling with UML, Addison-Wesley 1998Google Scholar
  26. 27.
    Yoder, J. and Johnson, R.: Inventory and Accounting patterns,
  27. 28.
    Yoder, J., Balaguer, F.: Using metadata and active object-models to implement Fowler’s analysis Patterns, Tutorial Notes, OOPSLA’99Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2000

Authors and Affiliations

  • Eduardo B. Fernandez
    • 1
  • Xiaohong Yuan
    • 1
  1. 1.Department of Computer Science and EngineeringFlorida Atlantic UniversityBoca Raton

Personalised recommendations