Modeling Requirements (Week 3)

20-question practice flashcards covering modeling requirements concepts, types, techniques, tools, stakeholders, steps, best practices, common mistakes, and illustrative diagrams.

What are Modeling Requirements?

The process of capturing, analyzing, and documenting what a system should do using models or diagrams.

What is the purpose of modeling requirements?

To communicate understanding, support system design, and reduce ambiguity.

Name the four types of requirements.

Functional, Non-Functional, Business, and User Requirements.

Give an example of a Functional Requirement.

The system should allow users to log in and generate reports.

Give an example of a Non-Functional Requirement.

Performance or security requirements; e.g., the system should respond within 2 seconds.

What is a Business Requirement?

Why the system is needed and how it supports business goals.

What are User Requirements?

What the user expects, often expressed as user stories or personas.

Name two textual techniques for modeling requirements.

Use Cases and User Stories.

Name two graphical techniques for modeling requirements.

Data Flow Diagrams (DFD) and Entity-Relationship Diagrams (ERD) or UML.

What is a Prototype in modeling?

Wireframes or Mockups used to visualize the user interface.

Name a free diagram tool.

Draw.io / Diagrams.net.

Name a cloud-based modeling tool.

Lucidchart.

Name a professional diagramming tool.

Microsoft Visio.

Name a UI/UX prototyping tool.

Figma or Adobe XD.

What is the role of stakeholders in modeling requirements?

To gather, validate, and review requirements (e.g., Business Analyst, Client, End-User, Software Developer, Project Manager, QA Tester).

List the steps in identifying modeling requirements.

Requirements Gathering, Analysis and Clarification, Modeling, Validation, Documentation.

Why is it best practice to involve all stakeholders early?

To ensure alignment and catch gaps or conflicts early.

Name one common mistake to avoid in modeling requirements.

Jumping to design before understanding needs.

What does a Use Case Diagram illustrate?

The set of use cases provided by the system functionality and the interactions between actors and the system.

What is a Level 1 Data Flow Diagram (DFD)?

A high-level breakdown of the core process into major subprocesses and data flows, showing external entities like Client, Factory, Supplier, and Manager.