Model Driven System Design Working Group: FOUNDATIONAL CONCEPTS FOR MODEL DRIVEN SYSTEM DESIGN

Baker, Loyd; Clemente, P. C. M.; Cohen, Bob; Permenter, Larry; Purves, B.; Salmon, Pete

doi:10.1002/j.2334-5837.1996.tb02139.x

Cited by 16 publications

(12 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Preparedness [3], [5], [13], [15], [16], Time of Hit (Emergency) [8], [11] Recovery [4], [6], [10], [14] Chakraborty et. al.…”

Section: Event Phasementioning

confidence: 99%

“…A key enabler of MBSE is a standardized and robust modeling language, one which can be used to produce good models, in the sense of Baker et al [16]. SysML is a generalpurpose modeling language that supports the specification, design, analysis, and verification of systems [9].…”

Section: Background On Sysmlmentioning

confidence: 99%

“…[6] studied the 978-1-4244-5883-7/10/$26.00 ©2010 IEEE physical and social impacts of earthquake as assessed during the recovery phase. Hurricane [3], [12], [13], [14], [15], [16] Earthquake [5], [6], [10] Wildfire [19] Pandemic [18] …”

Section: Introductionmentioning

confidence: 99%

“…The preparedness period occurring before the disaster [15,16], in which studies may result, for example, in new safety standards [5]. The emergency period (i.e.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

A model-based systems engineering approach to capturing disaster management systems

Soyler

Sala-Diakanda

2010

2010 IEEE International Systems Conference

View full text Add to dashboard Cite

The purpose of this paper is to initiate the design of a framework for defining and capturing disaster management systems (DMS). Recognizing the management of disasters as complex adaptive systems (CAS), whose performance cannot be improved through the isolated optimization of their constituents, this paper proposes the adoption of model-based systems engineering (MBSE) to capturing the behavior of such systems, as well as the structure responsible for their behaviors. Using a domain-independent language such as the systems modeling language (SysML) to implement MBSE, the holistic approach proposed here effectively introduces a new paradigm in disaster management studies that is aimed at reducing the aforementioned complexity. By enforcing traceability between the DMS subsystems, and by leveraging artifacts such as viewpoints to develop perspectives that are tailored to specific stakeholders and users, it is anticipated that a MBSE-based holistic approach such as the one presented in this paper will promote proper use of the scientific method for the design, verification, validation and improvement of disaster management systems.

show abstract

“…Preparedness [3], [5], [13], [15], [16], Time of Hit (Emergency) [8], [11] Recovery [4], [6], [10], [14] Chakraborty et. al.…”

Section: Event Phasementioning

confidence: 99%

Section: Background On Sysmlmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

“…The preparedness period occurring before the disaster [15,16], in which studies may result, for example, in new safety standards [5]. The emergency period (i.e.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

A model-based systems engineering approach to capturing disaster management systems

Soyler

Sala-Diakanda

2010

2010 IEEE International Systems Conference

View full text Add to dashboard Cite

show abstract

“…It does not provide any forward indicator or success or failure. Although not widely practiced, modeldriven design (e. g., Baker et al, 1997) promises to allow early detection of design errors, thus saving the time and money required when later discovery means significant amounts of rework .…”

Section: Figure 1 -Information Flow For the Msdcmentioning

confidence: 99%

7.7.2 The Mission System Design Center: A Pilot of Formulation‐Phase Concurrent Engineering in Aerospace Design

Wall

2001

INCOSE International Symp

View full text Add to dashboard Cite

In this paper we describe pilots of a concurrent‐engineering, formulation‐phase design team demonstrated in spacecraft missions. This “Mission Team” operates within a design center called the Mission System Design Center, where design tools are linked via a central database and use large‐screen projection systems to engage the entire team in system‐level trade discussions. In these pilots, the Mission Team was able to manage complex trades, resolve conflicts, and rebalance requirements in the face of typical formulation phase issues. This team operates to periodically re‐evaluate requirements and resource allocations (e. g., mass, power, funds, datarate) in the face of both externally and internally imposed changes.

show abstract

Specifying a System Using Era Information Models

Baker¹,

Long²

2018

INSIGHT

View full text Add to dashboard Cite

Stating the requirements for systems or business processes as a hierarchical collection of English text that can only be analyzed/ verified by human inspection has proven time and again to be labor intensive and generally, inadequate. Projects employing a traditional document-centered system engineering approach have experienced significant numbers of mis-interpretations of the customer's requirements, or late-detected design errors results in increased costs, schedule slips, reduced capability, or canceled programs. We have historically fixed requirements problems, that should have been understood and resolved early, during integration and test where it is more costly to identify and fix. Now that computerized system engineering support tools are available on the engineer's desktop, the leading edge aerospace/commercial corporations are transitioning from a document-centered to a model-driven system engineering approach to developing, analyzing, and managing explicit system/process specifications. Information and operational models (of varying levels of detail) not only aid in the understanding and communication of intentions such that incorrect assumptions can be eliminated early, they directly support the development of system verification plans.

show abstract

Model Driven System Design Working Group: FOUNDATIONAL CONCEPTS FOR MODEL DRIVEN SYSTEM DESIGN

Cited by 16 publications

References 0 publications

A model-based systems engineering approach to capturing disaster management systems

A model-based systems engineering approach to capturing disaster management systems

7.7.2 The Mission System Design Center: A Pilot of Formulation‐Phase Concurrent Engineering in Aerospace Design

Specifying a System Using Era Information Models

Contact Info

Product

Resources

About