Toward Reference Models for Requirements Traceability
IEEE Transactions on Software Engineering
Logic-based regulation compliance-assistance
ICAIL '03 Proceedings of the 9th international conference on Artificial intelligence and law
Requirements Engineering and Downstream Software Development: Findings from a Case Study
Empirical Software Engineering
ACCA: An Architecture-Centric Concern Analysis Method
WICSA '05 Proceedings of the 5th Working IEEE/IFIP Conference on Software Architecture
RE '06 Proceedings of the 14th IEEE International Requirements Engineering Conference
Complying with Law for RE in the Automotive Domain
RELAW '08 Proceedings of the 2008 Requirements Engineering and Law
Why Eliciting and Managing Legal Requirements Is Hard
RELAW '08 Proceedings of the 2008 Requirements Engineering and Law
Choosing compliance solutions through stakeholder preferences
REFSQ'13 Proceedings of the 19th international conference on Requirements Engineering: Foundation for Software Quality
Hi-index | 0.00 |
[Context & motivation] Large contractual projects often have to comply against government regulations and standards. [Question/problem] In such a context, the contractual document can be voluminous, and there can be a large number of standards and regulations to follow. These documents typically form a complex interrelationship network. This means that in the requirements engineering (RE) process, this network needs to be analysed for deriving project requirements to be implemented. A key activity of this RE process is to demonstrate compliance by showing, through appropriate traces, that all relevant requirements have been elicited from the regulatory documents. [Principal ideas/results] [Contribution] In this problem-statement paper, we describe some key impediments to achieving requirements-compliance that we have identified in a large systems engineering project.