212- Agile Modeling

Agile Modeling Principles

• Models should be lightweight, "barely sufficient"; goal = shared vision / definition of done.
• Favor low-tech, high-touch visuals over complex documentation.

Use Case Diagram

• Diagram of user (actor) interactions with system functions.
• Clarifies scope & user goals (e.g., waiter orders, chef cooks, client eats, cashier takes payment).
• Quick, visual, and easy to understand.

Data Models

• Show relational structure: tables, fields, and their relationships.
• Example one-to-many: (\text{Customer} \rightarrow \text{Orders}).
• Primarily for database designers; likely low exam emphasis.

Screen Design (Mock Screenshots)

• Simple sketches or digital mock-ups of each UI/report.
• Lets stakeholders "see" the product; UI is their main focus.
• Fast, inexpensive feedback loop before coding.

Wireframes (Low-Fidelity Prototypes)

• Sequence of static screens with buttons/links; no real code.
• Shows what screen appears after each action, clarifying workflow.
• Validates "what done looks like" early, minimizing rework.