IEEE Transactions on Software Engineering · 1992 · 286 citations · 38 references
ComputingInformation SystemsProject ManagementKnowledge RepresentationRequirements EngineeringSoftware EngineeringDesign ProcessProcess ModelingRequirements ManagementRequirements ModelingSoftware DesignSystems Development Life CycleConceptual Model DevelopmentProblem-solving BehaviorProcess Knowledge CaptureProcess Knowledge ManagementRequirements CaptureRequirements Engineering ProcessRequirements Knowledge RepresentationSoftware Development Life Cycle
Support for various stakeholders involved in software projects (designers, maintenance personnel, project managers and executives, end users) can be provided by capturing the history about design decisions in the early stages of the system's development life cycle in a structured manner. Much of this knowledge, which is called the process knowledge, involving the deliberation on alternative requirements and design decisions, is lost in the course of designing and changing such systems. Using an empirical study of problem-solving behavior of individual and groups of information systems professionals, a conceptual model called REMAP (representation and maintenance of process knowledge) that relates process knowledge to the objects that are created during the requirements engineering process has been developed. A prototype environment that provides assistance to the various stakeholders involved in the design and management of large systems has been implemented.< <ETX xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">></ETX>
38
Dilemmas in a general theory of planning
Horst W. J. Rittel, Melvin M. Webber · Policy Sciences · 1973 · 15.3K citations · Full text
Group Dynamics: The Psychology of Small Group Behavior
S. D. Vander Ark · Journal of Music Therapy · 1972 · 1.1K citations
Software processes are software too
Leon J. Osterweil · 1987 · 874 citations