In software engineering, Model-Based Architecting and Software Engineering (MBASE) is a software development process developed by Barry Boehm and Dan Port in the late 1990s. MBASE focuses on ensuring that a project’s product models (architecture, requirements, source code, etc.), process models (tasks, activities, milestones), property models (cost, schedule, performance, dependability), and success models (stakeholder win-win, IKIWISI - I’ll Know It When I See It, business case) are consistent and mutually enforcing. To meet Wikipedias quality standards, this article or section may require cleanup. ... Software requirements analysis is the activity of eliciting, analyzing, and recording requirements for software systems. ... Software architecture or software systems architecture can best be thought of as a representation of an engineered (or To Be Engineered) software system, and the process and discipline for effectively implementing the design(s) for such a system. ... For programming in music, see Programming (music). ... Software testing is the process used to help identify the correctness, completeness, security and quality of developed computer software. ... This article needs to be wikified. ... Agile software development is a conceptual framework for undertaking software engineering projects. ... The Cleanroom Software Engineering process is a software development process intended to produce software with a certifiable level of reliability. ... Iterative and Incremental development is a software development process, as opposed to more traditional waterfall model. ... Rapid application development (RAD), is a software development process developed initially by James Martin in the 1980s. ... The Rational Unified Process (RUP) is an iterative software development process created by the Rational Software Corporation, now a division of IBM. The RUP is not a single concrete prescriptive process, but rather an adaptable process framework. ... The spiral model is a software development process combining elements of both design and prototyping-in-stages, in an effort to combine advantages of top-down and bottom-up concepts. ... The waterfall model is a software development model (a process for the creation of software) in which development is seen as flowing steadily downwards (like a waterfall) through the phases of requirements analysis, design, implementation, testing (validation), integration, and maintenance. ... Extreme Programming (XP) is a software engineering methodology, the most prominent of several agile software development methodologies. ... Software Configuration Management (SCM) is part of configuration management (CM). ... Software Documentation or Source Code Documentation is written text that accompanies computer software. ... Project management is the discipline of organizing and managing resources in such a way that these resources deliver all the work required to complete a project within defined scope, time, and cost constraints. ... Software engineering (SE) is the profession of people who create and maintain software systems by applying technologies and practices from computer science, project management, engineering, application domains and other fields. ... To meet Wikipedias quality standards, this article or section may require cleanup. ... Barry W. Boehm is known for many contributions to software engineering. ... See also 1990s, the band The 1990s decade refers to the years from 1990 to 1999, inclusive, sometimes informally including popular culture from 2000 and 2001. ... Software architecture or software systems architecture can best be thought of as a representation of an engineered (or To Be Engineered) software system, and the process and discipline for effectively implementing the design(s) for such a system. ... A requirement is a singular documented need of what a particular product or service should be or do. ... Source code (commonly just source or code) is any series of statements written in some human-readable computer programming language. ...

MBASE is an approach to the development of software systems that integrates the system’s process (PS), product (PD), property (PY) and success (SS) models, models that are documented in the following system definition elements (also referred to as “artifacts” or “deliverables”):

• Operational Concept Description (OCD)
• System and Software Requirements Definition (SSRD)
• System and Software Architecture Description (SSAD)
• Life Cycle Plan (LCP)
• Feasibility Rationale Description (FRD)
• Construction, Transition, Support (CTS) plans and reports
• Risk-driven prototypes

The essence of the LeanMBASE approach is to develop the system definition elements concurrently, through iterative refinement, using the risk-driven, three-anchor point, Win–Win Spiral approach defined in Boehm's Anchoring the Software Process. Barry W. Boehm is known for many contributions to software engineering. ...

History

Over the three years (1995 to 1998) of developing digital library products for the libraries at University of Southern California (USC), Barry Boehm and Dan Port had been evolving an approach called Model-Based (System) Architecting and Software Engineering (MBASE). Edward L. Doheny Jr. ... Barry W. Boehm is known for many contributions to software engineering. ...

See also

• Model-driven engineering (i.e. OMG's MDA applied in the Platform/Technology-Independent Model (PIM/TIM) and Platform/Technology-Specific Model (PSM/TSM) in MBASE's SSAD)

Model-driven engineering (MDE) is an emerging technique in software, system and data engineering, based on the systematic use of models. ... Object Management Group (OMG) is a consortium, originally aimed at setting standards for distributed object-oriented systems, and now focused on modeling (programs, systems and business processes) as well as model-based standards in some 20 vertical markets. ... The Model-Driven Architecture (MDA) is a software design approach, proposed and sponsored by the Object Management Group. ...

References

• USC Center for Software Engineering (CSE) MBASE Research
• Barry Boehm: Anchoring the Software Process
• Barry Boehm and Dan Port: Conceptual Modeling Challenges for Model-Based Architecting and Software Engineering (MBASE)
• Barry Boehm, et al.: Guidelines for Lean Model-Based (System) Architecting and Software Engineering (LeanMBASE)

Barry W. Boehm is known for many contributions to software engineering. ... Barry W. Boehm is known for many contributions to software engineering. ... Barry W. Boehm is known for many contributions to software engineering. ...

External links

• Barry Boehm, David M. Wong, and Raffi Tikidjian: Reconciling LeanMBASE with Role-based Agility