Chapter 5 System Analysis

These flashcards cover the key concepts and definitions related to use case analysis and modeling in systems analysis and design as taught by Dr. Prince Waqas Khan.

What defines the scope and behavioral requirements of a system in software development?

Use cases.

What are the four steps for creating use cases?

1. Identify the use cases 2. Identify the major steps 3. Identify elements within steps 4. Confirm the use case.

What does a use case represent in a system?

A function or action that the system performs.

What are the four main components of a use case diagram?

1. Actors 2. Use Cases 3. System Boundary 4. Relationships.

What are actors in a use case diagram?

External entities that interact with the system.

What is a primary actor in a use case context?

An actor that initiates use cases independently.

What is meant by 'system boundary' in a use case diagram?

It defines the scope and limits of what the system includes.

What type of relationship shows the participation of an actor in a use case?

Association.

What does the ‘<>’ relationship imply in use cases?

Mandatory inclusion of functionality from one use case into another.

How should use cases be named according to best practices?

Using action phrases that are distinct and meaningful, often starting with a verb.

What is the main focus of use case analysis?

Capturing functional requirements from the user’s perspective.

Why are use cases important for project planning?

They help identify features and plan iterations, particularly in Agile methodologies.

What should a use case diagram illustrate?

The interactions between actors and use cases, focusing on high-level functionality.

What does event-driven modeling focus on?

Viewing a system as a series of discrete, meaningful events that occur over time.

What is the purpose of validating a use case during the confirmation step?

To ensure it is correct and complete by walking through the steps with a user.

What type of diagrams support visualizing, constructing, and documenting software systems?

Unified Modeling Language (UML) diagrams.

What are secondary actors in the context of use cases?

Actors that are used by the system but do not initiate use cases.

Why is it important to use standard UML notation in diagrams?

To ensure clarity and understanding among stakeholders.