Boehm, B.W. and P. Bose (1994), "A Collaborative Spiral Software Process Model Based on Theory W," In Proceedings of 3rd International Conference on the Software Process, Applying the Software Process, IEEE, Reston, VA.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....a specific application and or process area in software engineering. Examples of subdomain process models are process models of: Requirement engineering processes [82] System engineering processes [5] Software and IT acquisition processes [20] The Spiral software processes [10] . The Rational software development processes [60] For details, readers may wish to consult the references provided above. 4.5 Process Based Software Engineering In the software industry, the software engineering process systems have been seen as a fundamental infrastructure for ....

Boehm, B. and Bose, P. (1994), A Collaborative Spiral Software process Model based on Theory W, Proceedings of 3rd International Conference on the Software Process, IEEE Computer Society Press, Reston, VA, October, pp.59-68.

.... do not explicitly support different stakeholder perspectives [9,12,16 18,23] and those that do, often limit the number of stakeholders and assume that consensus can be reached [24] Boehm s Win Win approach is the only major risk management approach that focuses on stakeholder goals [6]. The Riskit method extends Boehm s approach by maintaining links between risks and stakeholders explicitly. These links are visualized in Figure 2. The Riskit method contains templates and guidelines on how to identify, analyze and document all the elements listed in Figure 2. When risk ....

B.W. Boehm and Bose P., A Collaborative Spiral Software Process Model Based on Theory W 1994. Proceedings of the 3 rd International Conference on the Software Process. IEEE Computer Society. Washington, DC.

....names chosen from within a domain whose name is controlled by the party Continued on page 7 . All the types of artifacts in a typical software development lifecycle can be edited using WebDAV, including requirements, design documents, test cases, code, and more. So, while WebDAV provides HTML [7] and XML [2] authoring support, it just as easily supports authoring of existing word processing, spreadsheet, text, graphics, and all other formats. WebDAV and HTTP provide a common interface to a wide range of repositories, such as configuration management, file systems, databases, document ....

....Vol. 41, No. 8, August, 1998, pages 84 92. 6] Y. Y. Goland, E. J. Whitehead, Jr. A. Faizi, S. R. Carter, D. Jensen. Extensions for Distributed Authoring on the World Wide Web WEBDAV. Proposed Standard Request for Comments (RFC) 2518, February, 1999. ftp: ftp.isi.edu in notes rfc2518.txt [7] D. Raggett, A. Le Hors, I. Jacobs. HTML 4.0 Specification W3C Recommendation REC html40, April 24, 1998 www.w3.org pub WWW TR REC html40.html [8] S. Reddy, D. Jensen, S. Reddy, R. Henderson, J. Davis, A. Babich. DAV Searching and Locating. InternetDraft, Work in Progress, ....

B. Boehm and P. Bose, "A Collaborative Spiral Software Process Model Based on Theory W", Third International Conference on the Software Process, 1994.

....Projects Agency (ARPA) through Rome Laboratory under contract F30602 94 C 0195 and by the Industrial Affiliates of the Center for Software Engineering. August 8, 1995 2 other stakeholders concurrently in the initial stages of design when requirements and system design decisions are made [4, 5, 6, 9]. The challenge is providing collaboration support that aid in such decision making. As noted by Fred Brooks, in his article No Silver Bullets [1] significant gains in software productivity are likely to be based on tools for aiding organization and design rather than traditional software ....

....to include decisions on requirements and design. August 8, 1995 3 2 The WinWin Approach The WinWin approach [7] is aimed at addressing collaboration for the requirements engineering phase of the software life cycle. The three key ideas in the approach are: WinWin Spiral process. The process [6] consists of two main steps: i) Identifying stakeholders and their win conditions ii) Creating win win relationships collaboratively and negotiating to confront win lose and lose lose situations. A key aspect of the process is that it introduces economic, product quality and risk considerations ....

[Article contains additional citation context not shown here]

. B. Boehm and P. Bose, "A Collaborative Spiral Software Process Model Based on Theory W" ,3rd International Process Conference, 1994.

No context found.

Boehm, B.W. and P. Bose (1994), "A Collaborative Spiral Software Process Model Based on Theory W," In Proceedings of 3rd International Conference on the Software Process, Applying the Software Process, IEEE, Reston, VA.

No context found.

Boehm, B. & Bose, P. "A Collaborative Spiral Software Process Model Based on Theory W." Proceedings, ICSP 3, IEEE, Reston, VA, Oct. 1994

....further extensions to the model. One difficulty involves answering the question, Where do the elaborated objectives, constraints, and alternatives come from The WinWin Spiral Model resolves this difficulty by adding three activities to the front of each spiral cycle, as illustrated in Figure 2 [5]. First, identify the system or subsystem s key stakeholders. Second, identify the stakeholders win conditions for the system or subsystem and, third, negotiate win win reconciliation of the stakeholders win conditions. What this means is that for each cycle we need to identify all important ....

Boehm, B.W., Bose, P. (1994) "A Collaborative Spiral Software Process Model Based on Theory W," Proceedings, 3 rd International Conference on the Software Process, Applying the Software Process, IEEE, Reston, VA, October.

....points above. This section discusses recent software process standards such as MIL STD 498 [DoD, 1994] currently evolving into EIA IEEE J STD 016 [EIA IEEE, 1995] and ISO IEC Standard 12207 [ISO, 1995] It also describes recent elaborations of the spiral model, such as the Win Win Spiral Model [Boehm Bose, 1994] and their relation to the three anchor points. It concludes with a discussion of the applicability of the anchor points not just to individual projects, but to the management of software product lines with domain architectures and reusable components. 3.1 MIL STD 498: Software Development and ....

....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. The recently developed Win Win Spiral Model [Boehm Bose, 1994] uses the Theory W (win win) approach [Boehm Ross, 1989] to converge on a system s next level objectives, constraints, and alternatives. This Theory W approach involves identifying the system s stakeholders and their win conditions, and using negotiation processes to determine a mutually ....

, B.W. Boehm and P. Bose, "A Collaborative Spiral Software Process Model Based on Theory W," Proceedings, ICSP 3, IEEE, Reston, Va. October 1994. 26

....extensions to the model. One difficulty involves answering the question, Where do the elaborated objectives, constraints, and alternatives come from The WinWin Spiral Model resolves this difficulty by adding three activities to the front of each spiral cycle, as illustrated in Figure 1 [4]. Identify the system or subsystem s key stakeholders. Identify the stakeholders win conditions for the system or subsystem. Negotiate win win reconciliation of the stakeholders win conditions. We found that these steps indeed produced the key product and process objectives, constraints, ....

Boehm, B.W., Bose, P. (1994), "A Collaborative Spiral Software Process Model Based on Theory W," Proceedings, 3 rd International Conference on the Software Process, Applying the Software Process, IEEE, Reston, VA, October.

....further extensions to the model. One difficulty involves answering the question, Where do the elaborated objectives, constraints, and alternatives come from The WinWin Spiral Model resolves this difficulty by adding three activities to the front of each spiral cycle, as illustrated in Figure 1 [Boehm Bose, 1994]. Identify the system or subsystem s key stakeholders. Identify the stakeholders win conditions for the system or subsystem. Negotiate win win reconciliations of the stakeholders win conditions. Figure 1. The WinWin Spiral Model 2. Identify Stakeholders win conditions 1. Identify ....

.... constraints, alternatives In an experiment involving a bootstrap application of the WinWin groupware system to the definition of an improved version of itself, we found that these steps indeed produced the key product and process objectives, constraints, and alternatives for the next version [Boehm et al., 1994]. The overall stakeholder WinWin negotiation approach is similar to other team approaches for software and system definition such as CORE [Mullery, 1979] gIBIS [Conklin Begeman, 1991] GRAIL [Dardenne et al. 1993] Tuiqiao [Potts Takahashi, 1993] Participatory Design and JAD [Carmel et al. ....

[Article contains additional citation context not shown here]

. B.W. Boehm and P. Bose, "A Collaborative Spiral Software Process Model Based on Theory W," Proceedings, 3 rd International Conference on the Software Process, Applying the Software Process, IEEE, Reston, Va. October 1994.

.... Contribute to software engineering and SE education state of art, state ofpractice Manageable workload Rewarding intellectual, social experience 5 2. Course Development and Evolution Strategy In developing and evolving the course, we used a combination of the WinWin Spiral Model [Boehm and Bose 1994] and the Experience Factory [Basili et al. 1986] The approach is summarized in Figure 1. We used the WinWin Spiral Model to develop the initial version of the course and its instrumentation. Each project uses the WinWin Spiral Model to define, develop, and transition its application product. We ....

....further extensions to the model. One difficulty involves answering the question, Where do the elaborated objectives, constraints, and alternatives come from The WinWin Spiral Model resolves this difficulty by adding three activities to the front of each spiral cycle, as illustrated in Figure 2 [Boehm and Bose 1994]. Identify the system or subsystem s key stakeholders. Identify the stakeholders win conditions for the system or subsystem. Negotiate win win reconciliations of the stakeholders win conditions. In an experiment involving a bootstrap application of the WinWin groupware system to the ....

[Article contains additional citation context not shown here]

Boehm, B.W., Bose, P. (1994), "A Collaborative Spiral Software Process Model Based on Theory W," Proceedings, 3 rd International Conference on the Software Process, Applying the Software Process, IEEE, Reston, Va.

No context found.

B. Boehm and P. Bose. A Collaborative Spiral Software Process Model Based on Theory W. In Proc. 3rd International Conf. on the Software Process, pages 59--68, Reston, VA, 1994.

No context found.

Boehm, B. and P. Bose, "A Collaborative Spiral Software Process Model Based on Theory W," University of Southern California Technical Report USC-CSE-94-501.

No context found.

B. Boehm and P. Bose, "A Collaborative Spiral Software Process Model Based on Theory W," Proc. Int'l Conf. Software Process, IEEE CS Press, Los Alamitos, Calif., 1994, pp. 59-68.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC