Explore the evolution and application of Use-Case 2.0 in modern software development through this comprehensive ACM SIGSOFT webinar. Delve into the integration of agile methodologies with traditional use case techniques, learning how this approach combines the simplicity of user stories with the power of modeling. Discover how Use-Case 2.0 scales from small agile teams to complex system development, utilizing concepts like "slicing" to enhance flexibility and efficiency. Gain insights from Dr. Ivar Jacobson, a pioneer in software engineering, as he discusses the principles, implementation, and benefits of Use-Case 2.0 in various development scenarios. Understand the role of OMG Essence standard in this methodology and how it revolutionizes software engineering practices. Explore practical applications, including use case diagrams, value-focused development, and incremental system delivery, while learning to adapt the approach to meet specific team and client needs.
Use-Case 2.0 - The Hub of Modern Software Development
Association for Computing Machinery (ACM) via YouTube
Overview
Syllabus
Welcome to today's ACM SIGSOFT Webinar Use-case 2.0: The Hub of Modern Software Development
Abstract
AGILE USE CASES
A brief history of use cases
The lightness of user stories with the power of modeling
Powered by OMG Essence Essence: A visual standard language for describing practices and ESSENCE a standard Software Engineering Kemel context for practices
A use case is still a use case
First Principles
Keep it simple by telling stories • Make requirements understandable and testable by telling stories • Use cases provide a way to identify and capture all the different but related stories in a simple but comprehensive way.
Understand the big picture • A use-case diagram is a simple way of presenting an overview of a system's requirements.
Focus on value • When trying to understand how a system will be used it is always Important to focus on the value it will provide to its users and other stakeholders • Each use case provides value to a particular user • When does the story end? When value is fulfilled!
Too many stories for a single release
Too many stories for a single increment
So we slice up the use cases to drive the development
Drive development with use case slices • Breakdown use case into slices for development
Build the system in slices • The system should be built in slices, each of which has clear value to the users.
Deliver the system in increments • Each increment builds on the previous increment to add more functionality or improve the quality of what has come before.
Adapt to meet the team's and the client's needs . All of the work products are defined with a number of levels of detail. . Choose the level of detail you need
Different Situations Require Different Approaches
Spot the Difference
Use Cases enable agility
A truly scalable solution
Getting started is easy. You only need to model what is important to you
The practice summarized on a set of cards
Use Case 2.0 with One-Piece Flow
Apply Complementary Techniques
Use Case 2.0 solve many problems
Taught by
Association for Computing Machinery (ACM)
