Use case
A use case(a good one) typically represents a major piece of functionality that is complete from beginning to end
Activity diagrams
-Graphically represents the flow of events/logic within a program(use case)
-Shows the steps of a computation
-Use case descriptors are usually written from an outside actor’s perspective
-Activity models take an inside system’s viewpoint
-Depict flow of activities in the execution of a use case
-DO NOT show object that perform the activities
Constructing an Activity Diagram
-Add swim lanes for the actors and system
-Start with one initial node
-Add activities for each step in the UC narrative
-Show flows between each activity
-Add decisions,forks and joins as necessary
-End with a single end node
Use case
A textual model that lists and describes the processing details for a use case
Precondition
A condition that must be true before a use case begins
Post condition
What must be true upon the successful completion of a use case