Communicating sequential processes
Communicating sequential processes
Introduction to mathematical logic (3rd ed.)
Introduction to mathematical logic (3rd ed.)
ACM Transactions on Software Engineering and Methodology (TOSEM)
Programming from specifications (2nd ed.)
Programming from specifications (2nd ed.)
Four dark corners of requirements engineering
ACM Transactions on Software Engineering and Methodology (TOSEM)
Problem frames: analyzing and structuring software development problems
Problem frames: analyzing and structuring software development problems
CREWS-SAVRE: Scenarios for Acquiring and Validating Requirements
Automated Software Engineering
Goal-Oriented Requirements Engineering: A Guided Tour
RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
Architecture-driven Problem Decomposition
RE '04 Proceedings of the Requirements Engineering Conference, 12th IEEE International
A refinement calculus for communicating processes with state
IW-FM'97 Proceedings of the 1st Irish conference on Formal Methods
Progressing problems from requirements to specifications in problem frames
Proceedings of the 3rd international workshop on Applications and advances of problem frames
Pattern-Based Confidentiality-Preserving Refinement
ESSoS '09 Proceedings of the 1st International Symposium on Engineering Secure Software and Systems
Software engineering as the design theoretic transformation of software problems
Innovations in Systems and Software Engineering
| Hi-index | 0.01 |
Achieving a proper understanding of the problem space before providing the design in the solution space is one of the basic tenets in requirements engineering. The Problem Frames approach provides a way for people to understand and solve software problems.Recently, a denotational semantics for Problem Frames was defined to relate the various elements of Problem Frames together. One of the problems of the semantics is that, as denotation, a problem has the set of all satisfying solution specifications. Whereas this is a sensible initial choice, it does not lend itself easily to the construction of solution specifications.The contribution of this paper is to provide a formal technique which in the context of the given semantics allows for the systematic derivation of software specifications from requirements.