Software requirements for architectured systems

Recently, increased attention has been paid to how to establish and strengthen the relationships between requirements and architectural design. In particular, how the process must encompass changes to requirements over time and their effects upon a system's architecture. We sketch our work-in-progress in this field, which we concern about a methodology to guide the architecture development from the inception.

[1]  John-Jules Ch. Meyer,et al.  Objects, Agents, and Features , 2004, Lecture Notes in Computer Science.

[2]  John Mylopoulos,et al.  Non-Functional Requirements in Software Engineering , 2000, International Series in Software Engineering.

[3]  Jennifer Pérez,et al.  Requirements and Architecture: a marriage for Quality Assurance , 2003, Jornadas de Ingeniería del Software y Bases de Datos.

[4]  John B. Shoven,et al.  I , Edinburgh Medical and Surgical Journal.

[5]  W. van der Hoek,et al.  Agent Programming with Declarative Goals , 2000, ATAL.

[6]  Stephen Fickas,et al.  Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..

[7]  Neil A. M. Maiden,et al.  CREWS-SAVRE: Scenarios for Acquiring and Validating Requirements , 1998, Automated Software Engineering.

[8]  G. G. Stokes.  "J." , 1890, The New Yale Book of Quotations.

[9]  Colette Rolland,et al.  Experience with goal-scenario coupling in requirements engineering , 1999, Proceedings IEEE International Symposium on Requirements Engineering (Cat. No.PR00188).

[10]  Bashar Nuseibeh,et al.  Weaving the Software Development Process Between Requirements and Architectures , 2001 .