@article{ross77a, title = {Structured Analysis (SA): A language for communicating ideas}, author = {D. T. Ross}, journal = {IEEE Transactions on Software Engineering}, number = 1, pages = {16-34}, volume = 3, year = 1977, abstract = {Structured analysis (SA) combines blueprint-like graphic language with the nouns and verbs of any other language to provide a hierarchic, top-down, gradual exposition of detail in the form of an SA model. The things and happenings of a subject are expressed in a data decomposition and an activity decomposition, both of which employ the same graphic building block, the SA box, to represent a part of a whole. SA arrows, representing input, output, control, and mechanism, express the relation of each part to the whole. The paper describes the rationalization behind some 40 features of the SA language, and shows how they enable rigorous communication which results frorn disciplined, recursive application of the SA maxim: "Everything worth saying about anything worth saying something about must be expressed in six or fewer pieces."}, biburl = {http://www.bibsonomy.org/bibtex/2b5fc0a3afbb27299581beb5fa118dcff/neilernst}, keywords = {seminal requirements} } @book{Zielczynski2007, title = {Requirements Management Using IBM Rational RequisitePro}, author = {Peter Zielczynski}, edition = 1, publisher = {IBM Press}, year = 2007, url = {http://www.amazon.com/Requirements-Management-Using-Rational-RequisitePro/dp/0321383001%3FSubscriptionId%3D13CT5CVB80YFWJEPWS02%26tag%3Dws%26linkCode%3Dxm2%26camp%3D2025%26creative%3D165953%26creativeASIN%3D0321383001}, ean = {9780321383006}, asin = {0321383001}, isbn = {0321383001}, dewey = {005.3}, description = {Amazon.com: Requirements Management Using IBM(R) Rational(R) RequisitePro(R)}, biburl = {http://www.bibsonomy.org/bibtex/2dfebc341e28d7699992dad27b43f4168/ist_spl}, keywords = {testing Use-Cases requirements engineering black-box} } @book{Schneider2001, title = {Applying Use Cases: A Practical Guide}, author = {Geri Schneider and Jason P. Winters}, edition = 2, publisher = {Addison-Wesley Professional}, series = {Addison-Wesley Object Technology Series}, year = 2001, url = {http://www.amazon.com/Applying-Use-Cases-Addison-Wesley-Technology/dp/0201708531%3FSubscriptionId%3D13CT5CVB80YFWJEPWS02%26tag%3Dws%26linkCode%3Dxm2%26camp%3D2025%26creative%3D165953%26creativeASIN%3D0201708531}, ean = {9780201708530}, asin = {0201708531}, isbn = {0201708531}, dewey = {005.1}, description = {Amazon.com:}, biburl = {http://www.bibsonomy.org/bibtex/22d88473e29a09fbb90f03fe407dec4a4/ist_spl}, keywords = {Use-Cases UML requirements engineering} } @incollection{Bertolino2006, title = {Product Line Use Cases: Scenario-Based Specification and Testing of Requirements}, author = {Antonia Bertolino and Alessandro Fantechi and Stefania Gnesi and Giuseppe Lami}, booktitle = {Software Product Lines - Research Issues in Engineering and Management}, chapter = 11, crossref = {DBLP:conf/splc/2006book}, pages = {425--445}, publisher = {Springer-Verlag}, year = 2006, url = {http://dx.doi.org/10.1007/978-3-540-33253-4_11}, biburl = {http://www.bibsonomy.org/bibtex/2b6dd6c002f57a73dba61be882ba86864/ist_spl}, keywords = {product PLUC cases specification use line testing scenario-based requirements PLUTO} } @inproceedings{Gutierrez2006, title = {An approach to generate test cases from use cases}, address = {New York}, author = {Javier Jes\'{u}s Guti\'{e}rrez and Mar\'{\i}a Jos\'{e} Escalona and Manuel Mej\'{\i}as and Jes\'{u}s Torres}, booktitle = {ICWE '06: Proceedings of the 6th international conference on Web engineering}, pages = 113, publisher = {ACM}, year = 2006, url = {http://portal.acm.org/citation.cfm?id=1145606&dl=ACM&coll=portal}, location = {Palo Alto, California, USA}, isbn = {1-59593-352-2}, doi = {http://doi.acm.org/10.1145/1145581.1145606}, description = {pages = 113--114 address = New York, NY, USA}, abstract = {The system testing allows to verify the behaviour of the systemunder test and to guarantee the satisfaction of its requirements.This work describes a complete process to generate test casesfrom use cases for web applications. This process also resolves the lacks detected in existing approaches.}, biburl = {http://www.bibsonomy.org/bibtex/20752d81b352451d691b01c8dfd1ebcdb/ist_spl}, keywords = {cases test testing Use-Cases requirements based} } @book{Cockburn2000, title = {Writing Effective Use Cases}, author = {Alistair Cockburn}, publisher = {Addison-Wesley}, year = 2000, url = {http://www.amazon.com/Writing-Effective-Cases-Software-Development/dp/0201702258%3FSubscriptionId%3D13CT5CVB80YFWJEPWS02%26tag%3Dws%26linkCode%3Dxm2%26camp%3D2025%26creative%3D165953%26creativeASIN%3D0201702258}, ean = {9780201702255}, asin = {0201702258}, isbn = {0201702258}, dewey = {005.3}, description = {series = The Agile Software Development Series publisher = Addison-Wesley Professional}, biburl = {http://www.bibsonomy.org/bibtex/29e36f9f7b3ec792147cba178e3db2ca5/ist_spl}, keywords = {data Use-Cases requirements engineering} } @incollection{Nebut2006, title = {System Testing of Product Lines: From Requirements to Test Cases}, author = {Cl{\'e}mentine Nebut and Yves Le Traon and Jean-Marc J{\'e}z{\'e}quel}, booktitle = {Software Product Lines}, crossref = {DBLP:conf/splc/2006book}, pages = 447, publisher = {Springer-Verlag}, year = 2006, url = {http://dx.doi.org/10.1007/978-3-540-33253-4_12}, description = {pages = 447--477}, biburl = {http://www.bibsonomy.org/bibtex/2b7b5fe3e770c66b6452c90fd9dd170a3/ist_spl}, keywords = {product system cases OCL use line testing TGV UML LTS requirements} } @book{Pohl2008a, title = {Requirements Engineering: Grundlagen, Prinzipien,Techniken}, author = {Klaus Pohl}, edition = 2, publisher = {dpunkt.Verlag GmbH}, year = 2008, url = {http://www.amazon.de/Requirements-Engineering-Grundlagen-Prinzipien-Techniken/dp/3898645509%3FSubscriptionId%3D13CT5CVB80YFWJEPWS02%26tag%3Dws%26linkCode%3Dxm2%26camp%3D2025%26creative%3D165953%26creativeASIN%3D3898645509}, ean = {9783898645508}, asin = {3898645509}, isbn = {3898645509}, description = {edition = 2., korrigierte Auflage. Amazon.de: Requirements Engineering: Grundlagen, Prinzipien,Techniken: Klaus Pohl: Bücher}, biburl = {http://www.bibsonomy.org/bibtex/272264ad3d2203fabd5bb52ae26cf8b73/ist_spl}, keywords = {product fundamentals line ScenTED requirements engineering SSE} } @book{Pohl2007, title = {Requirements Engineering. Grundlagen, Prinzipien, Techniken}, author = {Klaus Pohl}, edition = 1, publisher = {Dpunkt.Verlag GmbH}, year = 2007, url = {http://www.amazon.de/Requirements-Engineering-Grundlagen-Prinzipien-Techniken/dp/3898643425%3FSubscriptionId%3D13CT5CVB80YFWJEPWS02%26tag%3Dws%26linkCode%3Dxm2%26camp%3D2025%26creative%3D165953%26creativeASIN%3D3898643425}, ean = {9783898643429}, asin = {3898643425}, isbn = {3898643425}, biburl = {http://www.bibsonomy.org/bibtex/23d3fe69cfc985a731293a2051f688458/ist_spl}, keywords = {product fundamentals line ScenTED requirements engineering SSE} } @book{DSouza1998, title = {Objects, Components, and Frameworks with UML: The Catalysis Approach}, author = {Desmond Francis D'Souza and Alan Cameron Wills}, publisher = {Addison-Wesley Professional}, year = 1998, url = {http://www.amazon.com/Objects-Components-Frameworks-UML-Addison-Wesley/dp/0201310120%3FSubscriptionId%3D13CT5CVB80YFWJEPWS02%26tag%3Dws%26linkCode%3Dxm2%26camp%3D2025%26creative%3D165953%26creativeASIN%3D0201310120}, ean = {9780201310122}, asin = {0201310120}, isbn = {0201310120}, dewey = {005.117}, description = {series = Addison-Wesley Object Technology Series}, biburl = {http://www.bibsonomy.org/bibtex/24237bc58be5725a4c36355b39f1fc73d/ist_spl}, keywords = {software modeling Use-Cases components requirements engineering} } @article{nissen96, title = {Managing multiple requirements perspectives with metamodels}, author = {H.W. Nissen and M.A. Jeusfeld and M. Jarke and G.V. Zemanek and H. Huber}, journal = { IEEE Software}, month = {Mar}, number = 2, pages = {37-48}, volume = 13, year = 1996, url = {http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=506461}, issn = {0740-7459}, doi = {10.1109/52.506461}, abstract = {Stakeholder conflicts can be productive in requirements engineering. Capturing, monitoring, and resolving multiple perspectives is difficult and time consuming when done by hand. Our experience with ConceptBase shows that a simple but customizable metamodeling approach, combined with an advanced query facility, produces higher quality requirements documents in less time}, biburl = {http://www.bibsonomy.org/bibtex/2e058c0621b224adb2ab7aaf80f292895/neilernst}, keywords = {metamodels telos requirements} } @inproceedings{jureta08re, title = {Revisiting the Core Ontology and Problem in Requirements Engineering}, address = {Barcelona}, author = {Ivan J. Jureta and John Mylopoulos and Stéphane Faulkner}, booktitle = {International Conference on Requirements Engineering}, year = 2008, abstract = {In their seminal paper in the ACM Transactions on Software Engineering and Methodology, Zave and Jackson established a core ontology for Requirements Engineering (RE) and used it to formulate the “requirements problem”, thereby defining what it means to successfully complete RE. Given that stakeholders of the system-to-be communicate the information needed to perform RE, we show that Zave and Jackson’s ontology is incomplete. It does not cover all types of basic concerns that the stakeholders communicate. These include beliefs, desires, intentions, and attitudes. In response, we propose a core ontology that covers these concerns and is grounded in sound conceptual foundations resting on a foundational ontology. The new core ontology for RE leads to a new formulation of the requirements problem that extends Zave and Jackson’s formulation. We thereby establish new standards for what minimum information should be represented in RE languages and new criteria for determining whether RE has been successfully completed.}, biburl = {http://www.bibsonomy.org/bibtex/2971c9eea4bab0cff18d5f00d3e6510a8/neilernst}, keywords = {ontology requirements} } @phdthesis{Reuys2006, title = {Anforderungsbasierte Ableitung von Systemtestfall-Szenarien in der Software-Produktlinien-Entwicklung}, author = {Andreas Reuys}, publisher = {Logos Berlin}, school = {Universität Duisburg-Essen}, year = 2006, url = {http://www.amazon.de/gp/redirect.html%3FASIN=383251435X%26tag=ws%26lcode=xm2%26cID=2025%26ccmID=165953%26location=/o/ASIN/383251435X%253FSubscriptionId=13CT5CVB80YFWJEPWS02}, ean = {9783832514358}, asin = {383251435X}, isbn = {383251435X}, description = {MR: Die Referenzarbeit für auf ScenTED basierende Forschung.}, abstract = {Kurzbeschreibung Ziel der Einführung von Software-Produktlinien in einer industriellen Software-Entwicklung ist die Reduzierung der Entwicklungszeit und u2013kosten bei gleichzeitiger Steigerung der Qualität gegenüber der Einzelsystem-Entwicklung. Neben konstruktiven Entwicklungsphasen müssen in der Produktlinien-Entwicklung Maßnahmen zur Qualitätssicherung durchgeführt werden. Der Systemtest ist Bestandteil der analytischen Qualitätssicherungsmaßnahmen. Eine Aufgabe des Systemtests ist die Überprüfung der richtigen Umsetzung der funktionalen Anforderungen eines Systems. Dazu werden System-Testfälle aus den spezifizierten funktionalen Anforderungen abgeleitet. Die Anwendung existierender Test-Techniken, -Methoden und -Verfahren aus der Einzelsystem-Entwicklung ist durch die Konzepte der Produktlinien-Entwicklung, der Trennung von Domänen- und Applikations-Entwicklung sowie Variabilität, problematisch. Es ist ein effizientes Verfahren entwickelt worden, das den Systemtest in der Software-Produktlinien-Entwicklung unterstützt. An das Verfahren wurden die folgenden Anforderungen gestellt: Um einen geringen Aufwand bei dem Systemtest zu haben, soll die Wiederverwendung von Testfällen unterstützt werden. Die Wiederverwendung kann nur erfolgen, wenn die Nachvollziehbarkeit zwischen Anforderungen und Testfällen aufgezeichnet wurde. Durch wiederverwendete Anforderungen in Applikationen der Produktlinie können die wiederzuverwendenden Testfälle ermittelt werden. Zusätzlich soll eine frühe Validierung während des Domänen-Tests unterstützt werden, um Fehler frühzeitig zu ermitteln. Die Umsetzung der Anforderungen erfolgt im ScenTED-Verfahren (Scenario-based TEst case Derivarion) durch die folgenden Kernideen: - Erstellung von Testfällen mit Variabilität im Domänen-Test: Es wurden unterschiedliche Strategien zum Test in der Produktlinien-Entwicklung beurteilt. Es wurde eine Strategie umgesetzt, in der Testfälle für Gemeinsamkeiten und für die Varianten der Produktlinie ermittelt werden. Die Testfälle mit Variabilität enthalten die Ausprägungen der Varianten und können deshalb mit geringen Anpassungen beim Testen von Applikationen der Produktlinie verwendet werden. - Ableitung der Testfälle aus Domänen-Use-Cases und Szenarien: Die Ableitung der Testfälle erfolgt aus den Anforderungen. Die Anforderungen liegen als Domänen-Use-Cases und dazu gehörigen Szenarien vor. Diese Typen von Anforderungen sind eine gute Grundlage zur Ermittlung der Testfälle, da sie Abläufe beschreiben, die einem Systemtest sehr ähnlich sind. - Umsetzung eines Modell-basierten Vorgehens: Modell-basierte Vorgehen sind in der Einzelsystem-Entwicklung bekannt. Sie haben einige Vorteile, wie z.B. nachvollziehbare Mengen von Testfällen und Überprüfung der Anforderungen durch die Erstellung des Test-Modells. Als Test-Modell wurde ein Aktivitätsmodell verwendet, welches um Variabilität erweitert wurde. Zur Unterstützung des ScenTED-Vorgehens sind zwei Prototypen implementiert worden. Der erste Prototyp realisiert die Erstellung eines Test-Modells für den Domänen-Test. Der zweite Prototyp nimmt dieses Test-Modell als Eingabe, um daraus Testfall-Szenarien im Domänen-Test zu ermitteln. Das Verfahren wurde in zwei Fallstudien angewendet. Zum einen wurde eine imaginäre Produktlinie getestet. Zum anderen wurde das ScenTED-Verfahren erfolgreich in einer Kooperation mit der Firma Siemens AG in einer realen Entwicklung genutzt, um den Systemtest einer Software-Produktlinie zu unterstützen. Es ist einmal eine kleine Menge von Testfall-Szenarien ermittelt worden. Diese Testfall-Szenarien wurden zum Test von drei Applikationen der Produktlinie herangezogen. Die Testfälle wurden systematisch wiederverwendet, was den Aufwand zur Ermittlung der Testfälle reduzieren soll. }, biburl = {http://www.bibsonomy.org/bibtex/24336a1857dfafb495786b25d49c7600f/ist_spl}, keywords = {product software scenario line testing ScenTED requirements SSE based} } @inproceedings{Spillner2005, title = {Zuerst die Anforderungen testen! Wie soll das gehen?}, address = {Bad Kissingen}, author = {Andreas Spillner}, booktitle = {Tagungsband Requirements Days 2005}, month = {#jun#}, year = 2005, biburl = {http://www.bibsonomy.org/bibtex/272fd63cac1f4eec3f1f67c0fa62203b2/ist_spl}, keywords = {process W-Model testing requirements engineering} } @proceedings{yijun04, title = {From goals to aspects: discovering aspects from requirements goal models}, author = {Yijun Yu and J. Sampai and J. Mylopoulos}, journal = {Requirements Engineering Conference, 2004. Proceedings. 12th IEEE International}, pages = {33--42}, year = 2004, url = {http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=1335662}, id = {101891}, priority = {0}, biburl = {http://www.bibsonomy.org/bibtex/2b4592cb6ee2ce26c7050678f24584479/neilernst}, keywords = {aspects requirements openome goal} } @misc{Dalvik, title = {Dalvik Virtual Machine Internals}, author = {Dan Bornstein}, howpublished = {Google I/O 2008}, month = {Juni}, year = 2008, url = {http://de.youtube.com/watch?v=ptjedOZEXPM}, abstract = {Dalvik — the virtual machine with the unusual name — runs your code on Android. Join us to learn about the motivation for its design and get some details about how it works. You'll also walk away with a few tips for how to write code that works well with the platform. Be prepared for a deep dive into technical details. Questions encouraged!}, biburl = {http://www.bibsonomy.org/bibtex/262e1a333748559a836b2d7c1e67853a1/gron}, keywords = {Me:MastersThesis Dalvik VM Requirements embedded Optimization} } @inproceedings{cabot03uml, title = {Representing Temporal Information in UML}, address = {San Francisco}, author = {Jordi Cabot and Antoni Olivé and Ernest Teniente}, booktitle = {International Conference on the Unified Modeling Language (UML)}, editor = {Perdita Stevens and Jon Whittle and Grady Booch}, month = {October}, pages = {44-59}, publisher = {Springer}, series = {Lecture Notes in Computer Science}, volume = 2863, year = 2003, url = {http://springerlink.metapress.com/openurl.asp?genre=article&issn=0302-9743&volume=2863&spage=44}, description = {dblp}, abstract = {The UML is a non-temporal conceptual modeling language. Conceptual schemas in the UML assume that the information base contains the current instances of entity and relationship types. For many information systems, the above assumption is acceptable. However, there are some information systems for which that assumption is a severe limitation. This happens when the functions of the information system require the knowledge of past states of the information base. In this paper we extend the UML to define a set of temporal features of entity and relationship types, and to provide notational devices to refer to any past state of the information base. Using this extension, a designer may use the UML/OCL as if it were a temporal conceptual modeling language. We also present a method for the transformation of a conceptual schema in this extended language into a conventional one. The method can be automated, and we describe an implementation. The result of our transformation method is a conceptual schema that can be processed by ordinary CASE tools. }, biburl = {http://www.bibsonomy.org/bibtex/20f40844b28d787cb7f62c0384cf90fa8/neilernst}, keywords = {temporal ocl uml requirements} } @inproceedings{fabbrini07, title = {Controlling Requirements Evolution: a Formal Concept Analysis-Based Approach}, author = {F. Fabbrini and M. Fusani and S. Gnesi and G. Lami}, booktitle = {International Conference on Software Engineering Advances}, pages = 68, publisher = {IEEE Computer Society}, year = 2007, url = {http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=4299948}, isbn = {0-7695-2937-2}, doi = {http://dx.doi.org/10.1109/ICSEA.2007.24}, abstract = {Requirements evolve during the software development process. Requirements specification evolution determines changes both in terms of level of details and style of representation and it brings the requirements from the initial statement of the customer needs towards more detailed documents able to drive the software design, construction and verification. Controlling the evolution of requirements, usually written in natural language, is very important for the success of the whole software project because every step in the evolutionary path of requirements can introduce undesired changes or lacks of information. This paper describes an approach based on the Formal Concepts Analysis that allows a systematic and precise verification of the consistency among different stages of natural language requirements evolution.}, biburl = {http://www.bibsonomy.org/bibtex/2044a9c8af12b0b7b225c242f14df4159/neilernst}, keywords = {requirements evolution} } @inproceedings{Nebut2003b, title = {Requirements by Contracts allow Automated System Testing}, address = {Washington, DC, USA}, author = {Cl\'{e}mentine Nebut and Franck Fleurey and Yves Le Traon and Jean-Marc J\'{e}z\'{e}quel}, booktitle = {ISSRE '03: Proceedings of the 14th International Symposium on Software Reliability Engineering}, pages = 85, publisher = {IEEE Computer Society}, year = 2003, url = {http://portal.acm.org/citation.cfm?coll=GUIDE&dl=GUIDE&id=952350}, isbn = {0-7695-2007-3}, description = {Requirements by Contracts allow Automated System Testing}, abstract = {Use-cases and scenarios have been identified as good inputsto generate test cases and oracles at requirement level.Yet to have an automated generation, information is missingfrom use cases and sequence diagrams, such as the exactinputs of the system, and the ordering constraints betweenthe use case. The contribution of this paper is then two-fold.First we propose a contract language for functionalrequirements expressed as parameterized use cases. Thenwe provide a method, a formal model and a prototype toolto automatically derive both functional and robustness testcases from the requirements enhanced with contracts. Westudy the efficiency of the generated test cases on a casestudy.}, biburl = {http://www.bibsonomy.org/bibtex/2a088cb171d50dfe3aabd477fbe68e32d/ist_spl}, keywords = {automated systemtest coverage contracts Use-Cases UML LTS Criteria requirements diagrams activity} } @techreport{Denger2003a, title = {Guidelines - creating use cases for embedded systems}, address = {Kaiserslautern}, author = {Christian Denger and Barbara Paech and Sebastian Benz}, institution = {Fraunhofer IESE}, number = {078.03/E}, year = 2003, url = {http://publica.fraunhofer.de/starweb/servlet.starweb?path=pub.web&search=N-18701}, abstract = {In the automotive domain, the increasing complexity of software demands a requirements process that is tailored to the needs of the stakeholders involved in the development process. UCs and Statecharts are commonly used as specification techniques in many projects. In this report we present guidelines to derive UCs for embedded systems in a systematic, repeatable und verifiable way. We illustrate them with a case study for developing an electronic control unit for a car. These guidelines have been collected from literature and from several case studies. In the second part of the report we describe in detail an evaluation of these guidelines in the context of a Praktikum at the University of Kaiserslautern in summer term 2003.}, biburl = {http://www.bibsonomy.org/bibtex/2172c97f5433a4c64008efd156a8cdd03/ist_spl}, keywords = {QUASAR specification data Use-Cases requirements} }