Use case guidelines
From: KP Bhat (kbhat_at_sta.samsung.com)
Date: 12/29/04
- Next message: Rich MacDonald: "Re: Encapsulation vs separation of concerns"
- Previous message: H. S. Lahman: "Re: encapsulation , data hiding"
- Next in thread: H. S. Lahman: "Re: Use case guidelines"
- Reply: H. S. Lahman: "Re: Use case guidelines"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 29 Dec 2004 14:45:41 -0800
Fellow nettors,
I am trying to identify guidelines for identifying use cases. Here's
what I have come up with so far. Kindly feel free to provide
additions/alterations.
1) A use case should be triggered or observed by users (i.e. actors)
that lie outside the system boundary
2) A use case should only deal with "business functionality" and not
implementation details
3) A use case should provide "business value" to the users (i.e.
actors)
4) Use case titles should begin with a verb
Regards,
Bhat
- Next message: Rich MacDonald: "Re: Encapsulation vs separation of concerns"
- Previous message: H. S. Lahman: "Re: encapsulation , data hiding"
- Next in thread: H. S. Lahman: "Re: Use case guidelines"
- Reply: H. S. Lahman: "Re: Use case guidelines"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]