Problem frames: analyzing and structuring software development problems

By H. Edwards. Software testing, verification & reliability, 2002

633 citations recorded by the source corpus.

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Early aspects: a model for aspect-oriented requirements engineering (2002, methodology): “We can use: goal-oriented requirements which cover functional and non-functional concerns [10]; use cases or scenario-based approaches, by specifying which use cases/scenarios are crosscut by a concern; problem frames which can be viewed as concerns [8].”
Modularisation and composition of aspectual requirements (2003, methodology): “The latter is carried out using an existing requirements level separation of concerns mechanism such as viewpoints [13], use cases [17], goals [19] or problem frames [16].”
Software Factories: Assembling Applications with Patterns, Models, Frameworks, and Tools (2004, background): “To paraphrase Jackson, the value of an abstraction increases with its specificity to some problem domain [19].”
Software Abstractions - Logic, Language, and Analysis (2006, background): “The ideas that are most relevant to this example can be found in several of the short pieces in his essay collection [38] (in particular “Definitions,” “Designations,” “Domains,” “Machines,” and “Requirements”), and are elaborated more fully in his book on problem frames [39].”