Software requirements as negotiated win conditions

@article{Boehm1994SoftwareRA,
  title={Software requirements as negotiated win conditions},
  author={Barry W. Boehm and Prasanta K. Bose and Ellis Horowitz and Mingjune Lee},
  journal={Proceedings of IEEE International Conference on Requirements Engineering},
  year={1994},
  pages={74-83}
}
  • B. Boehm, P. Bose, Mingjune Lee
  • Published 18 April 1994
  • Computer Science
  • Proceedings of IEEE International Conference on Requirements Engineering
Current processes and support systems for software requirements determination and analysis often neglect the critical needs of important classes of stakeholders, and limit themselves to the concerns of the developers, users and customers. These stakeholders can include maintainers, interfacers, testers, product line managers, and sometimes members of the general public. This paper describes the results to date in researching and prototyping a next-generation process model (NGPM) and support… 

Figures and Tables from this paper

Applying WinWin to quality requirements: a case study
TLDR
It is suggested that knowledge-based automated aids have potential to significantly enhance process effectiveness and efficiency and that such processes and tools have theoretical and practical implications in the quest for better software requirements elicitation.
Requirements engineering, expectations management, and the Two Cultures
TLDR
Initial results indicate that the simplifiers and complicators approach successfully reduced the number of projects having serious feasibility problems, and helped manage the expectations of both the developers and the customers/users.
Developing Groupware for Requirements Negotiation: Lessons Learned
TLDR
A series of groupware implementations for the WinWin requirements negotiation approach, which involves having a system's success-critical stakeholders participate in a negotiation process so they can converge on a mutually satisfactory or win-win set of requirements.
Analysis of Software Requirements Negotiation Behavior Patterns
TLDR
The data analysis shows that expectations of uniform group behavior were generally not realized, and a number of hypotheses were formulated about the results, e.g. that the uniform set of initial conditions would lead to uniform results.
A collaborative spiral software process model based on Theory W
  • B. BoehmP. Bose
  • Computer Science
    Proceedings of the Third International Conference on the Software Process. Applying the Software Process
  • 1994
TLDR
An extension of the spiral model, called the Next Generation Process Model (NGPM), is presented, which uses the Theory W(win-win) approach (Boehm-Ross, 1989) to converge on a system's next-level objectives, constraints, and alternatives.
Using WinWin Quality Requirements Management Tools: A Case Study
TLDR
Two exploratory knowledge-based tools for conflict identification and resolution are described and how they were used in the digital library projects of a USC Software Engineering class during the 1996/97 school year and it is concluded that the tools helped stakeholders surface and negotiate conflicts.
Aids for Identifying Conflicts Among Quality Requirements
TLDR
An exploratory knowledge-based tool for identifying potential conflicts among quality attributes early in the software/system life cycle and examines the quality attribute tradeoffs involved in software architecture and process strategies.
The WinWin Requirements Negotiation System � a Model Driven Approach
TLDR
Current research is presented on constructing and reconciling several formal and semi-formal models of the WinWin requirements engineering system and its operations, including inter-artifact relationship, artifact life cycles, and equilibrium model.
Software Requirements Negotiation and Renegotiation Aids: A Theory-W Based Spiral Approach
TLDR
Needs and capabilities required to address the problem of negotiation and renegotiation that arises when the Theory-W based Spiral Model is applied to incremental requirements engineering are identified.
Software Cost Option Strategy Tool (S-COST)
  • B. BoehmH. In
  • Business
    Proceedings of 20th International Computer Software and Applications Conference: COMPSAC '96
  • 1996
TLDR
Initial analyses of S-COST's capabilities indicate that its semiautomated approach provides users with improved capabilities for addressing cost-requirements issues.
...
...

References

SHOWING 1-10 OF 19 REFERENCES
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.
Process integration in CASE environments
TLDR
The developer's interface, a working environment that lets developers enact an SPM, and the manager's interface which gives managers and analysts the tools to define, monitor, and control the SPMs that developers are working on concurrently are discussed.
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.
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.
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.
Viewpoint Oriented Software Development: Mehtods and Viewpoints in Requirements Engineering
TLDR
A central thread in this work the -concept of "ViewPoint"- is examined, motivated and systematically characterised, and the implications for methods to support the construction of formal specifications are considered.
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.
Software processes are software too
The major theme of this meeting is the exploration of the importance of process as a vehicle for improving both the quality of software products and the way in which we develop and evolve them. In
Computer systems and the design of organizational interaction
TLDR
A theory of language as social action, which differs from the generally taken-for-granted understandings of what goes on in an organization is proposed and illustrated.
...
...