Webinars - Business/Systems Analysis

All Business Analysis Webinars | Search

Webinar: The Use Case Technique: An Overview

Statistics:Article Rating (13360 Views) (7 Comments)


Use cases are an effective and widely used technique for eliciting software requirements. The use-case approach focuses on the goals that users have with a system, rather than emphasizing system functionality. This webinar presents an overview of the use-case approach to requirements elicitation in a practical and straightforward fashion.

Topics covered include:

· Where use cases fit into the requirements development process

· Types of projects for which use cases are and are not well suited

· User classes and actors

· Scenarios and use cases

· Components of a use case

· Use case diagrams

· Deriving functional requirements from use cases


Karl E. Wiegers

Principal Consultant

Process Impact

Karl E. Wiegers has provided training and consulting services worldwide on many aspects of software development, management and process improvement. Prior to starting Process Impact in 1997, Karl spent 18 years at Eastman Kodak Company in a variety of roles. Karl is the author of many books including: Software Requirements & More About Software Requirements. 

DURATION: 60 minute presentation and interactive question and answer session.


RequirementOneRequirementOne offers 5 integrated Apps that allow youto maximize the productivity and success of your projects; planning,specification, feedback, tenders and issues. RequirementOneis the only cloud product on the market that offers this breadth offunctionality - integrated into one easy to use platform.

Access webinar ->  Webinar: The Use Case Technique: An Overview

Download slides -> Slides: The Use Case Technique: An Overview

PDU & CDU Information: PDUs & CDUs for Modern Analyst Webinars

By c naylor @ Thursday, July 26, 2012 1:07 PM
Really enjoyed the presentation. Would like to see something similar that focuses on a more agile approach e.g. how to take input from Use Cases (agile stories) and write "just enough" SRS content.

By sourabh @ Thursday, July 26, 2012 1:10 PM
Really nice presentation.would like to see some more live example with use case diagrams & off course how to implement use case in agile process

By rahul @ Thursday, July 26, 2012 2:54 PM
Nice presentation. Please share the presentation deck.

By Adrian M. @ Friday, July 27, 2012 8:30 AM
The webinar recording is now up and ready.

By Ikenna @ Friday, July 27, 2012 5:08 PM
Nice presentation and very useful. I just introduced use cases to a BA team I work in and they warmed up to it :)

You stressed that use cases are used to capture what goals a user wants to accomplish from a system. In the template you used, why did you need to document the system response to an actor actions? Wont that end up describing the user interface and making the user think more of what they want the system to do and less of their own goals?

By Karl Wiegers @ Monday, August 13, 2012 9:32 AM
@Ikenna: At the very top level of abstraction, yes, the use case simply states the goal the user is trying to accomplish. However, a richer description of the use case provides additional information regarding the way a user might interact with a system to accomplish that goal. This is the information that leads to deriving the functional requirements that developers must implement to let the user perform the use case. That conceptual description of the dialogue between the user and the system also does lead to user interface design. After all, that information has to come from somewhere. However, the description of the use case should not include specific UI details. As I mentioned in the webinar, I don't even like to use terms like "User clicks on OK" in the use case description, preferring to keep it more abstract so the UI designer is not overly constrained.

By shankari @ Thursday, November 8, 2012 6:58 PM
Great learning experience for me. Very well presented.

Only registered users may post comments.



Copyright 2006-2024 by Modern Analyst Media LLC