Avoiding the software model-clash spiderweb

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 safety and privacy arise. The authors offer two techniques for avoiding the conflicting assumptions that often snare software projects in a costly and time-consuming spiderweb.