Systems Analysis Chapter 5

Detailed descriptions of how a system should work in a particular scenario

Visual models that show flow of activities for a use case, highlighting complexities and decision points.

Diagrams highlighting inputs and outputs for a use case, showing system messages.

Show the states and transitions of an object or domain class over time.

What the system does, described by use cases and associated diagrams.

Conditions that must be true before a use case can begin.

Conditions that are true after a use case completes successfully.

Users (or other systems) interacting with a system.

Business practice of selling products not currently in stock, promising delivery once inventory replenishes.

A specific type of sequence diagram focusing on a single object (the system) to illustrate input and output messages for a use case.

Describes messages using a format that includes conditions (true/false), the message name, input parameters, and returned data.

Indicates a repeating message or set of messages, often within the diagram.

A true/false condition [ ] determining the sending of a message. If the condition is false, the message is not sent.

SSD message format shows repeating message/function(parameters), and variable-returning data when a message is fulfilled/sent

Steps to create a system sequence diagram include identifying input messages according to the use case flow of activities or activity diagram.

A structural diagram that shows the classes, attributes, and relationships in a system.

A diagram that shows the interactions between actors and the system, focusing on system functionality.

A dynamic diagram that shows the sequence of interactions between objects in a system.

A dynamic diagram illustrating the flow of activities within a use case, highlighting decisions and loops.

A dynamic diagram that shows how an object (or class) changes state over time.

A detailed textual description of how a system behaves when an actor performs a use case.

The event that initiates the execution of a use case by an actor.

Conditions that must be true before a use case can begin.

Conditions that are true after a use case completes successfully.

Users or other systems that interact with a system to perform a use case.

A sequence of steps describing the actions performed by the system or an actor in a use case.

Conditions that indicate an error or unusual situation that might occur during a use case.

A way of describing messages sent from external actors to a system, using verb-noun phrases to show what the system should do, and including necessary parameters.

Special rules or limitations about inputs received by the system, including potentially looping or conditional inputs.

Values a system returns after processing a message, either included in the message itself (e.g., calculations) or as separate outputs.

A specific condition or situation for an object (or system) at a certain point in time.

The change from one state to another in an object's lifecycle.

A true or false test that decides if a transition in a state machine diagram can happen or not.

A state containing other states and transitions within it, allowing for more complex behaviors.

Multiple independent paths within a composite state.

A special state in a state machine diagram that marks the start of a process.

The initial, starting state of an object or process.

The state reached after a transition.

A diagram that illustrates the states and transitions of an object or class over time.

A systematic process for creating state machine diagrams, involving reviewing classes, identifying states, transitions, and expanding transitions with details.

Represents the different states that a 'SaleItem' object can be in, like 'active', 'backordered', or 'archived'.

Represents the different conditions that a 'Sale' object can be in; order placement, for example.

Combining different models (use cases, activity diagrams, domain models, state machine diagrams) to create a complete system understanding.

Specific factors influencing or creating the need for a project. Often documented, but not defined in the provided context.

Describes what a system does, using use cases and diagrams.

Specific scenarios detailing how a system functions.

Visual models showing activities in a use case, highlighting complexity.

Diagrams focusing on system input/output messages in use cases.

Illustrate object states and transitions over time between use cases.

Conditions needed before a use case starts.

Conditions true after a use case completes successfully.

Users or systems interacting with the system.

Limitations and rules impacting a project.

Software to manage requirements, changes, and traceability.