212- Agile Modeling

0.0(0)
studied byStudied by 0 people
GameKnowt Play
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/10

flashcard set

Earn XP

Description and Tags

Vocabulary flashcards covering key agile modeling concepts—use case diagrams, data models, screen designs, wireframes, and related database terminology—used to create a shared vision of "done."

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

11 Terms

1
New cards

Use Case Diagram

A visual model that shows how different users (actors) interact with an application to accomplish tasks, e.g., waiter orders food, chef prepares it.

2
New cards

Data Model

A diagram that outlines how data is organized in relational tables and the relationships between those tables.

3
New cards

Relational Database

A database structure that stores information in tables connected through relationships, typically one-to-many or many-to-many.

4
New cards

Table (Database)

A set of rows and columns in a relational database used to store related records, such as customers or orders.

5
New cards

Field (Column)

An individual attribute within a database table, e.g., customer name, address, or phone number.

6
New cards

One-to-Many Relationship

A database relationship in which a single record in one table (e.g., Customer) is linked to multiple records in another table (e.g., Orders).

7
New cards

Screen Design

A simple, often hand-drawn representation (screenshot) that shows how an application or report should appear to the user.

8
New cards

Wireframe

A low-fidelity prototype composed of successive screens illustrating what appears when specific buttons or links are clicked.

9
New cards

Low Fidelity Prototype

A quick mock-up (no real code) used to validate the look and flow of a product before development begins; synonymous with wireframe.

10
New cards

Low Tech, High Touch

The agile principle of using simple, highly visual artifacts to communicate effectively with stakeholders.

11
New cards

Lightweight (Barely Sufficient) Model

An agile guideline stating that documentation and diagrams should be kept minimal yet adequate for shared understanding.