Requirements Specification with BPMN 2.0 in WTO procurement Présentation du projet CARES à l'occasion du Workshop BPM im Öffentlichen Sektor (BPMÖS) organisé dans le cadre de la conférence Informatik 2014.

1. Institut d’Informatique
de Gestion
CARES: Computer-Aided Requirements
Engineering Software
Requirements Specification with BPMN
2.0 in WTO procurement
Prof. Florian Evéquoz, Daniel Hadrian
HES-SO Valais // Wallis, 2014
HES-SO Master Lausanne

2. Institut d’Informatique
de Gestion
Overview
• Context: Public Procurement
– Regulations
– Appeals, costs
– Problem: specify the need à RS
• Requirements specification (RS)
– comprehensiveness, completeness, reduce ambiguity
– avoid extra cost
– business context
– assessment and evaluation
• CARES Methodology
– Innovation by using business processes as a foundation (systematic,
business oriented)
– Incorporate literature and best practices
• Prototype
• Conclusion & Perspectives
23.09.2014 2

3. Institut d’Informatique
de Gestion
CONTEXT: PUBLIC
PROCUREMENT
23.09.2014 © 2013 Daniel Hadrian, Florian Evéquoz Hes-so Valais//Wallis 3

4. Institut d’Informatique
de Gestion
Context: Public procurement
• Regulations:
– Threshold values for public expenditure
• 150’000 – 250’000
– Equity of treatment
– Fair use of public funds
– Transparency
23.09.2014 © 2013 Daniel Hadrian, Florian Evéquoz Hes-so Valais//Wallis 4

5. Institut d’Informatique
de Gestion
REQUIREMENTS
SPECIFICATION
23.09.2014 © 2013 Daniel Hadrian, Florian Evéquoz Hes-so Valais//Wallis 5

6. Institut d’Informatique
de Gestion
Known issues in public procurements
Quelle: Peter Fischer,
Delegierter ISB
23.09.2014 © 2013 Daniel Hadrian, Florian Evéquoz Hes-so Valais//Wallis 6

7. Institut d’Informatique
de Gestion
What happens with bad specification?
23.09.2014 © 2013 Daniel Hadrian, Florian Evéquoz Hes-so Valais//Wallis 7

8. Institut d’Informatique
de Gestion
How to deal with public procurements
Public procurement
Call for bids
Decision
Need
23.09.2014 © 2013 Daniel Hadrian, Florian Evéquoz Hes-so Valais//Wallis 8
Need satsified
• Specify the
whole need
• Specify the
requirements
• Validate
requirements
• Select a
procedure
• Evaluate the
bidders
• Check legal
aspects
• Evaluate the
bidders
• Decide
• Appeals

9. Institut d’Informatique
de Gestion
What is a good Requirements
Specification
• Comprehensive and complete to avoid extra cost
• No ambiguity
– validated by business users
– used by IT-specialists
• Allows the precise assessment and evaluation of
the bids
– To ensure quality in the decision process
– To avoid appeals
– To evaluate the product
23.09.2014 © 2013 Daniel Hadrian, Florian Evéquoz Hes-so Valais//Wallis 9

10. Institut d’Informatique
de Gestion
CARES METHODOLOGY
23.09.2014 © 2013 Daniel Hadrian, Florian Evéquoz Hes-so Valais//Wallis 10

11. Institut d’Informatique
de Gestion
Methodology for RS
Model business
processes
Specify
requirements
Weight
requirements
Consolidate
in a template
23.09.2014 © 2013 Daniel Hadrian, Florian Evéquoz Hes-so Valais//Wallis 11

12. Institut d’Informatique
de Gestion
Why start with business processes?
• Allow the business users to validate the
requirements
• Make sure the whole need is specified
• Use BPMN
– International standard for process documentation
– Bridge the gap between business and IT people
Model business
processes
Specify
requirements
Weight
requirements
Consolidate in
a template
23.09.2014 © 2013 Daniel Hadrian, Florian Evéquoz Hes-so Valais//Wallis 12

13. Institut d’Informatique
de Gestion
Why start with business processes?
The first level gives an overview of the
domains of activities (inventory of services).
Services are delivered by processes.
The second level gives details on each service
group of the inventory.
The third level show the end-to-end process
delivering the service selected on the second
The fourth level show all details and
complexity of the process selected on the
Model business
processes
level
third level.
Specify
requirements
Weight
requirements
Consolidate in
a template
Inventory
(Process landscape)
Services
Processes
Sub-Proceses
23.09.2014 © 2013 Daniel Hadrian, Florian Evéquoz Hes-so Valais//Wallis 13

14. Institut d’Informatique
de Gestion
How to specify requirements?
• Systematically review the processes
• Add requirements on
– processes (global requirements)
– shapes (functional requirements)
– messages (mostly non functional requirements)
• Use a standardized phrase pattern
à Business user do it themselves
Model business
processes
Specify
requirements
Weight
requirements
Consolidate in
a template
23.09.2014 © 2013 Daniel Hadrian, Florian Evéquoz Hes-so Valais//Wallis 14

15. Institut d’Informatique
de Gestion
How to specify requirements?
Model business
processes
Specify
requirements
Weight
requirements
Consolidate in
a template
23.09.2014 © 2013 Daniel Hadrian, Florian Evéquoz Hes-so Valais//Wallis 15

16. Institut d’Informatique
de Gestion
Weight requirements
• Common understanding between users of the
importance of the requirements
• Foundation for the evaluation
– The evaluation scale is public
– Guarantees the equity of treatment
Model business
processes
Specify
requirements
Weight
requirements
Consolidate in
a template
23.09.2014 © 2013 Daniel Hadrian, Florian Evéquoz Hes-so Valais//Wallis 16

17. Institut d’Informatique
de Gestion
Use a standard template
• Using the same template allows:
– systematization for the writers of the RS
– the bidders to familiarize easier and faster with the
documents
• Our template is based on the recommendations of
– IEEE 830-1998 recommended practice for software
requirements specifications
– IEEE 1233-1998 Guide for Developing System
Requirements Specifications
Model business
processes
Specify
requirements
Weight
requirements
Consolidate in
a template
23.09.2014 © 2013 Daniel Hadrian, Florian Evéquoz Hes-so Valais//Wallis 17

18. Institut d’Informatique
de Gestion
Modified IEEE Recommended Practices
template
– Product perspective* CONVERSATION DIAGRAMS FOR SYSTEM PERIMETER
– Product functions* PROCESS MAPS
– User characteristics
– Constraints
– Assumptions and dependencies
• Specific requirements* END-TO-END PROCESSES
Model business
processes
Specify
requirements
Weight
requirements
Consolidate in
a template
• Introduction
– Purpose
– Scope
– Definitions, acronyms, and abbreviations
– References
– Overview *
• Overall description
– End-to-end process 1 “Name of the Process”
• Use-case 1 “Name of the use-case”
• Use-case 2 “Name of the use-case”
– End-to-end process 2 “Name of the Process”
• Use-case 1 “Name of the use-case”
• Use-case 2 “Name of the use-case”
– Etc.
23.09.2014 © 2013 Daniel Hadrian, Florian Evéquoz Hes-so Valais//Wallis 18

19. Institut d’Informatique
de Gestion
PROTOTYPE
23.09.2014 © 2013 Daniel Hadrian, Florian Evéquoz Hes-so Valais//Wallis 19

20. Institut d’Informatique
de Gestion
Concept of «CARES»
• CARES: Computer Aided Requirements
Engineering Software:
– Supports the methodology
– Simplifies communication
– Guides the user in the process of gathering,
specifying and weighting requirements
– Allows for traceability of requirements
23.09.2014 © 2013 Daniel Hadrian, Florian Evéquoz Hes-so Valais//Wallis 20

21. Institut d’Informatique
de Gestion
Concept of «CARES»
Business
user
BPMN
Process
documentation
Procurement
documents
Project
manager
IT-Specialist
non-functional
requirements
&
weights
Monitoring / QS
Functional
requirements
&
weights
CARES
GUI DB
BPMN
Process
documentation
23.09.2014 © 2013 Daniel Hadrian, Florian Evéquoz Hes-so Valais//Wallis 21

22. Institut d’Informatique
de Gestion
Information architecture
Home (login)
Selected by default
Projects Requirement
Manager Collaborator Learn
Cares Trash
My
Projects Shared
projects
New Cares Project 1 Project 2
Project
Add New
Requirement
Files Process Files Files
BPMN process with
requirements specified Requirements in
Tabular manner
Requirement
Specification Project
Details
Folders
23.09.2014 © 2013 Daniel Hadrian, Florian Evéquoz Hes-so Valais//Wallis 22

23. Institut d’Informatique
de Gestion
Information architecture
Home (login)
Selected by default
Projects Requirement
Manager Collaborator Learn Cares Trash
Latest Projects (All
Requirements)
Tabular
View Graphical
View
Projects browser
search Edit Save/Print Customize
Requirement
Specification
Filters Add/delete/
23.09.2014 © 2013 Daniel Hadrian, Florian Evéquoz Hes-so Valais//Wallis 23

24. Institut d’Informatique
de Gestion
Information architecture
Home (login)
Selected by default
Projects Requirement Manager Collaborator Learn Cares Trash
Latest working project
Projects browser
Share Approval Comments Live discussion Customize
23.09.2014 © 2013 Daniel Hadrian, Florian Evéquoz Hes-so Valais//Wallis 24

25. Institut d’Informatique
de Gestion
Demo
23.09.2014 © 2013 Daniel Hadrian, Florian Evéquoz Hes-so Valais//Wallis 25

26. Institut d’Informatique
de Gestion
CONCLUSION &
PERSPECTIVES
23.09.2014 © 2013 Daniel Hadrian, Florian Evéquoz Hes-so Valais//Wallis 26

27. Institut d’Informatique
de Gestion
Validation
• Informal validation of the methodology has been
carried out in real projects
– Canton Bern
– Canton Basel-Stadt
– City of Lucerne
• Procurement process using the methodology
successful (incl. no appeals)
23.09.2014 © 2014 Daniel Hadrian, Florian Evéquoz Hes-so Valais//Wallis 27

28. Institut d’Informatique
de Gestion
Perspectives
• Business model
• Further development
• Searching for business partners
• Target private corporations as well as the public
sector
23.09.2014 © 2014 Daniel Hadrian, Florian Evéquoz Hes-so Valais//Wallis 28

29. Institut d’Informatique
de Gestion
Thank you
Contact
Prof. Dr. Florian Evéquoz
Technoark 3
3960 Sierre
florian.evequoz@hevs.ch
23.09.2014 © 2013 Daniel Hadrian, Florian Evéquoz Hes-so Valais//Wallis 29