Use-Case 2.0 - The Hub of Modern Software Development

Use-Case 2.0 - The Hub of Modern Software Development

Association for Computing Machinery (ACM) via YouTube Direct link

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 simpl…

9 of 27

9 of 27

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 simpl…

Class Central Classrooms beta

YouTube videos curated by Class Central.

Classroom Contents

Use-Case 2.0 - The Hub of Modern Software Development

Automatically move to the next video in the Classroom when playback concludes

  1. 1 Welcome to today's ACM SIGSOFT Webinar Use-case 2.0: The Hub of Modern Software Development
  2. 2 Abstract
  3. 3 AGILE USE CASES
  4. 4 A brief history of use cases
  5. 5 The lightness of user stories with the power of modeling
  6. 6 Powered by OMG Essence Essence: A visual standard language for describing practices and ESSENCE a standard Software Engineering Kemel context for practices
  7. 7 A use case is still a use case
  8. 8 First Principles
  9. 9 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 simpl…
  10. 10 Understand the big picture • A use-case diagram is a simple way of presenting an overview of a system's requirements.
  11. 11 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…
  12. 12 Too many stories for a single release
  13. 13 Too many stories for a single increment
  14. 14 So we slice up the use cases to drive the development
  15. 15 Drive development with use case slices • Breakdown use case into slices for development
  16. 16 Build the system in slices • The system should be built in slices, each of which has clear value to the users.
  17. 17 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.
  18. 18 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
  19. 19 Different Situations Require Different Approaches
  20. 20 Spot the Difference
  21. 21 Use Cases enable agility
  22. 22 A truly scalable solution
  23. 23 Getting started is easy. You only need to model what is important to you
  24. 24 The practice summarized on a set of cards
  25. 25 Use Case 2.0 with One-Piece Flow
  26. 26 Apply Complementary Techniques
  27. 27 Use Case 2.0 solve many problems

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.