Model-Based System Design Using SysML

Enterprise information system architecture design is the process of defining and optimizing its structure (both software and hardware) to effectively support provided functionality. System architects are combining software and hardware vital components, usually defined by other stakeholders, and are dealing with both functional and non functional requirements. Alternative architecture solution evaluation is usually a part of the design process, aiming to determine if the defined requirements are satisfied. A model-based approach, constituted of discrete views, each of which facilitates a discrete design task, has been proposed, while Systems Modeling Language (SysML) has been adopted for the model representation. In this paper, emphasis is given on the Evaluation View, aiming at the exploration of alternative software and hardware combination scenarios proposed in other views. The view facilitates the management of simulation experiments and results and the verification of predefined requirements. A case study, where the proposed model-based design approach has been applied is also discussed.

2014

A Practical Guide to SysML, Third Edition, fully updated for SysML version 1.4, provides a comprehensive and practical guide for modeling systems with SysML. With their unique perspective as leading contributors to the language, Friedenthal, Moore, and Steiner provide a full description of the language along with a quick reference guide and practical examples to help you use SysML. The book begins with guidance on the most commonly used features to help you get started quickly. Part 1 explains the benefits of a model-based approach, providing an overview of the language and how to apply SysML to model systems. Part 2 includes a comprehensive description of SysML that provides a detailed understanding that can serve as a foundation for modeling with SysML, and as a reference for practitioners. Part 3 includes methods for applying model-based systems engineering using SysML to specify and design systems, and how these methods can help manage complexity. Part 4 deals with topics relate...

2010

In this paper, the Systems Modelling Language (SysML) is introduced as a technique for the design of a product-service system (PSS). In examples of the requirements diagram in SysML, this paper shows that: (1) a PSS can be analysed by the SysML technique, and (2) the SysML can model the requirements of a PSS in orientations according to product, use or result. Recommendations based on the example will then be used to suggest improvements in the design of a PSS.

Kybernetes

Innovations in Systems and Software Engineering, 2010

This article describes a work-in-progress in the framework of a research project aiming at combining requirements engineering methods with formal methods. The main idea is to extend the SysML language with concepts of existing requirements engineering methods. In this article we present extensions to SysML with concepts from the goal model of the KAOS method and we give rules to derive a formal B specification from this goal model. The approach is then illustrated on a case study.

The Journal of Object Technology, 2007

In this paper we present an overview of the capabilities of the Systems Modeling Language (SysML.) SysML is a standard from the Object Management Group. It is geared toward incrementally refinable description of conceptual design and product architecture. Elements in the design represent abstractions of artifacts in the various engineering disciplines involved in the development of the system. The design represents how these artifacts collaborate to provide the product functionalities. This paper explores all the diagrams available in SysML through the real-life example of an embedded system.

2006 10th IEEE International Enterprise Distributed Object Computing Conference (EDOC'06), 2006

System engineering is the process of defining the desired architecture of a system and exploring performance requirements, ensuring that all system components are identified and properly allocated and system resources can provide the desired performance. A consistent framework for enterprise information engineering, compatible to Zachman framework is proposed. It consists of a metamodel describing different system views and the relations between them, a corresponding methodology of discrete stages, performed by the system designer or software tools, and a UML 2.0 profile for view representation.

IBM Systems Journal, 2000

The advent of integrated, shared-data systems has made it increasingly necessary to address the application development process from the architectural and manufacturing perspective rather than from a build-asyou-go job shop viewpoint. Although the Business Systems Planning (BSP) methodology provides an enterprise-wide strategic Information Systems plan, it is still at an abstraction level that leaves the traditional gap between "requirements" and implementations untouched. The Information System Model and Architecture Generator (ISMOD) tool complements and enhances BSP by mechanizing the planning process, thus providing a facility to narrow this gap by allowing orderly and consistent top-to-bottom architectural decomposition of the enterprise environment. It is an enterprise planning vehicle and not an implementation system, but it is the first critical component to support an integrated systems architecture effort. It automates and, to a large extent, formalizes a laborious require ments documentation process preceding code development, and it does this "top to bottom," from a global, enterprise-wide, information requirements viewpoint. This paper discusses the overall architectural concepts of integrated data systems development, the place of ISMOD within it, and the specific facilities, techniques, and information provided by the system.

INCOSE International Symposium, 2011

Requirements are attributed as a common cause of failure in system development. Not only are text requirements ambiguous, the domain conditions under which they are to be satisfied are vague. Until operating conditions and requirements are formally captured, they will continue to be vague with ill‐defined verification criteria. SysML used in a Model‐Based Systems Engineering (MBSE) development process can enable mitigation of this primary source of error. By representing the system under design and its operating environment as a composite SysML model with parametric diagrams, requirements can be formalized in a precise manner. Formalization of requirements and constraints with parametric diagrams enables them to be verified and flowed down during the development process. An example will be used to illustrate how parametric diagrams can be used to develop requirements and constraints.