Documente Academic
Documente Profesional
Documente Cultură
Many Business Analysts use a Use Case template to capture scenarios. Tailor
the template for use case definitions to your own project needs to provide
effective project documentation. Just be sure to understand that use cases are
only the starting point for analysis and understanding of software applications.
The following are some of the entries for a Use Case Narrative template:
Behind each Use Case is a series of actions to achieve the proper functionality,
as well as alternate paths for instances where validation fails, or errors occur.
These actions can be further defined in a Use Case description. Because this is
not addressed in UML, there are no standards for Use Case descriptions.
However, there are some common templates you can follow, and whole books
on the subject of writing Use Case descriptions.
This example will use the basic flow of the scenario of the overused “Make
Hotel Reservation”:
11. The system displays the reservation details, including the room type, start
and end dates, and reservation number.
12. The use case terminates.
Remember, the information that you document in a use case scenario includes
what actors are involved, the steps that the use case performs, business rules,
and so forth. For each action and communication in a Use Case develop a
scenario. A use case specification document should include the following:
Use Case ID, Use Case Name, Brief description, Assumptions, Actors,
Pre-conditions, Normal Scenario, Inputs, Outputs, Alternate Scenarios,
Post-conditions (see example following).