Software Requirements Analysis Chapter 3

An event that happens outside the system, usually triggered by an external source.

An event triggered by a specific point in time.

An event happening inside the system that starts an action.

A situation or scenario where a system performs a specific task.

A description of the actions involved in a use case, showing the steps taken.

The process of finding and eliminating duplicate entries in a dataset, particularly when these duplicates have similar purposes or functionalities. This helps ensure data consistency and accuracy.

Process of categorizing potential users based on their roles within an organization (e.g., operations, management, executives). This helps tailor the system's functionalities to meet specific user needs.

Identifying the specific objectives a user aims to achieve by using a new system. This includes both existing needs and opportunities for enhanced features that add value.

A significant event that triggers a system response. It's something specific that happens at a particular time and location, and the system must remember and react to it.

A request from a customer for specific details on a product is an external event.

Internal outputs are reports generated within the system, like management summaries or operational details.

An internal output event occurs when a report is generated at a specific time.

External outputs are like bills, reminders, and status reports sent outside of the system.

Events triggered by time are often related to deadlines, like sending out bills or statements.

Tracing a sequence of transactions helps understand the flow of events and their impact on the system.

Multiple events can occur as a result of a single transaction, creating a complex chain of interaction.

An activity that the system executes, often in response to a user request.

The use cases define the system's functionalities. They are essential in understanding what the system should do.

The process of breaking down a system into its individual use cases.

A technique used to identify use cases by focusing on the goals of users of the system.

A technique used to identify use cases by analyzing events that might trigger actions within the system.

A technique used to identify use cases by asking users about the tasks they need the system to perform and then refining these tasks into specific goals.

A list of potential users of the system, categorized by their roles or functions.

The process of identifying use cases based on real stories about the system's functionality.

Identifying the specific use case triggered by an external event.

Determining the exact point in time when a temporal event triggers a use case.

Identifying the use case triggered by a state event and the subsequent system state change.

Verifying the necessity of identified events and use cases using the principle of perfect technology.

Excluding routine system management tasks like login, logout, password changes, and database restoration during event decomposition.

A short, simple description of a user's work-related task that aims to achieve a specific goal or result.

A sentence describing the user's desired functionality. It starts with 'I want to...' and explains what the user wants to achieve with the software.

A sentence explaining the user's motivation for using the software feature. It starts with 'so that...' and describes the benefit the user will gain.

A template used for creating user stories. It states: 'As a [user type], I want to [functionality] so that [value]' to describe the user, the desired feature, and its benefit.

Specific features that must exist within the system for the user story to be considered complete. They are usually written as a list of 'Given, When, Then' statements.

Describes the user category for whom the functionality is being developed. It helps to determine if the feature is being built for the right user.

A section in the 'Given, When, Then' format that describes the initial state or condition of the system before the user's action.

A section in the 'Given, When, Then' format that describes the user's action that triggers the expected outcome.

A section in the 'Given, When, Then' format that describes the expected outcome or result after the user's action.