Use Case Modelling

Specify the functional requirements and objectives for the development of an application.

Each type of use is defined as a use case. Initital situation and initital conditions are described. Only actions and events that are recognizable from the user's point of view may be described.

To describe the specified run of a use case, the actions and interaction steps necessary for certain tasks are defined in modular and easy-to-understand narrative texts.

The content of a use case looks like this: name and version, short description, actors involved, preconditions, postconditions, execution (scenario description), exceptions, comments, user interface

Preconditions: Precise knowledge and definition of the (different) target group(s). Collection of extensive data about the target group(s), e.g. with the help of suitable methods (requirements analysis with KANO, focus groups, onsite survey, panel survey, personas, in-depth interviews, usability test in the laboratory)

Actors and use cases are determined on the basis of a comprehensive target group analysis. The design of the individual use cases takes place in modular and easy-to-understand narrative texts. When creating the use cases themselves, no actual users are involved. At a minimum, at least two usability experts are required for a use case workshop (for example, customer and analyst).

Anything to improve with the method description? Just send an e-mail with your suggestion. Thank you!

HIDE GENERAL TAGSSHOW GENERAL TAGS

When creating the use cases, no actual users (subjects) are required
Helpful or necessary for the preparation of a tender and system specifications
Detailed description of the behavior of the system from the user's point of view
Overview of the functionality of a system
Comparison possibility (during and after the end of the development process) of current status with the objectives initially defined (actual target comparison) in terms of quality assurance
no material costs
Use Cases are relatively specific and have a high significance.
The end result in the form of fully formulated applications is very helpful.

Depending on requirements, relatively high effort: For less complex applications (in terms of the number of possible or planned functions and contents), the creation of modeled use cases incl. prioritization takes about 3 to 5 days (Source: eResult)
Design and Review Use Case model can also last between 5 and 15 man days (Source: "Usability Engineering kompakt").
The (internal) time required for the formulation is relatively high.
The originality is limited, it is at best a well-structured text document.

Anything to improve with the method description? Just send an e-mail with your suggestion. Thank you!

Project phase

Focus

Topic

Activities

Project phase

Focus

Topic

Activities

Use Case Modelling