Supporting Systems Development by Capturing Deliberations During Requirements Engineering
IEEE Transactions on Software Engineering - Special issue on knowledge representation and reasoning in software development
Goal-directed requirements acquisition
6IWSSD Selected Papers of the Sixth International Workshop on Software Specification and Design
Four dark corners of requirements engineering
ACM Transactions on Software Engineering and Methodology (TOSEM)
Integrating obstacles in goal-driven requirements engineering
Proceedings of the 20th international conference on Software engineering
Towards integrated safety analysis and design
ACM SIGAPP Applied Computing Review - Special issue on saftey-critical software
Problem frames: analyzing and structuring software development problems
Problem frames: analyzing and structuring software development problems
Software safety: where's the evidence?
SCS '01 Proceedings of the Sixth Australian workshop on Safety critical systems and software - Volume 3
Towards Modeling and Reasoning Support for Early-Phase Requirements Engineering
RE '97 Proceedings of the 3rd IEEE International Symposium on Requirements Engineering
Goal-Oriented Requirements Engineering: A Guided Tour
RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
Elaborating Security Requirements by Construction of Intentional Anti-Models
Proceedings of the 26th International Conference on Software Engineering
Requirements Engineering
Establishing regulatory compliance for software requirements
ER'11 Proceedings of the 30th international conference on Conceptual modeling
Arguing regulatory compliance of software requirements
Data & Knowledge Engineering
Hi-index | 0.00 |
A key goal in safety-critical system development is to provide assurance that the critical requirements are sufficiently addressed. This goal is typically refined into three sub-goals, namely that the safety requirements are validated, satisfied and traceable. The achievement of these sub-goals is typically communicated by means of a safety argument supported by items of evidence (e.g. testing, review or analysis). In this paper, we explore the relationships between goals, requirements, and arguments. We discuss how argumentation is used to assure the decomposition and traceability of requirements in safety-critical applications. Particularly, we focus on the achievement of goals related to both the requirements artefacts and the underlying requirements process.