M(in)BASE: an upward-tailorable process wrapper framework for identifying and avoiding model clashes

Authors:
David Klappholz;Daniel Port
Affiliations:
Stevens Institute of Technology, Department of Computer Science, New Jersey;Department of Information Technology Management, University of Hawaii at Manoa, Honolulu, Hawaii
Venue:
SPW'05 Proceedings of the 2005 international conference on Unifying the Software Process Spectrum
Year:
2005

Citing 10
Cited 0

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
The Rational Unified Process: an introduction

The Rational Unified Process: an introduction
Escaping the software tar pit: model clashes and how to avoid them

ACM SIGSOFT Software Engineering Notes
When Models Collide: Lessons from Software Systems Analysis

IT Professional
Using the WinWin Spiral Model: A Case Study

Computer
Avoiding the Software Model-Clash Spiderweb

Computer
Anchoring the Software Process

IEEE Software
The MBASE Life Cycle Architecture Milestone Package

WICSA1 Proceedings of the TC2 First Working IFIP Conference on Software Architecture (WICSA1)
Conceptual Modeling Challenges for Model-Based Architecting and Software Engineering (MBASE)

Selected Papers from the Symposium on Conceptual Modeling, Current Issues and Future Directions
Using a Model Framework In Developing and Delivering a Family of Software Engineering Project Courses

CSEET '01 Proceedings of the 14th Conference on Software Engineering Education and Training

Quantified Score

Hi-index	0.01

Visualization

Abstract

MBASE (Model-Based [System] Architecting & Software Engineering) is a framework that can be wrapped around any software development process to deal with project failures caused by “model clashes.” Existing MBASE guidelines have all been designed to cover large classes of projects, and are intended to be tailored down, based on risk considerations, to the project at hand. Experience has shown that tailoring down is quite hard to learn and apply; based upon this observation, we are developing M(in)BASE, a minimal version of MBASE intended to be tailored up. In this paper, we review the fundamentals of MBASE, discuss, in detail, the reasons for creating M(in)BASE, and describe M(in)BASE.