Avoiding the Software Model-Clash Spiderweb

@article{Boehm2000AvoidingTS,
  title={Avoiding the Software Model-Clash Spiderweb},
  author={Barry W. Boehm and Daniel Port and Mohammed Al-Said},
  journal={Computer},
  year={2000},
  volume={33},
  pages={120-122}
}
Experience and studies of software-model clashes confirm that every software project is unavoidably confronted by a spiderweb of potential model clashes derived from the success models of the project's key stakeholders. These stakeholders usually include the software system's users, acquirers, developers and maintainers. Additional key stakeholders can include venture capitalists, marketers, proprietors of mutually developed interoperating systems, and the general public when issues such as… 

Figures from this paper

M(in)BASE: An Upward-Tailorable Process Wrapper Framework for Identifying and Avoiding Model Clashes
TLDR
The fundamentals of MBASE are reviewed, the reasons for creating M(in)BASE are discussed, and a minimal version ofMBASE intended to be tailored up is described.
Integration of Software Models An Overview of Possible Issues
TLDR
Steps for constructing a process of model integration in complex situations are suggested and the dangers of software project can be avoided by appropriate selection and integration of models.
Value-based software engineering: reinventing
TLDR
The paper introduces an example order-processing software project, and shows how the use of Benefits Realization Analysis, stake-holder value proposition elicitation and reconciliation, and business case analysis provides a framework for stakeholder-earned-value monitoring and control.
Stronger Than Ever
TLDR
The authors in this article show how the spiral model and its recent extension – Model-Based Architecting and Software Engineering – can be used to tailor a project's balance of discipline and flexibility via risk considerations.
Software quality analysis: a value-based approach
TLDR
A Value-Based Software Quality Analysis framework that integrates the stakeholder/value approach into quality attribute definitions, metrics, models and development processes aiming at achieving the appropriate quality levels for software systems is developed.
A Collaborative Approach for Reengineering-based Product Line Scoping
TLDR
A collaborative approach which is intended to complement existing approaches for reengineering of legacy products in product line engineering and supports success-critical stakeholders working collaboratively to converge on a product map and a definition of reusable infrastructures is proposed.
Making a Difference in the Software Century
In the 21st century, software engineers face the often formidable challenges of simultaneously dealing with rapid change, uncertainty and emergence, dependability, diversity, and interdependence, but
Evidence-Based Software Processes
TLDR
This paper provides processes for developing and reviewing feasibility evidence, and for using risk to determine how to proceed at major milestones, and provides quantitative result on "how much investment in evidence is enough," as a function of the project's size, criticality, and volatility.
Value-Based Software Engineering: Seven Key Elements and Ethical Considerations
  • B. Boehm
  • Business
    Value-Based Software Engineering
  • 2006
TLDR
This chapter presents seven key elements that provide candidate foundations for value-based software engineering and shows how some of these elements can be used to incorporate ethical considerations into daily software engineering practice.
...
...