SlideShare a Scribd company logo
1 of 76
Download to read offline
FROM USE CASE to  USER STORIES
Use Case Introduction
 
Why are Requirements important ,[object Object],[object Object],[object Object],USE CASE MODEL
Why should you be interested ? ,[object Object],[object Object],[object Object]
What are Requirements ,[object Object],[object Object],[object Object],[object Object],[object Object],defined operational capabilities business needs satisfy
Software Requirements ,[object Object],[object Object],[object Object],[object Object]
Business Level ,[object Object],[object Object],[object Object],[object Object]
User Level ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]
Technical Level ,[object Object],[object Object],[object Object]
Use Case Concepts and Definitions
Use Case ,[object Object],[object Object]
Use Case ,[object Object],[object Object]
Actors ,[object Object],[object Object],[object Object],[object Object]
Primary Actor ,[object Object]
Supporting Actor ,[object Object],[object Object]
Scenario ,[object Object],[object Object]
Scenario ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]
Main Success Scenario ,[object Object],[object Object]
Extensions ,[object Object],[object Object]
Extensions ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]
Use Case Properties ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]
Design Scope ,[object Object],[object Object]
Design Scope ,[object Object],[object Object],[object Object]
Use Case Level ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],source : Alistair Cockburn, Writing Effective Use Cases
Use Case level ,[object Object],[object Object],[object Object]
Stakeholder & Primary Actor ,[object Object],[object Object],[object Object],[object Object]
Description ,[object Object]
Preconditions ,[object Object],[object Object]
Post conditions ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]
Trigger ,[object Object]
Use cases Process Flow
Develop in Iterations ,[object Object],[object Object],[object Object]
MoSCoW List ,[object Object],[object Object],[object Object],[object Object]
Actor-Goal List L Find unfinished task and reject it Reject unfinished task Support H Receive request and approve it Approve Request Approver H Make change in edit group and send it Submit Change Request Requestor Prio Brief Descriptions Goals Actor
Recipe ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]
Cheat Sheet ,[object Object],[object Object],[object Object]
Use Case Best Practices
7 Best Practices ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]
1. Scope the Domain ,[object Object],[object Object]
How to name a Use Case ,[object Object],[object Object],What’s in a name ?
Best practices (1) ,[object Object],[object Object],[object Object],[object Object],[object Object]
Best Practices (2) ,[object Object],[object Object],[object Object]
2. Scope Your Use Cases ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]
2. Scope Your Use Cases ,[object Object],[object Object],[object Object]
2. Scope Your Use Cases ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]
2. Scope Your Use Cases ,[object Object],[object Object],[object Object],[object Object]
3. Validate Use Cases ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]
4. Define the Requirements Model ,[object Object],[object Object],[object Object],[object Object],[object Object]
4. Define the Requirements Model ,[object Object],[object Object],[object Object],[object Object],[object Object]
5.Determine Your Elicitation Strategy ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]
5. Determine Your Elicitation Strategy ,[object Object],[object Object],[object Object]
6. Settle on Standard Format ,[object Object],[object Object],[object Object],[object Object]
6. Settle on Standard Format ,[object Object],[object Object]
 
7. Develop Glossary ,[object Object],[object Object],[object Object]
USE CASE Modeling
Use case Modeling ,[object Object],[object Object]
Actor ,[object Object],[object Object]
Actor / Use case Associations ,[object Object],[object Object],[object Object]
Generalization ,[object Object],[object Object]
Inclusion ,[object Object]
Extension ,[object Object],[object Object],[object Object],Abort Transaction Trigger : any time in  Buy Ticket  the Car Driver can abort the trans. Main Success Scenario 1. The Ticket Machine returns the coins that have been entered
User Stories Scrum methodology
What is a User Story ? ,[object Object]
User Story Description ,[object Object],[object Object],[object Object]
How detail should a User Story be ? ,[object Object],[object Object]
User Stories Summary ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]
Use Case vs User Stories When to use What
Structured Requirements ,[object Object],[object Object],[object Object],[object Object],[object Object],source:  Software Requirements, 2 nd  Edition, Karl E Wiegers
Documentation Overhead source : http://tynerblain.com
What are the differences ? ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]
Level of Details captured source : http://tynerblain.com
Level of Reader expertise source : http://tynerblain.com
References ,[object Object],[object Object],[object Object],[object Object]
Q&A

More Related Content

What's hot

Writing Effective User Stories
Writing Effective User StoriesWriting Effective User Stories
Writing Effective User StoriesJaneve George
 
Writing Good User Stories (Hint: It's not about writing)
Writing Good User Stories (Hint: It's not about writing)Writing Good User Stories (Hint: It's not about writing)
Writing Good User Stories (Hint: It's not about writing)one80
 
Introducing Agile User Stories
Introducing Agile User StoriesIntroducing Agile User Stories
Introducing Agile User StoriesRam Srivastava
 
Introduction to User Stories
Introduction to User StoriesIntroduction to User Stories
Introduction to User StoriesMike Cohn
 
Best Practices for a CoE
Best Practices for a CoEBest Practices for a CoE
Best Practices for a CoESplunk
 
Product Backlog - Refinement and Prioritization Techniques
Product Backlog - Refinement and Prioritization TechniquesProduct Backlog - Refinement and Prioritization Techniques
Product Backlog - Refinement and Prioritization TechniquesVikash Karuna
 
User story slicing
User story slicing User story slicing
User story slicing Ankit Tandon
 
Estimating with story points
Estimating with story pointsEstimating with story points
Estimating with story pointsWalid Farag
 
Microservices for Enterprises
Microservices for Enterprises Microservices for Enterprises
Microservices for Enterprises Kasun Indrasiri
 
Effective User Story Writing
Effective User Story WritingEffective User Story Writing
Effective User Story WritingAhmed Misbah
 
Introduction to story points
Introduction to story pointsIntroduction to story points
Introduction to story pointsAnil Kulkarni CSM
 
Event Driven Architecture
Event Driven ArchitectureEvent Driven Architecture
Event Driven ArchitectureStefan Norberg
 
Invest In Good User Stories
Invest In Good User StoriesInvest In Good User Stories
Invest In Good User StoriesCraig Brown
 

What's hot (20)

Writing Effective User Stories
Writing Effective User StoriesWriting Effective User Stories
Writing Effective User Stories
 
User Stories
User StoriesUser Stories
User Stories
 
Effective User Stories
Effective User StoriesEffective User Stories
Effective User Stories
 
User Story
User StoryUser Story
User Story
 
Event driven architecture
Event driven architectureEvent driven architecture
Event driven architecture
 
Effective user stories for your agile or Scrum team
Effective user stories for your agile or Scrum teamEffective user stories for your agile or Scrum team
Effective user stories for your agile or Scrum team
 
Writing Good User Stories (Hint: It's not about writing)
Writing Good User Stories (Hint: It's not about writing)Writing Good User Stories (Hint: It's not about writing)
Writing Good User Stories (Hint: It's not about writing)
 
Introducing Agile User Stories
Introducing Agile User StoriesIntroducing Agile User Stories
Introducing Agile User Stories
 
Introduction to User Stories
Introduction to User StoriesIntroduction to User Stories
Introduction to User Stories
 
Best Practices for a CoE
Best Practices for a CoEBest Practices for a CoE
Best Practices for a CoE
 
Product Backlog - Refinement and Prioritization Techniques
Product Backlog - Refinement and Prioritization TechniquesProduct Backlog - Refinement and Prioritization Techniques
Product Backlog - Refinement and Prioritization Techniques
 
User Story Mapping
User Story MappingUser Story Mapping
User Story Mapping
 
User story slicing
User story slicing User story slicing
User story slicing
 
Estimating with story points
Estimating with story pointsEstimating with story points
Estimating with story points
 
Microservices for Enterprises
Microservices for Enterprises Microservices for Enterprises
Microservices for Enterprises
 
Effective User Story Writing
Effective User Story WritingEffective User Story Writing
Effective User Story Writing
 
Introduction to story points
Introduction to story pointsIntroduction to story points
Introduction to story points
 
Story of user story
Story of user storyStory of user story
Story of user story
 
Event Driven Architecture
Event Driven ArchitectureEvent Driven Architecture
Event Driven Architecture
 
Invest In Good User Stories
Invest In Good User StoriesInvest In Good User Stories
Invest In Good User Stories
 

Viewers also liked

Viewers also liked (6)

Raport marketing doswiadczen_2013
Raport marketing doswiadczen_2013Raport marketing doswiadczen_2013
Raport marketing doswiadczen_2013
 
Machine learning’s impact on utilities webinar
Machine learning’s impact on utilities webinarMachine learning’s impact on utilities webinar
Machine learning’s impact on utilities webinar
 
Intelligent Production: Deploying IoT and cloud-based machine learning to opt...
Intelligent Production: Deploying IoT and cloud-based machine learning to opt...Intelligent Production: Deploying IoT and cloud-based machine learning to opt...
Intelligent Production: Deploying IoT and cloud-based machine learning to opt...
 
Artificial Intelligence in Oil and Gas
Artificial Intelligence in Oil and GasArtificial Intelligence in Oil and Gas
Artificial Intelligence in Oil and Gas
 
Artificial Intelligence Application in Oil and Gas
Artificial Intelligence Application in Oil and GasArtificial Intelligence Application in Oil and Gas
Artificial Intelligence Application in Oil and Gas
 
Snapchat Visual Marketing Strategy
Snapchat Visual Marketing StrategySnapchat Visual Marketing Strategy
Snapchat Visual Marketing Strategy
 

Similar to From Use case to User Story

Requirements Are Optional, Right?
Requirements Are Optional, Right?Requirements Are Optional, Right?
Requirements Are Optional, Right?thomstrat
 
Use Case Workshop
Use Case WorkshopUse Case Workshop
Use Case Workshopelkensteyin
 
BABoK V2 Requirements Analysis (RA)
BABoK V2 Requirements Analysis (RA)BABoK V2 Requirements Analysis (RA)
BABoK V2 Requirements Analysis (RA)AMJAD SHAIKH
 
27 pso business_requirements
27 pso business_requirements27 pso business_requirements
27 pso business_requirementsMarcelo Mesti
 
Writing Requirements Right
Writing Requirements RightWriting Requirements Right
Writing Requirements RightHani Massoud
 
Chapter 3.pptx
Chapter 3.pptxChapter 3.pptx
Chapter 3.pptxTekle12
 
The Art and Science of Requirements Gathering
The Art and Science of Requirements GatheringThe Art and Science of Requirements Gathering
The Art and Science of Requirements GatheringVanessa Turke
 
Non-functional requirements
Non-functional requirements Non-functional requirements
Non-functional requirements Rohela Raouf
 
Automation Hub Best Practices - Large Scale Rollouts.pdf
Automation Hub Best Practices - Large Scale Rollouts.pdfAutomation Hub Best Practices - Large Scale Rollouts.pdf
Automation Hub Best Practices - Large Scale Rollouts.pdfCristina Vidu
 
OOAD U1.pptx
OOAD U1.pptxOOAD U1.pptx
OOAD U1.pptxanguraju1
 
Lecture7 use case modeling
Lecture7 use case modelingLecture7 use case modeling
Lecture7 use case modelingShahid Riaz
 
Use Cases and Use in Agile world
Use Cases and Use in Agile worldUse Cases and Use in Agile world
Use Cases and Use in Agile worldRavikanth-BA
 

Similar to From Use case to User Story (20)

Requirements Are Optional, Right?
Requirements Are Optional, Right?Requirements Are Optional, Right?
Requirements Are Optional, Right?
 
Use Case - Introduction
Use Case - IntroductionUse Case - Introduction
Use Case - Introduction
 
Use Case Workshop
Use Case WorkshopUse Case Workshop
Use Case Workshop
 
BABoK V2 Requirements Analysis (RA)
BABoK V2 Requirements Analysis (RA)BABoK V2 Requirements Analysis (RA)
BABoK V2 Requirements Analysis (RA)
 
27 pso business_requirements
27 pso business_requirements27 pso business_requirements
27 pso business_requirements
 
Writing Requirements Right
Writing Requirements RightWriting Requirements Right
Writing Requirements Right
 
Chapter 3.pptx
Chapter 3.pptxChapter 3.pptx
Chapter 3.pptx
 
Ch07
Ch07Ch07
Ch07
 
Ch07
Ch07Ch07
Ch07
 
Defining The System
Defining The SystemDefining The System
Defining The System
 
Reqs analysis
Reqs analysisReqs analysis
Reqs analysis
 
Usecase
UsecaseUsecase
Usecase
 
The Art and Science of Requirements Gathering
The Art and Science of Requirements GatheringThe Art and Science of Requirements Gathering
The Art and Science of Requirements Gathering
 
Game plan wkshp1
Game plan wkshp1Game plan wkshp1
Game plan wkshp1
 
Non-functional requirements
Non-functional requirements Non-functional requirements
Non-functional requirements
 
Automation Hub Best Practices - Large Scale Rollouts.pdf
Automation Hub Best Practices - Large Scale Rollouts.pdfAutomation Hub Best Practices - Large Scale Rollouts.pdf
Automation Hub Best Practices - Large Scale Rollouts.pdf
 
OOAD U1.pptx
OOAD U1.pptxOOAD U1.pptx
OOAD U1.pptx
 
Requirements Engineering
Requirements EngineeringRequirements Engineering
Requirements Engineering
 
Lecture7 use case modeling
Lecture7 use case modelingLecture7 use case modeling
Lecture7 use case modeling
 
Use Cases and Use in Agile world
Use Cases and Use in Agile worldUse Cases and Use in Agile world
Use Cases and Use in Agile world
 

Recently uploaded

IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019
IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019
IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019IES VE
 
UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...
UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...
UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...UbiTrack UK
 
Machine Learning Model Validation (Aijun Zhang 2024).pdf
Machine Learning Model Validation (Aijun Zhang 2024).pdfMachine Learning Model Validation (Aijun Zhang 2024).pdf
Machine Learning Model Validation (Aijun Zhang 2024).pdfAijun Zhang
 
Comparing Sidecar-less Service Mesh from Cilium and Istio
Comparing Sidecar-less Service Mesh from Cilium and IstioComparing Sidecar-less Service Mesh from Cilium and Istio
Comparing Sidecar-less Service Mesh from Cilium and IstioChristian Posta
 
Empowering Africa's Next Generation: The AI Leadership Blueprint
Empowering Africa's Next Generation: The AI Leadership BlueprintEmpowering Africa's Next Generation: The AI Leadership Blueprint
Empowering Africa's Next Generation: The AI Leadership BlueprintMahmoud Rabie
 
AI Fame Rush Review – Virtual Influencer Creation In Just Minutes
AI Fame Rush Review – Virtual Influencer Creation In Just MinutesAI Fame Rush Review – Virtual Influencer Creation In Just Minutes
AI Fame Rush Review – Virtual Influencer Creation In Just MinutesMd Hossain Ali
 
UiPath Community: AI for UiPath Automation Developers
UiPath Community: AI for UiPath Automation DevelopersUiPath Community: AI for UiPath Automation Developers
UiPath Community: AI for UiPath Automation DevelopersUiPathCommunity
 
UiPath Studio Web workshop series - Day 8
UiPath Studio Web workshop series - Day 8UiPath Studio Web workshop series - Day 8
UiPath Studio Web workshop series - Day 8DianaGray10
 
NIST Cybersecurity Framework (CSF) 2.0 Workshop
NIST Cybersecurity Framework (CSF) 2.0 WorkshopNIST Cybersecurity Framework (CSF) 2.0 Workshop
NIST Cybersecurity Framework (CSF) 2.0 WorkshopBachir Benyammi
 
Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™Adtran
 
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCostKubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCostMatt Ray
 
How Accurate are Carbon Emissions Projections?
How Accurate are Carbon Emissions Projections?How Accurate are Carbon Emissions Projections?
How Accurate are Carbon Emissions Projections?IES VE
 
OpenShift Commons Paris - Choose Your Own Observability Adventure
OpenShift Commons Paris - Choose Your Own Observability AdventureOpenShift Commons Paris - Choose Your Own Observability Adventure
OpenShift Commons Paris - Choose Your Own Observability AdventureEric D. Schabell
 
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve DecarbonizationUsing IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve DecarbonizationIES VE
 
Designing A Time bound resource download URL
Designing A Time bound resource download URLDesigning A Time bound resource download URL
Designing A Time bound resource download URLRuncy Oommen
 
9 Steps For Building Winning Founding Team
9 Steps For Building Winning Founding Team9 Steps For Building Winning Founding Team
9 Steps For Building Winning Founding TeamAdam Moalla
 
Introduction to Matsuo Laboratory (ENG).pptx
Introduction to Matsuo Laboratory (ENG).pptxIntroduction to Matsuo Laboratory (ENG).pptx
Introduction to Matsuo Laboratory (ENG).pptxMatsuo Lab
 
Computer 10: Lesson 10 - Online Crimes and Hazards
Computer 10: Lesson 10 - Online Crimes and HazardsComputer 10: Lesson 10 - Online Crimes and Hazards
Computer 10: Lesson 10 - Online Crimes and HazardsSeth Reyes
 
Bird eye's view on Camunda open source ecosystem
Bird eye's view on Camunda open source ecosystemBird eye's view on Camunda open source ecosystem
Bird eye's view on Camunda open source ecosystemAsko Soukka
 

Recently uploaded (20)

IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019
IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019
IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019
 
UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...
UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...
UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...
 
201610817 - edge part1
201610817 - edge part1201610817 - edge part1
201610817 - edge part1
 
Machine Learning Model Validation (Aijun Zhang 2024).pdf
Machine Learning Model Validation (Aijun Zhang 2024).pdfMachine Learning Model Validation (Aijun Zhang 2024).pdf
Machine Learning Model Validation (Aijun Zhang 2024).pdf
 
Comparing Sidecar-less Service Mesh from Cilium and Istio
Comparing Sidecar-less Service Mesh from Cilium and IstioComparing Sidecar-less Service Mesh from Cilium and Istio
Comparing Sidecar-less Service Mesh from Cilium and Istio
 
Empowering Africa's Next Generation: The AI Leadership Blueprint
Empowering Africa's Next Generation: The AI Leadership BlueprintEmpowering Africa's Next Generation: The AI Leadership Blueprint
Empowering Africa's Next Generation: The AI Leadership Blueprint
 
AI Fame Rush Review – Virtual Influencer Creation In Just Minutes
AI Fame Rush Review – Virtual Influencer Creation In Just MinutesAI Fame Rush Review – Virtual Influencer Creation In Just Minutes
AI Fame Rush Review – Virtual Influencer Creation In Just Minutes
 
UiPath Community: AI for UiPath Automation Developers
UiPath Community: AI for UiPath Automation DevelopersUiPath Community: AI for UiPath Automation Developers
UiPath Community: AI for UiPath Automation Developers
 
UiPath Studio Web workshop series - Day 8
UiPath Studio Web workshop series - Day 8UiPath Studio Web workshop series - Day 8
UiPath Studio Web workshop series - Day 8
 
NIST Cybersecurity Framework (CSF) 2.0 Workshop
NIST Cybersecurity Framework (CSF) 2.0 WorkshopNIST Cybersecurity Framework (CSF) 2.0 Workshop
NIST Cybersecurity Framework (CSF) 2.0 Workshop
 
Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™
 
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCostKubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
 
How Accurate are Carbon Emissions Projections?
How Accurate are Carbon Emissions Projections?How Accurate are Carbon Emissions Projections?
How Accurate are Carbon Emissions Projections?
 
OpenShift Commons Paris - Choose Your Own Observability Adventure
OpenShift Commons Paris - Choose Your Own Observability AdventureOpenShift Commons Paris - Choose Your Own Observability Adventure
OpenShift Commons Paris - Choose Your Own Observability Adventure
 
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve DecarbonizationUsing IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
 
Designing A Time bound resource download URL
Designing A Time bound resource download URLDesigning A Time bound resource download URL
Designing A Time bound resource download URL
 
9 Steps For Building Winning Founding Team
9 Steps For Building Winning Founding Team9 Steps For Building Winning Founding Team
9 Steps For Building Winning Founding Team
 
Introduction to Matsuo Laboratory (ENG).pptx
Introduction to Matsuo Laboratory (ENG).pptxIntroduction to Matsuo Laboratory (ENG).pptx
Introduction to Matsuo Laboratory (ENG).pptx
 
Computer 10: Lesson 10 - Online Crimes and Hazards
Computer 10: Lesson 10 - Online Crimes and HazardsComputer 10: Lesson 10 - Online Crimes and Hazards
Computer 10: Lesson 10 - Online Crimes and Hazards
 
Bird eye's view on Camunda open source ecosystem
Bird eye's view on Camunda open source ecosystemBird eye's view on Camunda open source ecosystem
Bird eye's view on Camunda open source ecosystem
 

From Use case to User Story

Editor's Notes

  1. discuss background, and explain about segments and at the end of each segments I will pause for any discussions
  2. Here is how we visualize a software project
  3. Typical software projects spend roughly one-third of their overall budget correcting errors that originate in requirements project stakeholders such as clients, end users, develoeprs, testers and managers Years of experience led to development of a number of techniques and models to assist the process Use case model is the most well-known
  4. You might say that this is more for the IT folks, that is not completely true. Example is IDEO story. How innovation is produced from multidiscipline cooperation You will also be involved from .
  5. To understand Use Case, first let’s take a look at Requirements. Requirements are the defined operational capabilities of a system or process that must exist to satisfy a business need. User requirements: tasks that users need to achieve using the software.
  6. Requirements don’t come out of thin air. They are products of systematic discovery and definition process where analyst plays a key role. Software requirements came from process of thinking through three perspectives of requirements.
  7. At the highest level (or business level), you begin by understanding and clarifying the business’ goals and objectives. Then you define the vision on how to achieve it. You ensure that you will build the right software. In addition, you also define the correct project stakeholders.
  8. This is where use cases come in. Use cases is the interaction between an external actor and the system
  9. Technical requirements include functional requirements based on user requirements and nonfunctional requirements
  10. Use cases are fundamentally a text form. The scenario describes how the system should respond to a request of a primary actor to deliver a specific goal of that actor.
  11. (bullet points first) Incidentally actor can be a person, job title or a thing, although generally it is a role The SuD is also an actor.
  12. A scenario describes a sequence of steps that are executed in order to fulfill the goal the use case is supposed to deliver.
  13. We just discussed about some of the use cases components, now we’ll look into the detail of different properties of the each use case
  14. There are different scope depends on the type of use cases
  15. From Alistair Cockburn.
  16. How do we develop use cases
  17. example is shown in the table
  18. scope creep: scope of the projects expands as the work proceeds requirements may change because of changing market and business conditions -> unavoidable manage the avoidable scope creep
  19. The first step is to just name the use cases, and not the details
  20. best practice on how to give a name
  21. elicit: to draw or bring out or forth; educe; evoke: to elicit the truth; to elicit a response with a question.
  22. This is different than the Design Scope
  23. trigger: customer wants money, responses: ATM gave out the money
  24. a context diagram is a simple diagram that represents the system as a single ‘black box” surrounded by its major interfaces, thus showing the system in its environment.
  25. Ensure that each one is necessary to meet the business opportunities in your product vision. To validate, answers the following questions; How does this uc help us achieve our goals and visions Does this use case address some aspect of the problem in our problem statement ? Does this use case differentiate our product in some way ? Do we have use cases to address all the stakeholder and user groups we identified in our vision statement Which use cases will be implemented in our initial release ?
  26. A requirement model is a set of models which acts as a blueprint for a software product. Example are: event lists, use cases, context diagrams, data models, business rules, actor maps, storyboards Defining requirement is a discovery process for users and customers. It evolve from the process of users trying out their requirements through models. Using multiple views (behavior, structure, dynamics, or control ) gives a rich context for eliciting user requirements and aligns with separation of concerns.
  27. The list is with order of increasing complexity
  28. A man is flying in a hot air balloon and realizes he is lost. He reduces height and spots a man down below. He lowers the balloon further and shouts: "Excuse me, can you tell me where I am?" The man below says: "Yes you're in a hot air balloon, hovering 30 feet above this field." "You must be a software developer," says the balloonist. "I am," replies the man. "How did you know?" "Well," says the balloonist, "everything you have told me is technically correct, but it's of no use to anyone." The man below says, "You must work in business as a manager." "I do," replies the balloonist, "but how did you know?" "Well," says the man, "you don't know where you are or where you are going, but you expect me to be able to help. You're in the same position you were before we met but now it's my fault."
  29. conventionally you read use case diagrams from left to right, with actors initiating use cases on the left and actors that receive use case results on the right. Also put primary actor on the top.
  30. When use case A specializes use case B (or B generalizes A) you express that A is “a kind of” B, implying that whatever applies to B also applies to A. A adds to or may override behavior of B.
  31. A typical example is a Summary use case that includes User Goal use cases, or User Goal use case that includes some reusable Subfunction use case. The included use case is typically not complete on its own and is required part of the larger use cases.
  32. Karl Wieger’s Structured Requirements Software Requirements, 2nd Edition, Karl E. Wiegers .
  33. See next screen. Formal and informal use cases describes different permutations. Use case brief may use single paragraph. User stories provides the least context. http://tynerblain.com/blog/2009/02/02/user-stories-and-use-cases/comment-page-1/#comment-497898
  34. http://tynerblain.com/blog/2009/02/02/user-stories-and-use-cases/ Use case briefs may be a single paragraph use case
  35. User stories, as it has less overhead of documentation, it also captures less detail. It is ok with assumption the communication is high. At some point it becomes inefficient.
  36. The level of conversation will be influenced by the level of the reader domain expertise. If the reader already understand the requirements, user stories might be enough. When the developer team struggles to implement the stories, then a more structured documentation is needed. Can the writer trust the reader will understand with brief information ?