It is our great pleasure to welcome you to the Third International Workshop on Applications and Advances of Problem Frames - IWAAPF'08.
Problem Frames are, this year, fourteen years old. It all started with an idea in the Jackson's 1994 paper "Software Development Method" that appeared in "A Classical Mind: Essays in Honour of C A R Hoare." There were, at that time, no diagrams but the idea was sweet. (Diagrams came later in "Problem Complexity" published in the proceedings of Third IEEE International Conference on Engineering of Complex Systems (ICECCS'97) in 1997.)
As a measure of the popularity, google-scholaring "Problem Frames" returns 741 hits. Right at the top is Jackson's 2001 eponymous book "Problem frames: analyzing and structuring software development problems".
This year, we add another 14 excellent papers to that count, one for each year, with our workshop. Those papers come from authors located in six countries. Some describe work completed, some work in progress and some work yet to be done. There are variants of Problem Frames, ontologies for Problem Frames, and the continuing work on taking Problem Frames closer to the solution space and more traditional software engineering techniques. Moreover, the workshop boasts a keynote presentation from Professor John Knight, Virginia, that places Problem Frames squarely as a useful engineering technique in the real-world.
Proceeding Downloads
Towards the integration of sysml and problem frames
Today, analysts are offered a wide set of conceptual tools for requirements enginering, including modelling languages, like UML and SysML, and methodological approaches, like Problem Frames. However, these conceptual tools, which address different needs ...
Implementable requirements in problem orientation
The goal of this paper is to demonstrate how Problem Oriented Software Engineering (POSE), an extension and generalisation of Problem Frames, supports the systematic transformation of requirements from overall system level requirements through to ...
Communicating requirements for business: UML or problem frames?
We compared two prominent software development notations: Problem Frames and the UML, to establish which is more effective at conveying the problem domain and software requirements. The UML scored slightly higher in both the comprehension and perceived ...
A method for web service description by using problem frames approach
This paper proposes a method for web service description by using problem frame approach. Different from existing methods, this method uses problem diagram to describe the capability of available web service and use it to identify precise requirements. ...
RGPS: a unified requirements meta-modeling frame for networked software
Networked software, a special kind of applications in service-oriented computing and ultra-large-scale systems, is a complex software system deploying on network environment. Requirements engineering of networked software poses many problems owing to ...
An ontology-guided process for developing problem frame specification: an example
Problem Frames approach is a new and prospective tool for classifying, analyzing and structuring software development problems. However, there is not yet efficient CASE tool for guiding the problem frame specification development. An ontology based ...
Problem frames for intelligent building services: a suitability study
In this paper, we explore suitability of the Problem Frames framework for intelligent building software requirements gathering. The research was conducted through a pilot application presented to intelligent building specialists, with a follow-up survey ...
Functional size measurement based on problem frames: a case study
The approach to requirements modelling based on problem frames is gaining increasing attention and popularity. However, the usage of problem frames in industrial software development processes requires that some industrial practices, like cost ...
Problem frames and business strategy modelling
Requirements engineering describes how an IT implementation will support business functions. Most IT systems are operational in nature and typical requirements engineering techniques and methods are usually adequate in capturing and documenting the ...
Progressing problems from requirements to specifications in problem frames
One of the problems with current practice in software development is that customer requirements are often not well captured, understood and analysed, and there is no clear traceable path from customer requirements to software specifications. This often ...
Using problem frames to model the requirements ofa system for monitoring dangerous goods transportation
The approach to requirements modelling based on problem frames is gaining increasing attention and popularity. This paper reports an experience in the application of problem frames to modelling the requirements of a system for monitoring the ...
Non-monotonic modelling from initial requirements: a proposal and comparison with monotonic modelling methods
Researchers make a significant effort to develop new modelling languages and tools. However, they spend less effort developing methods for constructing models using these languages and tools. We are developing a method for building an embedded system ...
Using the event calculus to reason about problem diagrams
Central to the problem frames approach is the distinction of three different descriptions: requirements R, domain assumptions W and specifications S, tied together with the so-called 'frame concern', a proof obligation that has to hold between them if a ...
Relating problem oriented engineering to current development processes: a research agenda
In this position paper, we propose research into expressing software development processes in terms of one generic theory, namely Problem Oriented Engineering (POE). Our aim is to relate the POE process to those available in the Rational Unified Process ...