Summary
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.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Similar content being viewed by others
References
C. Babcock, “New Jersey Motorists in Software Jam,” ComputerWorld, September 30, 1985, pp. 1, 6.
B. Boehm, Software Risk Management, IEEE-CS Press, 1989.
B. Boehm, “Anchoring the Software Process,” IEEE Software, July 1996, pp. 73–82.
B. Boehm, A. Egyed, J. Kwan, and R. Madachy, “Developing Multimedia Applications with the WinWin Spiral Model,” Proceedings, ESEC/ FSE 97, Springer Verlag, 1997.
B. Boehm and P. Bose, “A Collaborative Spiral Process Model Based on Theory W,” Proceedings, ICSP3, IEEE, 1994.
B. Boehm and H. In, “Identifying Quality-Requirement Conflicts,” IEEE Software, March 1996, pp. 25–35.
D. Garlan, R. Allen, and J. Ockerbloom, “Architectural Mismatch: Why Reuse is So Hard,” IEEE Software, November 1995, pp. 17–26.
M. A. Jackson, Principles of Program Design, Academic Press, 1975.
I. Jacobson, M. Griss, and P. Jonsson, Software Reuse, Addison Wesley, 1997.
R. Kazman, L. Bass, G. Abowd, and M. Webb, “SAAM: A Method for Analyzing the Properties of Software Architectures,” Proceedings, ICSE 16, ACM/IEEE, 1994, pp. 81–90.
M.J. Lee, Formal Modeling of the WinWin Requirements Negotiation System, Ph.D. Thesis, USC Computer Sciences Dept., 1996.
R. Madachy, “Knowledge-Based Risk Assessment Using Cost Factors”,Automated Software Engineering, 2, 1995.
J. Marenzano, “System Architecture Validation Review Findings,” in D. Garlan, ed., ICSE17 Architecture Workshop Proceedings, CMU, Pittsburgh, PA 1995.
D. Port, Integrated Systems Development Methodology, Telos Press, 1998 (to appear).
Rational Objectory Process, Version 4.1, Rational Software Corp., Santa Clara, CA, 1997.
P.E. Rosove, Developing Computer-Based Information Systems, John Wiley and Sons, Inc., 1967.
D.T. Ross and K.E. Schoman, “Structured Analysis for Requirements Definition,” IEEE Trans. SW Engr., January 1977, pp. 41–48.
W.E. Royce, Unified Software Management, Addison Wesley, 1998 (to appear).
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 1999 Springer-Verlag Berlin Heidelberg
About this chapter
Cite this chapter
Boehm, B., Port, D. (1999). Conceptual Modeling Challenges for Model-Based Architecting and Software Engineering (MBASE). In: Goos, G., et al. Conceptual Modeling. Lecture Notes in Computer Science, vol 1565. Springer, Berlin, Heidelberg. https://doi.org/10.1007/3-540-48854-5_3
Download citation
DOI: https://doi.org/10.1007/3-540-48854-5_3
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-65926-6
Online ISBN: 978-3-540-48854-5
eBook Packages: Springer Book Archive