Use of patterns in formal development: Systematic transition from problems to architectural designs

Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)

Volumn 2755, Issue , 2003, Pages 201-215

  Choppy, Christine ^a   Heisel, Maritta ^b  

^a UNIVERSITÉ PARIS 13   (France)

^b OTTO VON GUERICKE UNIVERSITY   (Germany)

Author keywords

[No Author keywords available]

Indexed keywords

LIFE CYCLE; SPECIFICATIONS;

ARCHITECTURAL SPECIFICATIONS; ARCHITECTURAL STYLE; DESIGN AND IMPLEMENTATIONS; FORMAL DEVELOPMENT; PROBLEM FRAMES; SECOND PHASE; SOFTWARE LIFE CYCLES; SOFTWARE SYSTEMS;

FORMAL SPECIFICATION;

EID: 0348216688     PISSN: 03029743     EISSN: 16113349     Source Type: Book Series    
DOI: 10.1007/978-3-540-40020-2_11     Document Type: Article

References (16)

1. T. Bolognesi and E. Brinksma. Introduction to the ISO specification language LOTOS. Computer Networks and ISDN Systems, North-Holland, 14:25-59, 1987.
2. L. Bass, P. Clements, and R. Kazman. Software Architecture in Practice. Addison-Wesley, 1998.
3. M. Bidoit, R. Hennicker, and A. Kurz. On the Integration of Observability and Reachability Concepts. In Proc. 5th Int. Conf. Foundations of Software Science and Computation Structures (FOSSACS'2002), LNCS 2303, pages 21-36. Springer Verlag, 2002.
4. B. Blanc. 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.
5. M. Bidoit and P. Mosses. CASL User Manual, 2002. http://vww.brics.dk/Projects/CoFI/.
6. F. Buschmann, R. Meunier, H. Rohnert, P. Sommerlad, and M. Stal. Pattern-Oriented Software Architecture: A System of Patterns. John Wiley & Sons, 1996.
7. C. Choppy and M. Heisel. Systematic transition from problems to architectural designs. Technical report, Université Paris Nord, 2003. To appear.
8. C. Choppy and G. Reggio. Using CASL to Specify the Requirements and the Design: A Problem Specific Approach. In Recent Trends in Algebraic Development Techniques, LNCS 1827, pages 104-123. Springer Verlag, 2000.
9. E. Gamma, R. Helm, R. Johnson, and J. Vlissides. Design Patterns - Elements of Reusable Object-Oriented Software. Addison Wesley, Reading, 1995.
10. M. Heisel. Agendas - a concept to guide software development activites. In R. N. Horspool, editor, Proc. Systems Implementation 2000, pages 19-32. Chapman & Hall London, 1998.
11. M. Heisel and N. Lévy. Using LOTOS patterns to characterize architectural styles. In M. Bidoit and M. Dauchet, editors, Proceedings TAPSOFT'97, LNCS 1214, pages 818-832. Springer-Verlag, 1997.
12. M. Jackson. Software Requirements & Specifications: a Lexicon of Practice, Principles and Prejudices. Addison-Wesley, 1995.
13. M. Jackson. Problem Frames. Analyzing and structuring software development problems. Addison-Wesley, 2001.
14. M. Roggenbach and T. Mossakowski. What is a good CASL specification, 2002. WADT.
15. M. Shaw and D. Garlan. Software Architecture. Perspectives on an Emerging Discipline. Prentice-Hall, 1996.
16. J. Souquières and M. Heisel. Structuring the first steps of requirements elicitation. Technical Report A00-R-123, LORIA, Nancy, France, 2000.