Integrated Model-driven Development Environments for Equation-based Object-oriented Languages




НазваниеIntegrated Model-driven Development Environments for Equation-based Object-oriented Languages
страница9/55
Дата04.10.2012
Размер0.98 Mb.
ТипДокументы
1   ...   5   6   7   8   9   10   11   12   ...   55

2.7System Modeling Language (SysML)


The Unified Modeling Language (UML) has been created to assist software development processes by providing means to capture software system structure and behavior. This eventually evolved into the main standard for Model Driven Development.

The System Modeling Language (SysML) (OMG [114]) is a graphical modeling language for systems engineering applications. SysML was developed and submitted by systems engineering experts, and adopted by the OMG in 2006. SysML is built on top of UML2.0 and tailored to the needs of system engineers by supporting specification, analysis, design, verification and validation of a broad range of systems and system-of-systems.

The main goal behind SysML is to unify and replace different document-centric approaches in the system engineering field with a single systems modeling language. A single model-centric approach improves communication, assists to manage complex system design and allows its early validation and verification.



Figure 2 14. SysML diagram taxonomy.

The taxonomy of SysML diagrams is presented in Figure 2 -14. The following major extensions compared to UML are made in SysML:

  • Requirements diagrams support requirements presentation in tabular or in graphical notation, allows composition of requirements and supports traceability, verification and “fulfillment of requirements”. This is a new type of a diagram added to capture system requirements.

  • Block diagrams extend the Composite Structure diagram of UML2.0. The purpose of this diagram is to capture system components, their parts and connections between parts. Connections are handled by means of connecting ports which may contain data, material, or energy flows.

  • Parametric diagrams help perform engineering analysis such as performance analysis. Parametric diagrams contain constraint elements, which define mathematical equations, linked to properties of model elements.

  • Activity diagrams show system behavior as data and control flows. Activity diagrams are similar to Extended Functional Flow Block Diagrams (EFFBDs), which are already widely used by system engineers. Activity decomposition is supported by SysML.

  • Allocations are used to define mappings between model elements: For example, a certain Activity may be allocated to a Block, which implies that activity will be performed by the block.

For a full description of SysML see (SysML, 2006) (OMG [114]).



Figure 2 15. SysML block definitions.

2.7.1SysML Block Definitions


SysML block definitions are shown in Figure 2 -15. A SysML block can include properties to specify block parts, values, and references to other blocks. A separate compartment is dedicated for each of these features. To describe the behavior of a block the “Operations” compartment is reused from UML and it lists operations that describe certain behavior. SysML defines a special form of compartment for constraint definitions owned by a block. The use of the “Constraint” compartment is optional. A “Namespace” compartment may appear if nested block definitions exist for a block. A “Structure” compartment may appear to show internal parts and connections between parts within a block definition.

SysML defines two types of ports: standard ports and flow ports. Standard ports, which are reused from UML, are service-oriented ports required or provided by a block. Flow ports specify interaction points through which items may flow between blocks, and between blocks and environment. A flow port definition may include single item specification or complex flow specification through the FlowSpecification interface; flow ports define what “can” flow between the block and its environment. Flow direction can be specified for a flow port in SysML. SysML also defines a notion of Item flows that specify “what” does flow in a particular usage context.
1   ...   5   6   7   8   9   10   11   12   ...   55

Похожие:

Integrated Model-driven Development Environments for Equation-based Object-oriented Languages iconThe Domain Analysis Integrated in an Object Oriented Development Methodology

Integrated Model-driven Development Environments for Equation-based Object-oriented Languages iconHypergraph-based Object-oriented Model for gis application

Integrated Model-driven Development Environments for Equation-based Object-oriented Languages iconObject-Oriented Object-Oriented Languages

Integrated Model-driven Development Environments for Equation-based Object-oriented Languages iconApplying uml and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition)

Integrated Model-driven Development Environments for Equation-based Object-oriented Languages iconModel Development of a Total Integrated Maintenance System

Integrated Model-driven Development Environments for Equation-based Object-oriented Languages iconAn integrated framework for model-based flow assurance in deep-water oil and gas production

Integrated Model-driven Development Environments for Equation-based Object-oriented Languages iconThis paper introduces the basic concepts of Agile Database Techniques, and effective ways to go about the Data-Oriented aspects of Object Oriented software

Integrated Model-driven Development Environments for Equation-based Object-oriented Languages iconObject-Oriented Metrics: an Annotated Bibliography

Integrated Model-driven Development Environments for Equation-based Object-oriented Languages iconAn Introduction and Brief Examination of Object-Oriented Data Modeling

Integrated Model-driven Development Environments for Equation-based Object-oriented Languages iconAn Object-Oriented Support Tool for the Design of Casting Procedures

Разместите кнопку на своём сайте:
Библиотека


База данных защищена авторским правом ©lib.znate.ru 2014
обратиться к администрации
Библиотека
Главная страница