System Maintenance:
There may be intermittent impact on performance while updates are in progress. We apologize for the inconvenience.
By Topic

When models collide: lessons from software systems analysis

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

2 Author(s)
Boehm, B. ; Center for Software Eng., Univ. of Southern California, USA ; Port, D.

Sooner or later, the assumptions people make about what a system should do will conflict. Here's how to recognize it before it's too late. Systems analysis is rapidly coming of age. Many projects have successfully used a new approach called MBASE (Model-Based System Architecting and Software Engineering). The MBASE approach integrates the four common development models (success, product, process, and property) around the creation and use of a software architecture package. As analysts explicitly integrate models using MBASE, they can recognize and reconcile model clashes as a matter of course, instead of after the fact

Published in:

IT Professional  (Volume:1 ,  Issue: 1 )