Use case activity diagrams7/31/2023 Nebut, C., Fleurey, F., Le Traon, Y., Jezequel, J.M.: Automatic test generation: A use case driven approach. In: ICSE Workshop on Modeling in Software Engineering (2009) Mustafiz, S., Kienzle, J., Vangheluwe, H.: Model transformation of dependability-focused requirements models. Kruchten, P.: The Rational Unified Process: An Introduction. Kermeta: Kermeta metaprogramming environment. Research, Management and Applications (2006) Ilieva, M.G., Ormandjieva, O.: Models Derived from Automatically Analyzed Textual User Requirements. In: Czarnecki, K., Ober, I., Bruel, J.-M., Uhl, A., Völter, M. Gutiérrez, J.J., Clémentine, N., Escalona, M.J., Mejías, M., Ramos, I.M.: Visualization of Use Cases through Automatically Generated Activity Diagrams. Gomaa, H.: Designing Concurrent, Distributed, and Real-Time Applications with UML. Eng. 61, 433–448 (2007)įowler, M.: UML distilled: a brief guide to the standard object modeling language. 55-63 (2005)Įclipse Foundation: Eclipse Modeling Frameworkįliedl, G., Kop, C., Mayr, H.C., Salbrechter, A., Vöhringer, J., Weber, G., Winkler, C.: Deriving static and dynamic concepts from software requirements using sophisticated tagging. Prentice-Hall, Englewood Cliffs (2009)Ĭhen, T.Y., Tang, S.F., Poon, P.L., Tse, T.H.: Identification of categories and choices in activity diagrams. Routledge (1992)īruegge, B., Dutoit, A.H.: Object-Oriented Software Engineering Using UML, Patterns, and Java. Addison-Wesley, Boston (2002)īrown, E.K., Miller, J.E.: Syntax: a linguistic introduction to sentence structure. ICSE (2004)īittner, K., Spence, I.: Use Case Modeling. 830-1998, IEEE Standard for Software Requirement Specification (1998)īerenbach, B., Inc, S.C.R., Princeton, N.J.: The evaluation of large, complex UML analysis and design models. Our analysis also shows that our approach outperforms existing academic approaches and commercial tools. ![]() The results show that high quality activity diagrams can be generated. Our approach is implemented in a tool, which we used to perform five case studies. Data flow information can also be generated and added to these activity diagrams. In this paper, we propose an approach to automatically generate activity diagrams from use cases while establishing traceability links. Additionally, traceability could be established through automated transformation, which could then be used for instance to relate requirements to design decisions and test cases. Therefore the automated support for the transition from use cases to activity diagrams would provide significant, practical help. Use cases are commonly used to structure and document requirements while UML activity diagrams are often used to visualize and formalize use cases, for example to support automated test case generation.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |