Intelligent Content Driving of Engineering Model System in Modeling Platform

2020 ◽  
Author(s):  
László Horváth
Keyword(s):  
Situation Awareness ◽  
Model System ◽  
Software Systems ◽  
Engineering Model ◽  
Academic Organizations ◽  
Autonomous Operation ◽  
Modeling Software ◽  
High Level ◽  
Engineering Modeling ◽  
Component Models

Engineering modeling software systems have been developed during a long integration process from separated partial solutions to current modeling software platforms (MSPs). MSP is expected to provide all necessary model creation and application capabilities during integrated innovation and the life cycle of commercial and industrial products (CIP). Recently, advanced CIP is operated by component systems organized within an increasingly autonomous cyber physical system (CPS). CIP is represented by the engineering model system (EMS). EMS is driven by active contexts between the outside world and EMS, between component models of EMS, and between objects in a component model. EMS reacts to any new contribution using all formerly represented contexts. Consistent structure of contexts gives autonomous operation capability for EMS. Active contexts between the outside world and EMS make EMS sensitive to outside world changes. In the other direction, EMS can generate advice for the outside world using high level and well-organized active knowledge as context. Contributing to research in key issues around EMS and the relevant software technology, this paper introduces results in requirements against MSP capabilities to represent intelligent driving content (IDC) in EMS. A novel organized structure of IDC and continuous engineering (CE) aspects of IDC development are explained and discussed placing the main emphasis on situation awareness. Finally, a new concept is introduced in which purposeful EMS acts as the only media in communication of researchers. Specially configured MSP facilitates participation from industrial, institutional, and academic organizations. The research proceeds at the Laboratory of Intelligent Engineering Systems (IESL) in the organization of the Óbuda University.

CoJACK: A high-level cognitive architecture with demonstrations of moderators, variability, and implications for situation awareness

2012 ◽  
Vol 1 ◽  
pp. 2-13 ◽  
Author(s):  
Frank E. Ritter ◽  
Jennifer L. Bittner ◽  
Sue E. Kase ◽  
Rick Evertsz ◽  
Matteo Pedrotti ◽  
...  
Keyword(s):  
Situation Awareness ◽  
Cognitive Architecture ◽  
High Level

High-level information fusion and situation awareness

2009 ◽  
Vol 10 (1) ◽  
pp. 2-5 ◽  
Author(s):  
Mieczyslaw M. Kokar ◽  
Gee Wah Ng
Keyword(s):  
Information Fusion ◽  
Situation Awareness ◽  
Level Information ◽  
High Level

Dynamically Reconfigurable Architectures

2014 ◽  
pp. 26-43
Author(s):  
Marek Rychly
Keyword(s):  
Ad Hoc ◽  
Reconfigurable Architectures ◽  
Software Systems ◽  
Actual State ◽  
Dynamically Reconfigurable ◽  
Component Models

Dynamic aspects of behavior of software systems in dynamically reconfigurable runtime architectures can result in significant architectural violations during runtime. In such cases, a system's architecture evolves during the runtime according to the actual state of the system's environment, and consequently, runtime reconfigurations may eventually lead to incorrect architecture configurations that were not considered during the system's design phases. These architectural violations are known as architectural erosion or architectural drift, and they contribute to an increasing brittleness of the system, or a lack of its coherence and clarity of its form. This chapter describes and compares possible measures to prevent architectural violations in dynamic service and component models. The aim of this chapter is to evaluate the applicability of those measures in combination with advanced features of reconfigurable runtime architectures such as ad hoc reconfiguration, service or component mobility, composition hierarchy preservation, and architectural aspects.

State of the Art of Software Architecture Design Methods Used in Main Software Development Methodologies

2015 ◽  
pp. 7359-7370
Author(s):  
Reyes Delgado Paola Yuritzy ◽  
Mora Tavarez José Manuel ◽  
Duran-Limon Hector Alejandro ◽  
Rodríguez-Martínez Laura Cecilia ◽  
Mendoza González Ricardo ◽  
...  
Keyword(s):  
Software Development ◽  
Software Architecture ◽  
Design Methods ◽  
Software Systems ◽  
Design Activity ◽  
Negative Effects ◽  
Modern Development ◽  
Core Components ◽  
Software Development Methodologies ◽  
High Level

The design Software Architecture (SA) is an essential activity in the modern development software systems. This SA design activity defines its core components, the interrelationships among them, and a set of essential attributes expected for the final software. While this design is realized in a high level of abstraction, missing this activity or a wrong conduction of it will have negative effects in further software development phases, and lately in the final software. Thus, SA design methods are relevant to be studied and applied. In this article, we review the SA design methods that are (explicitly or implicitly) included in five well-known Software Development Methodologies (SDMs). We report: (1) a brief description of the five SDMs; (2) a substantial description of the SA design methods used in each SDM; and (3) a comparative analysis among them using an evaluation template posited by well-recognized experts in this topic. Our results suggest that SA design methods, while sharing a similar design purpose and some activities, they also present a varied structured and nomenclature.

Architecture-Centered Integrated Verification

2012 ◽  
pp. 201-222
Author(s):  
Yujian Fu ◽  
Zhijang Dong ◽  
Xudong He
Keyword(s):  
Petri Nets ◽  
Software Architecture ◽  
Large Scale ◽  
Future Research ◽  
Software Systems ◽  
Compositional Verification ◽  
Software Product ◽  
Implementation Level ◽  
High Level ◽  
Florida International University

The approach aims at solving the above problems by including the analysis and verification of two different levels of software development process–design level and implementation level-and bridging the gap between software architecture analysis and verification and the software product. In the architecture design level, to make sure the design correctness and attack the large scale of complex systems, the compositional verification is used by dividing and verifying each component individually and synthesizing them based on the driving theory. Then for those properties that cannot be verified on the design level, the design model is translated to implementation and runtime verification technique is adapted to the program. This approach can highly reduce the work on the design verification and avoid the state-explosion problem using model checking. Moreover, this approach can ensure both design and implementation correctness, and can further provide a high confident final software product. This approach is based on Software Architecture Model (SAM) that was proposed by Florida International University in 1999. SAM is a formal specification and built on the pair of component-connector with two formalisms – Petri nets and temporal logic. The ACV approach places strong demands on an organization to articulate those quality attributes of primary importance. It also requires a selection of benchmark combination points with which to verify integrated properties. The purpose of the ACV is not to commend particular architectures, but to provide a method for verification and analysis of large scale software systems in architecture level. The future research works fall in two directions. In the compositional verification of SAM model, it is possible that there is circular waiting of certain data among different component and connectors. This problem was not discussed in the current work. The translation of SAM to implementation is based on the restricted Petri nets due to the undecidable issue of high level Petri nets. In the runtime analysis of implementation, extraction of the execution trace of the program is still needed to get a white box view, and further analysis of execution can provide more information of the product correctness.

Threat Representation Methods for Composite Service Process Models

2013 ◽  
Vol 4 (2) ◽  
pp. 1-18 ◽  
Author(s):  
Per Håkon Meland ◽  
Erlend Andreas Gjære
Keyword(s):  
Business Processes ◽  
Process Models ◽  
Software Systems ◽  
Related Information ◽  
Process Collaboration ◽  
Version 2.0 ◽  
Composite Services ◽  
Technical Specifications ◽  
Business Process Modeling Notation ◽  
High Level

The Business Process Modeling Notation (BPMN) has become a popular standard for expressing high level business processes as well as technical specifications for software systems. However, the specification does not contain native support to express security information, which should not be overlooked in today’s world where every organization is exposed to threats and has assets to protect. Although a substantial amount of work enhancing BPMN 1.x with security related information already exists, the opportunities provided by version 2.0 have not received much attention in the security community so far. This paper gives an overview of security in BPMN and investigates several possibilities of representing threats in BPMN 2.0, in particular for design-time specification and runtime execution of composite services with dynamic behavior. Enriching BPMN with threat information enables a process-centric threat modeling approach that complements risk assessment and attack scenarios. We have included examples showing the use of error events, escalation events and text annotations for process, collaboration, choreography and conversation diagrams.

Meta-Modelling and Graph Transformation for the Definition of Multi-View Visual Languages

2011 ◽  
pp. 74-101 ◽  
Author(s):  
Esther Guerra ◽  
Juan de Lara
Keyword(s):  
Whole Language ◽  
Model Simulation ◽  
Graph Transformation ◽  
Software Systems ◽  
Small Subset ◽  
Consistency Checking ◽  
Visual Languages ◽  
Meta Model ◽  
Definition Of ◽  
High Level

In this chapter, we present our approach for the definition of Multi-View Visual Languages (MVVLs). These are languages made of a set of different diagram types, which are used to specify the different aspects of a system. A prominent example of this kind of languages is UML, which defines a set of diagrams for the description of the static and dynamic elements of software systems. In the multi-view approach, consistency checking is essential to verify that the combination of the various system views yields a consistent description of the system. We use two techniques to define environments for MVVLs: meta-modelling and graph transformation. The former is used to describe the syntax of the whole language. In addition, we define a meta-model for each diagram type of the language (that we call viewpoint) as a restriction of the complete MVVL meta-model. From this high-level description, we can generate a customized environment supporting the definition of multiple system views. Consistency between views is ensured by translating each one of them into a unique repository model which is conformant to the meta-model of the whole language. The translation is performed by automatically generated graph transformation rules. Whenever a change is performed in a view, some rules are triggered to update the repository. These updates may trigger other rules to propagate the changes from the repository to the rest of the views. In our approach, graph transformation techniques are also used for other purposes, such as model simulation, optimization and transformation into other formalisms. In this chapter, we also discuss the integration of these concepts in the AToM3 tool, and show some illustrative examples by generating an environment for a small subset of UML.

Sign in / Sign up

Export Citation Format

Share Document