2.3.1 SysML – an Assessment

Herzog, Erik D.; Pandikow, Asmus

doi:10.1002/j.2334-5837.2005.tb00670.x

Cited by 12 publications

(7 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The capability to model requirements objects in SysML is useful, but the format for requirements modeling does not scale up, as reported in Herzog and Pandikow [2005]. For full acceptance, SysML tools must provide flexible navigation, editing, searching, and reporting.…”

Section: Support For Large-scale Requirements Analysis and Managementmentioning

confidence: 99%

Experience from introducing Unified Modeling Language/Systems Modeling Language at Saab Aerosystems

Andersson¹,

Herzog²,

Johansson³

et al. 2009

Systems Engineering

Self Cite

View full text Add to dashboard Cite

A Unified Modeling Language/Systems Modeling Language (UML/SysML) subset was the modeling notation selected for an aerospace systems engineering project at Saab Aerosystems. In this paper, the rationale for selecting UML/SysML is given, along with a description of the situation at the project planning stage regarding business conditions, method and tools support. The usage of use case, sequence, and activity diagrams are described as well as definition of functional chains with SysML. Furthermore, the connections to system implementation activities including code generation and simulation are discussed. The advantages and disadvantages of using UML/SysML from experience in an industrial context are reported. It is also described how UML/SysML is related to industrial research projects in the Model Based Systems Engineering (MBSE) methods and tools area. Introducing UML/SysML with a methodology and a supporting toolset in an operative organization require a clear strategy, including planning, just-in-time training, and mentor support. Finally, industrial needs for further development of SysML are discussed.

show abstract

Section: Support For Large-scale Requirements Analysis and Managementmentioning

confidence: 99%

Experience from introducing Unified Modeling Language/Systems Modeling Language at Saab Aerosystems

Andersson¹,

Herzog²,

Johansson³

et al. 2009

Systems Engineering

Self Cite

View full text Add to dashboard Cite

show abstract

“…AP-233 uses both EXPRESS and UML for representing the data structures [18]. AP-233 overlaps, in some of its functionalities, with SysUML [19]…”

Section: Integration Of Applicationsmentioning

confidence: 99%

An ontology-based approach to knowledge representation for Computer-Aided Control System Design

Benavides

García-Rodríguez

Alaiz

et al. 2018

Data & Knowledge Engineering

View full text Add to dashboard Cite

Different approaches have been used in order to represent and build control engineering concepts for the computer. Software applications for these fields are becoming more and more demanding each day, and new representation schemas are continuously being developed. This paper describes a study of the use of knowledge models represented in ontologies for building Computer Aided Control Systems Design (CACSD) tools. The use of this approach allows the construction of formal conceptual structures that can be stated independently of any software application and be used in many different ones. In order to show the advantages of this approach, an ontology and an application have been built for the domain of design of lead/lag controllers with the root locus method, presenting the results and benefits found.

show abstract

“…Unlike other metamodels, SysML allows designers to model text-based requirements, which can be integrated with other development artefacts. Nevertheless, it is questioned if the set of inter-requirements relationships provided is enough (Herzog and Pandikow, 2005).…”

Section: Related Workmentioning

confidence: 99%

A MODEL-DRIVEN ENGINEERING APPROACH TO REQUIREMENTS ENGINEERING - How These Disciplines May Benefit Each Other

Moros¹,

Vicente-Chicote²,

Toval³

2007

Proceedings of the Second International Conference on Software and Data Technologies

View full text Add to dashboard Cite

The integration of Model Driven Engineering (MDE) principles into Requirements Engineering (RE) could be beneficial to both MDE approaches and RE. On the one hand, the definition of a requirements metamodel would allow requirements engineers to integrate all RE concepts in the same model and to know which elements are part of the RE process and how they are related. Besides, this requirement metamodel could be used as a common conceptual model for requirements management tools supporting the RE process. On the other hand, this requirements metamodel could be related to other metamodels describing analysis and design artefacts. This would align requirements to models and, as a consequence, requirements could be more easily integrated into the current MDE approach. To achieve this, the traditional RE process, focused on a document-based requirements specification, should be changed into a requirements modelling process. Thus, in this paper we propose a requirements modelling language (metamodel) aimed at easing the integration of requirements into a MDE approach. This metamodel, called REMM, is the basis of a requirements graphical modelling tool also implemented as part of this work. This tool allows requirements engineers to depict all the elements involved in the RE process and to trace relationships between them.

show abstract

2.3.1 SysML – an Assessment

Cited by 12 publications

References 15 publications

Experience from introducing Unified Modeling Language/Systems Modeling Language at Saab Aerosystems

Experience from introducing Unified Modeling Language/Systems Modeling Language at Saab Aerosystems

An ontology-based approach to knowledge representation for Computer-Aided Control System Design

A MODEL-DRIVEN ENGINEERING APPROACH TO REQUIREMENTS ENGINEERING - How These Disciplines May Benefit Each Other

Contact Info

Product

Resources

About