USC-CSE TUTORIAL
MBASE, CMMI, and Evolutionary/Spiral Development
July 27, 2000





 Theme: Transitioning to the Integrated Capability Maturity Model via MBASE
Location:
University of Southern California 
Los Angeles, CA

Several recent government and commercial initiatives involve changes toward integrated capability maturity models and toward evolutionary/spiral acquisition and development. This is causing many software-intensive organization to explore new approaches for integrating software/system and product/process practices, and applying them to evolutionary/spiral acquisition and development.

Model-Based (System) Architecting and Software Engineering (MBASE) is an approach for integrating not only product and process model considerations, but also equally important property and success model considerations, in the development and evolution of software-intensive systems. It is based on the spiral model, which it extends in a number of significant ways. It has been successfully applied not only on large projects, but also on over 100 smaller high-tech, rapid-development software-intensive systems.

Successfully transitioning to integrated CMMs and evolutionary/spiral acquisition and development will involve software-intensive organizations with many new process areas and practices to integrate, such as shared vision definition; business case analysis; customer/developer/supplier negotiation and change management; decision analysis; COTS evaluation and integration; and integrated product and process definition, often with cost/schedule-as-independent-variable considerations.

It will also involve the organization with new classes of software/system pitfalls and challenges. A particularly significant source of pitfalls and challenges are "model clashes" among a system's process, product, property, and success models. These model clashes are hidden conflicts among the models the software and system stakeholders (users, customers, developers, maintainers, marketers, and others) bring to a software/system project.

The first half of this tutorial presents the MBASE framework and approach for tailoring and integrating these four classes of models to apply to specific software-system project situations. It shows how the MBASE framework maps onto the CMMI framework, and how the MBASE approach can be used to apply the CMMI processes and practices to software/system projects. It also provides examples of successful MBASE application to large and small projects.

The second half of the tutorial provides hands-on training in using the web-based MBASE Electronic Process Guide. This will include hyperlink navigation among the MBASE EPG's activities, artifacts and agents; use of the EPG's MBASE document templates; application of the EPG and templates to a case study; and procedures for tailoring the EPG to your organization's particular practices.
 
The morning session will be lecture-and-discussion with unlimited attendance.  The afternoon session will be hands-on training on using the web-based MBASE Electronic Process Guide and its document templates.

For any questions, please let LaDonna Pierce know at the address below:

Ms. LaDonna Pierce
Center for Software Engineering
University of Southern California
Los Angeles, CA 90089-0781
Phone: (213) 740-5703
Fax: (213) 740-4927
Email: ladonna@sunset.usc.edu
 
              < Previous Event
     Next Event >

To the Upcoming Event 

Copyright 1995, 1996, 1997, 1998 The University of Southern California
 

The written material, text, graphics, and software available on this page and all related pages may be copied, used, and distributed freely as long as the University of Southern California as the source of the material, text, graphics or software is always clearly indicated and such acknowledgement always accompanies any reuse or redistribution of the material, text, graphics or software; also permission to use the material, text, graphics or software on these pages does not include the right to repackage the material, text, graphics or software in any form or manner and then claim exclusive proprietary ownership of it as part of a commercial offering of services or as part of a commercially offered product.