http://www.bibsonomy.org/burst/concept/tag/diagrams+modelBibSonomy BuRST Feed for /concept/tag/diagrams+model2008-12-02T01:34:16+01:00Automating Mappings between Use Case Diagrams and Feature Models for Software Product Lineshttp://www.bibsonomy.org/bibtex/2fa8b293e480a80239c6dd7aec83886c7/ist_splist_spl2008-08-27T15:05:25+02:00product model QVT OCL line feature Use-Cases UML transformation diagrams <span style="color:#555555;">Alexandre <a href="http://www.bibsonomy.org/author/Braganca">Braganca</a> and Ricardo J. <a href="http://www.bibsonomy.org/author/Machado">Machado</a> </span><em>SPLC '07: Proceedings of the 11th International Software Product Line Conference, </em><em>page3--12. </em><em>Washington, DC, USA, </em><em>IEEE Computer Society, </em>(<em>2007</em>)Wed Aug 27 15:05:25 CEST 2008Washington, DC, USASPLC '07: Proceedings of the 11th International Software Product Line Conference3--12Automating Mappings between Use Case Diagrams and Feature Models for Software Product Lines2007product model QVT OCL line feature Use-Cases UML transformation diagrams 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.DBLP Record 'journals/re/KostersSW01'http://www.bibsonomy.org/bibtex/2e1527a0313d851fe11d7bef3d21b8612/ist_splist_spl2008-07-29T12:52:47+02:00model class testing Use-Cases UML requirements engineering diagrams activity <span style="color:#555555;">Georg <a href="http://www.bibsonomy.org/author/K{\&#034;o}sters">K&#246;sters</a> and Hans-Werner <a href="http://www.bibsonomy.org/author/Six">Six</a> and Mario <a href="http://www.bibsonomy.org/author/Winter">Winter</a> </span><em>Requir. Eng.</em><em>6(1):3-17</em>(<em>2001</em>)Tue Jul 29 12:52:47 CEST 2008Requir. Eng.13-17Coupling Use Cases and Class Models as a Means for Validation and Verification of Requirements Specifications62001model class testing Use-Cases UML requirements engineering diagrams activity In many applications, especially from the business domain, the requirements specification mainly deals with use cases and class models. Unfortunately, these models are based on different modelling techniques and aim at different levels of abstraction, such that serious consistency and completeness problems are induced. To overcome these deficiencies, we refine activity graphs to meet the needs for a suitable modelling element for use case behaviour. The refinement in particular supports the proper coupling of use cases via activity graphs and the class model. The granularity and semantics of our approach allow for a seamless, traceable transition of use cases to the class model and for the verification of the class model against the use case model. The validation of the use case model and parts of the class model is supported as well. Experience from several applications has shown that the investment in specification, validation and verification not only pays off during system and acceptance testing but also significantly improves the quality of the final product.MR: Besonders wertvoll sind die Kapitel: Chapter 12 discusses the importance of mapping the use cases to the analysis object model. [object models describes the static structure of the system] Techniques such as CRUD matrixes, object to use case tables, and sequence diagrams are outlined. Es wird die Idee vermittelt, dass die Anforderungsanalyse beides benötigt: Use-Case-Modellsicht und die Sicht auf statisches Objektmodell (mit Objektinteraktionen und statischen Beziehungen). Chapter 13 discusses the concept and utilization of scenarios to complement the use case model. The final phase of any software engineering process is testing. Chapter 14 discusses testing and documenting the system and the role use cases play in driving these activities.http://www.bibsonomy.org/bibtex/282c4fe6f09a6ea20a4168ad50d6dbaa7/ist_splist_spl2008-07-21T11:53:43+02:00software model development sequence modeling Use-Cases object UML requirements engineering scenarios diagrams <span style="color:#555555;">Frank <a href="http://www.bibsonomy.org/author/Armour">Armour</a> and Granville <a href="http://www.bibsonomy.org/author/Miller">Miller</a> </span><em>The Addison-Wesley Object Technology Series </em><em>Addison-Wesley Professional, </em>(<em>2001</em>)Mon Jul 21 11:53:43 CEST 2008The Addison-Wesley Object Technology SeriesAdvanced Use Case Modeling: Software Systems2001software model development sequence modeling Use-Cases object UML requirements engineering scenarios diagrams Amazon.de: The Object Constraint Language: Getting your models ready for MDA (Addison-Wesley Object Technology): Jos Warmer, Anneke Kleppe: Englische Bücherhttp://www.bibsonomy.org/bibtex/2aea06bad3e6a351e3140a3dd04330b92/ist_splist_spl2008-06-25T16:38:54+02:00model MDA OCL sequence Use-Cases UML diagrams activity <span style="color:#555555;">Jos <a href="http://www.bibsonomy.org/author/Warmer">Warmer</a> and Anneke <a href="http://www.bibsonomy.org/author/Kleppe">Kleppe</a> </span><em>Addison Wesley, </em><em>2. A. edition, </em>(<em>2003</em>) <em>MR: Referenz f&amp;#252;r OCL Wertvoll: Es wird gezeigt wie mit OCL Modelle gebaut werden. MDA eher nur am Rande erkl&amp;#228;rt Wichtigster Satz (Kapitel 3.2): T<span class="info">...<span>MR: Referenz f&#252;r OCL Wertvoll: Es wird gezeigt wie mit OCL Modelle gebaut werden. MDA eher nur am Rande erkl&#228;rt Wichtigster Satz (Kapitel 3.2): The use of OCL strongly relies on the types (classes, datatypes, and so on) defined in a UML class diagram. This diagram should be build first.</span></span> . </em>Wed Jun 25 16:38:54 CEST 20082. A.MR: Referenz für OCL Wertvoll: Es wird gezeigt wie mit OCL Modelle gebaut werden. MDA eher nur am Rande erklärt Wichtigster Satz (Kapitel 3.2): The use of OCL strongly relies on the types (classes, datatypes, and so on) defined in a UML class diagram. This diagram should be build first.The Object Constraint Language: Getting your models ready for MDA2003model MDA OCL sequence Use-Cases UML diagrams activity "In this thoroughly revised edition, Jos and Anneke offer a concise, pragmatic, and pedagogic explanation of the Object Constraint Language (OCL) and its different applications. Their discussion of OCL's potential role in Model Driven Architecture (MDA) is timely and offers great insight into the way that UML can be taken to the next level of automated software development practice. I highly recommend this book to anyone who is looking to get the most out of UML." —Shane Sendall, PhD, Senior Researcher, Swiss Federal Institute of Technology in Lausanne The release of Unified Modeling Language (UML) 2.0 places renewed emphasis on the Object Constraint Language (OCL). Within UML, OCL is the standard for specifying expressions that add vital information to object-oriented models and other object-modeling artifacts. Model Driven Architecture (MDA) relies on OCL to add the level of programming detail necessary to enable platform-specific models (PSM) to communicate with platform-independent models (PIM). This book is a practical, accessible guide to OCL for software architects, designers, and developers. Much care has been taken during the redesign of OCL to ensure that the syntax remains readable and writable by the average software modeler. The Object Constraint Language, Second Edition, utilizes a case study to show how to exercise these compact but powerful expressions for maximum effect. This newly updated edition # Explains why OCL is critical to MDA--and why UML alone is not enough # Introduces an SQL-like syntax to OCL # Defines the new language constructs of OCL 2.0 # Demonstrates how OCL can be incorporated into code # Shares tips and tricks for applying OCL to real-world modeling challenges—showing which can be solved with UML and which require OCL Using a combination of UML and OCL allows developers to realize the effective, consistent, and coherent models that are critical to working with MDA. The authors' pragmatic approach and illustrative use of examples will help application developers come quickly up to speed with this important object-modeling method—and will serve as a ready reference thereafter.Transformation methodology for UML 2.0 activity diagram into colored Petri netshttp://www.bibsonomy.org/bibtex/2ea43d6d3a99db3fabdcdba40c3fe560c/ist_splist_spl2008-06-05T18:27:12+02:00model petri colored UML net transformation diagrams activity <span style="color:#555555;">U. <a href="http://www.bibsonomy.org/author/Farooq">Farooq</a> and C. P. <a href="http://www.bibsonomy.org/author/Lam">Lam</a> and H. <a href="http://www.bibsonomy.org/author/Li">Li</a> </span><em>ACST'07: Proceedings of the third conference on IASTED International Conference, </em><em>page128--133. </em><em>Anaheim, CA, USA, </em><em>ACTA Press, </em>(<em>2007</em>)Thu Jun 05 18:27:12 CEST 2008Anaheim, CA, USAACST'07: Proceedings of the third conference on IASTED International Conference128--133Transformation methodology for UML 2.0 activity diagram into colored Petri nets2007model petri colored UML net transformation diagrams activity Symbolic model checking of UML activity diagramshttp://www.bibsonomy.org/bibtex/2b04b2dcf818c31ae7290c04f2016ed33/ist_splist_spl2008-06-02T11:26:26+02:00model symbolic UML NuSMV diagrams checking activity <span style="color:#555555;">Rik <a href="http://www.bibsonomy.org/author/Eshuis">Eshuis</a> </span><em>ACM Trans. Softw. Eng. Methodol.</em><em>15(1):1--38</em>(<em>2006</em>)Mon Jun 02 11:26:26 CEST 2008New York, NY, USAACM Trans. Softw. Eng. Methodol.11--38Symbolic model checking of UML activity diagrams152006model symbolic UML NuSMV diagrams checking activity Two translations from activity diagrams to the input language of NuSMV, a symbolic model verifier, are presented. Both translations map an activity diagram into a finite state machine and are inspired by existing statechart semantics. The requirements-level translation defines state machines that can be efficiently verified, but are a bit unrealistic since they assume the perfect synchrony hypothesis. The implementation-level translation defines state machines that cannot be verified so efficiently, but that are more realistic since they do not use the perfect synchrony hypothesis. To justify the use of the requirements-level translation, we show that for a large class of activity diagrams and certain properties, both translations are equivalent: regardless of which translation is used, the outcome of model checking is the same. Moreover, for linear stuttering-closed properties, the implementation-level translation is equivalent to a slightly modified version of the requirements-level translation. We use the two translations to model check data integrity constraints for an activity diagram and a set of class diagrams that specify the data manipulated in the activities. Both translations have been implemented in two tools. We discuss our experiences in applying both translations to model check some large example activity diagrams.http://www.bibsonomy.org/bibtex/22194a8b05b7731e5501e819634045914/michaelmichael2007-06-28T16:59:01+02:00model Diagrams <span style="color:#555555;">A. <a href="http://www.bibsonomy.org/author/Bakker">Bakker</a> and M.H.G. <a href="http://www.bibsonomy.org/author/Hoffmann">Hoffmann</a> </span><em>Educational Studies in Mathematics</em><em>60(3):333-358</em><em>November2005. </em>Thu Jun 28 16:59:01 CEST 2007Educational Studies in MathematicsNovember3333-358Diagrammatic Reasoning as the Basis for Developing Concepts: A Semiotic Analysis of Students' Learning about Statistical Distribution602005model Diagrams In recent years, semiotics has become an innovative theoretical framework in mathematics education. The purpose of this article is to show that semiotics can be used to explain learning as a process of experimenting with and communicating about one's own representations (in particular ‘diagrams') of mathematical problems. As a paradigmatic example, we apply a Peircean semiotic framework to answer the question of how students develop a notion of ‘distribution' in a statistics course by ‘diagrammatic reasoning' and by forming ‘hypostatic abstractions', that is by forming new mathematical objects which can be used as means for communication and further reasoning. Peirce's semiotic terminology is used as an alternative to concepts such as modeling, symbolizing, and reification. We will show that it is a precise instrument of analysis with regard to the complexity of learning and communicating in mathematics classrooms.