home
Home

Notation for Modeling With Use Cases

Submitted by baldrick on Mon, 2009-06-22 23:59

by Leslie Munday

This article is part of a much larger project that Leslie Munday is working on. In this particular chapter excerpt Leslie describes  business use cases and application use cases, identifies the differences between the two types of use cases and introduces templates for writing use cases. Leslie also defines a notation for modeling use cases using UML.

AttachmentSize
RQNG-Notation_for_Modeling_with_Use_Cases.pdf988.95 KB

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Chapters 1 thru 5 are on my blog by baldrick

    Sponsored Announcements & Special Offers

view counter

Whitepaper from HP - Why Focus on Requirements Definition Management in the Application Lifecycle?

Increasingly, smart businesses are looking much closer at requirements definition (RD) and requirements management (RM) (sometimes grouped together under the Gartner-coined phrase, requirements definition management (RDM)) to streamline the entire application lifecycle. Why? Because systematic and effective RDM captures software defects earlier in the lifecycle, and it reduces the overall likelihood that defects will be introduced. That’s important. How important? According to one study, the cost to fix a defect after delivery is more than 100 times the cost to fix it in the requirement and design phase. No business wants to be hit with that bill. Now to add to this the growing interest in agile development techniques as a way to deliver higher quality applications and we have an interesting recipe for success.

Download a Free Copy

view counter
© 2007-2010 Requirements Networking Group All rights reserved. contact | advertise | privacy
Requirements Networking Group