Conceptual Modeling Challenges for Model-Based Architecting and Software Engineering (MBASE)

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.

[1]  Perry E. Rosove Developing Computer-based Information Systems , 1967 .

[2]  Michael Jackson,et al.  Principles of program design , 1975 .

[3]  Douglas T. Ross,et al.  Structured Analysis for Requirements Definition , 1977, IEEE Transactions on Software Engineering.

[4]  Charles W. Krueger,et al.  Software reuse , 1992, CSUR.

[5]  Raymond J. Madachy,et al.  Knowledge-based risk assessment and cost estimation , 1994, Proceedings KBSE '94. Ninth Knowledge-Based Software Engineering Conference.

[6]  Barry Boehm,et al.  A collaborative spiral software process model based on Theory W , 1994, Proceedings of the Third International Conference on the Software Process. Applying the Software Process.

[7]  Leonard J. Bass,et al.  SAAM: a method for analyzing the properties of software architectures , 1994, Proceedings of 16th International Conference on Software Engineering.

[8]  David Garlan,et al.  Architectural Mismatch: Why Reuse Is So Hard , 1995, IEEE Softw..

[9]  Barry W. Boehm,et al.  Anchoring the Software Process , 1996, IEEE Softw..

[10]  Barry W. Boehm,et al.  Identifying Quality-Requirement Conflicts , 1996, IEEE Softw..

[11]  Barry W. Boehm,et al.  Software Risk Management , 1989, ESEC.

[12]  Barry Boehm,et al.  Developing multimedia applications with the WinWin spiral model , 1997, ESEC '97/FSE-5.