@inproceedings{Braganca2007, title = {Automating Mappings between Use Case Diagrams and Feature Models for Software Product Lines}, address = {Washington, DC, USA}, author = {Alexandre Braganca and Ricardo J. Machado}, booktitle = {SPLC '07: Proceedings of the 11th International Software Product Line Conference}, pages = {3--12}, publisher = {IEEE Computer Society}, year = 2007, url = {http://portal.acm.org/citation.cfm?id=1308171.1308183&coll=&dl=}, isbn = {0-7695-2888-0}, doi = {http://dx.doi.org/10.1109/SPLC.2007.11}, description = {Automating Mappings between Use Case Diagrams and Feature Models for Software Product Lines}, abstract = {Features have been widely used by the product line community to model variability. They represent the common and variable characteristics of the members of a product line. They are very well suited for the configuration of product line members. Outside the product line community, use cases are also widely used to model the functionality of systems at a similar level of abstraction but from a user perspective. Significant work has been done by several authors regarding the possible relationship between these two perspectives of a system. Nonetheless, this has been done in an informal way. In this paper we explore the relationships between these two perspectives and describe a possible approach to automate the transformation from UML use case to feature models.}, biburl = {http://www.bibsonomy.org/bibtex/2fa8b293e480a80239c6dd7aec83886c7/ist_spl}, keywords = {Use-Cases transformation product model diagrams QVT OCL UML feature line} } @mastersthesis{Rinke2004, title = {Ableitung von Domänen-Testfall-Szenarien aus Domänen-Aktivitätsdiagrammen unter Gewährleistung der Zweigabdeckung }, author = {Thomas Rinke}, school = {Universität Duisburg-Essen}, type = {Diplomarbeit}, year = 2004, description = {MR: Gewissermaßen ein Teil der Diss von Andreas Reuys und der ScenTED-Methode.}, biburl = {http://www.bibsonomy.org/bibtex/277be542bac60389552ee830a4671476b/ist_spl}, keywords = {ScenTED activity scenario-based line product FTPS ddgraph branch UML MBT coverage diagrams testing} } @article{journals/sosym/HalmansP03, title = {Communicating the Variability of a Software-Product Family to Customers}, author = {G{\"u}nter Halmans and Klaus Pohl}, journal = {Software and System Modeling}, number = 1, pages = {15-36}, volume = 2, year = 2003, bibsource = {DBLP, http://dblp.uni-trier.de}, description = {DBLP Record 'journals/sosym/HalmansP03'}, abstract = {Variability is a central concept in software product family development. Variability empowers constructive reuse and facilitates the derivation of different, customer specific products from the product family. If many customer specific requirements can be realised by exploiting the product family variability, the reuse achieved is obviously high. If not, the reuse is low. It is thus important that the variability of the product family is adequately considered when eliciting requirements from the customer. In this paper we sketch the challenges for requirements engineering for product family applications. More precisely we elaborate on the need to communicate the variability of the product family to the customer.We differentiate between variability aspects which are essential for the customer and aspects which are more related to the technical realisation and need thus not be communicated to the customer. Motivated by the successful usage of use cases in single product development we propose use cases as communication medium for the product family variability.We discuss and illustrate which customer relevant variability aspects can be represented with use cases, and for which aspects use cases are not suitable. Moreover we propose extensions to use case diagrams to support an intuitive representation of customer relevant variability aspects.}, biburl = {http://www.bibsonomy.org/bibtex/2c37414fb6a915ce97fd08495ccf0fe48/ist_spl}, keywords = {requirements product variability engineering line UML Use-Cases} } @mastersthesis{Hoegemann2005, title = {Erstellung von Aktivitätsdiagrammen aus Domänen Use Cases zum Testen von Produktfamilien}, address = {Essen}, author = {Dirk Högemann}, school = {Universität Duisburg-Essen}, type = {Bachelorarbeit}, year = 2005, description = {MR: Der Entwickelte Prototyp wurde auch in der Diss von Andreas Reuys (TransUse) beschrieben.}, biburl = {http://www.bibsonomy.org/bibtex/247b2991613f919ed3cdd461442a2c2c6/ist_spl}, keywords = {product UML ScenTED testing Use-Cases line diagrams activity} } @misc{Hoegemann2004, title = {Pattern-Identification for the derivation of V-Activity Diagrams from Domain Use Cases}, author = {Dirk Högemann}, howpublished = {Universität Duisburg-Essen}, note = {Projektseminararbeit}, year = 2004, biburl = {http://www.bibsonomy.org/bibtex/25572f6d31c4837e5884c395b61dfa3c4/ist_spl}, keywords = {ScenTED Use-Cases diagrams variability UML product activity testing line} } @inproceedings{Reuys2003, title = {Derivation of Domain Test Scenarios from Activity Diagrams}, address = {Erfurt}, author = {Andreas Reuys and Sacha Reis and Erik Kamsties and Klaus Pohl}, editor = {Klaus Schmid and Birgit Geppert}, note = {Proceedings of the PLEES’03 International Workshop on Product Line Engineering: The Early Steps: Planning, Modeling, and Managing}, year = 2003, description = {MR: Einer der Grundsteine für die Diss von Andreas Reyus.}, abstract = {Requirements are often reported as not suitable for testing, because they are, for instance, incomplete. We argue in this paper for early steps in requirements engineering to ensure the testability of requirements in the context of product families. This paper describes the early derivation of test scenarios from use cases represented as activity diagrams. Use cases are often supplemented with activity diagrams if the control structure of the use case includes loops or branches. The use of activity diagrams allows defining a coverage criterion to ensure a particular degree of completeness of the test scenarios. The approach described in this paper is intended for use cases at the domain engineering level. It is discussed how variability in these use cases can be captured in activity diagrams, and, most important, how to address variability while deriving test scenarios so that a particular degree of completeness is reached. For this purpose, we adapt the existing branch coverage criterion to the needs of product families and provide an operational procedure that helps in deriving a set of test scenarios that fulfills our extended coverage criterion. Eventually, the derivation of test scenarios gives an early feedback to the requirements engineer when performed from the tester’s perspective. This increases the requirements quality.}, biburl = {http://www.bibsonomy.org/bibtex/26d3b132574891802906b2f5896efbd0c/ist_spl}, keywords = {test product ScenTED activity testing scenarios line diagrams UML Use-Cases} } @mastersthesis{Stricker2006, title = {Datenflussbasierte Identifikation erneut auszuführender Applikationstestfälle in der Produktlinienentwicklung }, author = {Vanessa Stricker}, school = {Universität Duisburg-Essen}, type = {Bachelorarbeit}, year = 2006, biburl = {http://www.bibsonomy.org/bibtex/2637eeb497465541bb566aefabf5db130/ist_spl}, keywords = {line defs-uses activity product UML diagrams ScenTED testing} } @misc{Stricker2005, title = {Anforderungen an ein Modell zur Selektion erneut auszuführender Applikationstetsartefakte}, author = {Vanessa Stricker}, note = {Projektseminar; Lehrstuhl Software Systems Engineering; Professor Dr. Klaus Pohl; SS 2005}, year = 2005, description = {MR: Die Arbeit beinhaltet eine Übersicht über Regressions-, Impact-Analysis und Delta-Techniken. Die Auswirkungen der Variabilität werden betrachtet. Und Einfluesse die aus der Ablauflogik (Aktivitätsdiagramme, Sequenzdiagramme) und den Datenabhängigkeiten sich ableiten werden analysiert. Gute Idee: Aktivitätsdiagramme mit angehängten Informationen zu Datenaustausch... Wertvoll: Literaturverweise (auch auf die SSE-Eigenen Arbeiten)}, biburl = {http://www.bibsonomy.org/bibtex/28d7c9e3717b02928dc7c69641e5f0769/ist_spl}, keywords = {product OVM diagrams activity dependencies reuse ScenTED data UML application line testing variability} } @inproceedings{Hartmann2004, title = {A {UML}-based Approach for Validating Product Lines}, address = {Boston, MA}, author = {Jean Hartmann and Marlon Vieira and Axel Ruder}, booktitle = {Proceedings of the International Workshop on Software Product Line Testing ({SPL}i{T} 2004)}, editor = {Birgit Geppert and Charles Krueger and Jenny Li}, month = {August}, note = {ST:Basiert auf UML-Aktivitätsdiagrammen Entwicklung eines Tools auf Basis von Rational-Rose. Für die Testdatengewinnung wird eine Ä-Klassenanalyse durchgeführt. Wichtig sind daher die Bedingungen an der Verzweigungspunkten im Aktivitätsdiagramm, da die Auswahl des Testfalls von diesen abhängt. Nutzer wählt Produkt aus und das Tool generiert für ein produkt Testfälle Fazit: Es werden zwar Testfälle mit Testdaten für die Produkte einer Produktlinie automatisch generiert, aber es findet keine Trennung zwischen Domain- und Application Engineering statt. Es ist kein Wiederverwendungsansatz erkennbar. Außerdem arbeitet das Tool auf Basis anderer kommerzieller Tools (Rose). MR: Die Ä-Klassenanalyse wird nach der Category-Partition-Methode durchgeführt, d.h. dass die die Testdaten (mit erwarteten Ausgaben) teilweise manuell erstellt werden müssen.}, pages = {58--65}, year = 2004, category = {Testing}, available = {1}, newinversion = {3.5}, description = {Computer Science Bibliography Collection}, abstract = {The Unified Modeling Language (UML) is gaining wide acceptance in industry as the new de facto visual modeling language and as such it is being used within Siemens to model large, complex new product lines. As a result, we are extending our existing UML-based approaches to component and system validation to address the needs of product line validation. In this paper, we will focus on describing the extensions made to our system testing approach in which Activity Diagrams that form the basis for the test specification are annotated with variation points and conformance tests are then automatically generated to validate each product variant. We are also implementing these extensions as part of our Test Development Environment for UML (TDE/UML) automated test generation technology, which is currently integrated with the IBM/Rational Rose UML modeling tool and coupled with test execution tools, such as a graphical capture/replay tool. This paper provides an outline of our existing UML-based approach to system validation, but focuses on how we supplement the existing UML diagrams with information concerning the variation points for product-line validation.}, biburl = {http://www.bibsonomy.org/bibtex/242adeda1515608dae46ba044035d5904/ist_spl}, keywords = {category-partition activity UML line TSL product Use-Cases TDE/UML systemtest diagrams} } @incollection{Nebut2006, title = {System Testing of Product Lines: From Requirements to Test Cases}, author = {Clementine Nebut and Yves Traon and Jean-Marc ER Jezequel}, booktitle = {Software Product Lines - Research Issues in Engineering and Management}, editor = {Timo Kakola and Juan Carlos Duenas}, note = {MR: Bei dem beschriebenen Ansatz ist es notwendig die Testdaten manuell einzufügen für die Testgenerierung und Simulation. Im Artikel wird trotzdem von der Generierung der konkreten Testfälle gesprochen, die konkreten Daten werden aber ausgeblendet! Ansatz baut auf Use Cases als Anforderungen auf, die mit UML-Sequenzdiagrammen (als Systemscenarios) erweitert sind und als Eingabe gedacht sind. Aus diesen werden automatisch Testszenarien abgeleitet. Nützliche Ideen: - OCL zur Beschreibung von Pre- und Postbedingungen für die Testszenarios. - Test Synthesis zur Effizienzsteigerung bei der Ableitung der Testfälle. - Verwandschaft zu ScenTED wurde skizziert. Usefulness for IST-SPL (-/0/+/++/+++): ++ (Verwandschaft zu ScenTED) }, pages = {447--477}, publisher = {Springer-Verlag}, year = 2006, url = {http://dx.doi.org/10.1007/978-3-540-33253-4_12}, biburl = {http://www.bibsonomy.org/bibtex/2a20ee1265fe5c6f075c5b2d05ee032bb/ist_spl}, keywords = {cases OCL testing product requirements use TGV LTS system line UML} }