DOCSLIB.ORG

Flexible Views for View-Based Model-Driven Development

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Flexible Views for View-Based Model-Driven Development Flexible Views for View-Based Model-Driven Development Erik Burger Karlsruhe Institute of Technology Am Fasanengarten 5 Karlsruhe, Germany [email protected] ABSTRACT is presented to the developer and structure the way of dis- Model-driven development processes suffer from growing com- playing and manipulating information. Pre-defined views plexity, which leads to information spread across heterogen- are however often limited to the information contained in eous metamodels as well as drift and erosion between ar- one specific metamodel, and cannot be defined by the de- chitecture and implementation. In this paper, we present a velopers themselves. view-based modeling approach based on Orthographic Soft- In this paper, model-driven development techniques are ware Modeling (OSM), and introduce flexible views as a used to define a view-based modeling approach based on the concept for the creation of custom, user-specific views. The Orthographic Software Modeling concept by Atkinson et al. envisioned benefit of the approach is to improve software [2]. Dynamically created, so called flexible views are intro- quality, to increase consistency between the various model- duced to help the software developer to focus on the parts ing artifacts in model-driven software development, and to of the system which are relevant for his or her current role, reduce the complexity for software developers. and offer an abstraction for the rest of the system. Flexible views can be defined by a lightweight domain-specific lan- guage (DSL), and are part of a novel construction method Categories and Subject Descriptors for the single underlying model (SUM), a central concept on D.2.2 [Design Tools and Techniques]: Object-oriented which the OSM approach is built. design methods; D.2.11 [Software Architectures]: Lan- The goal of our approach is to improve software quality guages by giving developers permanent access to consistent, up- to-date and complete information about the system under development, tailored to the information needs of different General Terms developer roles, e.g., domain experts, system architects, or Keywords software developers. Flexible views are customized to the needs of a single developer and can be defined by the de- Model-driven software development; View-based modeling; velopers themselves. They reduce the complexity by dis- Orthographic Software Modeling playing only the type of information which is relevant at the time of modeling. Flexible views may also be used to hide 1. INTRODUCTION information and thus to implement access control to parts Most of today's software delopment processes make use of of a software system. models and model-based technologies to cope with the com- plexity of larger systems by expressing features of the system 2. FOUNDATIONS on a higher level of abstraction. With the extensive use of models in complex systems, these models can themselves 2.1 Model-Driven Development grow large and become too complex to be understood by a single developer. These models are often instances of sev- Model-driven development (MDD) [28, 26] puts models eral heterogeneous metamodels, across which information is into the centre of the development process and provides a spread. Thus, inconsistencies can occur, leading to drift and clear separation of views and models. During the MDD erosion between the models and the implementation of the process, several models can be used, which may differ in the system. To lower the complexity for the developer, partial level of abstraction and the type of modeled information, but views on the system restrict the amount of information that should essentially represent the same system. Developers have to take manual efforts to achieve synchronisation of information across these models. This is why developers Permission to make digital or hard copies of all or part of this work for usually work in only one kind of model at a time. personal or classroom use is granted without fee provided that copies are In view-based modeling [16], all access to the models is not made or distributed for profit or commercial advantage and that copies organised in views, which in general are partial, i.e., do not bear this notice and the full citation on the first page. To copy otherwise, to show the complete model, thus reducing the complexity for republish, to post on servers or to redistribute to lists, requires prior specific the developer by presenting him or her only the relevant permission and/or a fee. parts of a system. WCOP’13, June 17, 2013, Vancouver, BC, Canada. Copyright 2013 ACM 978-1-4503-2125-9/13/06 The terms view and view point have been defined for soft- http://dx.doi.org/10.1145/2465498.2465501 ...$15.00. ware architectures and architectural description languages in the IEEE 1471/ISO 42010 standard [18, 19], which only view2 view2 give a broad definition of the terms and do not distinguish view1 view1 between view types and actual view instances. We will use view3 view3 the more precise definition of Goldschmidt et al. [15, 16], given in Definition 1, instead. SUM view7 view7 Definition 1. A view type defines the set of metaclasses view4 view4 whose instances a view can display. It comprises a definition view6 view6 of a concrete syntax plus a mapping to the abstract metamo- view5 view5 del syntax. The actual view is an instance of a view type showing an actual set of objects and their relations using a Figure 1: Hub-and-spoke vs. peer-to-peer certain representation. A view point defines a concern. In UML, for example, diagram types such as sequence or class diagrams would be view types. A view is the actual propagated back to the SUM likewise. Although writing bi- diagram containing classes A, B and C. The static architec- directional transformations is a difficult task, the complexity ture or dynamic aspects of a system would be view points of a hub-and-spoke architecture like OSM is linear in terms in UML. of the number of transformations that have to be written The main difference of this definition to the IEEE/ISO and maintained, in contrast to the exponential number of standard is the introduction of the term view type, which transformations in a peer-to-peer synchronisation scenario can be interpreted as a metamodel for actual views. Gold- for views, which must also be bi-directional (see Figure 1). schmidt also defines defines different notions for complete- The KobrA Method [3] is a prototypical implementation ness and partiality of view types and views, such as contain- of the OSM approach, based on UML and OCL. KobrA is ment-completeness, selectional completeness, and a defini- however lacking a method for the construction of the single tion for overlaps of view types [15, sect. 4.4]. underlying model (and the metamodel it is based on), which A developer will rarely use a complete view on a system is supposed to carry all information of the software develop- because it is often too complex and tends to be confusing. ment lifecycle. This is why today's software modeling tools offer possibilit- ies to restrict a view to certain elements; the possibilities for 2.3 Bidirectional Transformations creating custom views are however limited to the selection Depending on the transformation language used, bidirec- mechanisms implemented in the tools, so that often only a tionality is difficult to maintain or to prove. Algebraic frame- manual selection of elements is possible. The idea of restric- works and methods like the lenses approach by the Harmony ted views for developers goes back to the 1990s [13, 20, 24], group [14] offer a sound theoretical foundation, but are not but has not been accepted as a development paradigm yet. yet mature enough to be used in practice. Triple graph We are conviced that today's model-driven techniques like grammars [21] can be used to define bidirectional trans- model transformations and the support for textual syntaxes formation rules, which are in practice often transformed into offers greater possibilities for view-based approaches. pairs of unidirectional transformations. Perdita Stevens distinguishes bidirectional transformations 2.2 Orthographic Software Modeling from bijective transformations [29], and identifies several re- With the Orthographic Software Modeling (OSM) [2] ap- quirements that bidirectional transformations should satisfy: proach, Atkinson et al. aim to establish views as first- In the context of QVT-R, the basic requirements are cor- class entities of the software engineering process. In the en- rectness (the transformation engine produces models that visioned view-centric development process, all information satisfy the relations), hippocraticness (models that satisfy about a system is represented in a single underlying model a relation are not modified by the executions of the trans- (SUM); thus, the SUM even transcends the function of being formation engine), and additionally undoability. Diskin et al. a model, but becomes the system itself. This makes the ap- [11] give a weaker definition for undoability and invertibility proach radical in the sense that even source code is treated that is more suitable for practical applications of bidirec- as only a special textual view. The SUM itself has to con- tional transformation and which is based on lenses. They tain all execution semantics and could theoretically also be also argue that delta-based approaches are superior to state- executed without the use of source code. based approaches: While state-based transformations have The authors of OSM suggest that user-specific custom the complete models in their current status as input and views be generated dynamically, based on model transform- output, delta-based approaches use the differences between ations from and to the SUM. These views are organized in models. These deltas may carry semantic information that dimensions that are ideally independent from each other cannot be computed by comparing model versions, such as (orthogonal).
Load more

Recommended publications
  • ASP.NET MVC with Entity Framework and CSS
    ASP.NET MVC with Entity Framework and CSS Lee Naylor ASP.NET MVC with Entity Framework and CSS Lee Naylor Newton-le-Willows, Merseyside United Kingdom ISBN-13 (pbk): 978-1-4842-2136-5 ISBN-13 (electronic): 978-1-4842-2137-2 DOI 10.1007/978-1-4842-2137-2 Library of Congress Control Number: 2016952810 Copyright © 2016 by Lee Naylor This work is subject to copyright. All rights are reserved by the Publisher, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilms or in any other physical way, and transmission or information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed. Trademarked names, logos, and images may appear in this book. Rather than use a trademark symbol with every occurrence of a trademarked name, logo, or image we use the names, logos, and images only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. The use in this publication of trade names, trademarks, service marks, and similar terms, even if they are not identified as such, is not to be taken as an expression of opinion as to whether or not they are subject to proprietary rights. While the advice and information in this book are believed to be true and accurate at the date of publication, neither the authors nor the editors nor the publisher can accept any legal responsibility for any errors or omissions that may be made.
    [Show full text]
  • Configuring Metadata Manager Privileges and Permissions
    Configuring Metadata Manager Privileges and Permissions © Copyright Informatica LLC 1993, 2021. Informatica LLC. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica LLC. All other company and product names may be trade names or trademarks of their respective owners and/or copyrighted materials of such owners. Abstract You can configure privileges to allow users access to the features in Metadata Manager. You can configure permissions to allow access to resources or objects in Metadata Manager. This article describes the privileges and permissions that you can configure in Metadata Manager. Supported Versions • Metadata Manager 9.6.1 Table of Contents Introduction................................................................ 2 Users, Groups, Privileges, and Roles................................................ 3 Privileges ................................................................. 4 Catalog Privilege Group...................................................... 4 Load Privilege Group........................................................ 6 Model Privilege Group....................................................... 7 Security Privilege Group...................................................... 7 Permissions................................................................ 8 Types of Permissions........................................................ 9 Rules and Guidelines.......................................................
    [Show full text]
  • Architectural Improvement of Display Viewer 5 Software
    Teemu Vähä-Impola Architectural Improvement of Display Viewer 5 Software Master’s Thesis in Information Technology November 6, 2020 University of Jyväskylä Faculty of Information Technology Author: Teemu Vähä-Impola Contact information: [email protected] Supervisors: PhD Raino Mäkinen, MSc Tommy Rikberg, and MSc Lauri Saurus Title: Architectural Improvement of Display Viewer 5 Software Työn nimi: Display Viewer 5 -ohjelmiston arkkitehtuurin parantaminen Project: Master’s Thesis Study line: Software Technology Page count: 76+1 Abstract: In this thesis, an improved architecture for Display Viewer 5 (DV5) software was studied. The new architecture would enforce MVVM architecture more strongly, make clearer divisions of the software’s parts and enhance maintainability and reusability of the software, thus making the software more customizable for new projects and suitable for the customers’ needs. As a result, the existing MVVM architecture was strengthened by enforcing division into models, views and viewmodels. In addition, redundant duplications were removed and certain code was divided into their own separate entities. Keywords: architecture, software engineering Suomenkielinen tiivistelmä: Tässä tutkielmassa Display Viewer 5 (DV5) -ohjelmistolle pyrittiin löytämään parempi arkkitehtuuri, jonka seurauksena huollettavuus ja uudelleenkäytet- tävyys kasvavat ja ohjelmiston kustomointi uusille asiakkaille helpottuu. Tuloksena päädyt- tiin vahvistamaan jo nykyistä MVVM-arkkitehtuuria tekemällä jokaiselle luokalle tarvitta- van arkkitehtuurin
    [Show full text]
  • Sysml Distilled: a Brief Guide to the Systems Modeling Language
    ptg11539604 Praise for SysML Distilled “In keeping with the outstanding tradition of Addison-Wesley’s techni- cal publications, Lenny Delligatti’s SysML Distilled does not disappoint. Lenny has done a masterful job of capturing the spirit of OMG SysML as a practical, standards-based modeling language to help systems engi- neers address growing system complexity. This book is loaded with matter-of-fact insights, starting with basic MBSE concepts to distin- guishing the subtle differences between use cases and scenarios to illu- mination on namespaces and SysML packages, and even speaks to some of the more esoteric SysML semantics such as token flows.” — Jeff Estefan, Principal Engineer, NASA’s Jet Propulsion Laboratory “The power of a modeling language, such as SysML, is that it facilitates communication not only within systems engineering but across disci- plines and across the development life cycle. Many languages have the ptg11539604 potential to increase communication, but without an effective guide, they can fall short of that objective. In SysML Distilled, Lenny Delligatti combines just the right amount of technology with a common-sense approach to utilizing SysML toward achieving that communication. Having worked in systems and software engineering across many do- mains for the last 30 years, and having taught computer languages, UML, and SysML to many organizations and within the college setting, I find Lenny’s book an invaluable resource. He presents the concepts clearly and provides useful and pragmatic examples to get you off the ground quickly and enables you to be an effective modeler.” — Thomas W. Fargnoli, Lead Member of the Engineering Staff, Lockheed Martin “This book provides an excellent introduction to SysML.
    [Show full text]
  • Model and Tool Integration in High Level Design of Embedded Systems
    Model and Tool Integration in High Level Design of Embedded Systems JIANLIN SHI Licentiate thesis TRITA – MMK 2007:10 Department of Machine Design ISSN 1400-1179 Royal Institute of Technology ISRN/KTH/MMK/R-07/10-SE SE-100 44 Stockholm TRITA – MMK 2007:10 ISSN 1400-1179 ISRN/KTH/MMK/R-07/10-SE Model and Tool Integration in High Level Design of Embedded Systems Jianlin Shi Licentiate thesis Academic thesis, which with the approval of Kungliga Tekniska Högskolan, will be presented for public review in fulfilment of the requirements for a Licentiate of Engineering in Machine Design. The public review is held at Kungliga Tekniska Högskolan, Brinellvägen 83, A425 at 2007-12-20. Mechatronics Lab TRITA - MMK 2007:10 Department of Machine Design ISSN 1400 -1179 Royal Institute of Technology ISRN/KTH/MMK/R-07/10-SE S-100 44 Stockholm Document type Date SWEDEN Licentiate Thesis 2007-12-20 Author(s) Supervisor(s) Jianlin Shi Martin Törngren, Dejiu Chen ([email protected]) Sponsor(s) Title SSF (through the SAVE and SAVE++ projects), VINNOVA (through the Model and Tool Integration in High Level Design of Modcomp project), and the European Embedded Systems Commission (through the ATESST project) Abstract The development of advanced embedded systems requires a systematic approach as well as advanced tool support in dealing with their increasing complexity. This complexity is due to the increasing functionality that is implemented in embedded systems and stringent (and conflicting) requirements placed upon such systems from various stakeholders. The corresponding system development involves several specialists employing different modeling languages and tools.
    [Show full text]
  • From Requirements to Design Specifications- a Formal Approach
    INTERNATIONAL DESIGN CONFERENCE - DESIGN 2010 Dubrovnik - Croatia, May 17 - 20, 2010. FROM REQUIREMENTS TO DESIGN SPECIFICATIONS- A FORMAL APPROACH W. Brace and K. Thramboulidis Keywords: requirements, requirements checklist, design specification, requirements formalization, model-centric requirements engineering 1. Introduction The traditional development process for mechatronic systems is criticized as inappropriate for the development of systems characterized by complexity, dynamics and uncertainty as is the case with today’s products. Software is playing an always increasing role in the development of these systems and it has become the evolving driver for innovations. It does not only implement a significant part of the functionality of today’s mechatronic systems, but it is also used to realize many of their competitive advantages [Thramboulidis 2009]. However, the current process is traditionally divided into software, electronics and mechanics, with every discipline to emphasize on its own approaches, methodologies and tools. Moreover, vocabularies used in processes and methodologies are different making the collaboration between the disciplines a great challenge. System development activities such as requirements and design specification, implementation and verification are well defined in software engineering. In terms of software engineering the term “design specification” is used to refer to the various models that are produced during the design process and describe the various models of the proposed solutions. Therefore, “design specifications” are descriptions of solution space while “analysis specifications” are descriptions of problem space. Analysis specifications include both requirements specifications but also the problem space structuring that is represented by analysis models such as class diagrams that capture the key concepts of the problem domain and in this sense they provide a specific structuring of the problem space.
    [Show full text]
  • Applications of Reinforcement Learning to Routing and Virtualization in Computer Networks
    Applications of Reinforcement Learning to Routing and Virtualization in Computer Networks by Soroush Haeri B. Eng., Multimedia University, Malaysia, 2010 Dissertation Submitted in Partial Fulfillment of the Requirements for the Degree of Doctor of Philosophy in the School of Engineering Science Faculty of Applied Science © Soroush Haeri 2016 SIMON FRASER UNIVERSITY Spring 2016 All rights reserved. However, in accordance with the Copyright Act of Canada, this work may be reproduced without authorization under the conditions for “Fair Dealing.” Therefore, limited reproduction of this work for the purposes of private study, research, criticism, review and news reporting is likely to be in accordance with the law, particularly if cited appropriately. Abstract Computer networks and reinforcement learning algorithms have substantially advanced over the past decade. The Internet is a complex collection of inter-connected networks with a numerous of inter-operable technologies and protocols. Current trend to decouple the network intelligence from the network devices enabled by Software-Defined Networking (SDN) provides a centralized implementation of network intelligence. This offers great computational power and memory to network logic processing units where the network intelligence is implemented. Hence, reinforcement learning algorithms viable options for addressing a variety of computer networking challenges. In this dissertation, we propose two applications of reinforcement learning algorithms in computer networks. We first investigate the applications of reinforcement learning for deflection routing in buffer- less networks. Deflection routing is employed to ameliorate packet loss caused by contention in buffer-less architectures such as optical burst-switched (OBS) networks. We present a framework that introduces intelligence to deflection routing (iDef).
    [Show full text]
  • Composition of Software Architectures Christos Kloukinas
    Composition of Software Architectures Christos Kloukinas To cite this version: Christos Kloukinas. Composition of Software Architectures. Computer Science [cs]. Université Rennes 1, 2002. English. tel-00469412 HAL Id: tel-00469412 https://tel.archives-ouvertes.fr/tel-00469412 Submitted on 1 Apr 2010 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Composition of Software Architectures - Ph.D. Thesis - - Presented in front of the University of Rennes I, France - - English Version - Christos Kloukinas Jury Members : Jean-Pierre Banâtre Jacky Estublier Cliff Jones Valérie Issarny Nicole Lévy Joseph Sifakis February 12, 2002 Résumé Les systèmes informatiques deviennent de plus en plus complexes et doivent offrir un nombre croissant de propriétés non fonctionnelles, comme la fiabi- lité, la disponibilité, la sécurité, etc.. De telles propriétés sont habituellement fournies au moyen d’un intergiciel qui se situe entre le matériel (et le sys- tème d’exploitation) et le niveau applicatif, masquant ainsi les spécificités du système sous-jacent et permettant à des applications d’être utilisées avec dif- férentes infrastructures. Cependant, à mesure que les exigences de propriétés non fonctionnelles augmentent, les architectes système se trouvent confron- tés au cas où aucun intergiciel disponible ne fournit toutes les propriétés non fonctionnelles visées.
    [Show full text]
  • Comprehensive Measurement Framework for Enterprise Architectures
    International Journal of Computer Science & Information Technology (IJCSIT) Vol 3, No 4, August 2011 COMPREHENSIVE MEASUREMENT FRAMEWORK FOR ENTERPRISE ARCHITECTURES Mahesh R. Dube 1 and Shantanu K. Dixit 2 1Department of Computer Engineering, VIT, Pune, India [email protected] 2Department of Electronics and Telecommunications, WIT, Solapur, India [email protected] ABSTRACT Enterprise Architecture defines the overall form and function of systems across an enterprise involving the stakeholders and providing a framework, standards and guidelines for project-specific architectures. Project-specific Architecture defines the form and function of the systems in a project or program, within the context of the enterprise as a whole with broad scope and business alignments. Application-specific Architecture defines the form and function of the applications that will be developed to realize functionality of the system with narrow scope and technical alignments. Because of the magnitude and complexity of any enterprise integration project, a major engineering and operations planning effort must be accomplished prior to any actual integration work. As the needs and the requirements vary depending on their volume, the entire enterprise problem can be broken into chunks of manageable pieces. These pieces can be implemented and tested individually with high integration effort. Therefore it becomes essential to analyze the economic and technical feasibility of realizable enterprise solution. It is difficult to migrate from one technological and business aspect to other as the enterprise evolves. The existing process models in system engineering emphasize on life-cycle management and low-level activity coordination with milestone verification. Many organizations are developing enterprise architecture to provide a clear vision of how systems will support and enable their business.
    [Show full text]
  • An Annotated Bibliography for ISO/IEC/IEEE 42010
    An Annotated Bibliography for ISO/IEC/IEEE 42010 version 4.4.b October 15, 2020 Introduction An annotated bibliography of papers, reports and books on topics pertaining to ISO/IEC/- IEEE 42010:2011 (revision of the former IEEE Std 1471:2000). Originally prepared for ISO/IEC JTC1/SC7 WG42, the Architecture Working Group of the Systems and Software Engineering Subcommittee of ISO. Currently the bibliography is undergoing a major up- date as ISO/IEC/IEEE 42010 is being revised. The current draft is a work-in-progress; it has many new entries, but these are not necessarily complete. The bibliography includes 1) items which were inspirations for the Standard; 2) items citing or about the Standard or its development; and 3) items inspired by or built upon the Standard and its concepts. Note: with version 4.x, we switch to producing the bibliography using the biblatex package. There may be errors. Please send corrections and additions to [email protected]. References 12th Working IEEE/IFIP Conference on Software Architecture (WICSA 2015), 4–7 May 2015, Montr´eal,Qu´ebec,Canada. IEEE Computer Society, Apr. 2015. A. Anwar et al. “A Formal Approach to Model Composition Applied to VUML”. In: 2011 16th IEEE International Conference on Engineering of Complex Computer Systems. Keywords: graph grammars, process algebra, model composition, MBSE. Apr. 2011, pp. 188–197. DOI: 10.1109/ICECCS.2011.26. Annotations: -. 1 Abstract: Several approaches adopted by the software engineering community rely on the principle of multi-modeling which allows to separate concerns and to model a sys- tem as a set of less complex sub-models.
    [Show full text]
  • Collaboration Analytics Need More Comprehensive Models and Methods. an Opinion Paper Areum Han1, Florian Krieger2, Samuel Greiff3
    Volume 8(1), 13–29. http://doi.org/10.18608/jla.2021.7288 Collaboration Analytics Need More Comprehensive Models and Methods. An Opinion Paper Areum Han1, Florian Krieger2, Samuel Greiff3 Abstract As technology advances, learning analytics is expanding to include students’ collaboration settings. Despite their increasing application in practice, some types of analytics might not fully capture the comprehensive educational contexts in which students’ collaboration takes place (e.g., when data is collected and processed without predefined models, which forces users to make conclusions without sufficient contextual information). Furthermore, existing definitions and perspectives on collaboration analytics are incongruent. In light of these circumstances, this opinion paper takes a collaborative classroom setting as context and explores relevant comprehensive models for collaboration analytics. Specifically, this paper is based on Pei-Ling Tan and Koh’s ecological lens (2017, Situating learning analytics pedagogically: Towards an ecological lens. Learning: Research and Practice, 3(1), 1–11. https://doi.org/10.1080/23735082.2017.1305661), which illustrates the co-emergence of three interactions among students, teachers, and content interwoven with time. Moreover, this paper suggests several factors to consider in each interaction when executing collaboration analytics. Agendas and recommendations for future research are also presented. Notes for Practice • Studies of educational contexts using collaboration analytics are being implemented, but some analytics practices may unintentionally fail to fully capture the comprehensive context (e.g., when users without sufficient contextual information must make final decisions based on data collected without predefined learning models). Furthermore, definitions and perspectives on collaboration analytics vary across disciplines and underlying perspectives on collaboration.
    [Show full text]
  • Nato Architecture Framework (Naf)
    NATO ARCHITECTURE FRAMEWORK Version 4 Architecture Capability Team Consultation, Command & Control Board January 2018 Acknowledgments for NAFv4 Publication Throughout the development of version 4 of this publication numerous individual experts of NATO Nations participated, resulting in this significant achievement: The realization of the NATO Architecture Framework. This work would not have been possible without the continuous support of the Ministries of Defence of United Kingdom and France, and the NATO Science and Technology Organization. Also special thanks goes to Partner Nations and Industry Partners for their unwavering support in assigning and providing their best professional resources in the architecture domain. The NATO Architecture Framework is a substantial achievement for the Architecture Capability Team under the Consultation, Command and Control Board. Each member of the Architecture Capability Team worked determinedly over the last four years to provide extensive professional guidance and personal effort in the development of this product. The Architecture Capability Team is grateful to all for their contributions to this effort. 4 NAFv4 NAFv4 5 CONTENTS Chapter 1 - Introduction 1 GENERAL ....................................................................................................................................................................... 11 1.1 Purpose ........................................................................................................................................................................
    [Show full text]