Is there any "switch case" in use-case specification?
In the requirements:
How can I specify this use-case in my use-case specification?
Those two "case" will be in basic flow, won't they? Then how can I specify the "switch-case"?
Edit: (Because many mistakes what I'm doing, I will make it clear)
I'm not in progress of drawing use-case or drawing activity diagram, I'm in the between. I'm writing use-case specification (which is used to describe a use-case, and will be used later to draw activity diagram).
For more detail: https://www.google.com.vn/search?q=use-case+specification&biw=1280&bih=683&source=lnms&tbm=isch&sa=X&ved=0CAYQ_AUoAWoVChMIn6ujsMDRxwIVC5COCh3aNQGY#
In this installment we detail the use case specifications that define the use cases presented on the UML Use Case Diagram and which are realized in the form of Sequence Diagrams. A UML Use Case is an atomic system function with a well-defined and standardized specification, which is performed by or o behalf of a system user or ‘actor’.
The UC diagram itself shows which features the system provides and how (by whom) they are executed. However, there is no additional information about individual use cases except their names. This problem solves the Use Case Specification. It's an additional document that is attached to the use case diagram.
UML specifications until UML 2.5 required that use case functionality is initiated by an actor . In UML 2.5 this was removed, meaning that there could be some situations when system functionality is started by system itself while still providing useful result to an actor.
The functional requirements from the perspective of all internal and external users is captured and represented. The first component of the Use Case diagram is the system scope called the system boundary or the subject. All the tasks covered under the system’s subject are the use cases.
If you are describing the use case in the notes then write something like
Step m: User selects ?? from combobox. If selection is "contract" resume at Step n. If selection is "Funding" resume at Step o. ... ...
Step n: Resume at Step p.
Step o: Resume at Step p.
Step p: ...
where m, n, o
and p
are subsequent step numbers in your scenario.
If you are using Activities with Actions you can use a Decision node from where you have multiple outgoing transitions. Each transition then has a guard describing the switch (kind of a multi-if).
I think this one fulfill the purpose of the cases and follows the UML decision object rules.
PlantUML suggests elseif-chains which gives also a nice graph.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With