Optimizing Software Product Integrity through Life-Cycle Process Integration (2009)
Managed and optimized – these are the names for the levels 4 and 5 of the Capability Maturity Model (CMM) respectively. With that the Software Engineering Institute (SEI) pays tribute to the fact...
Rome Lab, US Army Research Labs, Xerox. Graduate Assistants: (2009)
Chris Abts, Brad Clark, Sunita Devnani-chulani, The Cocomo, Ii Dr, Barry Boehm
1 Abstract Calibrating Software Cost Models Using Bayesian Analysis (2009)
Sunita Chulani, Barry Boehm, Bert Steece
The COCOMO II research effort started in 1994 with the aim of updating software cost estimation models, such as the 1981 COnstructive COst MOdel and its 1987 Ada update. Both the earlier models...
Realizing the Benefits of the CMMI SM with the CeBASE Method (2009)
Barry Boehm, Dan Port, Victor Basili, U. Of Maryl
Future systems will be increasingly software-intensive, but the type of software development they will need is not well covered by current development and maturity models such as the waterfall model...
The business case for automated software engineering (2009)
Menzies, Tim, Elrawas, Oussama, Hihn, Jairus M., Feather, Martin S., Madachy, Ray, Boehm, Barry
Adoption of advanced automated SE (ASE) tools would be more favored if a business case could be made that these tools are more valuable than alternate methods. In theory, software prediction models...
Tailor the Value-Based Software Quality Achievement Process to Project Business Cases (2009)
Liguo Huang, Hao Hu, Jidong Ge, Barry Boehm, Jian Lü
Abstract. This paper proposes a risk-based process strategy decision-making approach. To improve the flexibility in applying the Value-Based Software Quality Achievement (VBSQA) process framework, we...
• Investment: Cost of developing for reuse • Payoff: Net value added via reuse • Return on Investment ROI = NPV(Payoff)- NPV(Investment) NPV(Investment) • NPV: Net Present Value –...
23 Coming Events 34 Letters to the Editor (2008)
Dr. Barry Boehm, Wilfred J. Hansen, Luncheonb Onapril, Highlightedinanapril Tutorialandonmay Track, Patrick J. Schroeder, ...
The Spiral Model as a Tool for Evolutionary Acquisition The Department of Defense has recently rewritten the defense acquisition regulations to incorporate “evolutionary acquisition, ” a strategy...
Lawrence H. Putnam, Dr. Barry Boehm, Ricardo Valerdi, Jo Ann Lane, A. Winsor Brown
This article walks the reader through the basic process and considerations needed to determine the project scope for new development, including maintenance builds. by William Roetzheim Software Cost...
Barry Boehm, Dan Port, Kevin Sullivan
integration of a software system’s stakeholder value propositions into the system’s definition, design, development, deployment, and evolution is critical to the system’s success. This white...
There is a pressing need to make software system acquisition more agile and adaptive, through evolutionary modeling, simulation, and development of the system being acquired. Here we’ll describe a...
Introducing Risk Management Techniques Within Project Based Software Engineering Courses (2008)
In 1996, USC switched its core two-semester software engineering course from a hypothetical-project, homeworkand-exam course based on the Bloom taxonomy of educational objectives (knowledge,...
focus return on investment The ROI of Software Dependability: The iDAVE Model (2008)
Barry Boehm, Liguo Huang, Apurva Jain, Ray Madachy
In most organizations, proposed investments in software dependability compete for limited resources with proposed investments in software and system functionality, response time, adaptability, speed...
Kenneth Littlejohn, Michael V. Delprincipe, Jonathan D. Preston, A. Calloni, Jahn A. Luke, ...
developed a legacy software reengineering capability that parses and converts JOVIAL source files into language-neutral graph-based representations of their operation.
Kent Bingham, Photo Credit, Nathan Allred, Provided Janna Jensen, Dr. Barry Boehm, Jo Ann Lane, ...
Using the Incremental Commitment Model to Integrate
Key Research Pointers The Authors Software Economics: A Roadmap (2008)
Principles, models, methods and tools for reasoning about and dynamic management of software development as an investment activity. Models for reasoning about benefits and opportunities in software...
The CeBASE Framework for Strategic Software Development and Evolution (2008)
One of the challenges highlighted in the EDSER-3 Call
Applying the Value/Petri Process to ERP Software Development in China (2008)
{liguohua, boehm} @ usc.edu Commercial organizations increasingly need software processes sensitive to business value, quick to apply, and capable of early analysis for subprocess consistency and...
The ROI of Systems Engineering: Some Quantitative Results (2008)
This paper presents quantitative results on the return on investment of systems engineering (SE-ROI) from an analysis of the 161 software projects in the COCOMO II database. The analysis shows that,...
1. Motivation & Context Educating Software Engineering Students to Manage Risk (2008)
The increasing pace of change in information technology (IT) makes one-size- fits-all, cookbook solutions increasingly inadequate. Yet students are largely educated on cookbook solutions to set-piece...
Composable Process Elements for Developing COTS-Based Applications EDSER-5 Position Paper (2008)
Ye Yang, Jesal Bhuta, Barry Boehm, Dan Port, Chris Abts
issued a challenge to the software engineering community to provide better methods for dealing with COTS-based software systems, and to present them at
Categories and Subject Descriptors (2008)
Most risk analysis tools and techniques require the user to enter a good deal of information before they can provide useful diagnoses. In this paper, we describe an approach to enable the user to...
This paper presents the Threat Modeling method based on Attacking Path Analysis (T-MAP) which quantifies security threats by calculating the total severity weights of relevant attacking paths for...
Categories and Subject Descriptors (2008)
Most risk analysis tools and techniques require the user to enter a good deal of information before they can provide useful diagnoses. In this paper, we describe an approach to enable the user to...
Calibration Approach and Results of the COCOMO II Post- Architecture Model (2008)
Sunita Devnani-chulani, Brad Clark, Barry Boehm, Bert Steece
COCOMO II is an effort to update software cost estimation models, such as the 1981 COnstructive COst MOdel and its 1987 Ada COCOMO update. Both these and other
IEEE SOFTWARE Anchoring the Software Process (2008)
or a few golden moments in the mid-‘7Os, it appeared that the software field had found a set of common anchor points: A sequence of mile-stones around which people could plan, organize, monitor,...
Effect of Schedule Compression on Project Effort (2008)
Ye Yang, Zhihao Chen, Ricardo Valerdi, Barry Boehm
Schedule pressure is often faced by project managers and software developers who want to quickly deploy information systems. Typical strategies to compress project time scales might include adding...
Contractor TRW Customer USAF Current status Delivered On-budget, On-schedule (2008)
Barry Boehm, General Best Practices, A Seminar, Software Best Practices, Study Overview, Core Metrics
Average number of75 people
focus return on investment The ROI of Software Dependability: The iDAVE Model (2008)
Barry Boehm, Liguo Huang, Apurva Jain, Ray Madachy
In most organizations, proposed investments in software dependability compete for limited resources with proposed investments in software and system functionality, response time, adaptability, speed...
The process of resolving conflicts among software quality requirements is complex and difficult because of incompatibilities among stakeholders ’ interests and priorities, complex cost-quality...
Abstract Calibration Results of COCOMO II.1997 (2008)
Barry Boehm, Brad Clark, Sunita Devnani-chulani
COCOMO II is an effort to update software cost estimation models, such as the 1981 COnstructive COst MOdel and its 1987 Ada COCOMO update. Both these and other 1980’s cost models have experienced...
Barry Boehm, Winsor Brown, Liguo Huang, Dan Port
In this article, we show how you can use the MBASE process framework to generate a family of acquisition process models for delivering user-satisfactory systems under schedule, cost, and quality...
books/co2000/pdf/ry116.pdf. Milutinovic:2000:IWG (2007)
The Mac Inprise/borl, Perl Dev, Kit Perl, Veljko Milutinovic, Dragana Cvetkovic, ...
adds VoIP and home networking to cable
Software Requirements Negotiation and Renegotiation Aids:October 12, 1994 1 (2007)
Software Requirements, Barry Boehm, Prasanta Bose, Ellis Horowitz, Ming June Lee
A major problem in requirements engineering is obtaining requirements that address the concerns of multiple stakeholders. An approach to such a problem is the Theory-W based Spiral Model. One key...
Calibration Approach and Results of the COCOMO II PostArchitecture Model (2007)
Sunita Devnani-chulani, Brad Clark, Barry Boehm, Bert Steece
This paper describes the calibration process incorporated and summarizes the results obtained. The Early Design Model calibration is obtained by aggregating the calibrated Effort Multipliers of the...
Calibration Approach and Results of the COCOMO II PostArchitecture Model (2007)
Sunita Devnani-chulani, Brad Clark, Barry Boehm, Bert Steece
This paper describes the calibration process incorporated and summarizes the results obtained. The Early Design Model calibration is obtained by aggregating the calibrated Effort Multipliers of the...
Some Critical Success Factors for Knowledge Based Software Engineering Applications (2007)
Barry Boehm, Prasanta Bose, Greg Toth
ions. This CSF involves the identification and use of a core set of abstractions which mapped well onto a software project's decision drivers, which provided useful distinctions for project...
Mikael Lindvall, Vic Basili, Barry Boehm, Patricia Costa, Forrest Shull, Roseanne Tesoriero, ...
Abstract. In recent years, the use of, interest in, and controversy about Agile methodologies have realized dramatic growth. Anecdotal evidence is rising regarding the effectiveness of agile...
1 Calibrating the COCOMO II Post-Architecture Model (2007)
Sunita Devnani-chulani, Bradford Clark, Barry Boehm
The COCOMO II model was created to meet the need for a cost model that accounted for future software development practices. This resulted in the formulation of three submodels for cost estimation,...
1 Chapter 1 The MBASE Life Cycle Architecture Milestone Package No Architecture Is An Island (2007)
Barry Boehm, Dan Port, Er Egyed, Marwan Abi-antoun
development, rationale capture. Abstract: This paper summarizes the primary criteria for evaluating software/system architectures in terms of key system stakeholders ' concerns. It describes the...
Model-based Architecting, Barry Boehm, Dan Port
The difference between failure and success in developing a software-intensive system can often be traced to the presence or absence of clashes among the models used to define the system’s product,...
A Comparison Study in Software Requirements Negotiation (2007)
Abstract. In a period of two years, two rather independent experiments were conducted at the University of Southern California. In 1995, 23 threeperson teams negotiated the requirements for a...
1 Software Requirements As Negotiated Win Conditions (2007)
Barry Boehm, Prasanta Bose, Ellis Horowitz, Ming-june Lee
Current processes and support systems for software requirements determination and analysis often neglect critical needs of important classes of stakeholders and limit themselves to concerns of the...
Barry Boehm, Barry Boehm, Norton L. Compton, Lt Col
COTS-Based Systems Unlimited distribution subject to the copyright. This report was prepared for the
Value Driven Security Threat Modeling Based on Attack (2007)
This paper presents a quantitative threat modeling method, the Threat Modeling method based on Attack Path Analysis (T-MAP), which quantifies security threats by calculating the total severity...
Value-Based Software Engineering: Overview and Agenda (2006)
value-neutral setting, in which every requirement, use case, object, test case, and defect is equally important. However most studies of the critical success factors distinguishing successful from...
Summit was to find ways of better integrating software engineering into the systems engineering and acquisition process. Concurrently, a National Research Council study was addressing the problem of...
Summit was to find ways of better integrating software engineering into the systems engineering and acquisition process. Concurrently, a National Research Council study was addressing the problem of...
A view of 20th and 21st century software engineering (2006)
George Santayana's statement, "Those who cannot remember the past are condemned to repeat it, " is only half true. The past also includes successful histories. If you...
Community Information Utilities: Conference Summary, (2005)
Parker,Edwin B., Boehm,Barry, Sackman,Harold
The conference was organized into three sections: services, design and management. The services group was charged with the responsibility of proposing what services should be offered on a prototype...
Empirical Results from an Experiment on Value-Based Review (2005)
As part of our research on value-based software engineering, we conducted an experiment on the use of value-based review (VBR) processes. We developed a set of VBR checklists with issues ranked by...
An Initial Theory of Value-Based Software Engineering (2005)
Copyright USC-CSE 2005 Abstract: This chapter presents an initial “4+1 ” theory of value-based software engineering (VBSE). The engine in the center is the stakeholder win-win Theory W, which...
The Future of Software and Systems Engineering Processes (2005)
Abstract. In response to the increasing criticality of software within systems and the increasing demands being put onto software-intensive systems, software and systems engineering processes will...
Mark Sherriff, Barry Boehm, Laurie Williams
Parametric modeling is a statistical technique whereby a dependent variable is estimated based on the values of and the relationships between the independent variable(s). The nature of the dependent...
Contributions Edward Colbert, Barry Boehm, Donald Reifer, Extend Cocomo Ii
– Model for costing development of secure systems – Extensions to COCOMO II for development of secure software systems
Dr. Barry Boehm, A. Winsor Brown, Dr. Victor Basili
Current trends toward the transformation of warfare (and other large-scale competitive pursuits) into network-centric and knowledge-based systems of systems show great promise for competitive...
Using Testbeds to Accelerate Technology Maturity and Transition: The SCRover Experience, USC (2003)
Barry Boehm, Jesal Bhuta, David Garlan, Eric Gradman, Liguo Huang, Er Lam, ...
alexankl,madachy,neon,stevenme,
Qualifying guidance committee (2002)
Nikunj R. Mehta, Michael Arbib, Barry Boehm, Ramesh Govindan, Ann Majrchzak
Software architecture-based approaches provide high-level abstractions to deal with complexity and richness of modern software systems. Many software systems have been found to share organizational...
Disaggregating and Calibrating the CASE Tool Variable in COCOMO II (2002)
Jongmoon Baik, Barry Boehm, Bert M. Steece
Abstract—CASE (Computer Aided Software Engineering) tools are believed to have played a critical role in improving software productivity and quality by assisting tasks in software development...
V.; "Empirical Findings in Agile Methods (2002)
Mikael Lindvall, Vic Basili, Barry Boehm, Patricia Costa, Kathleen Dangle, Roseanne Tesoriero, ...
Abstract. In recent years, the use of, interest in, and controversy about Agile methodologies have realized dramatic growth. Anecdotal evidence is rising regarding the effectiveness of agile...
What We Have Learned about Fighting Defects (2002)
Forrest Shull, Vic Basili, Barry Boehm, A. Winsor Brown, Patricia Costa, Mikael Lindvall, ...
The Center for Empirically Based Software Engineering helps improve software development by providing guidelines for selecting development techniques, recommending areas for further research, and...
V.; "Empirical Findings in Agile Methods (2002)
Mikael Lindvall, Vic Basili, Barry Boehm, Patricia Costa, Forrest Shull, Roseanne Tesoriero, ...
Abstract. In recent years, the use of, interest in, and controversy about Agile methodologies have realized dramatic growth. Anecdotal evidence is rising regarding the effectiveness of agile...
Lessons-Learned Repository for COTS-Based SW Development (2002)
Victor Basili, Mikael Lindvall, Iona Russ, Carolyn Seaman, Barry Boehm, Lon R. Dean, ...
Individuals acquire knowledge while working in software development projects but too often this knowledge is not documented or captured so that it can be shared or later reused. Dissemination of...
Dr. Barry Boehm, Dr. Daniel Port, Apurva Jain
Recent events in Afghanistan have convincingly demonstrated the value of
Get Ready for Agile Methods (2002)
Although many of their advocates consider the agile and plan-driven software development methods polar opposites, synthesizing the two can provide developers with a comprehensive spectrum of tools...
Barry Boehm, Wilfred J. Hansen, Carnegie Mellon Univ, Risk Analysis, Risk Analysis, Prototype Anal, ...
Since its original publication [Boehm 88], the spiral development model diagrammed in Figure 1 has been used successfully in many defense and commercial projects. To extend this base of success, the...
Using WinWin Quality Requirements Management Tools: A Case Study (2001)
Negotiating stakeholder win-win relationships among software quality requirements is a technique that emerged during the 1990’s in order to overcome the difficulties arising from contract-oriented...
Ada COCOMO and the Ada Process Model (2000)
Recently, three software development approaches have motivated the development of a revised version of COCOMO: the use of the Ada programming language, the use of incremental development, and the use...
Software development cost estimation approaches – A survey (2000)
Barry Boehm, Chris Abts, Sunita Chulani
This paper summarizes several classes of software cost estimation models and techniques: parametric models, expertise-based techniques, learning-oriented techniques, dynamics-based models,...
Gaining Intellectual Control of Software Development (2000)
this report recommends a "software engineering" or a "software research" agenda, and how software research should address such areas as operating systems, networking, artificial...
Next Generation Software Processes and Their Environment Support. (1999)
The USC Center for Software Engineering has developed a negotiation-based approach to software system requirements engineering, architecting, development, and management. It is based on three primary...
Managing Software Productivity and Reuse (1999)
There are three main strategies that your organization can use to improve its software productivity: 1. Working faster, via tools that automate or speed up previously labor-intensive tasks; 2....
Escaping the Software Tar Pit: Model Clashes and How to Avoid Them (1999)
“No scene from prehistory is quite so vivid as that of the mortal struggles of great beasts in the tar pits... Large system programming has over the past decade been such a tar pit, and many great...
Escaping the Software Tar Pit: Model Clashes and How to Avoid Them (1999)
“No scene from prehistory is quite so vivid as that of the mortal struggles of great beasts in the tar pits... Large system programming has over the past decade been such a tar pit, and many great...
Escaping the Software Tar Pit: Model Clashes and How to Avoid Them (1999)
"No scene from prehistory is quite so vivid as that of the mortal struggles of great beasts in the tar pits... Large system programming has over the past decade been such a tar pit, and many...
Requirements Engineering, Expectations Management, and the Two Cultures (1999)
Barry Boehm, Marwan Abi-Antoun, Julie Kwan, Anne Lynch, Dan Port
this paper provides overall motivation and context for addressing the twocultures problem and expectations management as significant opportunity areas in requirements engineering. Section 3 discusses...
Modeling Software Defect Introduction and Removal (1999)
Cost, schedule and quality are highly correlated factors in software development. They basically form three sides of the same triangle. Beyond a certain point (the "Quality is Free" point),...
Bayesian Analysis of Empirical Software Engineering Cost Models (1999)
Sunita Chulani, Barry Boehm, Bert Steece
To date many software engineering cost models have been developed to predict the cost, schedule and quality of the software under development. But, the rapidly changing nature of software development...
The MBASE Life Cycle Architecture Milestone Package: No Architecture is an Island (1999)
The Mbase Life, Barry Boehm, Dan Port, Er Egyed, Marwan Abi-antoun
This paper summarizes the primary criteria for evaluating software/system architectures in terms of key system stakeholders' concerns. It describes the Model Based Architecting and Software...
Comparing Software System Requirements (1999)
Negotiation Patterns Alexander, Er Egyed, Barry Boehm
In a period of two years, two rather independent experiments were conducted at the University of Southern California (USC). In 1995, 23 three-person teams negotiated the requirements for a...
Jung-won Park, Daniel Port, Barry Boehm
Software developers are seldom able to implement stakeholders ' requirements fully when time and resources are limited. To solve the problem, requirement engineers together with the stakeholders...
Escaping the Software Tar Pit: Model Clashes and How to Avoid Them (1999)
“No scene from prehistory is quite so vivid as that of the mortal struggles of great beasts in the tar pits... Large system programming has over the past decade been such a tar pit, and many great...
KBSA Life Cycle Evaluation, Volume 2 (1998)
Boehm, Barry, Brown, A. Winsor, Bose, Prasanta
The objective of this research effort was to develop and validate technical approaches for evaluating the effects of Knowledge Based Software Assistant (KBSA) and Evolutionary Design of Complex...
KBSA Life Cycle Evaluation, Volume 1 (1998)
Boehm, Barry, Brown, A. Winsor, Bose, Prasanta
The objective of this research effort was to develop and validate technical approaches for evaluating the effects of Knowledge Based Software Assistant (KBSA) and Evolutionary Design of Complex...
Spiral Development: Experience, Principles, and Refinements (1998)
Boehm, Barry, Hansen, Wilfred J.
Spiral development is a family of software development processes characterized by repeatedly iterating a set of elemental development processes and managing risk so it is actively being reduced. This...
WinWin Extensions for the Evolutionary Design of Complex Systems (1998)
This research focused on formulation and development of process models and their support environments that will enable the DoD and its contractors to shift from traditional fixed-contract models of...
Dynamic Assembly, Assessment, Assurance, and Adaptation via Heterogeneous Software Connectors (1998)
Boehm, Barry, Medvidovic, Nenad
This effort provided innovative capabilities for two key stages of software development. During specification and design time, component mismatch detection gauges are provided, indicating the...
WinWin Requirements Negotiation Processes: A Multi-Project Analysis (1998)
Fifteen 6-member-teams were involved in negotiating requirements for multimedia software systems for the Library of the University of Southern California. The requirements negotiation used the...
WinWin Requirements Negotiation Processes: A Multi-Project Analysis (1998)
Fifteen 6-member-teams were involved in negotiating requirements for multimedia software systems for the Library of the University of Southern California. The requirements negotiation used the...
Improving the Life-Cycle Process in Software Engineering Education (1998)
The success of software projects and the resulting software products are highly dependent on the initial stages of the life-cycle process-- the inception and elaboration stages. The most critical...
Calibrating Software Cost Models Using Bayesian Analysis (1998)
Sunita Chulani, Barry Boehm, Bert Steece
The COCOMO II research effort started in 1994 with the aim of updating software cost estimation models, such as the 1981 COnstructive COst MOdel and its 1987 Ada update. Both the earlier models...
Software Requirements Negotiation: Some Lessons Learned (1998)
Negotiating requirements is one of the first steps in any software system life cycle, but its results have probably the most significant impact on the system's value. However, the processes of...
Telecooperation experience with the win-win system (1998)
WinWin is a telecooperation system supporting the definition of software-based applications as negotiated stakeholder win conditions. Our experience in using WinWin in defining over 30 digital...
Calibration Results of COCOMO II.1997 (1998)
Sepg Authors, Barry Boehm, Brad Clark, Sunita Devnani-chulani, Sunita Devnani-chulani
COCOMO II is an effort to update software cost estimation models, such as the 1981 COnstructive COst MOdel and its 1987 Ada COCOMO update. Both these and other 1980's cost models have...
Using the WinWin Spiral Model: A Case Study (1998)
Barry Boehm, Alexander Egyed, Julie Kwan, Dan Port, Archita Shah, Ray Madachy, ...
In this article, we describe an experimental validation of this approach, focusing on the application of the WinWin spiral model. The case study involved extending USC's Integrated Library...
Requirements Engineering, Expectations Management, and the Two Cultures (1998)
Barry Boehm, Marwan Abi-Antoun, Dan Port, Julie Kwan, Anne Lynch
One of the difficulties in requirements negotiation is to determine a feasible and mutually satisfactory set of requirements for the developer and the user, a problem related to C.P. Snow's...
A Stakeholder Win-Win Approach to Software Engineering Education (1998)
Barry Boehm, Alexander Egyed, Er Egyed, Dan Port, Archita Shah, Julie Kwan, ...
We are applying the stakeholder win-win approach to software engineering education. The key stakeholders we are trying to simultaneously satisfy are the students; the industry recipients of our...
Z. Computer Standards Interfaces 21 1999 63--75 (1998)
Optimizing Software Product, Barry Boehm, Er Egyed
Z. Managed and optimized---these are the names for the levels 4 and 5 of the Capability Maturity Model CMM Z. respectively. With that the Software Engineering Institute SEI pays tribute to the fact...
Improving the Life-Cycle Process in Software (1998)
Engineering Education Barry, Barry Boehm, Er Egyed
The success of software projects and the resulting software products are highly dependent on the initial stages of the life-cycle process -- the inception and elaboration stages. The most critical...
Telecooperation Experience with the WinWin System (1998)
Alexander Egyed And, Er Egyed, Barry Boehm
WinWin is a telecooperation system supporting the definition of software-based applications as negotiated stakeholder win conditions. Our experience in using WinWin in defining over 30 digital...
Calibrating the COCOMO II Post-Architecture Model (1998)
Bradford Clark, Sunita Devnani-chulani, Barry Boehm
The COCOMO II model was created to meet the need for a cost model that accounted for future software development practices. This paper describes some of the experiences learned in calibrating COCOMO...
A Familiar Example Cost Schedule Quality (1998)
•Can’t simultaneously optimize all three •Criteria usually oversimplified –Development vs. life-cycle vs. product line –Software vs. sub-system vs. system –Dimensions of desired quality...
Analysis of System Requirement Negotiation Behavior Patterns (1997)
Roughly 35 three-person teams played the roles of user, customer, and developer in negotiating the requirements of a library information system. Each team was provided with a suggested set of...
Developing Multimedia Applications with the WinWin Spiral Model (1997)
Barry Boehm, Alex Egyed, Julie Kwan, Ray Madachy, Litton Data Systems
Fifteen teams recently used the WinWin Spiral Model to perform the system engineering and architecting of a set of multimedia applications for the USC Library Information Systems. Six of the...
Analysis of System Requirements Negotiation Behavior Patterns (1997)
Alexander Egyed And, Er Egyed, Barry Boehm
Roughly 35 three-person teams played the roles of user, customer, and developer in negotiating the requirements of a library information system. Each team was provided with a suggested set of...
Software Cost Option Strategy Tool (S-COST (1996)
Barry Boehm, Barry Boehm, Hoh In
and Application Conference)
The winwin requirements negotiation system: A model-driven approach (1996)
Requirements Engineering constitutes an important part of Software Engineering. The USC WinWin requirements negotiation system addresses critical issues in requirements engineering including (1)...
Aids for Identifying Conflicts Among Quality Requirements (1996)
One of the biggest risks in software requirements engineering is the risk of overemphasizing one quality attribute requirement (e.g., performance) at the expense of others at least as important...
Cost models for future software life cycle processes: Cocomo 2.0 (1995)
Barry Boehm, Bradford Clark, Ellis Horowitz, Chris Westl, Ray Madachy, Richard Selby
Current software cost estimation models, such as the 1981 Constructive Cost Model (COCO-MO) for software cost estimation and its 1987 Ada COCOMO update, have been experiencing increasing difficulties...
Software Requirements Negotiation and Renegotiation Aids: A Theory-W Based Spiral Approach (1995)
Barry Boehm, Prasanta Bose, Ellis Horowitz, Ming June Lee
A major problem in requirements engineering is obtaining requirements that address the concerns of multiple stakeholders. An approach to such a problem is the Theory-W based Spiral Model. One key...
Ten prototype knowledge-based software engineering (KBSE) applications were recently developed in a USC graduate course. These were expert-system applications falling into the Activity Coordination...
On the Definition of Software System Architecture (1995)
Cristina Gacek, Cristina Gacek, B. Clark, B. Boehm, A. Abd-Allah, Ahmed Abd-allah, ...
Although several definitions of "software architecture" have been presented, none of them to date enable a reviewer confronted with a complex of diagrams and symbols to determine whether it...
Reasoning about the Composition of Heterogeneous Architectures (1995)
ions for Software Architecture and Tools to Support Them. Carnegie Mellon University, Pittsburgh, February 1994 [SPIV92] J. Spivey. The Z Notation, Prentice Hall International, 1992 [STEP92] S....
Anchoring the Software Process (1995)
The current proliferation of software process models provides flexibility for organizations to deal with the unavoidably wide variety of software project situations, cultures, and environments. But...
Cost Models for Future Software Life Cycle Processes: COCOMO 2.0 (1995)
Barry Boehm, Bradford Clark, Ellis Horowitz, Chris Westland, Ray Madachy, Richard Selby
Current software cost estimation models, such as the 1981 Constructive Cost Model (COCOMO) for software cost estimation and its 1987 Ada COCOMO update, have been experiencing increasing difficulties...
Cost Models for Future Software Life Cycle Processes: COCOMO 2.0 (1995)
Barry Boehm, Bradford Clark, Ellis Horowitz, Chris Westland, Ray Madachy, Richard Selby
Current software cost estimation models, such as the 1981 Constructive Cost Model (COCOMO) for software cost estimation and its 1987 Ada COCOMO update, have been experiencing increasing difficulties...
Software Requirements Negotiation and Renegotiation Aids: A Theory-W Based Spiral Approach (1995)
Barry Boehm, Prasanta Bose, Ellis Horowitz, Ming June Lee
A major problem in requirements engineering is obtaining requirements that address the concerns of multiple stakeholders. An approach to such a problem is the Theory-W based Spiral Model. One key...
On the Definition of Software System Architecture (1995)
Cristina Gacek, Ahmed Abd-allah, Bradford Clark, Barry Boehm
Although several definitions of "software architecture" have been presented, none of them to date enable a reviewer confronted with a complex of diagrams and symbols to determine whether it...
Software Requirements Negotiation and Renegotiation Aids: A Theory-W Based Spiral Approach (1995)
Barry Boehm, Prasanta Bose, Ellis Horowitz, Ming June Lee
A major problem in requirements engineering is obtaining requirements that address the concerns of multiple stakeholders. An approach to such a problem is the Theory-W based Spiral Model. One key...
A Collaborative Spiral Software Process Model Based on Theory W (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...
A Collaborative Spiral Software Process Model Based on Theory W (1994)
Barry Boehm And, Barry Boehm, Prasanta Bose
This paper presents an extension of the spiral model, called the Next Generation Process Model (NGPM), which uses the Theory W (win-win) approach [Boehm-Ross, 1989] to converge on a system's...
Focused Workshop on Software Reuse: Issue Paper (1994)
Cristina Gacek, Bradford Clark, Barry Boehm
This paper is organized around the general topics that will be covered by the workshop discussion groups, therefore serving as a thought triggering mechanism.
Software Requirements As Negotiated Win Conditions (1994)
Barry Boehm, Prasanta Bose, Ellis Horowitz, Ming-june Lee
Current processes and support systems for software requirements determination and analysis often neglect critical needs of important classes of stakeholders and limit themselves to concerns of the...
KBSE Tool for Megaprogramming (1993)
lected a different data structure the options available would be extremely better for him/her. Thus, a KBSE tool developed to address this software construction approach should be able to assist the...
KBSE Tool for Megaprogramming (1993)
intelligent systems that can automate the construction of software|has been intensi ed in the last ten years, and is now addressing a full range of software engineering activities [Johnson 1993],...
The ROI of Software Dependability: The iDAVE Model (0000)
In most organizations, proposed investments in software dependability compete for limited resources with proposed investments in software and system functionality, response time, adaptability,...
The ROI of Software Dependability: The iDAVE Model
In most organizations, proposed investments in software dependability compete for limited resources with proposed investments in software and system functionality, response time, adaptability,...
Calibrating the COCOMO II Post-Architecture Model
Bradford Clark, Sunita Devnani-chulani, Barry Boehm
The COCOMO II model was created to meet the need for a cost model that accounted for future software development practices. This paper describes some of the experiences learned in calibrating COCOMO...