Case-based support for the design of dynamic system requirements

Funk, Peter; Robertson, David

doi:10.1007/3-540-60364-6_38

Cited by 2 publications

(1 citation statement)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In our point of view, explicit management of requirements is essential in non-routine redesign: addition, retraction and modification of the original requirements often forms a major part of any non-routine redesign task. Examples of such non-routine redesign tasks can be found in systems for redesign of compositional architectures (Brazier et aL, 1996b), simulation models (Pos & Akkermans, 1996;Pos et aL, 1997) and software specifications (Funk & Robertson, 1994).…”

Section: Revise Redesign Methodsmentioning

confidence: 99%

Problem solving for redesign

Pos¹,

Akkermans²,

Straatman

1997

Knowledge Acquisition, Modeling and Management

View full text Add to dashboard Cite

A knowledge-level analysis of complex tasks like diagnosis and design can give us a better understanding of these tasks in terms of the goals they aim to achieve and the different ways to achieve these goals. In this paper we present a knowledge-level analysis of redesign. Redesign is viewed as a family of methods based on some common principles, and a number of dimensions along which redesign problem solving methods can vary are distinguished. By examining the problem-solving behavior of a number of existing redesign systems and approaches, we came up with a collection of problem-solving methods for redesign and developed a task-method structure for redesign. In constructing a system for redesign a large number of knowledge-related choices and decisions are made. In order to describe all relevant choices in redesign problem solving, we have to extend the current notion of possible relations between tasks and methods in a PSM architecture. The realization of a task by a problemsolving method, and the decomposition of a problem-solving method into subtasks are the most common relations in a PSM architecture. However, we suggest to extend these relations with the notions of task refinement and method refinement. These notions represent intermediate decisions in a task-method structure, in which the competence of a task or method is refined without immediately paying attention to its operationalization in terms of subtasks. Explicit representation of this kind of intermediate decisions helps to make and represent decisions in a more piecemeal fashion.

show abstract

Section: Revise Redesign Methodsmentioning

confidence: 99%