/
Use Case and Data Flow Diagrams
Save to my account
Sign up
Use Case and Data Flow Diagrams
Use Case and Data Flow Diagrams
Study
1
Question
What is the primary focus of a Use Case Diagram in system modeling?
Answer
A Use Case Diagram focuses on 'what' the system will do, rather than 'how' it will do it, emphasizing the interaction between the system and external actors.
2
Question
What are the main purposes of creating a Use Case Diagram?
Answer
Its main purposes are to capture the functional requirements of a system, provide a high-level view of how users interact with the system, and identify user goals and system responsibilities.
3
Question
In Use Case Diagrams, what does an 'Actor' represent?
Answer
An actor represents roles (which can be humans) that interact with the system.
4
Question
What does each 'Use Case' represent in a Use Case Diagram?
Answer
Each use case represents a distinct interaction aimed at achieving a specific goal between the actor and the system.
5
Question
What are the three types of relationships used in Use Case Diagrams and what do they signify?
Answer
1. Association: shows communication between actor and use case; 2. Include: indicates one use case uses the behavior of another; 3. Extend: represents optional behavior that extends a base use case.
6
Question
What do Data Flow Diagrams (DFDs) graphically characterize in a business system?
Answer
DFDs graphically characterize data processes and flows, depicting system inputs, processes, and outputs.
7
Question
How are Data Flow Diagrams organized in terms of levels?
Answer
They are built in layers, with the top level being the Context-level diagram. Each process may explode (expand) to a lower-level diagram, numbered the same as its parent process. Processes that do not have child diagrams are called primitive.
8
Question
What is the significance of the Context-Level Data Flow Diagram?
Answer
The Context-Level DFD presents a high-level view of the system, showing the entire system as a single process and its interactions with external entities.