Agile Requirements Engineering with Use Case 2.0

Use Case 2.0 – Wie etabliertes Requirements Engineering
mit agiler Arbeitsweise wirklich zusammengeht
Burkhard Perkens-Golomb – Munich Re
Uwe Valentini – HOOD

Copyright © Munich Re, HOOD GmbH, Ivar Jacobson International SA.2Use Case 2.0 @ Munich Re
Use Case 2.0 @ Munich Re
1. IT Application Development of Munich Re
2. The capabilities of MR‘s Requirements Technique
3. Introducing Use Case 2.0 at Munich Re

The services for Munich Re Application Development
are distributed all over the globe
 Auckland
 Melbourne
 Perth
 Sydney
Munich
 London
 Madrid
 Malta

Moscow
Paris

Milan
Zurich
 Bogotá

 Caracas
 Mexico
 Santiago de Chile
 São Paulo
Buenos Aires
 Accra
 Cape Town

 Nairobi
 Port Louis
Johannesburg
 Beijing
 Calcutta
 Hong Kong
 Kuala Lumpur
 Mumbai
 Seoul
 Shanghai
 Singapore


Taipeh
Tokyo


Chicago
Columbus


Montreal


Philadelphia

Princeton

San Francisco

Toronto
Amelia
New York
Vancouver
Atlanta
Hartford

PM (int/ext)
REQ (int/ext)
TA (int/ext)
DEV Provider Mgmt.
Test Provider Mgmt.
System Operating (ext)
DEV (ext)
TEST (ext)
2nd level support (ext)
Service Desk (ext)
DEV .net (ext)
DEV .net (ext)
TEST (ext)
DEV SAP (ext)
AO (ext)
• The line organization of MR Application Development is divided into disciplines (PM,
Requirements, Technical Architecture, Development, Test etc.)
• High outsourcing & offshoring rates for the services Development and Test

Development
methodology
Iterative and
incremental
development
methodology
Risk-driven
development
approach
Transparency
regarding progress,
cost, and quality via
key figures and
metrics
Quality
Explicit orientation
towards quality
across all activities
and all roles involved
in a project
Explicit Quality
assurance
(e.g. via
Quality gates)
Test-oriented
development &
Continuous
Integration
Tooling and
reuse
Reuse of software
components and
platforms
Ready-made tool
support and
automation for
standard tasks
Learning and
Improvement
Systematic feedback
and continuous
improvement
Core Principles for MR Application Development

The goal of MR‘s approach to application
development, „MR Essentials“
Unlock productivity!

What do we expect from a Requirements Approach?
Much more than just documenting requirements!
Capabilities of
Requirements
Approach
Communicate
System Goals
&
Requirements
Providing
Context
Consistent
Scoping
Relating to
Realizations
Managing
Test Cases
Scaling up,
Scaling out,
Zooming in,
Versatile

Capabilities of
Requirements
Approach
Communicate
System Goals
&
Requirements
Providing
Context
Consistent
Scoping
Relating to
Realizations
Managing
Test Cases
Scaling up,
Scaling out,
Zooming in,
Versatile
How you could do it
(and how we did it in the past)
Inconsistent Approach
Less Efficiency
 substantial transformation
overhead
 high risk of inconsistency
 high risk of misunderstandings

Capabilities of
Requirements
Approach
Communicate
System Goals
&
Requirements
Providing
Context
Consistent
Scoping
Relating to
Realizations
Managing
Test Cases
Scaling up,
Scaling out,
Zooming in,
Versatile
What Use Case 2.0 promises
(and can deliver …)
Consistent
Approach
More
Efficiency

Everyone understands „Use Cases“ –
do we have the same understanding of „Use Cases“?
Imagine: A Scrum team consists of 8 members. They work to build an Ebay clone.
The team is very experienced and highly productive right from the beginning.
Your guess: Looking at a timeframe of 6 months, how many use cases can they
deliver (specify, implement, verify) in this timeframe?
1-10 Use Cases ready for go-live
11-100 Use Cases ready for go-live
>100 Use Cases ready for go-live
Please vote!

Everyone understands „Use Cases“ –
do we have the same understanding of „Use Cases“?
0-10
11-49
50-99
100-999
> 1000
Imagine: A Scrum team consists of 8 members. They work to build an Ebay clone.
The team is very experienced and highly productive right from the beginning.
Your guess: Looking at a timeframe of 6 months, how many use cases can they
deliver (specify, implement, verify) in this timeframe?
In the industry we do not have a common understanding of „Use Case“!
Distribution of answers by an industry
interest group for Requirements
Engineering (~ 40 people):
# of use cases implemented after 6
months by a team of 8.

Capabilities of
Requirements
Approach
Communicate
System Goals
&
Requirements
Providing
Context
Consistent
Scoping
Relating to
Realizations
Managing
Test Cases
Scaling up,
Scaling out,
Zooming in,
Versatile

Use Case Model Diagram
Use Case Catalog
Actor Catalog
The Use Case Model Survey describes system goals
and interaction
Locate
Store
Browse &
Shop
Checkout
Manage
Account
Manage
Orders
Maintain
Products
Shopper
Customer
Product
Manager
Mapping
System
Payment
System
Stock Control
System
Order Mgmt.
System
Product
Catalog
Name Brief Description
Browser Any individual browsing the store. They
may or may not have a Cyberstore online
shopping account. They can browse
products, locate stores and fill and
manage the contents of their shopping
basket.
Customer A Cyberstore customer that has an online
shopping account. They can checkout
and pay for purchases, maintain their
online account and manage their online
orders.
… …
Name Brief Description
Browse
and Shop
Enables visitors to the online store to
browse product information, add products
to a shopping basket and manage the
contents of their basket.
Checkout Enables customers to take a basket of
products through the checkout system by
finalizing their order options and paying
for their order.
… …

Use Case Narratives tell the story of how the system
and its users work together to achieve a particular goal
DIY-UC01 Browse and Shop
Enables visitors to the online store to browse product
information, add products to a shopping basket and
manage the contents of their basket.
DIY-UC04 Locate Store
Enables an online customer to find a store by browsing,
searching or specifying a post code.
Basic Flow
1) Browse Products by Category
2) Add Product to Basket
Alternative Flows
AF01 – Keyword Search for Products
AF02 – Add to Wish List
AF03 – Remove from Wish List
AF04 – Save for Later
AF05 – Delete from Basket
AF06 – Add Saved Item to Basket
AF07 – Add Wish List Item to Basket
AF08 – Basket Emptied
AF09 – Review a Product
AF10 – Publish List of Favorites
AF11 – Product Catalogue Unavailable
Basic Flow
1) Provide User Postcode
2) Submit Store Location Request
3) Display list of nearest three stores
4) Select store
5) Display map and directions
Alternative Flows
AF01 – Invalid Postcode
AF02 – Search Using Place Name
AF03 – Browse for Store
Browse &
Shop
Shopper Product Catalog
Locate
Store
Shopper Mapping System
… and Narratives in their most condensed form („bulleted outline“) might be enough to do the job!

UC 2.0: System Goals, Requirements , Context
Advantages & Challenges
Advantages Challenges
 Providing complete & consistent overview
 Providing context for every requirement
 Quickly created & easily understandable
 Solution-agnostic description
o Relearning what Use Cases are
o Finding the „right“ structure of the Use Case
Model
o Solution-agnostic description
o  Training & coaching is essential.

Capabilities of
Requirements
Approach
Communicate
System Goals
&
Requirements
Providing
Context
Consistent
Scoping
Relating to
Realizations
Managing
Test Cases
Scaling up,
Scaling out,
Zooming in,
Versatile

MR Essentials separates endeavours into
five levels of timeframes with different objectives
Product Lifecycle (PLC)
Iteration
Slice
Software Development Lifecycle (SDLC)
Task
Objective
Typical
Timeframe
Plan new
releases
Several
years
Provide a
release
Few months
to 1 year
Implement &
demonstrate
an increment
2-4 weeks
Implement &
verify a slice of
requirements
<= few days
Get some work
done
½-1 day
Release
LinkingElement?

Use Cases and Story Telling are relatives –
Use Case Narratives tell many stories!
Start of use case
End of use case
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Alt 1
Alt 2
Alt 3
A use-case
narrative
houses
tells
many stories!

Use Case Slices
represent a story
(a specific thread through
use case flows and
special requirements)
passed
failed
Executing Test Cases
verifies that the system
works as specified by
the requirements
Use Case Slices
represent a thread though
System Architecture and
its Components
A successful test is key to
close a slice and to show
progress in a project.
The use case slice drives all the work from
requirements to implemented and tested code
Use Case Slices define the scope
of a release and of an iteration
Cycle Time:
< few days!
 It‘s key to master many „slicing techniques“ to make Use Case Slices very small!

UC 2.0: Consistent Scoping
 Consistency of scope definitions across all
levels of scope
 Fostering collaboration
 Fulfilling quality criteria for backlog items
 Integrates easily in agile processes
o Replacing of established techniques
o Finding the „right“ structure of the Use Case
Model
o The „smallness“ of Use Case Slices is key
o Communication between all disciplines

Capabilities of
Requirements
Approach
Communicate
System Goals
&
Requirements
Providing
Context
Consistent
Scoping
Relating to
Realizations
Managing
Test Cases
Scaling up,
Scaling out,
Zooming in,
Versatile

Why you should base the management of Test Cases
on your requirements …
The Auditors asked me, if our
5.000 test cases cover the
specification good enough.
Can you please
provide evidence,
e.g. by a test
coverage report?
Ouch. That means
much work for
reengineering
Slide by Melanie Wohnert, the coaches

Enter
email
address
Use Cases Slices and therefore Use Case Flows
have a 1:n relationship to Test Cases
Scenario
derived
from the
Use Case
- Insert email address with no ‘@’
- Verify that error message appears
Inputs and
expected results
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Alt 1
Alt 2
Alt 3
Alt 4

UC 2.0: Managing Test Cases
 Easy navigation for Test Cases
 Test Design starts early
 Easy determination of test coverage
 Testers work incrementally without loosing
the big picture
o Incremental Testing is big change
o Trust between disciplines
o Tooling for Test Management

Capabilities of
Requirements
Approach
Communicate
System Goals
&
Requirements
Providing
Context
Consistent
Scoping
Relating to
Realizations
Managing
Test Cases
Scaling up,
Scaling out,
Zooming in,
Versatile

Scaling Up Scaling Out
Zooming In Versatile
As lightweight as you want, as scalable as you need,
applies in a wide range of situations !
Use-Case 2.0 scales without changing
the fundamentals from small teams and
small projects to large organizations
and large projects.
Though Use-Case 2.0 starts with
requirements, it scales to many other
lifecycle activities such as analysis,
design, code, test, user experience,
business design, etc.
Use-Case 2.0 allows you to be as light as
you want, focusing on the essentials only,
or to zoom in with more and more
detail for systems such as telecom or
defense systems or more regulated
systems such as life-critical systems.
Without changing the fundamentals, Use
Case 2.0 applies for
• traditional & agile approaches,
• COTS, MOTS, SAAS, etc.
• greendfield, brownfield,
• etc.

UC 2.0: Scaling, Zooming, Versatile
 Scaling Up for larger teams or organizations
 Scaling Out for all development activities
 Zooming In for greater level of detail
 Versatile for traditional & agile approaches,
COTS, SAAS, etc.
o Adoption per project necessary, needs
experience

What Use Case 2.0 provides:
Use Case
2.0
Communicate
System Goals
&
Requirements
Providing
Context
Consistent
Scoping
Relating to
Realizations
Managing
Test Cases
Scaling up,
Scaling out,
Zooming in,
Versatile

Engaged
Prepared
Aware
Practicing
Expert
Practitioner
Trainings
Coaching
(Teams &
Individuals)
Introductory
Training
Method Adoption Levels for Project Teams
The team is self-sufficient:
• continuously measures and
improves its performance
• Uses MR Essentials as
business-as-usual
• Has at least 1 master partitioner
per practice
They have all the essentials in-
place:
• The practice is being used
effectively for the benefit of the
team
• The team is being monitored and
encouraged to improve
They are being actively mentored:
• The practice is being used
• The team are pro-actively
working with the mentor to
improve things
They understand the practices
selected and what adopting them
would mean:
• Been on training events, read
the books etc
They are ready to start using the
practice in earnest:
• Achieved practitioner
certification
• Mentoring agreement in place /
mentoring plan in place
source:www.bilder.mzibo.net
Introducing MR Essentials: Get Started with the Help
through Training and by a Team Coach

The change needs strong coaching support: We
provide internal & external coaches at all sites

Thank You for Your Attention.
Do You have any Questions ?

Agile Requirements Engineering with Use Case 2.0

Recommended

Recommended

More Related Content

Similar to Agile Requirements Engineering with Use Case 2.0

Similar to Agile Requirements Engineering with Use Case 2.0 (20)

More from HOOD Group

More from HOOD Group (17)

Recently uploaded

Recently uploaded (20)

Agile Requirements Engineering with Use Case 2.0