Problem Oriented Software Engineering: A design-theoretic framework for software engineering

Authors:
Jon G. Hall;Lucia Rapanotti;Michael Jackson
Affiliations:
Open University, UK;Open University, UK;Open University, UK
Venue:
SEFM '07 Proceedings of the Fifth IEEE International Conference on Software Engineering and Formal Methods
Year:
2007

Citing 0
Cited 8

Implementable requirements in problem orientation

Proceedings of the 3rd international workshop on Applications and advances of problem frames
Non-monotonic modelling from initial requirements: a proposal and comparison with monotonic modelling methods

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
Bridging the gap between requirements and design: An approach based on Problem Frames and SysML

Journal of Systems and Software
Analysing monitoring and switching problems for adaptive systems

Journal of Systems and Software
Software engineering as the design theoretic transformation of software problems

Innovations in Systems and Software Engineering
Safety process improvement with POSE and alloy

SAFECOMP'07 Proceedings of the 26th international conference on Computer Safety, Reliability, and Security
Design rationale capture for process improvement in the globalised enterprise: an industrial study

Software and Systems Modeling (SoSyM)

Quantified Score

Hi-index	0.00

Visualization

Abstract

A key challenge for software engineering is to learn how to reconcile the formal world of the machine and its software with the non-formal real world. In this paper, we discuss elements of Problem Oriented Software Engineering (POSE), an approach that brings both nonformal and formal aspects of software development together in a single theoretical framework for software engineering design. POSE presents development as the representation and step-wise transformation of software problems. It allows for the identification and clarification of system requirements, the understanding and structuring of the problem world, the structuring and specification of a hardware/software machine that can ensure satisfaction of the requirements in the problem world, and the construction of adequacy arguments, convincing both to developers and to customers, users and other interested parties, that the system will provide what is needed. Examples are used throughout the paper to illustrate how formal and non-formal descriptions are reconciled under POSE.