Modeling Requirements - Flashcards (Week 3 Modeling: Requirements)

A set of 15 fill-in-the-blank flashcards covering modeling requirements concepts, techniques, tools, steps, and best practices from the lecture notes.

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

Modeling Requirements

The primary purpose of modeling requirements is to __.

communicate understanding

Functional Requirements describe what the system should do, such as __ or generate reports.

login

Non-Functional Requirements describe how the system should __.

behave

Business Requirements explain the __ for the system.

business goals

User Requirements cover what the __ expects (user stories, personas).

user

Among graphical techniques for modeling requirements, one option is __.

Data Flow Diagrams (DFD)

Prototypes used for modeling include __ and mockups.

wireframes

Common modeling tools include Draw.io (Diagrams.net), Lucidchart, Microsoft Visio, Figma/Adobe XD, and __.

Visual Paradigm

Steps in identifying Modeling Requirements include Requirements Gathering, Analysis and Clarification, Modeling, Validation, and __.

Documentation

Best Practice: Involve all stakeholders __.

early

Common Mistake: Jumping to __ before understanding needs.

design

Example: Use Case Diagram highlights use cases and __ to illustrate functionality.

user stories

Example: Data Flow Diagram (DFD) Level 1 breaks down the core process and identifies external entities like __.

Client, Factory, Supplier, and Manager

Example: Entity-Relationship Diagram (ERD) is used to model a __.

database