4.1.2 Extending UML to Support a Systems Modeling Language

Under the complex operational environment of the antimissile operation, the application of Systems Modeling Language (SysML) parametric model in weapon system effectiveness evaluation is explored. The function of parametric graph model, the construction process of the model and the optimization method of the model are researched. Using feedback mechanism to collect, collate and calculate the parameters of the model, and realize the leap from the index relationship description to the calculation of the index. Finally, the feasibility and effectiveness of the proposed method is verified by using the system of antimissile weapon system as an example.

The International Council on Systems Engineering (INCOSE) Space System Working Group (SSWG) has created the CubeSat System Reference Model (CSRM), a representation of the logical architecture of a CubeSat system, intended to be used by system architects and engineers as a starting point as they develop the logical architecture of the Space and Ground components of the CubeSat mission of interest to them. The CSRM is based on Model-Based System Engineering (MBSE) principles, is System Modeling Language (SysML) compliant, is hosted in a graphical modeling tool, and is intended to introduce quality enhancements and economies associated with reusability. The CSRM has been vetted by System Engineering professionals and has been introduced to the CubeSat mission development team community with favorable results. It has been submitted to the Object Management Group (OMG) as a CubeSat specification, and is being evaluated for that role. The SSWG has created a notional outline describing how the CSRM can be applied to a specific mission development effort; and has also identified possible future efforts to expand the applicability, value, and use of the CSRM by the satellite development community.

<title>ABSTRACT</title> <p>As systems become more complicated, managing them from conceptual design through disposal has become significantly more difficult. Traditional process- and document-based methods often struggle to cope with the realities of designing and fielding modern engineered systems; relevant information can become segmented and out-of-sync, leading to costly errors.</p> <p>The International Council on Systems Engineering (INCOSE) initiated a Model-Based Systems Engineering (MBSE) initiative nearly fifteen years ago; one of the fruits of this effort is the System Modeling Language (SysML). Modern SysML tools are quite mature and have considerable capabilities to capture, characterize, and connect information.</p> <p>A number of efforts are currently underway to maximize the value of SysML models, including the development of visualization, co-simulation, and robust model integration. An entire ecosystem of adjacent tools is evolving that will significantly impact the practice of systems engineering within the next five years. This paper presents an integrated look at publically-available information about existing worldwide efforts and their implications for systems engineering practitioners.</p>

This article describes activity modeling as specified by the Systems Modeling Language (as specified by the SysML Merge Team, http://doc.omg.org/ad/2006‐02‐01 , February 2006) and the finalization of the Unified Modeling Language version 2 (UML 2). It reviews and updates an earlier proposed alignment between Enhanced Functional Flow Block Diagrams (EFFBD), UML 2 Activities, and requirements developed by the International Council on Systems Engineering and Object Management Group. It presents a spectrum of activity modeling techniques, ranging from a widely used systems engineering diagram, the EFFBD, to continuous flow modeling. The techniques include control capabilities, continuous system concepts, and others related to functional decomposition and allocation. The article also describes refinements of activity modeling concepts identified during SysML development. © 2006 Wiley Periodicals, Inc. Syst Eng 9:160–186, 2006

Traditional document‐based practices in systems engineering are being transitioned to model‐based ones. Adoption of model‐based systems engineering (MBSE) continues to grow in industry and government, and MBSE continues to be a major research theme in the systems engineering community. In fact, MBSE remains a central element in the International Council on Systems Engineering (INCOSE)’s vision for 2025. Examining systems engineering literature, this paper presents an assessment of the extent to which benefits and value of MBSE are supported by empirical evidence. A systematic review of research and practice papers in major systems engineering archival journals and conference proceedings was conducted. Evidence was categorized in four types, two of which inductively emerged from the results: measured, observed (without a formal measurement process), perceived (claimed without evidence), and backed by other references. Results indicate that two thirds of claimed MBSE benefits are only supported by perceived evidence, while only two papers reported measured evidence. The aggregate assessment presented in this paper indicates that claims about the value and benefits of MBSE are mainly based on expectation. We argue that evidence supporting the value and benefits of MBSE remains inconclusive.

Very small entities, organizations with up to 25 people, are very important to the worldwide economy. The products they develop are either developed specifically for a customer or are integrated into products made by larger enterprises. To address the needs of Very small entities, a set of standards and guides have been developed using the systems engineering lifecycle standard ISO/IEC/IEEE 15288 as the main framework. The systems engineering handbook, developed by the International Council on Systems Engineering (INCOSE), is used as the reference for the development of a set of systems engineering deployment packages. Two pilot projects, using the new ISO/IEC 29110 guide for systems engineering, are presented as well as a cost and savings analysis. Finally, the certification scheme is discussed as well as the future developments.KeywordsVSEISO/IEC 29110ISOStandards

Chapter 15 - Water Distiller Example Using Functional Analysis

As the International Council On Systems Engineering (INCOSE) internationalizes its mission, there is a need to address the advancement of the Systems Engineering practice in all environments where improvement opportunities are achievable. This paper is an analysis of the application of Systems Engineering disciplines for commercial infrastructure systems development. The analysis addresses areas where Systems Engineering Science can be translated from a military context to assist sister projects on the commercial side of the industry. The paper also encourages INCOSE to consider the external side of its mission, and to find a culture that will assist those who need to know, instead of internally preaching to those who already know. © 1999 John Wiley & Sons, Inc. Syst Eng 2: 212–216, 1999

“Model-based Systems Engineering” is currently a hot topic at INCOSE (International Council on Systems Engineering). It involves multidisciplinary development based on the usage of models as main artifact. The frequent use of models during the development of the pico-satellite MOVE (Munich Orbital Verification Experiment) was attributed to the long history of the chair for astronautics at the TU München with Systems Engineering. The development of MOVE displayed many of the characteristics of a real-world multidisciplinary engineering project and resulted in a successful space flight of the engineered satellite. Within the satellite, communication was lead through a central bus between the different components and required expertise and coordination from all of the involved disciplines. An equivalent task of distributing information and energy can be found in automotive engineering: in the wire-harness. In contrast to the satellite bus, it does not distribute centrally created coordination commands, but supports the orchestration between distributed systems. Even though these two systems and their development processes are inherently different, they exhibit similar difficulties during their design phase (e.g. with compatibility) and can be modeled similarly. This paper uses the design of satellite bus systems and automotive wire-harnesses as examples, describes their common pitfalls, explains “Model-based Systems Engineering” and demonstrates how the development of communication systems in both satellite and automotive engineering can benefit from relying on it in early design and concept phases.

The International Council on Systems Engineering (INCOSE) has initiated a Future of Systems Engineering (FuSE) program that includes a stream for advancing the theoretical foundations of the discipline of Systems Engineering (SE). A near‐term goal of FuSE is to assess the adequacy of current theoretical foundations of SE. The discipline of SE is converging toward model‐based practices (i.e., MBSE) that have not yet reached the maturity of model‐based practices in other engineering domains. For example, finite element analysis and computational fluid dynamics are grounded in mathematical theory, while, generally, MBSE is not. However, some attempts have been made to underpin MBSE with theoretical richness. This article presents a systematic literature study that surveyed state of the art on providing MBSE with mathematical foundations. Our protocol collected over 2000 publications that were reviewed for inclusion/exclusion, categorized, and analyzed. We provide insights to the type of mathematical theories used, domains of applications, and areas of SE to which the math was applied to, among other analysis. We also provide a synthesized discussion about the field moving forward, emphasizing positive trends along with the negatives and areas of concern. Overall, we found the field to be nascent.

This paper highlights the accomplishments and shared vision between the International Council on Systems Engineering (INCOSE) and the Modeling and Simulation community (represented by the Society for Modeling and Simulation, International (SCS), and Simulation Interoperability Standards Organization (SISO, among others). We describe convergence between the model-based systems engineering initiative of the INCOSE community and the model-based simulation developments of the SCS community. The goal is not only to highlight the outstanding accomplishments of our time, but also to emphasize the parallels and relationships. The paper is intended to enhance communications and facilitate the outreach already in motion. Modeling and Simulation (M&S) represents a core capability and need for addressing today’s complex and grand challenges. We suggest a collaboration of INCOSE and SCS, as leaders in the systems and M&S communities, to solve these challenges complicated by multi-dimensional, hierarchical, and uncertain Big Data and propelled by exascale computational platforms.

<div class="section abstract"><div class="htmlview paragraph">Complex and/or highly integrated systems require the evaluation of Dependability (Reliability, Maintainability, Availability, etc.) throughout their life cycle. The designs of these systems have three main sets of activities: managerial, technical and quality. The recent literature suggests that: 1) the growth of the committed project cost is much greater than the cost spent in the initial stages; and also, the cost to eliminate the defects is smaller in the initial stages of project; and 2) the functions, responsibilities, and authorities of Project Management and Systems Engineering are strongly coupled. Thus, based on the recent literature and the INPE´s (National Institute for Space Research) experience, this paper will show a discussion on the interaction between Project Management and Systems Engineering to improve the Dependability of space and automotive projects. To do that, it incorporates the best of the PMI (Project Management Institute) and INCOSE (International Council on Systems Engineering) as part of a more extensive work. This paper also summarizes an analysis of the Dependability aspects of satellite projects. It expects to contribute to reduce their nonconformities and rework, and increase their operational efficiency.</div></div>

He obtained training in biomedical electronics and has been working in medical equipment maintenance and management for nearly 23 years.His responsibilities often mirror those of a hospital executive who oversees clinical engineering-budgets, personnel, long-term equipment planning-but there's no mistaking the differences that come with the uniform.Now nearing his military retirement, Curry recently spoke with BI&T about his years in military

This paper presents a compilation and empirical survey‐based evaluation of the metrics most commonly used by program managers during product development management. This work is part of a bigger project of Massachusetts Institute of Technology (MIT), Project Management Institute (PMI) and International Council on Systems Engineering (INCOSE). Three methodological procedures were applied: systematic literature review, focus‐group discussions, and survey. The survey results indicate the metrics considered to be the most and least useful for managing lean engineering programs, and reveals a shift of interest towards qualitative metrics, especially the ones that address the achievement of stakeholder values, and the absence of useful metrics regarding the lean principles People and Pull.

The evolution of industry through a competitive environment resulted in a need for optimising the manufacturing processes. Many studies focalised on this topic, especially in the case of software engineering processes, which led to the definition of a standard for development processes (SPEM) by the OMG (Object Management Group) and a race to implement it through different languages and meta-models. Even if there is a huge similarity between software engineering and systems engineering, the standard and its different implementations are still insufficient to fulfil the requirements expressed through systems engineering standards such as EIA 632. In this paper a meta-model keeps the fruitful approach of the Software Process Engineering Meta-model (SPEM) combined with some useful concepts from the System Modelling Language (SysML). This model was validated through some predefined criteria, the specification of the EIA 632 standard and a sample process for systems engineering.