VisualBuilder
  Home > Uml > Tutorials > Guidelines for creating Use Cases - UML Tutorial
Tell a friend
Link to us
Total Members
      Members: 84663
     
Sitemap Forum Chat
Home
UML Tutorial Home
1 . What is UML?
2 . What are Use Cases?
3 . Why Use Cases?
4 . Actors
5 . Use Case
6 . What does a Use Case Diagram look like?
7 . What does a Use Case Diagram look like?
8 . Use Case Description
9 . Use Case Relationships
10 . Guidelines for creating Use Cases
11 . Class Diagram
12 . Example Class Diagram
13 . Identifying Attributes
14 . Operations
15 . Tips for Creating Class diagrams
16 . Further Resources
 
 
UML Home
UML Members (1768)
UML Member Articles ( 1 )
UML Discussion (1)
UML Q & A ( 4 )
- UML Ask Question
- UML Questions
- UML Unanswered Questions
UML Resources
UML Source Code (0)
UML Articles (88)
UML Blogs (0)
UML Jobs (0)
UML Components (0)
UML Books (372)
UML Websites (15)
UML News (2)
 
GROUPS
.NET
ASP.NET
.NET
C#
ASP
Visual Basic
Java
Java
JSP
EJB
Other
Delphi
C++
Ajax
UML
JavaScript
PHP
Web Design
Web Hosting
SQL Server
Oracle
Project Management
More Groups

 
LEARNING CENTER
TUTORIALS
.NET
.NET Tutorial
ASP Tutorial
ASP.NET Database Tutorial
ASP.Net Security,Internationalisation And Deployment
ASP.NET Tutorial
C# Tutorial
Web Development
Flex Tutorial
HTML Tutorial
Learn AJAX Tutorial
PHP Tutorial
Software Development
Database Tutorial
SQL Tutorial
UML Tutorial
Java
Ant Tutorial
EJB 3 Tutorial
Hibernate Tutorial
Java Tutorial
Java Web Component Tutorial
Java XML Tutorial
JDBC Tutorial
JDK1.5 Tutorial
JSF Tutorial
JSP And J2EE Design Tutorial
JSP Tutorial
Spring Tutorial
Struts Tutorial

RESOURCES
Q & A (451 )
Source Code (3275 )
Articles (359 )
Books (372 )
Components (1596 )
News (892 )
Websites (1207 )

SUBMISSIONS
Submit Article
Submit Website
Submit News
Submit Source Code
Submit Component

COMMUNITY
Members Directory
Discussion Forum
Chat

SITE
About Us
Sitemap
Search
Contact Us
Link To Us
Feedback
Tell a Friend
Partners
Advertise

Uml Tutorial
 Guidelines for creating Use Cases
  << Prev: Use Case Relationships Next: Class Diagram >>


  • Start with high level use cases and drill down to detailed use cases.

     





  • Create them iteratively and incrementally

     





  • Use a standard template across the project

     





  • Think about the actor's tasks

     





  • Make sure they fully describe the users activities

     





  • Keep detail that should be in Activity or Sequence diagrams out

     





  • Document the alternative flows

     





  • Avoid analysis paralysis. Keep them simple and know when to stop.

     





  • Leave out design elements e.g. UI or technical design. Keep them focused on behaviour of the intended system.

     





  • Understand that the difference between traditional functional requirements and use case scenarios is that previously the focus was on describing what the system will do,use cases describe user actions and the system's responses.

     





  • Be explicit about the names of Actors and boundary objects.

     





  • Pre- and post-conditions should be used only if they are absolutely necessary

     





  • Actors don't need to be human,they can be external systems.

     





  • A list of Actors can help to find the Use Cases by working out what they will do.

     





  • Don?t forget non-functional requirements such as system performance.

     





 

 



 

 



 

 



Alistair Cockburn's process for creating Use Cases:

 



 

 





  1. Name the system scope and boundaries

     





  2. Brainstorm and list the actors

     





  3. Brainstorm and exhaustively list user goals for the system

     





  4. Capture the outmost summary use cases to see 'who really cares',check for an 'outmost' use case for each primary actor

     





  5. Reconsider and revise summary use cases. Add,subtract or merge goals

     





  6. Select one use case to expand

     





  7. Capture stakeholder interests,preconditions and guarantees

     





  8. Write the main success scenario

     





  9. Brainstorm and exhaustively list the extension conditions

     





  10. Write he extension handling steps

     





  11. Extract complex flows to sub use cases - merge trivial sub use cases

     





  12. Iterate and adjust

     







  << Prev: Use Case Relationships Next: Class Diagram >>
Uml Tutorial Home
Give feedback and win a prize.

 
   Printer Friendly
   Email to a friend
   Add to my Favourites    
  Download PDF version
   Report Bad Submissions
   Submit Feedback
 
  Delicious   Digg   Technorati   Blink   Furl   Reddit   Newsvine   Google Click each image to add
this page to each site.
 
 
Welcome Guest Signup
MEMBER'S PANEL
EMAIL
PASSWORD
Forgot your password?
New User? Click Here!
 
Resend Activation Email!
 
SEARCH
 
 
 
ADVERTISEMENT
Partner List
Code Project
ASP Alliance
More
 
 
 
 

Home | Login | About Us | Contact Us | Privacy Policy | Advertising