Model-driven software systems engineering in robotics: Covering the complete life-cycle of a robot

2015 ◽  
Vol 57 (2) ◽  
Author(s):  
Christian Schlegel ◽  
Alex Lotz ◽  
Matthias Lutz ◽  
Dennis Stampfer ◽  
Juan F. Inglés-Romero ◽  
...  
Keyword(s):  
Systems Engineering ◽  
System Integration ◽  
Software Systems ◽  
Model Driven ◽  
Domain Specific ◽  
Complete Life Cycle ◽  
Systems Software ◽  
Model Driven Software Development ◽  
Component Based Software Engineering ◽  
Software Systems Engineering

AbstractRobotic systems are complex, software intensive and heterogeneous composite systems. Software systems engineering and system integration is still a major challenge in robotics. We describe how component based software engineering (CBSE), model-driven software development (MDSD) and domain-specific languages (DSLs) for variability management complement each other in addressing the robotics software challenge. We outline how these approaches pave the way towards a software business ecosystem in robotics. We put a focus onto challenges still being considered as open and worth being addressed next.

scholarly journals A Process Model for Component-Based Model-Driven Software Development

Information ◽  
2020 ◽  
Vol 11 (6) ◽  
pp. 302
Author(s):  
Afrah Umran Alrubaee ◽  
Deniz Cetinkaya ◽  
Gernot Liebchen ◽  
Huseyin Dogan
Keyword(s):  
Software Development ◽  
Process Model ◽  
Development Process ◽  
Ad Hoc ◽  
Learning System ◽  
Software Systems ◽  
Software Development Process ◽  
Model Driven ◽  
Model Driven Software Development ◽  
Component Based Software Engineering

Developing high quality, reliable and on time software systems is challenging due to the increasing size and complexity of these systems. Traditional software development approaches are not suitable for dealing with such challenges, so several approaches have been introduced to increase the productivity and reusability during the software development process. Two of these approaches are Component-Based Software Engineering (CBSE) and Model-Driven Software Development (MDD) which focus on reusing pre-developed code and using models throughout the development process respectively. There are many research studies that show the benefits of using software components and model-driven approaches. However, in many cases the development process is either ad-hoc or not well-defined. This paper proposes a new software development process model that merges CBSE and MDD principles to facilitate software development. The model is successfully tested by applying it to the development of an e-learning system as an exemplar case study.

scholarly journals Modelling Software Architecture for Visual Simultaneous Localization and Mapping

Automation ◽  
2021 ◽  
Vol 2 (2) ◽  
pp. 48-61
Author(s):  
Bhavyansh Mishra ◽  
Robert Griffin ◽  
Hakki Erhan Sevil
Keyword(s):  
System Integration ◽  
Ad Hoc ◽  
Simultaneous Localization And Mapping ◽  
Software Systems ◽  
Model Driven ◽  
Performance Improvements ◽  
Software Model ◽  
Localization And Mapping ◽  
Stereo Cameras ◽  
Core Components

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.

Tightening the Linkage of CSE and Software Systems Engineering

2004 ◽  
Vol 48 (3) ◽  
pp. 698-702 ◽  
Author(s):  
Robert G. Eggleston ◽  
Catherine Burns ◽  
James Gualtieri ◽  
Gavan Lintern ◽  
Sterling Wiggins ◽  
...  
Keyword(s):  
Systems Engineering ◽  
Software Systems ◽  
Software Systems Engineering

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.

Sign in / Sign up

Export Citation Format

Share Document