Formal methods and traditional engineering
Journal of Systems and Software - Special issue on formal methods technology transfer
Concurrency: state models & Java programs
Concurrency: state models & Java programs
Mathematical foundations of software engineering: a roadmap
Proceedings of the Conference on The Future of Software Engineering
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Problem frames: analyzing and structuring software development problems
Problem frames: analyzing and structuring software development problems
The Prescription and Description of State Based Systems
Temporal Logic in Specification
Design Methods for Software Systems: YOURDON, Statemate and Uml
Design Methods for Software Systems: YOURDON, Statemate and Uml
Goal-Oriented Requirements Engineering: A Guided Tour
RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
Advanced Systems Design with Java, UML and MDA
Advanced Systems Design with Java, UML and MDA
Towards specification, modelling and analysis of fault tolerance in self managed systems
Proceedings of the 2006 international workshop on Self-adaptation and self-managing systems
Hi-index | 0.00 |
Any engineering method is based on the validity of some assumptions about the problem domain and about the artifacts used in any solution of an engineering problem. Engineers have learned, perhaps not perfectly, to lay bare these assumptions and to base their methods on effective use of these assumptions. Software engineers are less good at this, to the detriment of building effective methods. The paper discusses some assumptions that either are false or are not made properly explicit in methods and the detrimental effect on the relevant methods. Some ideas about dealing with these deficiencies are proposed and discussed.