Use cases and Actors

Use case - It is a high level piece of functionality Actor - Any one who interacts with the System
Do's

• Make communication relationships between use cases and actors


• Use "Include", "Uses" and "Extends" relationship between the use cases

For e.g. the use case "send message" may "extends" from "encrypt message" use case. (User want to encrypt the message before they send)

As and another example, use case "send message" may include "select receipient" use case. (User selecting the receipients before they send the message)

• Create atleast one use case for each functional requirement
• Additionaly you may set priority, stereo type (Include, extends etc...), Notes, Pre Condition, Post Condition, Status, Complexity, Language, Mulitplicity, constrains and etc to the use cases which are provided by individual use case tools (Rational Rose, Enterprise Architect etc...)

Dont's

• There should not be any actor to actor communication
• There shoud not be any information flow, activity flow and control flow.