Identifying the Actors

The term actor represents the role a user plays with respect to the system. A user may play more than one role,Click to edit Master can style however subtitle actor should represent a single user.

4/28/12

Candidates for actors can be found through the answers to the following questions:

Who is using the system ? Who is effected by the system? Or, which groups need help from the system to perform a task? Who affects the system? Or, which user groups are needed by the system to perform its functions? These functions can be both main functions and secondary functions , 4/28/12 such as administrators.

Which external hardware or other systems use the system to perform task? What problems does this application solve? And, finally, how do users use the system? What are they doing with the system.

4/28/12

Two-three rule: by Jacobson for identifying actors.

start with naming at least 2, preferably 3, people who could serve as the actors in the system. other actors can be identified in the subsequent iterations.

4/28/12

Each use case represents a particular scenario in the system. We can model either how the system currently works or how we want it to work. A design is broken down into packages. Example: a library system can be broken down into 3 packages member doing research, supplier 4/28/12 providing books and borrowing

Dividing use cases into packages

4/28/12

Naming a use case

Use-case names should provide a general description of the use-case function. The name should express what happens when an instance of the use case is performed. Jacobson recommend that the name should be active often expressed in the form of a verb or verb and noun.
4/28/12

Ex: deposit money, borrow books etc

Developing effective documentation

Documenting your project not only provides a valuable reference point and form of communication but often reveal issues an gaps in the analysis and design. A document can serve as an initial understanding of the requirements. In many projects , documentation can be an important factor in making 4/28/12 a decision about committing

Guidelines for developing effective documentation:

1.

Common cover: all the documents should share a common cover sheet that identifies the document , the current version , and the individual responsible for the content. 80-20 rule: 80% of work can be done with 20% of documentation. Familiar vocabulary: when developing documents use

2.

3.

4/28/12

4. Make the document as short as possible 5. Organize the document: use the rules of good organization within each section. Case tools provide documentation capability by providing customizable reports

4/28/12