scholarly journals Goal Modelling for Security Problem Matching and Pattern Enforcement

2017 ◽  
Vol 8 (3) ◽  
pp. 42-57 ◽  
Author(s):  
Yijun Yu ◽  
Haruhiko Kaiya ◽  
Nobukazu Yoshioka ◽  
Zhenjiang Hu ◽  
Hironori Washizaki ◽  
...  

This article describes how earlier detection of security problems and the implementation of solutions would be a cost-effective approach for developing secure software systems. Developing, gathering and sharing similar repeatable programming knowledge and solutions has led to the introduction of Patterns in the 90's. The same concept has been adopted to realise reoccurring security knowledge and hence security patterns. Detecting a security problem using the patterns in requirements models may lead to its early prevention. In this article, the authors have provided an overview of security patterns in the past two decades, followed by a summary of i*/Tropos goal modelling framework. Section 2 outlines model-driven development, meta-models and model transformation, within the context of requirements engineering. They have summarised security access control types, and formally described role-based access control (RBAC) in particular as a pattern that may occur in the stakeholder requirements models. Then the authors used the i* modelling language and some elements from its constructs - model-driven queries and transformations - to describe the pattern enforcement. This is applied to a number of requirements models within the literature, and the pattern-based transformation tool they designed has automated the detection and resolution of this security pattern in several goal-oriented stakeholder requirements. Finally, the article also reflects on a variety of existing applications and future work.

2011 ◽  
Vol 403-408 ◽  
pp. 2477-2480
Author(s):  
Zhen Wu Wang

The normal role-based access control (RBAC) model decouples users and permissions through roles,and different software systems have different implementation syteles.The paper proposes an engine model which can configure the RBAC management systems flexibly.It is a configuration tool to generate different RBAC management systems which meet different users’ requirements. The practice proves that the engine model can improve the efficiency and quality of software development. The role-based access control model decouples users and permissions through roles in order to simplify authorized operations and safety management[1]. Many literatures[2-6] discuss the RBAC model from different aspects. Some literatures[2-3] add new elements to the normal RBAC model,and these models are unidimensional according to the manipulated resources.For example, the NIST RBAC reference model [2] extends and standardize the RBAC96 [1] model reasonably.Some literatures[4-5] introduce time property to RBAC model and they are two-dimensional models according to the manipulated resources.Literature[6] furtherly add visual data muster to RBAC model and proposes a three-dimensional access control model. All of these models only discuss access control model theoretically,and different role-based access control modules in software systems have different instantiation sytles.For example, a RBAC module in one software system can not meet the access control requirements in another system because different RBAC modules have different table fields in order to realize certain requirements. This paper proposes a flexible role-based access control engine which can configure the RBAC module for different systmes according to each customer’s requirement.The engine is a configuration tool and it can realize various RBAC modules which have different table fields in database.The paper is organized as follows.Section I introduces the basic concepts of the NIST RBAC model;Seciton II details the description of RBAC engine model and gives the configuration steps using this engine to generate RBAC instances,and at last section III gives an example and concludes the paper.


Author(s):  
María-Cruz Valiente ◽  
Cristina Vicente-Chicote ◽  
Daniel Rodríguez

Currently, few projects applying a Model-Driven Engineering (MDE) approach start from high-level requirements models defined exclusively in terms of domain knowledge and business logic. Ontology Engineering (OE) aims to formalize and make explicit the knowledge related to a particular domain. In this vein, this paper presents a modeling approach, formalized in ontological terms, for defining high-level requirements models of software systems that provide support for the implementation of Information Technology Service Management Systems (ITSMSs). This approach allows for: (1) formalizing the knowledge associated to the ITSM processes contained in an ITSMS; (2) modeling the semantics of the activities associated to these processes in terms of workflows; (3) automatically generating the high-level requirements models of the workflow-based software systems needed to support (part of) the ITSM processes; and (4) from the latter, obtaining lower-level models (and eventually code) by means of automated model transformations. A real case study describing the use of this proposal to model an Incident Management System is also included to demonstrate the feasibility and the benefits of the proposed approach.


Author(s):  
María-Cruz Valiente ◽  
Cristina Vicente-Chicote ◽  
Daniel Rodríguez

Currently, few projects applying a Model-Driven Engineering (MDE) approach start from high-level requirements models defined exclusively in terms of domain knowledge and business logic. Ontology Engineering (OE) aims to formalize and make explicit the knowledge related to a particular domain. In this vein, this paper presents a modeling approach, formalized in ontological terms, for defining high-level requirements models of software systems that provide support for the implementation of Information Technology Service Management Systems (ITSMSs). This approach allows for: (1) formalizing the knowledge associated to the ITSM processes contained in an ITSMS; (2) modeling the semantics of the activities associated to these processes in terms of workflows; (3) automatically generating the high-level requirements models of the workflow-based software systems needed to support (part of) the ITSM processes; and (4) from the latter, obtaining lower-level models (and eventually code) by means of automated model transformations. A real case study describing the use of this proposal to model an Incident Management System is also included to demonstrate the feasibility and the benefits of the proposed approach.


Automation ◽  
2021 ◽  
Vol 2 (2) ◽  
pp. 48-61
Author(s):  
Bhavyansh Mishra ◽  
Robert Griffin ◽  
Hakki Erhan Sevil

Visual simultaneous localization and mapping (VSLAM) is an essential technique used in areas such as robotics and augmented reality for pose estimation and 3D mapping. Research on VSLAM using both monocular and stereo cameras has grown significantly over the last two decades. There is, therefore, a need for emphasis on a comprehensive review of the evolving architecture of such algorithms in the literature. Although VSLAM algorithm pipelines share similar mathematical backbones, their implementations are individualized and the ad hoc nature of the interfacing between different modules of VSLAM pipelines complicates code reuseability and maintenance. This paper presents a software model for core components of VSLAM implementations and interfaces that govern data flow between them while also attempting to preserve the elements that offer performance improvements over the evolution of VSLAM architectures. The framework presented in this paper employs principles from model-driven engineering (MDE), which are used extensively in the development of large and complicated software systems. The presented VSLAM framework will assist researchers in improving the performance of individual modules of VSLAM while not having to spend time on system integration of those modules into VSLAM pipelines.


Sign in / Sign up

Export Citation Format

Share Document