Systems Analysis and Design Chapter 3: Identifying User Stories and Use Cases

Vocabulary flashcards covering the key concepts of user stories, use cases, and identification techniques from Systems Analysis and Design 7th Edition Chapter 3.

User Story

A $1$-sentence description of a work-related task done by a user to achieve some goal or result, typically following the template: 'As a I want to so that '.

Acceptance Criteria

The features that must be present at the completion of a task to identify that a user story has been successfully implemented.

Use Case

An activity that the system performs, usually in response to a request by a user, used to define functional requirements.

Functional Decomposition

The process by which analysts decompose the system into a set of use cases.

User Goal Technique

A technique to identify use cases by identifying all potential categories of users and interviewing them to describe tasks where the computer can help them achieve specific goals.

Event Decomposition Technique

A comprehensive technique for identifying use cases by identifying the events to which the system must respond.

Event

Something that occurs at a specific time and place, can be described, and should be remembered by the system.

External Event

An event that occurs outside the system, usually initiated by an external agent or actor, such as a customer buying a product.

Temporal Event

An event that occurs as a result of reaching a point in time, such as the need to produce payroll or management reports.

State Event

An event that occurs when something happens inside the system that triggers a process, such as reaching a reorder point for an inventory item.

Perfect Technology Assumption

The assumption that technology and people have no limits, used during analysis to avoid including system controls like login or backup until the design phase.

Elementary Business Process (EBP)

A fundamental business process performed by $1$ person, in $1$ place, in response to a business event, which identifies the right level of analysis for a use case.

Brief Use Case Description

An often $1$-sentence description showing the main steps within a use case.

Use Case Diagram

A UML model used to graphically show use cases and their relationships to actors.

Unified Modeling Language (UML)

The standard for diagrams and terminology used for developing information systems.

Actor

The UML name for an end user who interacts with the system.

Automation Boundary

The boundary between the computerized portion of the application and the users who operate the application.

<> relationship

A relationship between use cases where one use case is stereotypically included within another, similar to a called subroutine.