Page 68 -

CHAPTER 2 THE PROCESS 39

FIGURE 2.9 2. Identify stakeholders'
The WINWIN win conditions 3a. Reconcile win conditions
spiral model 1. Identify 3b. Establish next-level objectives,
[BOE98]. next-level constraints and alternatives
stakeholders

4. Evaluate process and
product alternatives and
resolve risks

7. Review and comment
6. Validate product and 5. Define next level of

process definitions product and process,
including partitions

Boehm’s WINWIN spiral model [BOE98] defines a set of negotiation activities at
the beginning of each pass around the spiral. Rather than a single customer com-
munication activity, the following activities are defined:
1. Identification of the system or subsystem’s key “stakeholders.” 8
2. Determination of the stakeholders’ “win conditions.”
3. Negotiation of the stakeholders’ win conditions to reconcile them into a set of
Negotiating skills win-win conditions for all concerned (including the software project team).
Successful completion of these initial steps achieves a win-win result, which becomes
the key criterion for proceeding to software and system definition. The WINWIN spi-
ral model is illustrated in Figure 2.9.
In addition to the emphasis placed on early negotiation, the WINWIN spiral model
introduces three process milestones, called anchor points [BOE96], that help estab-
lish the completion of one cycle around the spiral and provide decision milestones
before the software project proceeds.
In essence, the anchor points represent three different views of progress as the
project traverses the spiral. The first anchor point, life cycle objectives (LCO), defines
a set of objectives for each major software engineering activity. For example, as part
of LCO, a set of objectives establishes the definition of top-level system/product
requirements. The second anchor point, life cycle architecture (LCA), establishes objec-
tives that must be met as the system and software architecture is defined. For exam-
ple, as part of LCA, the software project team must demonstrate that it has evaluated
the applicability of off-the-shelf and reusable software components and considered
their impact on architectural decisions. Initial operational capability (IOC) is the third

8 A stakeholder is anyone in the organization that has a direct business interest in the system or
product to be built and will be rewarded for a successful outcome or criticized if the effort fails.