AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
![]() To aid with the subsequent realization of the use case as a sequence diagram it is useful to document the flow of events in the form of a numbered list. While the basic flow describes what the system does at each step – for example, displaying a form or debiting a bank account – it does not describe exactly how the behavior will be realized in code. The basic flow shows the actor’s actions and the system’s responses in the most common scenario for the use case. ![]() Use case must have one flow of events and maybe more, with each flow of events (or ‘scenario’) being realized (ideally) as a separate sequence diagram.Ī user case is always initiated by a human or system actor. The description should briefly convey the role and purpose of the use case in a single paragraph. The generic template is comprised as follows: The article you are reading now uses a generic use case specification template that combines the most common elements from the available templates. Use case specifications tend to be written in a standardized form, and over the years a number of use case specification templates have been created including the one you can download from here.
0 Comments
Read More
Leave a Reply. |