ONTOLOGY-ENABLED TRACEABILITY MODELS FOR ENGINEERING SYSTEMS DESIGN AND MANAGEMENT

This thesis describes new models and a system for satisfying requirements, and an architectural framework for linking discipline-specific dependencies through inter- action relationships at the ontology (or meta-model) level. In a departure from state-of-the-art traceability mechanisms, we ask the question: What design concept (or family of design concepts) should be applied to satisfy this requirement? Solu- tions to this question establish links between requirements and design concepts. The implementation of these concepts leads to the design itself. These ideas, and support for design-rule checking are prototyped through a series of progressively complicated applications, culminating in a case study for rail transit systems management

Software Product Line

The Software Product Line (SPL) is an emerging methodology for developing software products. Currently, there are two hot issues in the SPL: modelling and the analysis of the SPL. Variability modelling techniques have been developed to assist engineers in dealing with the complications of variability management. The principal goal of modelling variability techniques is to configure a successful software product by managing variability in domain-engineering. In other words, a good method for modelling variability is a prerequisite for a successful SPL. On the other hand, analysis of the SPL aids the extraction of useful information from the SPL and provides a control and planning strategy mechanism for engineers or experts. In addition, the analysis of the SPL provides a clear view for users. Moreover, it ensures the accuracy of the SPL. This book presents new techniques for modelling and new methods for SPL analysis

A Systems Architectural Model for Man-Packable/Operable Intelligence, Surveillance, and Reconnaissance Mini/Micro Aerial Vehicles

With the increase in both technology push and operational pull of mini/micro aerial vehicles (MAVs) within DoD organizations, an understanding of their interactions and capabilities is necessary. Many MAVs have already been developed for a specific usage and much speculation has been made on their future uses. Despite the growth of MAVs, there is currently no overarching systems architecture which would envelop and guide the DoD\u27s MAV development efforts. The goal of this thesis is to apply sound systems engineering principals to develop a MAV architectural model describing their use in three separate but closely related mission areas: Over-the-Hill-Reconnaissance, Battle Damage Information, and Local Area Defense. This thesis focuses on single-man packable/operable MAVs utilized by small ground units synonymous with special operations forces. The three mission areas are combined to define a single overarching Intelligence, Surveillance, and Reconnaissance (ISR) MAV architecture. This architecture focuses on the current state of ISR MAVs and provides a baseline current capability. From this architecture, areas of interest relating to MAVs and their use in the DoD are discussed, focusing on enhancing both current and future capabilities of MAVs

Evaluating the Applicability of Requirements Engineering Tools for Distributed Software Development

Requirements engineering (RE) is the first part of the software engineering process. It consists of distinct phases in which certain stakeholders deal with the problem of creating and maintaining a systems requirements document. This artifact should clarify what the customer expects from the system and how the developer should design it. RE is often mentioned as the most critical phase in the software development process. Mistakes made during the requirements phase can cost up to a hundred times more than coding errors. Moreover, The Standish Group International (2003) found out, that on average only 54%, of the originally defined features of a project are delivered and 45% of those features that are delivered are never used. Misidentified requirements are the most significant source of customer dissatisfaction with delivered systems. The problem of creating the requirements document is reinforced through geographical distance between the different people involved in the RE process. Not only the distance between customers or users and the engineers constitutes a problem, often the engineers themselves are distributed all over the world, e.g. due to outsourcing decisions and offshoring projects. The number of firms participating in global software development was low, but today 203 of the US Fortune 500 engage in offshore outsourcing endeavors. Today, more than 50 nations participate in collaborative software development projects internationally. The reasons are cost advantages and a large and well-educated pool of labor—India is a famous example. Although RE is always distributed in some way due to the distance between the different stakeholders, the term distributed RE is used to emphasize the distance between them, e.g. in global RE processes. Instead of using simple text files or diagrams for communicating both requirements and possible changes to them, nowadays a lot of tools from different vendors exist to help mastering the RE process. These tools belong to the class of so-called computer-aided software engineering (CASE) tools. Many tools support a multi-user environment that is needed for distributed RE. These tools are intended to help overcoming some of the problems mentioned before. Therefore, the aim of this paper is to give an overview over existing RE tools on the market and to evaluate how they support the different phases of RE - especially a distributed RE process. The paper is structured as follows: In chapter 2 the generic phases of the RE process are shortly described, followed by a short market overview of tools in chapter 3. The four market leading tools are evaluated in detail in chapter 4, supplemented by a short description of some interesting other tools, especially from smaller German providers. Finally, chapter 5 summarizes the results of the evaluation

Model-Driven Methodology for Rapid Deployment of Smart Spaces based on Resource-Oriented Architectures

Advances in electronics nowadays facilitate the design of smart spaces based on physical mash-ups of sensor and actuator devices. At the same time, software paradigms such as Internet of Things (IoT) and Web of Things (WoT) are motivating the creation of technology to support the development and deployment of web-enabled embedded sensor and actuator devices with two major objectives: (i) to integrate sensing and actuating functionalities into everyday objects, and (ii) to easily allow a diversity of devices to plug into the Internet. Currently, developers who are applying this Internet-oriented approach need to have solid understanding about specific platforms and web technologies. In order to alleviate this development process, this research proposes a Resource-Oriented and Ontology-Driven Development (ROOD) methodology based on the Model Driven Architecture (MDA). This methodology aims at enabling the development of smart spaces through a set of modeling tools and semantic technologies that support the definition of the smart space and the automatic generation of code at hardware level. ROOD feasibility is demonstrated by building an adaptive health monitoring service for a Smart Gym

ELISA, a demonstrator environment for information systems architecture design

This paper describes an approach of reusability of software engineering technology in the area of ground space system design. System engineers have lots of needs similar to software developers: sharing of a common data base, capitalization of knowledge, definition of a common design process, communication between different technical domains. Moreover system designers need to simulate dynamically their system as early as possible. Software development environments, methods and tools now become operational and widely used. Their architecture is based on a unique object base, a set of common management services and they host a family of tools for each life cycle activity. In late '92, CNES decided to develop a demonstrative software environment supporting some system activities. The design of ground space data processing systems was chosen as the application domain. ELISA (Integrated Software Environment for Architectures Specification) was specified as a 'demonstrator', i.e. a sufficient basis for demonstrations, evaluation and future operational enhancements. A process with three phases was implemented: system requirements definition, design of system architectures models, and selection of physical architectures. Each phase is composed of several activities that can be performed in parallel, with the provision of Commercial Off the Shelves Tools. ELISA has been delivered to CNES in January 94, currently used for demonstrations and evaluations on real projects (e.g. SPOT4 Satellite Control Center). It is on the way of new evolutions

A formal verification framework and associated tools for enterprise modeling : application to UEML

The aim of this paper is to propose and apply a verification and validation approach to Enterprise Modeling that enables the user to improve the relevance and correctness, the suitability and coherence of a model by using properties specification and formal proof of properties

Identification of Technologies for Provision of Future Aeronautical Communications

This report describes the process, findings, and recommendations of the second of three phases of the Future Communications Study (FCS) technology investigation conducted by NASA Glenn Research Center and ITT Advanced Engineering & Sciences Division for the Federal Aviation Administration (FAA). The FCS is a collaborative research effort between the FAA and Eurocontrol to address frequency congestion and spectrum depletion for safety critical airground communications. The goal of the technology investigation is to identify technologies that can support the longterm aeronautical mobile communication operating concept. A derived set of evaluation criteria traceable to the operating concept document is presented. An adaptation of the analytical hierarchy process is described and recommended for selecting candidates for detailed evaluation. Evaluations of a subset of technologies brought forward from the prescreening process are provided. Five of those are identified as candidates with the highest potential for continental airspace solutions in L-band (P-34, W-CDMA, LDL, B-VHF, and E-TDMA). Additional technologies are identified as best performers in the unique environments of remote/oceanic airspace in the satellite bands (Inmarsat SBB and a custom satellite solution) and the airport flight domain in C-band (802.16e). Details of the evaluation criteria, channel models, and the technology evaluations are provided in appendixes

A Value-Driven Framework for Software Architecture

Software that is not aligned with the business values of the organization for which it was developed does not entirely fulfill its raison d’etre. Business values represent what is important in a company, or organization, and should influence the overall software system behavior, contributing to the overall success of the organization. However, approaches to derive a software architecture considering the business values exchanged between an organization and its market players are lacking. Our quest is to address this problem and investigate how to derive value-centered architectural models systematically. We used the Technology Research method to address this PhD research question. This methodological approach proposes three steps: problem analysis, innovation, and validation. The problem analysis was performed using systematic studies of the literature to obtain full coverage on the main themes of this work, particularly, business value modeling, software architecture methods, and software architecture derivation methods. Next, the innovation step was accomplished by creating a framework for the derivation of a software reference architecture model considering an organization’s business values. The resulting framework is composed of three core modules: Business Value Modeling, Agile Reference Architecture Modeling, and Goal-Driven SOA Architecture Modeling. While the Business value modeling module focuses on building a stakeholder-centric business specification, the Agile Reference Architecture Modeling and the Goal-Driven SOA Architecture Modeling modules concentrate on generating a software reference architecture aligned with the business value specification. Finally, the validation part of our framework is achieved through proof-of-concept prototypes for three new domain specific languages, case studies, and quasi-experiments, including a family of controlled experiments. The findings from our research show that the complexity and lack of rigor in the existing approaches to represent business values can be addressed by an early requirements specification method that represents the value exchanges of a business. Also, by using sophisticated model-driven engineering techniques (e.g., metamodels, model transformations, and model transformation languages), it was possible to obtain source generators to derive a software architecture model based on early requirements value models, while assuring traceability throughout the architectural derivation process. In conclusion, despite using sophisticated techniques, the derivation process of a software reference architecture is helped by simple to use methods supported by black box transformations and guidelines that facilitate the activities for the less experienced software architects. The experimental validation process used confirmed that our framework is feasible and perceived as easy to use and useful, also indicating that the participants of the experiments intend to use it in the future