Date post: | 15-Apr-2017 |
Category: |
Software |
Upload: | daniel-mendez |
View: | 67 times |
Download: | 0 times |
Daniel Méndez
Technische Universität MünchenGermany
PROFES 2013Paphos, Cyprus
13.06.2013
Technische Universität München
Improving Requirements Engineering by Artefact Orientation
Joint work withRoel Wieringa, University of Twente @mendezfe
• Software Process Improvement (SPI)
Requirements Engineering Process Improvement Context
Planning
Appraisal / Analysis
Imple-mentation
Evaluation
• Requirements Engineering (RE)➡Highly volatile discipline
(project-specific variations, dependency to application domains, ...)
How to conduct Requirements Engineering Process Improvement?
„Define and outline requirements“
➡Low degree of standardisation possible
ReferenceReference
Requirements Engineering Process Improvement Principles and Paradigms (simplified)Improvement Principles1. Solution-driven➡Assessment against external norm /
benchmark against pre-defined criteriaOther terms: deductive, prescriptive, normative
1
2
SW Process Paradigms (simplified)A. Activity-based
➡Focus on activities, methods, practices
2. Problem-driven➡Analysis of company-specific problems
and goal-driven improvement design(criteria for improvement elicited) Other terms: inductive, goal-driven
Socio-economic context
B. Artefact-based
➡Focus on artefacts, dependencies, roles
A
B
Improving RE by Artefact orientation Why?
• Reluctance against benchmark-driven, normative REPI approaches***Qualitative analyses
Metrics
0 20 40 60 80%
No solution-driven RE improvement
„I am not convinced of the benefits of external standards.“
Why Problem Orientation: Survey on RE
* Mendez et al. A Meta Model for Artefact Orientation: Fundamentals and Lessons Learnt in Requirements Engineering (MoDELS’10) Mendez et al. A Case Study on the Application of an Artefact-based Requirements Engineering Approach (EASE’11)** Mendez et al. Pattern-based Guideline to Empirically Analyse Software Development Processes (EASE’12)*** Mendez et al. Naming the Pain in Requirements Engineering (TR’13, EASE’13)
Why Artefact Orientation: Experiences from Research Projects• Application: Advantages w.r.t. certain criteria including flexibility in RE process and improvement of artefacts‘ syntactic quality*• Design: Eases RE analysis and (process) design **
Improving RE by Artefact orientation How?
Starting point: Empirical design science principles➡Knowledge/Technology transfer➡Problem and goal orientation
Design Science Activities
Practical Problem Solving
Knowledge Question
Investigation
Goal
Artefact
MutualNesting
Use
Add Knowledge Base
Socio-economic
Context, e.g., an Organisation
* R. Wieringa. Technical Action Research as a Validation Method in Information Systems Design Science (DESRIST 2012)
Implementation Evaluation / Problem Investigation
Treatment DesignDesign Validation
Treatment Implementation
Engineeringcycle
(simplified)
➡ Design treatment in an artefact-oriented manner!
➡ Design specific-purpose treatment to individual problem!
RE Improvement Problem Investigation
Design and Validation of Improvement Transfer
Artefact-based RE Improvement Design and Validation
Investigation of REArtefacts
Investigation of Stakeholdersand Goals
Stakeholder & Goal Elaboration
Goals&
Metrics
Art.-based RE Analysis
Reporting & Decision Analysis
Report
Kick-OffConceptualisation
art.-based RE
Constructionart.-based RE
Re-designedRE ConceptModel
ImplementedRE Approach
Design of Process Integration
Evaluation in Pilot
EvaluationReport
Artefact-based RE Reference Model ("BISA")
Artefact Meta Model
Project Planning & Decision
Validation
Training Design
ReleaseRelease Planning
Treatment Design & Design Validation
Improving RE by Artefact orientation Approach resulting from Research Projects
Application of empirical design science principles
Inference of least common denominators
Implementation Evaluation / Problem Investigation
Treatment DesignDesign Validation
Treatment Implementation
Engineeringcycle
Improving RE by Artefact orientation A brief Overview
RE Improvement Problem Investigation
Design and Validation of Improvement Transfer
Artefact-based RE Improvement Design and Validation
Investigation of REArtefacts
Investigation of Stakeholdersand Goals
Stakeholder & Goal Elaboration
Goals&
Metrics
Art.-based RE Analysis
Reporting & Decision Analysis
Report
Kick-OffConceptualisation
art.-based RE
Constructionart.-based RE
Re-designedRE ConceptModel
ImplementedRE Approach
Design of Process Integration
Evaluation in Pilot
EvaluationReport
Artefact-based RE Reference Model ("BISA")
Artefact Meta Model
Project Planning & Decision
Validation
Training Design
ReleaseRelease Planning
Treatment Design & Design Validation
Artefact-based
introduction
InterpretationPreparation Data Collection & Analysis
t
Jour Fixe 1 Jour Fixe ... Jour Fixe NKick-Off Final Discussion
Qualitative
analysis
of the data
External
researchers (TUM)
1 2 3
2 weeks 2 weeks
- Initial data collection
- Agreement on
study design- Discussion results
- Proposal of strategy
Incremental data
collection and
discussion of
(previous) results
Domain experts (DLH)
External
researchers (TUM)
Improving RE by Artefact orientation Investigation of Stakeholders & Goals
1. Stakeholders, goals (and criteria)2. Company background and RE definition3. REPI plan
* Mendez et al. Pattern-based Guideline to Empirically Analyse Software Development Processes (EASE 2012)
Goals1. Understand context2. Elicit background 3. Define goals and measurement of (improvement) success
Results
RE Improvement Problem Investigation
Design and Validation of Improvement Transfer
Artefact-based RE Improvement Design and Validation
Investigation of REArtefacts
Investigation of Stakeholdersand Goals
Stakeholder & Goal Elaboration
Goals&
Metrics
Art.-based RE Analysis
Reporting & Decision Analysis
Report
Kick-OffConceptualisation
art.-based RE
Constructionart.-based RE
Re-designedRE ConceptModel
ImplementedRE Approach
Design of Process Integration
Evaluation in Pilot
EvaluationReport
Artefact-based RE Reference Model ("BISA")
Artefact Meta Model
Project Planning & Decision
Validation
Training Design
ReleaseRelease Planning
Treatment Design & Design Validation
* Mendez et al. Field Study on Requirements Engineering: Investigation of Artefacts, Project Parameters, and Execution Strategies (IST 2012)
Improving RE by Artefact orientation Investigation of RE Artefacts
Results
Goals1. Analyse current state 2. Trigger self-reflection
1. „As-Is“ artefact model
2. Gap analysis (w.r.t. reference model and goals)
3. Expert opinion: - “Why is it as it is?”- “What could and should be changed?”
* Mendez et al. Pattern-based Guideline to Empirically Analyse Software Development Processes (EASE 2012)
RE Improvement Problem Investigation
Design and Validation of Improvement Transfer
Artefact-based RE Improvement Design and Validation
Investigation of REArtefacts
Investigation of Stakeholdersand Goals
Stakeholder & Goal Elaboration
Goals&
Metrics
Art.-based RE Analysis
Reporting & Decision Analysis
Report
Kick-OffConceptualisation
art.-based RE
Constructionart.-based RE
Re-designedRE ConceptModel
ImplementedRE Approach
Design of Process Integration
Evaluation in Pilot
EvaluationReport
Artefact-based RE Reference Model ("BISA")
Artefact Meta Model
Project Planning & Decision
Validation
Training Design
ReleaseRelease Planning
Treatment Design & Design Validation
Improving RE by Artefact orientation Artefact-based RE Improvement Design and Validation
Results
Goals1. Re-design “as-is” model (let the participants do it!)2. Knowledge transfer
1. Sketch of „to-be“ artefact model - (canonical) action research- Artefacts and dependencies- Roles and responsibilities- Variations (for Tailoring)
2. Conceptualisation
3. Implementation
class BusinessBehav iour
Artefact Type: Business Specification
Content Item: Business Capabilities
Content Item: BusinessService Model
Content Item: Business Process Model
«enumeration»Business Process
Category
core process supporting process
«Concept Type»Business Process
«Concept Item»Ev ent
«Concept Item»Actvity
- behaviour description- id
«Concept Type»Business Task
«Concept Item»Process Step
«Concept Type»Business Serv ice
- description- id- protocol
0..*
uses
0..*
1..*
has
1
0..*
1
*
relates to
*
0..*1
1..*
provides
0..*
0..*
1
0..*
1
0..*
uses
0..*
1triggers
1..*
RE Improvement Problem Investigation
Design and Validation of Improvement Transfer
Artefact-based RE Improvement Design and Validation
Investigation of REArtefacts
Investigation of Stakeholdersand Goals
Stakeholder & Goal Elaboration
Goals&
Metrics
Art.-based RE Analysis
Reporting & Decision Analysis
Report
Kick-OffConceptualisation
art.-based RE
Constructionart.-based RE
Re-designedRE ConceptModel
ImplementedRE Approach
Design of Process Integration
Evaluation in Pilot
EvaluationReport
Artefact-based RE Reference Model ("BISA")
Artefact Meta Model
Project Planning & Decision
Validation
Training Design
ReleaseRelease Planning
Treatment Design & Design Validation
Improving RE by Artefact orientation Design and Validation of Improvement Transfer
Results
Goals1. Evaluate results in projects (against goals)2. Prepare and support dissemination
1. Process integration
2. Evaluation (action research)
3. Training material (boring part...)
* Mendez et al. A Case Study on the Application of an Artefact-based Requirements Engineering Approach (EASE 2011)
RE Improvement Problem Investigation
Design and Validation of Improvement Transfer
Artefact-based RE Improvement Design and Validation
Investigation of REArtefacts
Investigation of Stakeholdersand Goals
Stakeholder & Goal Elaboration
Goals&
Metrics
Art.-based RE Analysis
Reporting & Decision Analysis
Report
Kick-OffConceptualisation
art.-based RE
Constructionart.-based RE
Re-designedRE ConceptModel
ImplementedRE Approach
Design of Process Integration
Evaluation in Pilot
EvaluationReport
Artefact-based RE Reference Model ("BISA")
Artefact Meta Model
Project Planning & Decision
Validation
Training Design
ReleaseRelease Planning
Treatment Design & Design Validation
Preliminary Results from Empirical Evaluation
Artefact-based RE Improvement (RQ 1)
Resulting RE Reference Model (RQ 2)
Our ApproachPreviously used Approach
Structuredness
Simplicity
Goal Orientation
Experience Orientation
Sustainability
Flexibility
Syntactic QualityRE Artefacts
Traceability
Semantic QualityRE Artefacts
Ease of Use
Testability
Process Integration
Adaptability(Tailoring)
Context• Wacker Chemie AG
• 5 process engineers
• 3 pilot projects
• Improvement goal: Traceability and integration of RE with QA
Research questions1. How well are process engineers
supported in their RE improvement task?2. How well are project participants
supported by the new RE reference model?
Evaluation
REPI endeavour
Preliminary rating
Final rating after completion of pilot
projects
Process Engineering View1. Support of knowledge transfer
2. Support of goal orientation
3. Confirmed experience orientation
Project View1. Increased syntactic quality (condensed)
2. Increased traceability (project goal)
Artefact-based RE Improvement (RQ 1)
Resulting RE Reference Model (RQ 2)
Our ApproachPreviously used Approach
Structuredness
Simplicity
Goal Orientation
Experience Orientation
Sustainability
Flexibility
Syntactic QualityRE Artefacts
Traceability
Semantic QualityRE Artefacts
Ease of Use
Testability
Process Integration
Adaptability(Tailoring)
Validity: Only preliminary results➡We need extension and further evaluations!
Preliminary Results from Empirical Evaluation
• So far, we seem to have avoided the pitfalls of current solution-driven REPI approaches– Focus on artefacts eases structuredness & supports quality in RE artefacts– Support of knowledge transfer and problem-driven improvement
• “Not invented here”-syndrom tackled by action research➡Early involvement of stakeholders➡Problem-driven analysis, design (and evaluations)
• Also: • Higher effort!• Does not replace solution-driven approaches!
We are still learning... • Rated as hard to be applied by others
➡ REPI is also about social skills!
• REPI is part of a holistic change process
Future Work• Support partner in change process (& learn from it!)• Finalise evaluation and report full results
Conclusion
A final note about the reviewers: “Thank you for some very good suggestions!”
Thank you!