The RAISE specification language
The RAISE specification language
Software requirements & specifications: a lexicon of practice, principles and prejudices
Software requirements & specifications: a lexicon of practice, principles and prejudices
What Is `Mathematicalness' in Software Engineering?
FASE '00 Proceedings of the Third Internationsl Conference on Fundamental Approaches to Software Engineering: Held as Part of the European Joint Conferences on the Theory and Practice of Software, ETAPS 2000
Using Algebraic Specification Techniques in Development of Object-Oriented Frameworks
FM '99 Proceedings of the Wold Congress on Formal Methods in the Development of Computing Systems-Volume II
Editorial: A roadmap of problem frames research
Information and Software Technology
An approach to formal automated analysis of problem-frame concerns
Information and Software Technology
A UML-based approach for problem frame oriented software development
Information and Software Technology
Deriving requirements from process models via the problem frames approach
Information and Software Technology
Combining problem frames and UML in the description of software requirements
FASE'06 Proceedings of the 9th international conference on Fundamental Approaches to Software Engineering
| Hi-index | 0.00 |
We attempt formal characterisations of M.A. Jackson's (1995) concept of problem frames-and illustrate the translation (JSP), control, information systems, connection and workpiece frames. The paper is based on the following definition of method: A set of principles for selecting and applying techniques and tools in order to efficiently develop an efficient (here software) artifact. Most "formal methods" fail this definition-and we wish to show how formal design calculi can fit into the above definition. The paper is also based on the tri-partite separation of concern wherein software development is seen as having three intertwined "stages/activities" : Domain analysis and theory construction, in which formal models of the application domain-without any reference to computing-"precedes" requirements capture which again "precedes" software design.