Software Requirements Analysis II

A model that shows how software responds to external events or stimuli.

Describes the sequence of interactions within the system, driven by events that trigger actions.

A diagram that visualizes the possible states of a system and how it transitions between them based on events.

Analyzing all use-cases to understand interactions and identify events that cause changes.

Creating a state diagram to summarize the system's behavior and transitions based on events.

Classes that are directly involved in the solution and will be implemented in the system's code. These classes are essential for the system to function.

Classes that describe the problem and its context, but are not directly implemented in the system's code. They help understand the problem and how the system will interact with it.

Classes that represent external entities such as other systems, devices, or people who interact with the system. They provide input or receive output from the system.

Classes that model things such as reports, displays, letters, or signals. They represent the information domain of the problem.

Classes that represent occurrences or events that happen within the system. They model the actions or processes happening within the system.

Classes that model the roles played by people interacting with the system. They represent the different functions performed by users.

Classes that represent organizational units such as divisions, groups, or teams. They show how the system is organized and how users are grouped.

Classes that represent places relevant to the problem and the functionality of the system. They create context and help understand the system's environment.

Represents the current status of an object's attributes.

Represents the current status of an object undergoing a transformation or processing.

A period of time where the object is inactive and waiting for an event.

An action that causes an object to move from one state to another.

An event that triggers a transition, causing the object to change state.

The condition that must be met for a transition to occur.

An action that is performed when a transition occurs.

A hierarchical arrangement of data elements, representing relationships between them, resembling a tree with branches.

A visual representation of how different components in a system interact with each other, often used in software development.

Describes the actions a user takes to achieve a goal within a system, often presented as a narrative.

Visually illustrates the order of steps in a process or interaction, showing how objects communicate with each other.

Describes the user interactions with a WebApp, including how they navigate, input data, and view information.

The process of defining the operations that a WebApp performs on its content based on user interactions and use cases.

Analyzing the system environment, infrastructure, and dependencies where a WebApp will be hosted, including hardware, software, and networks.

Situations where analysis and design activities are intertwined and occur together.

These are situations where a dedicated analysis phase is essential, particularly for large or complex projects involving multiple stakeholders.

Elements extracted from use cases that represent the data or information managed and presented by the WebApp.

The structure and connections among content objects in a WebApp, shown through diagrams or models.

The functional model in software development focuses on the observable actions performed by a web application for users and the internal operations within analysis classes that support those actions.

An activity diagram is a graphical representation of processing flow. It illustrates the sequence of actions and their dependencies, including branching and parallel execution paths.

An activity diagram can depict the flow of processing related to user observable functionality, such as the steps a web app takes to fulfill a user request.

Activity diagrams can also represent the internal operations within analysis classes, showing how objects interact and process data to execute behaviors.

In the context of a web application, the 'total cost' calculation would involve actions such as retrieving product prices from a database, calculating shipping costs, applying discounts, and accumulating the final cost.

When representing actions like calculating the total cost, an activity diagram might include decision points where alternative paths are taken based on conditions.

Activity diagrams can represent the flow of processing within a web application, showing the relationships between different parts of the system and the actions involved in fulfilling user requests.

Activity diagrams are a powerful tool for understanding and representing the functional aspects of a web application, helping developers and stakeholders visualize how the system interacts with users and performs its internal actions.