Use Case

Why write Use Cases?

Clearly defined Use Cases eliminate guesswork. Developers know exactly what to build, and testers know exactly what to verify. To complete the picture, we recommend always attaching a Use Case Diagram to the textual description to visually represent the relationships between actors and functions.

In our template, you will find two variants. Each serves a different purpose and project phase:

1. Basic Template: deal for the early stages of a project or for agile development. It contains only the essentials to keep the team moving fast without losing clarity:

• Basic Flow: The direct path to success.
• Alternative Flow: What happens when the user chooses a different path or an error occurs?
• Pre-conditions & Post-conditions: What must be true before we start (e.g., "User is logged in") and what the system state looks like after completion.

Projectman’s Field Tip

Write Use Cases in the language of the user, not the programmer. Instead of "the system calls the API and writes to the database," write "the system saves the order details and confirms its receipt." This is the only way to ensure that the analyst, the customer, and the developer all envision the same outcome when reading the same text.

At Projectman, we believe that the best technologies are those that don't get in people's way. With our Use Case templates, you ensure that your system is intuitive, logical, and built exactly according to the requirements.