Vorgestellt wird die Architektur des Data Centers der TU Chemnitz, die auf den neuen Technologie Data Center Bridging (DCB) und Fibre Channel over Ethernet (FCoE) basiert. Es werden die entsprechenden Standards dargestellt und ein Überblick zur gegenwärtig verfügbaren Technik gegeben. Das Rechenzentrum der TU Chemnitz setzt diese Technologien bereits erfolgreich im Kontext von VMware-Virtualisierung und bei Betrieb I/O-intensiver Systeme ein.

Concept-oriented model of data (COM) has been recently defined syntactically by means of the concept-oriented query language (COQL). In this paper we propose a formal embodiment of this model, called nested partially ordered sets (nested posets), and demonstrate how it is connected with its syntactic counterpart. Nested poset is a novel formal construct that can be viewed either as a nested set with partial order relation established on its elements or as a conventional poset where elements can themselves be posets. An element of a nested poset is defined as a couple consisting of one identity tuple and one entity tuple. We formally define main operations on nested posets and demonstrate their usefulness in solving typical data management and analysis tasks such as logic navigation, constraint propagation, inference and multidimensional analysis.

In 2011, a coalition of member states in the North Atlantic Treaty Organization together with partner nations outside of the alliance cooperated against the Libyan regime led by Colonel Muammar Khadaffi. The primary goals of the operations in Libya were to protect the civil population from attacks by the Libyan regime, maintain the no-flyzone and arms embargo. The operations in Libya proved to be successful and many authors claims that airpower were the main key to the victory.John A. Warden III and Robert A. Pape have been mentioned in discussions about airpower and there have also been a debate regarding which theory that best describes how air power should be used. Some authors who have examined the Libyan war claims that the outcome can be understood with John Wardens theories while other claims that it can be understood from Robert Papes theories.This study aims to examine and try to understand the outcome of the air campaign in Libya 2011. Based on the accomplishment of air power in the Libyan civil war along with the debate between John Warden and Robert Pape the conclusion of this study is that the success in the war can be identified in both theories. John Warden’s theory about strategic airpower together with Robert Pape’s theory about direct support of ground forces seems to be the key factor that ended the war with a successful outcome.

Model Driven Development (MDD) and Model Based Testing (MBT) are gaining inroads individually for their application in embedded software engineering projects. However, their full-edged and integrated usage in real-life embedded software engineering projects (e.g. industrially relevant examples) and executing MBT in resource constrained embedded systems (e.g. 16 bit system/64 KiByte memory) are emerging fields. Addressing the aforementioned gaps, this thesis proposes an integrated model-based approach and test framework for executing the model-based test cases, with minimal overhead, in embedded systems. Given a chosen System Under Test (SUT) and the system design model, a test framework generation algorithm generates the necessary artifacts (i.e., the test framework) for executing the model-based test cases. The main goal of the test framework is to enable test automation and test case execution at the host computer (which executes the test harness), thereby only the test input data is executed at the target. Significant overhead involved in interpreting the test data at the target is eliminated, as the test framework makes use of a target debugger (communication and decoding agent) on the host and a target monitor (software-based runtime monitoring routine) in the embedded system. In the prototype implementation of the proposed approach, corresponding (standardized) languages such as the Unified Modeling Language (UML) and the UML Testing Profile (UTP) are used for the MDD and MBT phases respectively. The applicability of the proposed approach is demonstrated using an experimental evaluation (of the prototype) in real-life examples. The empirical results indicate that the total time spent for executing the test cases in the target (runtime-time complexity), comprises of only the time spent to decode the test input data by the target monitor and execute it in the embedded system. Similarly, the only memory requirement in the target for executing the model-based test cases in the target is that of the software-based target monitor. A quantitative comparison on the percentage change in the memory overhead (runtime-memory complexity) for the existing approach and the proposed approach indicates that the existing approach (e.g. in a MDD/MBT tool-Rhapsody), introduces approximately 150% to 350% increase in memory overhead for executing the test cases. On the other hand, in the proposed approach, the target monitor is independent of the number of test cases to be executed and their complexity. Hence, the percentage change in the memory overhead for the proposed approach shows a declining trend w.r.t the increasing code-size for equivalent application scenarios (approximately 17% to 2%). Thus, the proposed test automation approach provides the essential benefit of executing model- based tests, without downloading the test harness in the target. It is demonstrated that it is feasible to execute the test cases specified at higher abstraction levels (e.g. using UML sequence diagrams) in resource constrained embedded systems and how this may be realized using the proposed approach. Further, as the proposed runtime monitoring mechanism is time and memory-aware, the overhead parameters can be accommodated in the earlier phases of the embedded software development cycle (if necessary) and the target monitor can be included in the final production code. The aforementioned advantages highlight the scalability, applicability, reliability and superiority of the proposed approach over the existing methodologies for executing the model-based test cases in embedded systems.

Une plateforme de conception est une solution totale qui permet à une équipe de conception de développer un système sur puce. Une telle plateforme se compose d'un ensemble de bibliothèques et de circuits réutilisables (IPs), d'outils de CAO et de kits de conception en conformité avec les flots de conception et les méthodologies supportés. Les spécifications de ce type de plateforme offrent un large éventail d'informations, depuis des paramètres de technologie, jusqu'aux informations sur les outils. En outre, les développeurs de bibliothèque/IP ont des difficultés à obtenir les données nécessaires à partir ces spécifications en raison de leur informalité et complexité. Dans cette thèse, nous proposons des méthodologies, des flots et des outils pour formaliser les spécifications d'une plateforme de conception et les traiter. Cette description proposée vise à être utilisée comme une référence pour générer et valider les bibliothèques et les IPs. Nous proposons un langage de spécification basé sur XML (nommé LDSpecX). De plus, nous présentons une méthode basée sur des références pour créer une spécification fiable en LDSpecX et des mots-clés basés sur des tâches pour en extraire les données efficacement. A l'aide des solutions proposées, nous développons une plateforme de spécification. Nous développons une bibliothèque de cellules standard en utilisant cette plateforme de spécification. Nous montrons ainsi que notre approche permet de créer une spécification complète et cohérente avec une réduction considérable du temps. Cette proposition comble également l'écart entre les spécifications et le système automatique existant pour le développement rapide de bibliothèques/IPs. / A design platform (DP) is a total solution to build a System-On-Chip (SOC). DP consists of a set of libraries/IPs, CAD tools and design kits in conformity with the supported design flows and methodologies. The DP specifications provide a wide range of information from technology parameters like Process-Voltage-Temperature (PVT) corners to CAD tools’ information for library/IP development. However, the library/IP developers have difficulties in obtaining the desired data from the existing specifications due to their informality and complexity. In this thesis, we propose methodologies, flows and tools to formalize the DP specifications for their unification and to deal with it. The proposed description is targeting to be used as a reference to generate and validate libraries (standard cells, I/O, memory) as well as complex IPs (PLL, Serdes, etc.). First, we build a suitable data model to represent all required information for library/IP development and then propose a specification language named Library Development Specification based on XML (LDSpecX). Furthermore, we introduce a reference-based method to create a reliable specification in LDSpecX and task-based keywords to efficiently extract data from it. On the basis of the proposed solutions, we develop a specification platform. Experimentally, we develop a standard cell library from the specification creation to library validation by using the specification platform. We show that our approach enables to create a complete and consistent specification with a considerable reduction in time. It also bridges the gap between the specification and current automatic system for rapid library/IP development.

No description available.

The networking of control devices is well advanced in a modern automobile. To ensure secure communications with each other and to prevent mistakes due to communication error, protocol tests are performed at the physical and data link layer level. In a modern car the diagnosis of the electronic devices (e.g. reading/deleting fault memory entries) is done with a standardized communication protocol (UDS - Unified Diagnostic Services). Modern control units have this diagnostic capabilities to detect this communication error among others. This data is provided for a guided troubleshooting the vehicle via a defined interface. In this communication test detection mechanisms are specifically stimulated and read afterwards. In order to read or delete these entries, a diagnosis query is performed on the basis of the diagnostic protocol UDS. The diagnostic requests are currently performed with a diagnostic service of bus analysis software Vector CANoe. This service requests can be performed directly on CAN but for the diagnosis of other bus systems a software gateway is used. The maintenance required and the error rate of the software gateways is very high and should be replaced in the future. Furthermore, additional bus systems can be integrated only with great effort. Therfore the main aim of the master thesis was to develop a concept for univesal UDS API and afterwards implementation of that concept using CAPL programming for modular use in test environments for vehicle communication testing.

Although originally designed as an extension for the Unifi ed Modeling Language (UML), today, the Object Constraint Language (OCL) has been broadly adopted in the context of both UML and other modeling and domain-specifi c languages. However, appropriate tooling, supporting modelers and software developers on using OCL is still scarce and lacks important features such as debugging support. As OCL constraints are likely to become rather complex for real world examples, it is hard to comprehend the in uence of single OCL expressions and subexpressions on the result of a completely evaluated OCL constraint in the context of speci fic constrained objects. Therefore, debugging is of topmost importance for both constraint comprehension and maintenance. Thus, the major task of this work is to develop a graphical debugger integrated into Dresden OCL and the Eclipse Integrated Development Environment (IDE) to fill this gap.:1 Introduction 2 The Dresden OCL Toolkit 2.1 The Dresden OCL Toolkit 2.2 The Dresden OCL2 Toolkit 2.3 Dresden OCL2 for Eclipse 2.4 Dresden OCL 3 The Eclipse Debugging Framework 3.1 The Debug Model 3.2 Interacting with the Debug Model 3.3 The Execution Control Commands 4 Requirements Analysis and Related Work 4.1 Requirements Analysis 4.2 Related Work 5 Design and Structure 5.1 Architecture 5.1.1 Package Structure 5.1.2 Class Structure 5.2 The OCL Debug Model 5.3 The Mapping from ASM to AST 5.4 The OCL Debugger 5.4.1 The Implementation of the Debugger 5.4.2 Testing the Debugger 6 Graphical User Interface Implementation 6.1 The Dresden OCL Debug Perspective 6.2 Using the Debugger 6.2.1 Selecting a Model 6.2.2 Selecting a Model Instance 6.2.3 Debugging 6.3 Summary 7 Evaluation and Future Work 33 7.1 Evaluation 7.2 Future Work 8 Summary and Conclusion

With the advent of the fourth industrial revolution, information technology and manufacturing systems are merging to form what is now known as Smart Manufacturing. However, with this newer technology being integrated with newer pieces of machining equipment, companies with legacy equipment occasionally are in a bind since these machines were not designed or built with the fundamental components of smart manufacturing systems: unified connectivity, real-time monitoring, and issue identification. The purpose of this research is to provide a solution for converting manual machining equipment into smart systems with these fundamental components of smart manufacturing. The pieces of equipment that were the subjects of this experimentation were an HJ-1100 Kingston lathe and four ACER Vertical Turret Milling machines. None of these machines had any of these capabilities at the inception of this project.These machines were successfully converted into smart systems with varying degrees of reliability between the lathe and the four mills in the case of real-time monitoring and issue identification. The setups and configurations to achieve these three smart components are described and provided.

The world of systems engineering methods is changing as rigorous ‘off-the-shelf’ systems engineering methods become more popular. One example of such a systems engineering method is Rational Unified Process. In order to cover all phases in a software development process, and a wide range of project-types, such methods need to be of an impressive size. Thus, the need for configuring such methods in a structured way is increasing accordingly. In this thesis, method configuration is considered as a particular kind of method engineering that focuses on tailoring a standard systems engineering method. We propose a meta-method for method configuration based on two fundamental values: standard systems engineering method’s rationality and reuse. A conceptual framework is designed, introducing the concepts Configuration Package and Configuration Template. A Configuration Package is a pre-made ideal method configuration suitable for a delimited characteristic of a (type of) software artifact, or a (type of) software development project, or a combination thereof. Configuration Templates with different characteristics are built combining a selection of Configuration Packages and used as a base for a situational method. The aim of the proposed meta-method is to ease the burden of configuring the standard systems engineering method in order to reach an appropriate situational method.