Please enable JavaScript.
Coggle requires JavaScript to display documents.
System use-case Modeling - Coggle Diagram
System use-case Modeling
System actors
-
Actors can also be external systems, system that are outside the scope of the project being developed
Human actors or external systems interact with the target system by sending and receiving information through an interface
Kinds of system actors
-
Secondary Actor are actors that just provide some service to the provide some service the process under discussion
System use cases
Use cases describe the interactions that take place between actors and IT systems during the execution of business processes
Single session a good system use case must be performed in a single session. This mean that it should begin and finish without interruption
Interactive : a use case must also be interactive, meaning that an actor must exist to interact with the system
Consistent result: a use case must product a consistent result, be it a complete entry or transformation on a piece of information, or simply a query where relevant information is passed to a user
Overview versus detail: two styles for writing use cases may be identified: An overview use case and A detail use case
Essential: two styles for writing use cases may be identified: Essential use cases and Concrete use cases
Brief: three types of use cases with regard to the level of detail: Brief, Casual and Fully Dressed
-
-
-
-
Find System Actors
-
-
For the IT system, this means that the actor is always the one who directly operates the IT system
-
-
