Specifying use case behavior with interaction models.

Abstract

Functional requirements for information systems can be modeled through use cases. Furthermore, use case models have been successfully used in broader contexts than software engineering, as systems engineering. Even if small systems may be modeled as a set of use cases, when large systems requirements are modeled with a plain use case model several difficulties arise. Traditionally, the behavior of use cases has been modeled through textual specifications. In this paper we present an alternate approach based on interaction modeling. The behavior modeling has two variants (one for UML 1.x and one for UML 2.0). We also integrate our behavior modeling with standard use case relationships.

Engineering the Development Process for User Interfaces: Toward Improving Usability of Mobile Applications

“…The necessity of integrating HCI and SE techniques has been expressed in several studies such as [9], [12], [16], [18], [19], [20], [21], [22], [23], [24], [25], [26], [27], [28]. Some of them manage a complete view of the development process, covering a general approach, but not oriented to a specific type of applications and platforms.…”

“…Other work with similar scope is presented in [22]. This model also emphasizes on the use case artifact as a tool to express the task analysis.…”

M-4REuse

“…Despite of the different efforts and results already obtained in the Requirements Engineering research area, to deal with reuse of existing projects (knowledge, experience and artifacts) [11], there are still many challenges [6]. An example is the specification of use cases, an extremely repetitive and exhausting process [12]. An illustrative example of functionality's repetition is the specification of an "object reservation" within different systems (for example: car reservation, bicycle reservation, electronics reservation, equipment reservation); all these systems include common use cases such as: client authentication, client and customer registering, reservation, and payment.…”