Part IV. Use-Case Blueprints

This part of the book presents a collection of use-case blueprints of how to model various common usages of systems. We have encountered models of these usages in many different use-case models over the years, and the blueprints in this part of the book are the result of distilling these models into general models of how to express these usages with use cases. The proposed blueprints are not the only ways to model the problems at hand, but they constitute models that we have found useful, understandable, and (last, but not least) correct. All blueprints solving the same modeling problem are grouped into a single chapter where they are presented and discussed.

All chapters in this part are organized in the same way:

  • Name of modeling problem—A descriptive name of the problem in a few words

  • Problem—A short description of the modeling problem

  • Characteristics—States whether the solutions are simple or complex, whether the modeling problem is common or infrequent

  • Keywords—A list of keywords characterizing the modeling problem

  • For each blueprint

    • Name—A descriptive name of the blueprint

    • Model—A use-case model of the blueprint

    • Description—A description of the blueprint model

    • Applicability—States when the blueprint should be used

  • Discussion—A comprehensive discussion on the modeling problem and the different solutions

  • Example—An example of the modeling problem and one or several of its solutions, including use-case descriptions

  • Analysis model—A platform-independent class model providing a realization of the use cases in the blueprint use-case models

The chapters containing the use-case blueprints are sorted alphabetically within this part. For each chapter, we list its contained blueprints together with the descriptions of the modeling problems they address.

Chapter 27. Access ControlThe system is required to include some kind of access security. Access to the information in the system and to the services of the system is stated by the specific access rights given to the individual user.

  • Access ControlEmbedded Check

  • Access ControlDynamic Security Rules

  • Access ControlExplicit Check

  • Access ControlInternal Assignment

  • Access ControlImplicit Details

Chapter 28. Future TaskA task is registered in the system at one point of time, although the actual performance of the task is to take place at some later time.

  • Future TaskSimple

  • Future TaskSpecialization

  • Future TaskExtraction

  • Future TaskPerformer Notification

Chapter 29. Item Look-UpThe system is to make it possible for the users to search for items in the system. This look-up procedure can be autonomous, but it can also be used in other use cases.

  • Item Look-UpStandalone

  • Item Look-UpResult Usage

  • Item Look-UpOpen Decision

Chapter 30. Legacy SystemThe system is to include or make use of an already existing system.

  • Legacy SystemEmbedded

  • Legacy SystemSeparate

Chapter 31. Login and LogoutThe users must register or identify themselves before using services offered by the system.

  • Login and LogoutStandalone

  • Login and LogoutAction Addition

  • Login and LogoutReuse

  • Login and LogoutSpecialization

  • Login and LogoutSeparate

Chapter 32. Message TransferA user uses the system to send a message to another user.

  • Message TransferDeferred Delivery

  • Message TransferImmediate Delivery

  • Message TransferAutomatic

Chapter 33. Passive External MediumThe system is to monitor or control an external medium that in itself is passive (for example, the surrounding air or a fluid).

  • Passive External Medium

Chapter 34. Report GenerationThe system is to contain a collection of templates for generating different kinds of reports that present information in accordance with the definition given in the templates. The templates also define how a report is to be formatted and similar matters.

  • Report GenerationSimple

  • Report GenerationSpecialization

  • Report GenerationDynamic Templates

Chapter 35. Stream InputAn actor provides a stream of input to the system, and the handling of this input is to be described by use cases. The solution to this problem depends on whether the stream consists of discrete values or of continuous values.

  • Stream InputDiscrete

  • Stream InputAnalog

Chapter 36. TranslatorThe system is to receive an input stream and produce an output stream based on some translation rules.

  • TranslatorStatic Definition

  • TranslatorDynamic Rules

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.20.234.120