Advertisement

Use of Patterns in Formal Development: Systematic Transition from Problems to Architectural Designs

  • Christine Choppy
  • Maritta Heisel
Part of the Lecture Notes in Computer Science book series (LNCS, volume 2755)

Abstract

We present a pattern-based software lifecycle and a method that supports the systematic execution of that lifecycle. First, problem frames are used to develop a formal specification of the problem to be solved. In a second phase, architectural styles are used to construct an architectural specification of the software system to be developed. That specification forms the basis for fine-grained design and implementation.

Keywords

Virtual Machine Formal Development Problem Frame Architectural Style Abstract Data Type 
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.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. [BB87]
    Bolognesi, T., Brinksma, E.: Introduction to the ISO specification language LOTOS. Computer Networks and ISDN Systems, North-Holland 14, 25–59 (1987)CrossRefGoogle Scholar
  2. [BCK98]
    Bass, L., Clements, P., Kazman, R.: Software Architecture in Practice. Addison-Wesley, Reading (1998)Google Scholar
  3. [BHK02]
    Bidoit, M., Hennicker, R., Kurz, A.: On the Integration of Observability and Reachability Concepts. In: Nielsen, M., Engberg, U. (eds.) FOSSACS 2002. LNCS, vol. 2303, pp. 21–36. Springer, Heidelberg (2002)CrossRefGoogle Scholar
  4. [Bla02]
    Blanc, B.: Prise en compte de principes architecturaux lors de la formalisation des besoins - Proposition d’une extension en CASL et d’un guide méthodologique associé. Thèse de Doctorat, ENS Cachan (2002)Google Scholar
  5. [BM02]
    Bidoit, M., Mosses, P.: CASL User Manual (2002), http://www.brics.dk/Projects/CoFI/
  6. [BMR+96]
    Buschmann, F., Meunier, R., Rohnert, H., Sommerlad, P., Stal, M.: Pattern- Oriented Software Architecture: A System of Patterns. John Wiley & Sons, Chichester (1996)Google Scholar
  7. [CH03]
    Choppy, C., Heisel, M.: Systematic transition from problems to architectural designs. Technical report, Université Paris Nord (2003) (to appear)Google Scholar
  8. [CR00]
    Choppy, C., Reggio, G.: Using CASL to Specify the Requirements and the Design: A Problem Specific Approach. In: Bert, D., Choppy, C., Mosses, P.D. (eds.) WADT 1999. LNCS, vol. 1827, pp. 104–123. Springer, Heidelberg (2000)CrossRefGoogle Scholar
  9. [GHJV95]
    Gamma, E., Helm, R., Johnson, R., Vlissides, J.: Design Patterns – Elements of Reusable Object-Oriented Software. Addison Wesley, Reading (1995)zbMATHGoogle Scholar
  10. [Hei98]
    Heisel, M.: Agendas – a concept to guide software development activites. In: Horspool, R.N. (ed.) Proc. Systems Implementation 2000, pp. 19–32. Chapman & Hall London, Boca Raton (1998)CrossRefGoogle Scholar
  11. [HL97]
    Heisel, M., Lévy, N.: Using LOTOS patterns to characterize architectural styles. In: Bidoit, M., Dauchet, M. (eds.) CAAP 1997, FASE 1997, and TAPSOFT 1997. LNCS, vol. 1214, pp. 818–832. Springer, Heidelberg (1997)CrossRefGoogle Scholar
  12. [Jac95]
    Jackson, M.: Software Requirements & Specifications: a Lexicon of Practice, Principles and Prejudices. Addison-Wesley, Reading (1995)Google Scholar
  13. [Jac01]
    Jackson, M.: Problem Frames. Analyzing and structuring software development problems. Addison-Wesley, Reading (2001)Google Scholar
  14. [RM02]
    Roggenbach, M., Mossakowski, T.: What is a good CASL specification. WADT (2002)Google Scholar
  15. [SG96]
    Shaw, M., Garlan, D.: Software Architecture. Perspectives on an Emerging Discipline. Prentice-Hall, Englewood Cliffs (1996)zbMATHGoogle Scholar
  16. [SH00]
    Souquières, J., Heisel, M.: Structuring the first steps of requirements elicitation. Technical Report A00-R-123, LORIA, Nancy, France (2000)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2003

Authors and Affiliations

  • Christine Choppy
    • 1
  • Maritta Heisel
    • 2
  1. 1.LIPNInstitut Galilée – Université Paris XIIIFrance
  2. 2.Fakultät für Informatik, Institut für Verteilte SystemeOtto-von-Guericke-Universität MagdeburgMagdeburgGermany

Personalised recommendations