Refinement of Software Product Line Architectures through Recursive Modeling Techniques
OTM '09 Proceedings of the Confederated International Workshops and Posters on On the Move to Meaningful Internet Systems: ADI, CAMS, EI2N, ISDE, IWSSA, MONET, OnToContent, ODIS, ORM, OTM Academy, SWWS, SEMELS, Beyond SAWSDL, and COMBEK 2009
Support for variability in use case modeling with refinement
Proceedings of the 7th International Workshop on Model-Based Methodologies for Pervasive and Embedded Software
CAiSE'10 Proceedings of the 22nd international conference on Advanced information systems engineering
Formal definition of syntax and semantics for documenting variability in activity diagrams
SPLC'10 Proceedings of the 14th international conference on Software product lines: going beyond
The UML «extend» relationship as support for software variability
SPLC'10 Proceedings of the 14th international conference on Software product lines: going beyond
Use-case and scenario metamodeling for automated processing in a reverse engineering tool
Proceedings of the 4th India Software Engineering Conference
On the refinement of use case models with variability support
Innovations in Systems and Software Engineering
Flexible development of variable software features for mobile business applications
Proceedings of the 17th International Software Product Line Conference co-located workshops
Defining variability in activity diagrams and Petri nets
Science of Computer Programming
A configurable use case modeling metamodel with superimposed variants
Innovations in Systems and Software Engineering
| Hi-index | 0.00 |
Software product lines and related approaches, like software factories, are starting to capture the attention of the industry practitioners. Nevertheless, their adoption outside the research community and big companies is still very restricted. We believe that model-driven approaches, like OMG's MDA, with proper tool support, can bring the advantages of product lines to a broader audience. For this to become a reality, model-driven methods should integrate requirements models into the software development process. In this paper, we discuss the semantics of use case relationships and their formalization using activity diagrams to support variability specification. Particularly, we propose an extension to the 芦extend禄 relationship that supports the adoption of UML 2.0 use case diagrams into modeldriven methods. Our proposal results from our work with 4SRS (4 Step Rule Set), a model-driven method in which use cases are the central model for requirements specification and model transformation.