First Experiment on Modeling Safety LifeCycle Process in Railway Systems

2011 ◽  
Vol 2 (2) ◽  
pp. 17-39 ◽  
Author(s):  
Brahim Hamid ◽  
Yulin (Huaxi) Zhang ◽  
Jacob Geisel ◽  
David Gonzalez
Keyword(s):  
Control Systems ◽  
Process Models ◽  
Functional Requirements ◽  
Safety Control ◽  
Safety Requirements ◽  
Model Driven ◽  
Railway Systems ◽  
Software Applications ◽  
Building Process ◽  
Development Processes

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.

Tool Based Integration of Requirements Modeling and Validation into Business Process Modeling

2014 ◽  
pp. 285-309
Author(s):  
Sven Feja ◽  
Sören Witt ◽  
Andreas Speck
Keyword(s):  
Business Process ◽  
Process Modeling ◽  
Process Models ◽  
Software Systems ◽  
Functional Requirements ◽  
Model Driven ◽  
Level Of Abstraction ◽  
Textual Representations ◽  
Model Driven Software Development ◽  
The One

Business process models (BPM) are widely used for specification of software systems, as the basis for model driven software development. Hence, it is crucial to ensure that these BPMs fulfill the requirements they have to comply with. These requirements may originate from various domains. Many may be considered non-functional requirements. They are affecting privacy, security, as well as compliance or economic aspects. In order to avoid error-prone manual checking, automated checking techniques should be applied wherever possible. This requires expressing requirements in a formal manner. The common textual representations for such formal requirements are not well accepted in the modeling domain, since they are settled on a lower level of abstraction, compared to BPMs. In this chapter, the authors present the Business Application Modeler (BAM), which integrates formal requirement specification and automated checking with process modeling. On the one hand BAM supports different notations for process modeling. On the other hand a graphical notation, called G-CTL, for the formal specification of requirements is provided. G-CTL is based on temporal logic, and statements are expressed on the level of abstraction of the graphical process models. Furthermore BAM provides the ability to define selective views on process models. This allows complex domain specific annotations of processes as well as the assignment of responsibilities regarding functional domains. Moreover, BAM integrates into common requirements engineering processes.

Tool Based Integration of Requirements Modeling and Validation into Business Process Modeling

2012 ◽  
pp. 512-536
Author(s):  
Sven Feja ◽  
Sören Witt ◽  
Andreas Speck
Keyword(s):  
Business Process ◽  
Process Modeling ◽  
Process Models ◽  
Software Systems ◽  
Functional Requirements ◽  
Model Driven ◽  
Level Of Abstraction ◽  
Textual Representations ◽  
Model Driven Software Development ◽  
The One

Business process models (BPM) are widely used for specification of software systems, as the basis for model driven software development. Hence, it is crucial to ensure that these BPMs fulfill the requirements they have to comply with. These requirements may originate from various domains. Many may be considered non-functional requirements. They are affecting privacy, security, as well as compliance or economic aspects. In order to avoid error-prone manual checking, automated checking techniques should be applied wherever possible. This requires expressing requirements in a formal manner. The common textual representations for such formal requirements are not well accepted in the modeling domain, since they are settled on a lower level of abstraction, compared to BPMs. In this chapter, the authors present the Business Application Modeler (BAM), which integrates formal requirement specification and automated checking with process modeling. On the one hand BAM supports different notations for process modeling. On the other hand a graphical notation, called G-CTL, for the formal specification of requirements is provided. G-CTL is based on temporal logic, and statements are expressed on the level of abstraction of the graphical process models. Furthermore BAM provides the ability to define selective views on process models. This allows complex domain specific annotations of processes as well as the assignment of responsibilities regarding functional domains. Moreover, BAM integrates into common requirements engineering processes.

Model-Driven Approach for End-to-End SOA Security Configurations

2011 ◽  
pp. 268-298 ◽  
Author(s):  
Fumiko Satoh ◽  
Yuichi Nakamura ◽  
Nirmal K. Mukhi ◽  
Michiaki Tatsubori ◽  
Kouichi Ono
Keyword(s):  
Security Requirements ◽  
Model Transformations ◽  
Functional Requirements ◽  
Application Development ◽  
Model Driven ◽  
Cross Domain ◽  
Development Processes ◽  
End To End ◽  
Soa Security ◽  
Security Configuration

The configuration of non-functional requirements, such as security, has become important for SOA applications, but the configuration process has not been discussed comprehensively. In current development processes, the security requirements are not considered in upstream phases and a developer at a downstream phase is responsible for writing the security configuration. However, configuring security requirements properly is quite difficult for developers because the SOA security is cross-domain and all required information is not available in the downstream phase. To resolve this problem, this chapter clarifies how to configure security in the SOA application development process and defines the developer’s roles in each phase. Additionally, it proposes a supporting technology to generate security configurations: Model-Driven Security. The authors propose a methodology for end-to-end security configuration for SOA applications and tools for generating detailed security configurations from the requirements specified in upstream phases model transformations, making it possible to configure security properly without increasing developers’ workloads.

Technology of Information Safety Control in Automated Control Systems

2005 ◽  
Vol 63 (4) ◽  
pp. 295-304
Author(s):  
Ya. E. Lvovich ◽  
A. S. Dubrovin ◽  
E. A. Rogozin ◽  
V. I. Sumin
Keyword(s):  
Control Systems ◽  
Automated Control ◽  
Safety Control ◽  
Information Safety

Use of Business Models within Model Driven Architecture

2009 ◽  
Vol 38 (38) ◽  
pp. 119-130
Author(s):  
Erika Asnina
Keyword(s):  
Business Models ◽  
Business Processes ◽  
Use Cases ◽  
Separation Of Concerns ◽  
Model Driven Architecture ◽  
Model Driven ◽  
Development Processes ◽  
Business Requirements ◽  
Complex Computer ◽  
Independent Model

Use of Business Models within Model Driven Architecture Model Driven Architecture is a framework dedicated for development of large and complex computer systems. It states and implements the principle of architectural separation of concerns. This means that a system can be modeled from three different but related to each other viewpoints. The viewpoint discussed in this paper is a Computation Independent one. MDA specification states that a model that shows a system from this viewpoint is a business model. Taking into account transformations foreseen by MDA, it should be useful for automation of software development processes. This paper discusses an essence of the Computation Independent Model (CIM) and the place of business models in the computation independent modeling. This paper considers four types of business models, namely, SBVR, BPMN, use cases and Topological Functioning Model (TFM). Business persons use SBVR to define business vocabularies and business rules of the existing and planned domains, BPMN to define business processes of both existing and planned domains, and use cases to define business requirements to the planned domain. The TFM is used to define functionality of both existing and planned domains. This paper discusses their capabilities to be used as complete CIMs with formally defined conformity between planned and existing domains.

scholarly journals Recommender systems in model-driven engineering

2021 ◽  
Author(s):  
Lissette Almonte ◽  
Esther Guerra ◽  
Iván Cantador ◽  
Juan de Lara
Keyword(s):  
Recommender Systems ◽  
Information Filtering ◽  
Research Work ◽  
Model Driven Engineering ◽  
Video Broadcasting ◽  
Model Driven ◽  
Challenges And Opportunities ◽  
Mapping Review ◽  
Development Processes ◽  
Systematic Mapping Review

AbstractRecommender systems are information filtering systems used in many online applications like music and video broadcasting and e-commerce platforms. They are also increasingly being applied to facilitate software engineering activities. Following this trend, we are witnessing a growing research interest on recommendation approaches that assist with modelling tasks and model-based development processes. In this paper, we report on a systematic mapping review (based on the analysis of 66 papers) that classifies the existing research work on recommender systems for model-driven engineering (MDE). This study aims to serve as a guide for tool builders and researchers in understanding the MDE tasks that might be subject to recommendations, the applicable recommendation techniques and evaluation methods, and the open challenges and opportunities in this field of research.

scholarly journals Semantic Clustering of Functional Requirements Using Agglomerative Hierarchical Clustering

Information ◽  
2018 ◽  
Vol 9 (9) ◽  
pp. 222 ◽  
Author(s):  
Hamzeh Eyal Salman ◽  
Mustafa Hammad ◽  
Abdelhak-Djamel Seriai ◽  
Ahed Al-Sbou
Keyword(s):  
Empirical Evaluation ◽  
Modern Society ◽  
Development Project ◽  
Functional Requirements ◽  
Software Projects ◽  
Daily Work ◽  
Software Development Project ◽  
Software Applications ◽  
Functional Quality ◽  
Functional Software

Software applications have become a fundamental part in the daily work of modern society as they meet different needs of users in different domains. Such needs are known as software requirements (SRs) which are separated into functional (software services) and non-functional (quality attributes). The first step of every software development project is SR elicitation. This step is a challenge task for developers as they need to understand and analyze SRs manually. For example, the collected functional SRs need to be categorized into different clusters to break-down the project into a set of sub-projects with related SRs and devote each sub-project to a separate development team. However, functional SRs clustering has never been considered in the literature. Therefore, in this paper, we propose an approach to automatically cluster functional requirements based on semantic measure. An empirical evaluation is conducted using four open-access software projects to evaluate our proposal. The experimental results demonstrate that the proposed approach identifies semantic clusters according to well-known used measures in the subject.

Sign in / Sign up

Export Citation Format

Share Document