Progressing problems from requirements to specifications in problem frames
Proceedings of the 3rd international workshop on Applications and advances of problem frames
Proceedings of the 3rd international workshop on Applications and advances of problem frames
Classifying Assumptions Made during Requirements Verification of Embedded Systems
REFSQ '08 Proceedings of the 14th international conference on Requirements Engineering: Foundation for Software Quality
A Formal Metamodel for Problem Frames
MoDELS '08 Proceedings of the 11th international conference on Model Driven Engineering Languages and Systems
A UML profile for requirements analysis of dependable software
SAFECOMP'10 Proceedings of the 29th international conference on Computer safety, reliability, and security
Making pattern- and model-based software development more rigorous
ICFEM'10 Proceedings of the 12th international conference on Formal engineering methods and software engineering
System verification through program verification
FM'11 Proceedings of the 17th international conference on Formal methods
Assessing project effort in requirements engineering: a report on design research in progress
DESRIST'10 Proceedings of the 5th international conference on Global Perspectives on Design Science Research
Identifying problem frames for location-based services
Proceedings of the 6th International Conference on Ubiquitous Information Management and Communication
Requirements modelling by synthesis of deontic input-output automata
Proceedings of the 2013 International Conference on Software Engineering
A taxonomy for requirements engineering and software test alignment
ACM Transactions on Software Engineering and Methodology (TOSEM)
Hi-index | 0.00 |
A technique is presented for obtaining a specification from a requirement through a series of incremental steps. The starting point is a Problem Frame description, involving a decomposition of the environment into interconnected domains and a formal requirement on phenomena of those domains. In each step, the requirement is moved towards the machine, leaving behind a trail of “breadcrumbs”—partial domain descriptions representing assumptions about the behaviors of those domains. Eventually, the transformed requirement references only phenomena at the interface of the machine and can therefore serve as a specification. Each step is justified by a mechanically checkable implication, ensuring that, if the machine obeys the derived specification and the domain assumptions are valid, the requirement will hold. The technique is formalized in Alloy and demonstrated on two examples.