This two-day advanced course will build on your existing knowledge of the use case approach to give you hands-on experience with the latest proven techniques for developing use cases, discovering other types of requirements, and documenting them expertly. Lively lectures combined with insightful demonstrations and realistic practice exercises will equip you with the capability and confidence to improve your project outcomes through better requirements and use case development.
You’ll gain a thorough understanding of common requirements and use case pitfalls and challenges, practical approaches for discovering and writing use cases and requirements, and strategies for applying the use case methodology throughout the project life cycle in your organization. If you already know the basics of use cases and you play a role in defining project scope, capturing requirements, or consuming them as a developer, tester, or technical business user, you can’t afford to miss this course.
Who Should Attend
If you're involved at all in defining and managing systems development projects, you should participate in this workshop:
Section I. Review of Requirements Development with Use Cases
Use cases are one of the best approaches for developing requirements. In this section of the workshop, we will review key definitions and terms, overview a requirements management framework, and review how use cases fit into the development life cycle. Well refresh your knowledge of how to find requirements from use cases, and well conclude with a discussion of use cases and Agile methods.
With your instructor, revisit key concepts of requirements engineering and then review poorly written requirements to discover characteristics of effective requirements. Work with your team to review and analyze several use cases and then extract possible requirements from those sample use cases.
Section II. IT Project Initiation and Use Cases
To exploit the full advantages of use cases, seasoned analysts plan for them from the very beginning of each project. This section explores project initiation and its relationship to use cases, particularly how to identify and capture them early in the project life cycle. In particular, youll review whether use cases are appropriate for a specific project. Youll strengthen your understanding of the connection between project scope and use cases. Well conclude this module with an exploration of other methods for identifying the use cases that comprise a system, and a chance for you to practice constructing a use case diagram.
Examine a hypothetical but realistic business and one of its emergent projects. Youll work in a small group to practice determining whether the use case approach is appropriate, identifying the use cases using the actor/goal identification method, and writing user stories and use case briefs for the case project. You will also practice diagramming the actors and the use cases.
Section III. Documenting Requirements with Use Cases
At some point, we must document the use cases and requirements discovered during the requirements elicitation process. This section of the workshop focuses on how to apply the knowledge you already have to writing better use cases. It also examines more complex aspects of uses cases, including includes and extends relationships and use case linking on larger systems.
Youll work with your team to write a fully dressed use case for our case project, including a preamble, the main success scenario, and the extension scenarios. Youll also have a chance to write an included (or sub-function) use case and an extension use case.
Section IV. Improving Use Case Quality
As with most aspects of system development, the quality of downstream work products (design elements, test plans, etc.) depends directly upon the quality of the use cases. During this part of the workshop, we will apply standards for quality to our use cases and requirements and look at some proven ways to prevent common problems. Well also explore how to derive maximum benefit from reviews throughout the life cycle.
Your team will review another teams use case using a quality checklist. Youll then have the opportunity to refine your own teams use case based on feedback from another team.
Section V. Use Cases and Other Requirements
Merely writing use cases is not sufficient for capturing all project requirements. While desired user functionality yields a major set of project requirements, experienced analysts know there are also non-functional aspects of the desired system that must be identified and captured. In this section, we will examine ways to derive other typical requirements from use cases and how to identify constraints on the solution design. In addition, well explore how use cases not only trace back to one or more business requirements, but also how they trace forward through the development life cycle to design and testing.
Your team will work together to derive and capture non-functional requirements from the use case your team has already refined. Then your instructor will work with the class to develop and document traceability between the requirements and the use cases for our course project.
Section VI. Use Cases and Testing
One of the most powerful aspects of the use case approach is its improvement in test procedure development. Well-written use cases directly impact the outcome of the very portion of the life cycle most likely to suffer when time is of the essence. Here, well look at how use cases can help identify test cases early in the life cycle. Next, well examine an example use case and its associated test plan side-by-side. Finally, well discuss how use of automated tools can reduce not only testing time, but also the time required to produce the test procedures.
Your instructor will demonstrate the use of a popular automated use case documentation tool and will then use it to develop a partial set of test procedures for our case project.
Section VII. Use Cases and Design Elements
Once we have the use cases developed, we can use them as a basis for discovering the elements needed for the design and development of the solution. In this section, well learn how to find typical design elements such as screens, messages, and dialog boxes, creating another layer of detail (sometimes called a system use case).
With your team, youll analyze the use case youve already written to identify and specify required design elements. With your instructor, prototype an interface design for a use case from our case project and use it to validate the requirements.