Agile Models

Different models help in defining the shared vision and understanding the requirements of the users. Agile models should always be lightweight and barely sufficient.

1. Use Case Diagram

A visual representation of how a user interacts with an application.

Example: A restaurant system where:

• A waiter orders food
• A chef prepares the food
• A customer eats the food
• A cashier processes the payment

2. Data Models

Defines how data is structured and related within a database.

Example: A customer database where:

• Customer table includes name, address, phone number
• Orders table relates to multiple customers
• Each customer can place multiple orders

3. Screen Design

Visual representation of application screens, often drawn on paper or created using design tools.

Example: A login screen sketch showing fields for:

• Username
• Password
• Login button

4. Wireframes

A low-fidelity prototype of an application layout with clickable elements.

Example: A wireframe for a shopping cart:

• Click "Add to Cart" → Redirect to Cart Page
• Click "Checkout" → Redirect to Payment Page
• No backend coding involved

Conclusion

These Agile models help set a shared vision and ensure clarity before development begins.