On the other hand the benefit of use case modeling is mainly rooted in its semi-formal nature. This is a non-trivial problem, because ensuring consistency between a UML model and the textual use case descriptions requires a certain degree of formality in the textual descriptions. In order to provide automated consistency checking between a UML use case model and its corresponding set of textual descriptions, the textual representations of the use case relationships contained in the UML model must be algorithmically and efficiently identifiable. Since the two views evolve in parallel during the process of use case modeling, ensuring consistency between them is an ongoing task. These two parts depict different views on the overall use case model and should of course not contradict each other. One part is a UML model, capturing the use cases and their relationships, the other part is a set of textual descriptions of the behavior represented by these use cases. Thus, the so-called use case model is actually a composite model consisting of two parts. proposed in, which are most widely used, are not addressed.Īs a consequence, when applying a UML-based development approach, use cases are first identified and structured by means of UML use case diagrams and then described in detail through textual descriptions. While the UML offers various diagram types (state machine, sequence, activity) to describe internal behavior, textual descriptions, e.g. There is a manifold of notations to describe the behavior captured by use cases in detail. Today, the Unified Modeling Language is a widely accepted standard defining the central use case modeling concepts. Since their invention by Ivar Jacobson in 1986, and although having some deficiencies use cases have gained wide-spread acceptance as a means to describe interactions between a system and its environment. With NaUTiluS we present an extensible, Eclipse-based toolkit, which offers integrated UML use case modeling support, as well as editing capabilities for their textual descriptions. Being formalized, consistency between UML-based use case representations and their textual descriptions can be automatically ensured. ![]() Hence, the known benefits of natural language use case descriptions are preserved. ![]() ![]() While being primarily targeted at supporting requirements engineers in creating consistent use case models, the metamodel defines a textual representation of use case behavior that is easily understandable for readers, who are unaware of the underlying metamodel. In this paper, we present a metamodel for textual use case descriptions, structurally conforming to the UML, to specify the behavior of use cases in a flow-oriented manner. Veit Hoffmann, Horst Lichter, Alexander Nyßen and Andreas Walter Towards the Integration of UML- and textual Use Case Modeling
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |