First Experiment on Modeling Safety LifeCycle Process in Railway Systems

B. Hamid, H. Zhang, Jacob Geisel, David González
{"title":"First Experiment on Modeling Safety LifeCycle Process in Railway Systems","authors":"B. Hamid, H. Zhang, Jacob Geisel, David González","doi":"10.4018/jdtis.2011040102","DOIUrl":null,"url":null,"abstract":"The conception and design of Resource Constrained Embedded Systems (RCES) is an inherently complex endeavor. Non-functional requirements from security and dependability are exacerbate this complexity. Model-Driven Engineering (MDE) is a promising approach for the design of trusted systems, as it bridges the gap between design issues and implementation concerns. The purpose of process models is to document and communicate processes, as well as reuse them. Thus, processes can be better taught and executed. However, most useful metamodels are activity-oriented, and the required concepts of safety lifecycle, such as validation, cannot be easily modeled. In this paper, the authors propose a safety-oriented process metamodel that extends exiting framework to support all safety control requirements. A new safety lifecycle development processes technique has been built to ease its use in a building process of system/ software applications with safety support. As a proof of concept, the feasibility of the approach has been evaluated with an example. The example is an engineering process for building industry control systems with safety requirements for software and hardware resources. A prototype implementation of the approach is provided and applied to the example of industry control systems in the railway domain. DOI: 10.4018/jdtis.2011040102 18 International Journal of Dependable and Trustworthy Information Systems, 2(2), 17-39, April-June 2011 Copyright © 2011, IGI Global. Copying or distributing in print or electronic forms without written permission of IGI Global is prohibited. putational processing power constraints. They can be found in many application sectors such as automotive, aerospace, and home control (Hamid, Desnos, Grepet, & Jouvray, 2010). They are in many types of devices, like sensors, automotive electronic control units, intelligent switches, and home appliances such as washing machines and smart-meters. In addition, they have different form factors (e.g., standalone systems, peripheral subsystems, and main computing systems). Computing resources of RCES, e.g., memory, tasks, and buffers, are generally statically determined. The generation of RCES therefore involves specific software building processes. These processes are often error-prone because they are not fully automated, even if some level of automatic code generation or even model driven engineering support is applied. Furthermore, many RCES also have assurance requirements, ranging from very strong levels involving certification (e.g., DO178 and IEC-61508 for safety-relevant embedded systems development) to lighter levels based on industry practices. The development of these systems by traditional processes is no longer applicable and the need for new methods is necessary to design and provide software for resources constrained embedded systems (RCES) correct by construction. We seek a mechanism which allows a safe, easier and fast RCES development process. To cope with the growing complexity of embedded system design, several development approaches have been proposed. The most popular are those using models as the main artifacts to be constructed and maintained. In these processes, software development consists of model transformations. Recent times have seen a paradigm shift in terms of design through the combination of multiple software engineering paradigms together, namely Model Driven Engineering and Software Product Line Engineering. Such a paradigm shift is changing the way systems are developed nowadays, reducing development time significantly. Embedded systems are a case in which a range of products for assorted domains such as energy, transportation, automotive, and so on are conceived as a family. However, most of the work so far has been focused on functional parts. MDE supports the designer to specify in a separate way non-functional requirements such as security and/or dependability issues at a higher level of abstraction. MDE has the potential to greatly ease daily activities of S&D experts. Previous work has shown the potential of Safety life cycle modeling solutions. They are created by experts, then validated, and finally stored in a repository that makes them available. Development process cycles, including analysis and design phases, are mainly iterative, resulting in different refinement levels of models. Several model-based architectures (e.g., MDA standard) exist and address these issues in specific contexts. Unfortunately, in most of these cases, the links between processed and refined models are still solved in an ad hoc manner, without adequate support. For instance, references between two models are not automated (i.e., checking non-existing and non-referenced elements, managing new elements). The required solutions involve generally more reliable processes, which essentially ensure consistency and traceability of the produced models. We are still waiting for widely-applicable technologies that solve these issues in RCES environment. Modeling software and system process is fundamental in order to improve the quality of the application. The main goal of these processes is to provide organizations with the means to define a conceptual framework. For this reason, several tentatives (i.e., including those developed by the OMG, an organization which normalizes the UML language) have been proposed to model software process. For instance, the SPEM specification is used for describing a concrete software development process or a family of related software development processes. It’s conformed to the OMG’s MOF metametamodel and it defines a UML profile. Meta-process modeling supports the effort of creating flexible process models. The purpose of process models is to document and communicate processes and to enhance the reuse 21 more pages are available in the full version of this document, which may be purchased using the \"Add to Cart\" button on the product's webpage: www.igi-global.com/article/first-experiment-modeling-safetylifecycle/65520?camid=4v1 This title is available in InfoSci-Journals, InfoSci-Journal Disciplines Computer Science, Security, and Information Technology. Recommend this product to your librarian: www.igi-global.com/e-resources/libraryrecommendation/?id=2","PeriodicalId":298071,"journal":{"name":"Int. J. Dependable Trust. Inf. Syst.","volume":"45 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2011-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"1","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Int. J. Dependable Trust. Inf. Syst.","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.4018/jdtis.2011040102","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 1

Abstract

The conception and design of Resource Constrained Embedded Systems (RCES) is an inherently complex endeavor. Non-functional requirements from security and dependability are exacerbate this complexity. Model-Driven Engineering (MDE) is a promising approach for the design of trusted systems, as it bridges the gap between design issues and implementation concerns. The purpose of process models is to document and communicate processes, as well as reuse them. Thus, processes can be better taught and executed. However, most useful metamodels are activity-oriented, and the required concepts of safety lifecycle, such as validation, cannot be easily modeled. In this paper, the authors propose a safety-oriented process metamodel that extends exiting framework to support all safety control requirements. A new safety lifecycle development processes technique has been built to ease its use in a building process of system/ software applications with safety support. As a proof of concept, the feasibility of the approach has been evaluated with an example. The example is an engineering process for building industry control systems with safety requirements for software and hardware resources. A prototype implementation of the approach is provided and applied to the example of industry control systems in the railway domain. DOI: 10.4018/jdtis.2011040102 18 International Journal of Dependable and Trustworthy Information Systems, 2(2), 17-39, April-June 2011 Copyright © 2011, IGI Global. Copying or distributing in print or electronic forms without written permission of IGI Global is prohibited. putational processing power constraints. They can be found in many application sectors such as automotive, aerospace, and home control (Hamid, Desnos, Grepet, & Jouvray, 2010). They are in many types of devices, like sensors, automotive electronic control units, intelligent switches, and home appliances such as washing machines and smart-meters. In addition, they have different form factors (e.g., standalone systems, peripheral subsystems, and main computing systems). Computing resources of RCES, e.g., memory, tasks, and buffers, are generally statically determined. The generation of RCES therefore involves specific software building processes. These processes are often error-prone because they are not fully automated, even if some level of automatic code generation or even model driven engineering support is applied. Furthermore, many RCES also have assurance requirements, ranging from very strong levels involving certification (e.g., DO178 and IEC-61508 for safety-relevant embedded systems development) to lighter levels based on industry practices. The development of these systems by traditional processes is no longer applicable and the need for new methods is necessary to design and provide software for resources constrained embedded systems (RCES) correct by construction. We seek a mechanism which allows a safe, easier and fast RCES development process. To cope with the growing complexity of embedded system design, several development approaches have been proposed. The most popular are those using models as the main artifacts to be constructed and maintained. In these processes, software development consists of model transformations. Recent times have seen a paradigm shift in terms of design through the combination of multiple software engineering paradigms together, namely Model Driven Engineering and Software Product Line Engineering. Such a paradigm shift is changing the way systems are developed nowadays, reducing development time significantly. Embedded systems are a case in which a range of products for assorted domains such as energy, transportation, automotive, and so on are conceived as a family. However, most of the work so far has been focused on functional parts. MDE supports the designer to specify in a separate way non-functional requirements such as security and/or dependability issues at a higher level of abstraction. MDE has the potential to greatly ease daily activities of S&D experts. Previous work has shown the potential of Safety life cycle modeling solutions. They are created by experts, then validated, and finally stored in a repository that makes them available. Development process cycles, including analysis and design phases, are mainly iterative, resulting in different refinement levels of models. Several model-based architectures (e.g., MDA standard) exist and address these issues in specific contexts. Unfortunately, in most of these cases, the links between processed and refined models are still solved in an ad hoc manner, without adequate support. For instance, references between two models are not automated (i.e., checking non-existing and non-referenced elements, managing new elements). The required solutions involve generally more reliable processes, which essentially ensure consistency and traceability of the produced models. We are still waiting for widely-applicable technologies that solve these issues in RCES environment. Modeling software and system process is fundamental in order to improve the quality of the application. The main goal of these processes is to provide organizations with the means to define a conceptual framework. For this reason, several tentatives (i.e., including those developed by the OMG, an organization which normalizes the UML language) have been proposed to model software process. For instance, the SPEM specification is used for describing a concrete software development process or a family of related software development processes. It’s conformed to the OMG’s MOF metametamodel and it defines a UML profile. Meta-process modeling supports the effort of creating flexible process models. The purpose of process models is to document and communicate processes and to enhance the reuse 21 more pages are available in the full version of this document, which may be purchased using the "Add to Cart" button on the product's webpage: www.igi-global.com/article/first-experiment-modeling-safetylifecycle/65520?camid=4v1 This title is available in InfoSci-Journals, InfoSci-Journal Disciplines Computer Science, Security, and Information Technology. Recommend this product to your librarian: www.igi-global.com/e-resources/libraryrecommendation/?id=2
铁路系统安全生命周期过程建模首次试验
资源约束嵌入式系统(RCES)的概念和设计本身就是一项复杂的工作。来自安全性和可靠性的非功能性需求加剧了这种复杂性。模型驱动工程(MDE)是设计可信系统的一种很有前途的方法,因为它在设计问题和实现关注点之间架起了桥梁。过程模型的目的是记录和交流过程,以及重用它们。因此,可以更好地教授和执行流程。然而,大多数有用的元模型都是面向活动的,并且安全生命周期所需的概念(例如验证)不能容易地建模。在本文中,作者提出了一个面向安全的过程元模型,该模型扩展了现有框架以支持所有安全控制需求。建立了一种新的安全生命周期开发过程技术,以简化其在具有安全支持的系统/软件应用程序的构建过程中的使用。作为概念验证,通过实例对该方法的可行性进行了评价。该示例是用于构建对软件和硬件资源有安全要求的工业控制系统的工程过程。给出了该方法的原型实现,并将其应用于铁路领域的工业控制系统实例。DOI: 10.4018 / jdtis。2011040102 18国际可靠与可信信息系统学报,2(2),17- 39,2011年4 - 6月版权所有©2011,IGI Global。未经IGI Global书面许可,禁止以印刷或电子形式复制或分发。计算处理能力约束。它们可以在许多应用领域找到,例如汽车,航空航天和家庭控制(Hamid, Desnos, Grepet, & Jouvray, 2010)。它们存在于许多类型的设备中,如传感器、汽车电子控制单元、智能开关以及洗衣机和智能电表等家用电器。此外,它们具有不同的外形因素(例如,独立系统、外围子系统和主计算系统)。RCES的计算资源,例如内存、任务和缓冲区,通常是静态确定的。因此,RCES的生成涉及特定的软件构建过程。这些过程往往容易出错,因为它们不是完全自动化的,即使应用了某种程度的自动代码生成或甚至模型驱动的工程支持。此外,许多RCES也有保证要求,从涉及认证的非常高的级别(例如,与安全相关的嵌入式系统开发的DO178和IEC-61508)到基于行业实践的较轻级别。这些系统的传统开发方法已经不再适用,需要新的方法来设计和提供资源受限嵌入式系统(RCES)的软件。我们寻求一种机制,使RCES开发过程安全、简单、快速。为了应对日益复杂的嵌入式系统设计,人们提出了几种开发方法。最流行的是使用模型作为构建和维护的主要工件。在这些过程中,软件开发由模型转换组成。最近,通过将多个软件工程范例结合在一起,即模型驱动工程和软件产品线工程,我们看到了设计方面的范式转变。这种模式的转变正在改变当今系统的开发方式,大大缩短了开发时间。嵌入式系统是一种情况,在这种情况下,用于各种领域(如能源、交通、汽车等)的一系列产品被视为一个家族。然而,到目前为止,大部分工作都集中在功能部分。MDE支持设计人员以一种单独的方式在更高的抽象级别上指定非功能需求,例如安全性和/或可靠性问题。MDE有可能极大地简化S&D专家的日常活动。之前的工作已经显示了安全生命周期建模解决方案的潜力。它们由专家创建,然后验证,最后存储在可用的存储库中。开发过程周期,包括分析和设计阶段,主要是迭代的,导致模型的不同细化级别。存在几个基于模型的体系结构(例如,MDA标准),并在特定的上下文中解决这些问题。不幸的是,在大多数情况下,经过处理的模型和精化的模型之间的联系仍然以一种特殊的方式解决,没有足够的支持。例如,两个模型之间的引用不是自动的(即,检查不存在和未引用的元素,管理新元素)。所需的解决方案通常涉及更可靠的过程,这从本质上确保了所生成模型的一致性和可追溯性。 我们仍然在等待广泛应用的技术来解决RCES环境中的这些问题。对软件和系统过程进行建模是提高应用程序质量的基础。这些过程的主要目标是为组织提供定义概念框架的方法。由于这个原因,已经提出了一些尝试(例如,包括OMG开发的那些,OMG是一个规范UML语言的组织)来建模软件过程。例如,SPEM规范用于描述一个具体的软件开发过程或一系列相关的软件开发过程。它符合OMG的MOF元模型,并定义了UML概要文件。元流程建模支持创建灵活的流程模型。过程模型的目的是记录和交流过程,并增强过程的重用。在本文档的完整版本中还有另外21页,可以使用产品网页上的“添加到购物车”按钮购买:www.igi-global.com/article/first-experiment-modeling-safetylifecycle/65520?camid=4v1。本标题可在InfoSci-Journals, InfoSci-Journal discipline Computer Science, Security, and Information Technology中找到。向您的图书管理员推荐此产品:www.igi-global.com/e-resources/libraryrecommendation/?id=2
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约1分钟内获得全文 求助全文
来源期刊
自引率
0.00%
发文量
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
copy
已复制链接
快去分享给好友吧!
我知道了
右上角分享
点击右上角分享
0
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:604180095
Book学术官方微信