Use case modelling
Visual representation and narrative description of behavioural requirements
-Activities that the system must perform to carry out/support system processes
Operational view of the system
-Depicts behaviour of the system as it appears to an outside user>outwardly visible and testable system behaviour
-Used to document work flow of business process activities
A use case represents
-A complete unit of functionality(main flow of logic)
-A function that is outwardly visible to an actor(user)
-A piece of functionality initiated by an actor(user)
-A piece of functionality of value to an actor(user)
Use case diagram
During analysis a use case diagram focuses on what an existing a new system does, as opposed to how the system works
Boundary
-Automated system boundary
-Denotes the boundary
-Between the environment, where the actors reside,and the internal functions of the automated system
Actors
-Actors are ‘external of the system’, they interact with the system from outside
-Actors are active, may initiate,control,input or receive information from the system
Use case
Is a sequence of actions a system performs that yields an observable result to a particular actor
Steps to develop a UC model