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
A Method for Requirements Elicitation and Formal Specification
ER '99 Proceedings of the 18th International Conference on Conceptual Modeling
Goal-directed concept acquisition in requirements elicitation
IWSSD '91 Proceedings of the 6th international workshop on Software specification and design
Requirement progression in problem frames: deriving specifications from requirements
Requirements Engineering
Problem Oriented Software Engineering: A design-theoretic framework for software engineering
SEFM '07 Proceedings of the Fifth IEEE International Conference on Software Engineering and Formal Methods
Goal-oriented requirements analysis and reasoning in the Tropos methodology
Engineering Applications of Artificial Intelligence
Proceedings of the 3rd international workshop on Applications and advances of problem frames
Hi-index | 0.00 |
We are investigating ways to improve the process of modelling of embedded systems for formal verification. In the modelling process, we make a mathematical model of the system software and its environment (the plant), and we prove that the requirement holds for the model. But we also want to have an argument that increases our confidence that the model represents the system correctly (with respect to the requirement). Therefore, we document some of the modelling decisions in form of a list of the system assumptions made while modelling. Identifying the assumptions and deciding which ones are relevant is a difficult task and it cannot be formalized. To support this process, we give a classification of assumptions. We show our approach on an example.