210 likes | 400 Views
Outline. GSNPast successRepresenting and communicating safety casesArgument patterns/meta-argumentsCurrent experimentsRequirements managementDesign rationalePreliminary safety argumentsFuture directionsMore applications such as assurance casesTighter integration with the system development
E N D
1. Requirements, Rationale and Arguments Weihang Wu
HISE Group
Department of Computer Science
2. Outline GSN
Past success
Representing and communicating safety cases
Argument patterns/meta-arguments
Current experiments
Requirements management
Design rationale
Preliminary safety arguments
Future directions
More applications such as assurance cases
Tighter integration with the system development process
More automation involved
Seamlessly incremental development
3. GSN Goal Structuring Notation
Goal, context, assumption, justification, and solution
GSN pattern features such as multiplicity and optionality
New modular features such as away goal
4. Past Success Representing and Communicating Safety Cases
Graphical notations
A hierarchical structure of safety arguments
How safety claims are met by evidence found
Use of explicit context
Developing Safety Cases
A generic development process
Introduction of safety case patterns
Multiplicity extension
Optionality extension
Entity abstraction extension
Introduction of modular development features
Safety case modules
Away goals
5. Requirements Management 1 Goal-Oriented Requirements Engineering
Requirements definition must say why a system is needed
Intent/Objective/Need/Goal
Goal formulation
Goal types and taxonomies
Semi-formal and formal techniques
Goal refinement
AND/OR refinement
Domain-specific patterns
A hierarchical goal structure via goal links
Goal-oriented approaches
KAOS (Knowledge Acquisition and autOmated Specification)
NFR (Non-Functional Requirements) framework
Benefits
Requirements traceability
Tradeoffs & conflicts management
V&V
6. Requirements Management 2 An Aircraft Wheel Braking System (WBS) Example Using KAOS