Software risk management
SAAM: a method for analyzing the properties of software architectures
ICSE '94 Proceedings of the 16th international conference on Software engineering
Developing multimedia applications with the WinWin spiral model
ESEC '97/FSE-5 Proceedings of the 6th European SOFTWARE ENGINEERING conference held jointly with the 5th ACM SIGSOFT international symposium on Foundations of software engineering
Architectural Mismatch: Why Reuse Is So Hard
IEEE Software
Architectural Mismatch: Why Reuse Is So Hard
IEEE Software
Identifying Quality-Requirement Conflicts
IEEE Software
Anchoring the Software Process
IEEE Software
Principles of Program Design
Structured Analysis for Requirements Definition
IEEE Transactions on Software Engineering
M(in)BASE: an upward-tailorable process wrapper framework for identifying and avoiding model clashes
SPW'05 Proceedings of the 2005 international conference on Unifying the Software Process Spectrum
An ontology definition framework for model driven development
ICCSA'06 Proceedings of the 2006 international conference on Computational Science and Its Applications - Volume Part IV
Hi-index | 0.00 |
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, process, property, and success characteristics. (Here, we use a simplified version of one of Webster's definitions of "model" a description or analogy used to help visualize something. We include analysis as a form of visualization). Section 2 of this paper introduces the concept of model clashes, and provides examples of common clashes for each combination of product, process, property, and success models. Section 3 introduces the Model-Based Architecting and Software Engineering (MBASE) approach for endowing a software project with a mutually supportive base of models. Section 4 presents examples of applying the MBASE approach to a family of digital library projects. Section 5 summarizes the main conceptual modeling challenges involved in the MBASE approach, including integration of multiple product views and integration of various classes of product, process, property, and success models. Section 6 summarizes current conclusions and future prospects.