Use Case
At TML we understand the importance of goal-orientated technical documents. We find use cases fit perfectly with our ethos of producing specifications which realise business requirements. The trick is (as with all forms of system/business analysis) is to find the right level of detail for multiple stakeholders and audiences; use cases enable us to do that.
A use case is a description of a system’s behaviour as it responds to a request that originates from outside of that system.
Use cases describe the interaction between a primary actor—the initiator of the interaction—and the system itself, represented as a sequence of simple steps. Actors are something or someone which exist outside the system under study, and that take part in a sequence of activities in a dialogue with the system, to achieve some goal: they may be end users, other systems, or hardware devices. Each use case is a complete series of events, described from the point of view of the actor.
Filed under: Uncategorized | Leave a Comment
Tags: actor, Business Analysis, requirements, stakeholders, system engineering, UML, use case
No Responses Yet to “Use Case”