Scenario modelling with aspects

There has been significant recent interest, within the aspect-oriented software development (AOSD) community, in representing crosscutting concerns at various stages of the software lifecycle. However, most of these efforts have concentrated on the design and implementation phases. The focus of this paper is on representing aspects during requirements modelling. In particular, the issue of how to model aspects as part of scenario-based modelling is addressed. The use of scenarios is common in requirements development and analysis. The authors describe how to represent and compose aspects at the scenario level. Aspectual scenarios are modelled as interaction pattern specifications (IPSs) and are composed with nonaspectual scenarios using instantiation and special composition operators. The composed collection of scenarios can then be translated automatically into a set of state machines using an existing state machine synthesis algorithm. The resulting set of state machines is an executable form of the scenarios and can be used for simulation and analysis of the requirements.

[1]  Sjouke Mauw,et al.  Message Sequence Chart (MSC) , 1996 .

[2]  Barry W. Boehm,et al.  Software Engineering Economics , 1993, IEEE Transactions on Software Engineering.

[3]  Robert B. France,et al.  UML Aspect Specification Using Role Models , 2002, OOIS.

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

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

[6]  Siobhán Clarke,et al.  Towards a standard design language for AOSD , 2002, AOSD '02.

[7]  Edmund M. Clarke,et al.  Model Checking , 1999, Handbook of Automated Reasoning.

[8]  Siobhán Clarke,et al.  Composition patterns: an approach to designing reusable , 2001, Proceedings of the 23rd International Conference on Software Engineering. ICSE 2001.

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

[10]  Ramnivas Laddad,et al.  Aspectj in Action: Practical Aspect-Oriented Programming , 2003 .

[11]  Pete Sawyer,et al.  Requirements Engineering: A Good Practice Guide , 1997 .

[12]  Robert B. France,et al.  A UML-based pattern specification technique , 2004, IEEE Transactions on Software Engineering.

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

[14]  Stanley M. Sutton,et al.  Modeling of software concerns in Cosmos , 2002, AOSD '02.

[15]  Alexander Egyed,et al.  Statechart simulator for modeling architectural dynamics , 2001, Proceedings Working IEEE/IFIP Conference on Software Architecture.

[16]  Manfred Broy,et al.  From MSCs to Statecharts , 1998, DIPES.

[17]  John C. Grundy,et al.  Aspect-oriented requirements engineering for component-based software systems , 1999, Proceedings IEEE International Symposium on Requirements Engineering (Cat. No.PR00188).

[18]  Anneke Kleppe,et al.  The object constraint language: precise modeling with UML , 1998 .

[19]  Indrakshi Ray,et al.  Using aspects to design a secure system , 2002, Eighth IEEE International Conference on Engineering of Complex Computer Systems, 2002. Proceedings..

[20]  John Mylopoulos,et al.  From E-R to "A-R" - Modelling Strategic Actor Relationships for Business Process Reengineering , 1994, Int. J. Cooperative Inf. Syst..

[21]  João Araújo,et al.  Crosscutting quality attributes for requirements engineering , 2002, SEKE '02.

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

[23]  Jon Whittle,et al.  From scenarios to code: An air traffic control case study , 2004, Software & Systems Modeling.