More requirements in a single use case – correct?
I have been arguying with a developer who insists that 1 functional request (FR) == 1 use case (UC). I think that is nonsense as there are requirements often describing situations arising from the same point – for this the use cases have alternate flows.
More requirements in a single use case – correct?
I have been arguying with a developer who insists that 1 functional request (FR) == 1 use case (UC). I think that is nonsense as there are requirements often describing situations arising from the same point – for this the use cases have alternate flows.
Is this a specific pattern and what is its purpose? [closed]
Closed 9 years ago.
Extension in use case diagram: Library management example?
I have problem to understand the extension relation in the use case diagrams, sometimes some relations seem extension.
Extension in use case diagram: Library management example?
I have problem to understand the extension relation in the use case diagrams, sometimes some relations seem extension.
Extension in use case diagram: Library management example?
I have problem to understand the extension relation in the use case diagrams, sometimes some relations seem extension.
Use case diagram, which behaviours should be included?
I teach OOD&A course to some students. When I want to draw a use case diagram or write the scenario of them for a system, I don’t know should I include everything (behavior) which is done in the system by human or computer or just focus on those which is done by computer.
Use case diagram, which behaviours should be included?
I teach OOD&A course to some students. When I want to draw a use case diagram or write the scenario of them for a system, I don’t know should I include everything (behavior) which is done in the system by human or computer or just focus on those which is done by computer.
Use case diagram, which behaviours should be included?
I teach OOD&A course to some students. When I want to draw a use case diagram or write the scenario of them for a system, I don’t know should I include everything (behavior) which is done in the system by human or computer or just focus on those which is done by computer.
Use case diagram : distingishing the actor of a use case
I know a system contains a set of use case diagrams and not one use case diagram, but anyway in the first step to find the system requirements or to analyze them I have problem in distinguishing the actor of a use case.