A Metamodeling Approach for Requirements Specification

There are many Requirements Engineering approaches and techniques that help to specify, analyze and validate requirements. However, they are neither widely accepted nor widely used by the industrial software community. One of the main problems faced when applying them is to what extent they can be easily adapted to the specific needs of the project. This has often led to unsatisfactory requirements management in industrial software development. In this work, a proposal for requirements modeling is presented that allows the integration of the expressiveness of some of the more relevant Requirements Engineering techniques by taking advantage of metamodeling. This proposal focuses on scalability with respect to expressiveness and adaptability to the application domain to establish some basic guidelines and extension mechanisms that lend coherence and semantic precision. A case study and 4 tool support are presented to describe the application of this proposal in a real-life project.

[1]  Bashar Nuseibeh,et al.  Requirements engineering: a roadmap , 2000, ICSE '00.

[2]  João Araújo,et al.  Early aspects: a model for aspect-oriented requirements engineering , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.

[3]  Gregor Kiczales,et al.  Aspect-oriented programming , 2001, ESEC/FSE-9.

[4]  uclm. es.  Goals and Quality Characteristics : Separating Concerns ∗ , 2004 .

[5]  A. Moreira,et al.  1 TOWARDS A COMPOSITION PROCESS FOR ASPECT-ORIENTED REQUIREMENTS , 2003 .

[6]  Klaus Pohl,et al.  Communicating the variability of a software-product family to customers , 2004, Informatik Forschung und Entwicklung.

[7]  Ian Sommerville,et al.  Editorial. The Viewpoints FAQ , 1996 .

[8]  Víctor Anaya,et al.  Customizing Traceability in a Software Development Process , 2005 .

[9]  Yijun Yu,et al.  From goals to aspects: discovering aspects from requirements goal models , 2004, Proceedings. 12th IEEE International Requirements Engineering Conference, 2004..

[10]  Jan Bosch,et al.  On the notion of variability in software product lines , 2001, Proceedings Working IEEE/IFIP Conference on Software Architecture.

[11]  Elena Navarro,et al.  UML Visualization for an Aspect and Goal-Oriented Approach , 2004 .

[12]  Ian Sommerville,et al.  The viewpoints FAQ , 1996 .

[13]  Keng Siau,et al.  Are use case and class diagrams complementary in requirements analysis? An experimental study on use case and class diagrams in UML , 2004, Requirements Engineering.

[14]  Dirk Muthig,et al.  Tailoring Use Cases for Product Line Modeling , 2002 .

[15]  Klaus Pohl,et al.  Modelling Dependencies between Variation Points in Use Case Diagrams , 2003 .

[16]  K. Siau,et al.  Technical communication in information systems development: the use of cognitive mapping , 2005, IEEE Transactions on Professional Communication.

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

[18]  Trevor Wood-Harper,et al.  A critical perspective on action research as a method for information systems research , 1996, J. Inf. Technol..

[19]  Paul Clements,et al.  Software product lines - practices and patterns , 2001, SEI series in software engineering.

[20]  Keng Siau,et al.  Improving the quality of conceptual modeling using cognitive mapping techniques , 2005, Data Knowl. Eng..

[21]  Peyman Oreizy,et al.  Architecture-based runtime software evolution , 1998, Proceedings of the 20th International Conference on Software Engineering.

[22]  Yoshikazu Yamamoto,et al.  Extending UML with Aspects: Aspect Support in the Design Phase , 1999, ECOOP Workshops.

[23]  Horst Lichter,et al.  Modeling Variability by UML Use Case Diagrams , 2002 .

[24]  Keng Siau,et al.  Evaluation Criteria for Information Systems Development Methodologies , 2005, AMCIS.

[25]  João Araújo,et al.  Modularisation and composition of aspectual requirements , 2003, AOSD '03.

[26]  Shmuel Katz,et al.  From aspectual requirements to proof obligations for aspect-oriented systems , 2004, Proceedings. 12th IEEE International Requirements Engineering Conference, 2004..

[27]  John Mylopoulos,et al.  Requirements analysis for customizable software: a goals-skills-preferences framework , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..

[28]  Mordechai Ben-Menachem,et al.  Writing effective use cases , 2001, SOEN.

[29]  Helen M. Edwards,et al.  Problem frames: analyzing and structuring software development problems , 2002, Softw. Test. Verification Reliab..

[30]  Gregor Kiczales,et al.  Discussing aspects of AOP , 2001, CACM.

[31]  Ana Moreira,et al.  Integrating the NFR framework in a RE model , 2004 .

[32]  Pericles Loucopoulos,et al.  Goal Modeling in Requirements Engineering: Analysis and Critique of Current Methods , 2005, Information Modeling Methods and Methodologies.

[33]  Axel van Lamsweerde,et al.  Goal-Oriented Requirements Engineering: A Guided Tour , 2001, RE.

[34]  Jennifer Pérez,et al.  Software requirements for architectured systems , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..

[35]  Axel van Lamsweerde,et al.  Deriving operational software specifications from system goals , 2002, SIGSOFT '02/FSE-10.

[36]  Ying Li,et al.  Modelling Strategic Actor Relationships to Support Intellectual Property Management , 2001, ER.

[37]  Pamela Zave.  Classification of research efforts in requirements engineering , 1997, ACM Comput. Surv..