• Corpus ID: 2752980

0 A Large Experimental NGPM Application : The STARS Program

@inproceedings{Boehm19940AL,
  title={0 A Large Experimental NGPM Application : The STARS Program},
  author={Barry W. Boehm and Prasanta K. Bose},
  year={1994}
}
The Spiral Model of software development [Boehm, 1988] begins each cycle of the spiral by performing the next level of elaboration of the prospective system's objectives, constraints, and alternatives. A primary difficulty in applying the spiral model has been the lack of explicit process guidance in determining these objectives, constraints, and alternatives. This paper presents an extension of the spiral model, called the Next Generation Process Model (NGPM), which uses the Theory W (win-win… 

Figures and Tables from this paper

References

SHOWING 1-10 OF 21 REFERENCES
Applying process programming to the spiral model
TLDR
The Spiral Model provides a candidate approach to determining the requirements, architecture, and design of a software process by determining which alternative process architecture minimizes the risk of not meeting the system objectives within the system constraints.
Software requirements as negotiated win conditions
TLDR
The results to date in researching and prototyping a next-generation process model (NGPM) and support system (NGPSS) which directly addresses the critical needs of important classes of stakeholders are described.
A spiral model of software development and enhancement
TLDR
An outline is given of the process steps involved in the spiral model, an evolving risk-driven approach that provides a framework for guiding the software process and its application to a software project is shown.
Supporting Systems Development by Capturing Deliberations During Requirements Engineering
TLDR
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 and a prototype environment that provides assistance to the various stakeholders involved in the design and management of large systems has been implemented.
Theory-W Software Project Management: Principles and Examples
TLDR
An extensive case study is presented and analyzed: the attempt to introduce new information systems to a large industrial corporation in an emerging nation shows that Theory W and its subsidiary principles do an effective job both in explaining why the project encountered problems, and in prescribing ways in which the problems could have been avoided.
Goal-directed concept acquisition in requirements elicitation
TLDR
The authors present an approach for model acquisition which is driven by goals to be achieved, and describe a conceptual meta-model in terms of which requirements models are acquired, which involves concepts that are usually not found in the final formal specification.
PD and joint application design: a transatlantic comparison
TLDR
This discussion and comparison of PD and JAD is presented in order to help researchers with cross-fertilization and to help practitioners understand their choices.
Process Model Evolution in the SPADE Environment
TLDR
The mechanisms a process language should possess in order to support changes are discussed and how the proposed mechanisms can be used to model different policies for changing a software process model are discussed.
An integrated environment for requirements engineering
TLDR
An integrated environment for requirements engineering that supports participatory development activities is described and case studies show it can support requirements engineering for groups of users determining system-level requirements for large, complex systems.
...
...