DOCSLIB.ORG

Unicorn Libraries, IDE Plugin, Container Packaging and Deployment Toolset Early Release

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Unicorn Libraries, IDE Plugin, Container Packaging and Deployment Toolset Early Release D2.1 Unicorn Libraries, IDE Plugin, Container Packaging and Deployment Toolset Early Release Unicorn Libraries, IDE Plugin, Container Packaging and Deployment Toolset Early Release Deliverable D2.1 Editors Athanasios Tryfonos Demetris Trihinas Reviewers Sotiris Koussouris (SUITE5) John Samuelsson, Erik Robertson (REDIKOD) Date 30 March 2018 Classification Public 1 D2.1 Unicorn Libraries, IDE Plugin, Container Packaging and Deployment Toolset Early Release Contributing Author # Version History Name Partner Description Table of Contents (ToC) and partner Demetris Trihinas UCY 1 contribution assignment. Athanasios Tryfonos UCY 2 Introduction of Section 5 and subsection 5.2 Finalized state-of-the-art and key technologies Zacharias Georgiou UCY 3 challenges and updates section. Initial content for subsection 5.1 has been George Pallis UCY 4 added. Julia Vuong CAS 5 Finalized Section 1 Monitoring and Elasticity, Perimeter Security Manos Papoutsakis FORTH 6 and Vulnerability Assessment models are added Giannis Ledakis UBITECH 7 Deliverable ready for review. Addressed comments from reviewers and 8 compiled final version ready for submission 2 D2.1 Unicorn Libraries, IDE Plugin, Container Packaging and Deployment Toolset Early Release Contents CONTENTS 3 1 INTRODUCTION 9 1.1 Document Purpose and Scope 10 1.2 Document Relationship with other Project Work Packages 11 1.3 Document Structure 11 2 STATE OF THE ART AND KEY TECHNOLOGY AXES CHALLENGES AND UPDATES 12 2.1 OASIS TOSCA Specification 12 2.2 Docker Container Technology Stack 13 2.3 Service Mesh and Container Design Patterns 15 3 UNICORN DESIGN LIBRARIES 18 3.1 Overview 18 3.2 Monitoring and Elasticity 18 3.2.1 Design Library Overview 18 3.2.2 Design Library Model Description 20 3.3 Perimeter Security and Risk & Vulnerability Assessment 23 3.3.1 Design Library Overview 23 3.3.2 Design Library Model Description 26 3.4 Privacy and Authorization 28 3.4.1 Design Library Overview 28 3.4.2 Design Library Model Description 30 4 DESIGN LIBRARIES IMPLEMENTATION 32 4.1 Design Libraries Implementation Aspects 32 4.2 Unicorn Service Graph Representation 33 4.3 Unicorn Compose File 36 4.3.1 Unicorn Compose Descriptor Interpreter 37 4.4 Unicorn Enabled Container Packaging 38 4.5 Unicorn Design Libraries Features 40 4.5.1 Monitoring and Elasticity Design Libraries Features 40 4.5.2 Perimeter Security Design Library Implementation 41 4.5.3 Risk and Vulnerability Assessment Implementation 41 4.5.4 Privacy and Authorization Implementation 43 5 UNICORN DASHBOARD 43 5.1 Unicorn Management Perspective 44 5.1.1 Entities and Entity Relationship in Unicorn Dashboard 44 5.1.2 Technical Approach 46 5.1.3 Provided Functionalities 47 5.1.4 Exposed APIs 51 5.2 Unicorn Development Perspective 56 6 CONCLUSION 60 3 D2.1 Unicorn Libraries, IDE Plugin, Container Packaging and Deployment Toolset Early Release 7 REFERENCES 61 8 ANNEX 62 8.1 Unicorn Enhanced Docker-Compose Model Specification 62 8.1.1 The format and the specification of the Unicorn Docker-Compose model 62 8.1.2 Unicorn Compose File Extended Example 70 4 D2.1 Unicorn Libraries, IDE Plugin, Container Packaging and Deployment Toolset Early Release List of Figures Figure 1 Unicorn Reference Architecture 10 Figure 2 Structural Elements of a Service Template and their relationships 12 Figure 3 Abstract view of the Docker Engine 13 Figure 4 Docker Swarm can be swapped out with different container orchestration technologies such as Kubernetes or Mesos 14 Figure 5 Docker-Compose that consists of 3 services; i) redis service which is bound onto frontend network, ii) db service that mounts a volume on the host machine called db-data and bound on the backend network and iii) a vote service bound on frontend network 14 Figure 6 x-custom special field definition. This field is not in the semantics of docker-compose language specification, however with its definition it is being ignored or handled in a different manner by docker- compose. 15 Figure 7 Example of a sidecar container that syncs the file system with a git repository 15 Figure 8 Example illustrating the Ambassador design pattern 16 Figure 9 Example illustrating the Adapter design pattern 16 Figure 10 Istio Architecture 17 Figure 11: Elasticity Policy Example 19 Figure 12 The security model conforming to the abstract syntax of the security meta-model 25 Figure 13 ABAC Model for Unicorn 30 Figure 14 Maven Import of Unicorn Monitoring Library 32 Figure 15 Timeit annotation that calculates the time needed for a method to be executed 32 Figure 16 Example of Unicorn Monitoring Annotation 33 Figure 17 Simple Service Graph with properties 34 Figure 18 Representation of Service Graph as Tosca YAML 35 Figure 19 The Unicorn Descriptor Interpreter 38 Figure 20 Example Dockerfile that builds a Unicorn parent image based on Ubuntu 16.04 40 Figure 21 The Dashboard layer divided into two perspectives. 44 Figure 22. Entities in Unicorn Dashboard. 45 Figure 23. Entity Relationship in Unicorn Dashboard. 46 Figure 24 Eclipse Che Architecture 57 Figure 25 Unicorn Che IDE Plugin High-Level Architecture 57 Figure 26 Unicorn Stack Configuration for Che 59 List of Tables Table 1 Metric EBNF Definition 20 Table 2 Monitoring Agent EBNF Definition 20 Table 3 Insight EBNF Definition 21 Table 4 Elasticity Policy EBNF Definition 22 Table 5 Elasticity Trigger EBNF Definition 22 Table 6 Elasticity Action EBNF Definition 23 Table 7 Perimeter Security and Risk & Vulnerability Assessment EBNF 26 Table 8 EBNF Definition of the ABAC model used in Unicorn 30 Table 9 Docker container requirements for Unicorn enabled microservices 39 Table 10 Monitoring and Elasticity Table of Features 40 Table 11 Perimeter Security Table of Features 41 Table 12 Risk and Vulnerability Assessment Table of Features 41 Table 13 Privacy and Authorization Table of Features 43 Table 14 User Registration Functionality 47 Table 15 Login/Logout Functionality 47 Table 16 Delete User Functionality 48 5 D2.1 Unicorn Libraries, IDE Plugin, Container Packaging and Deployment Toolset Early Release Table 17 Update User Profile Functionality 48 Table 18 Change Authorization Details Functionality 48 Table 19 Register a new Usergroup Functionality 48 Table 20 Update an existing usergroup Functionality 48 Table 21 Start a Unicorn-compliant app Functionality 49 Table 22 Stop an application Functionality 49 Table 23 Delete application Functionality 49 Table 24 Deploy Unicorn Compliant Application Functionality 49 Table 25 Get Monitoring Data Functionality 50 Table 26 Update Runtime Policies 50 Table 27 Update Service Graph Functionality 50 Table 28 Cloud Offering Marketplace Functionality 50 Table 29 Generate Service Graph Functionality 51 Table 30 Update Service Graph Functionality 51 Table 31 Launch Unicorn IDE Plugin 51 Table 32 Update Usergroup API 52 Table 33 Delete Usergroup by ID API 52 Table 34 Update User API 52 Table 35 Delete User API 53 Table 36 Get all Users API 53 Table 37 Get User by ID API 53 Table 38 Enable Registered user API 54 Table 39 Disable User API 54 Table 40 Create new Usergrup 54 Table 41 Register user API 55 Table 42 Login API 55 Table 43 Update Credentials API 56 6 D2.1 Unicorn Libraries, IDE Plugin, Container Packaging and Deployment Toolset Early Release Executive Summary The purpose of this deliverable is to report the progress made for the ongoing work regarding workpackage 2 and more specifically to document the early release of the Unicorn Libraries, IDE Plugin, Container Packaging and Deployment Toolset. The deliverable begins by presenting an updated state-of-the-art and key technology axes section. We identify and analyze technologies that are introduced for the first time within Unicorn and identify challenges and potential obstacles that current technologies may impose during the implementation and integration phases. More specifically, we introduce the concepts of sidecar architecture which is a multi-container architectural pattern that extends the functionality of a main container with additional containers, without performing any changes to its structure and functionality. Also, we present leading technologies that adhere to the sidecar architecture, such as Google’s Istio and Envoy Proxy, which will be used in the implementation of Unicorn. We elaborate on the concept of the service graph by adopting the OASIS Tosca specification, since the interrelation between nodes and edges of a graph can be mapped to structural components of the Tosca Specification. The final focus on this first section of the deliverable is on Docker and its technology stack and various tools that play an important role in Unicorn. Unicorn Design Libraries, assist developers to design cloud applications as Unicorn-enabled micro-services, with the minimum code intrusion that is required to enable portable security enforcement mechanisms, monitoring and elastic scaling, and to ensure data privacy constraints. To this end, Unicorn offers four design libraries namely i) Monitoring and Elasticity, ii) Perimeter Security, iii) Risk and Vulnerability Assessment and iv) Privacy and Authorization design libraries; their meta-models and language are presented in EBNF format later on Section 3. It should be noted that due to similarities and interdependencies of the concepts of the aforementioned design libraries, some are presented and represented as a single library, i.e. Monitoring and Elasticity and Perimeter Security with Risk and Vulnerability assessment. Minimum code intrusion in the development of Unicorn-enabled microservices is achieved by annotating specific bits of code, methods or variables with decorators that provide additional functionality, without being a necessity for developer to have deep knowledge of the annotating concepts. Even though deep knowledge of the concepts is not required, developers should at least provide initial policies and feature configuration that match their requirements for the developed microservice. For this purpose, Section 4 introduces a table with the features and policies that each design library exposes as functionality and at which stage of the continuous development and integration pipeline this feature applies to (it is either at design-time, using annotations or at run-time through configurations at the dashboard).
Load more

Recommended publications
  • Smart Execution of Distributed Application by Balancing Resources in Mobile Devices
    ALMA MATER STUDIORUM - UNIVERSITÀ DI BOLOGNA SCUOLA DI INGEGNERIA E ARCHITETTURA DISI INGEGNERIA INFORMATICA TESI DI LAUREA in Reti di Calcolatori M Smart execution of distributed application by balancing resources in mobile devices and cloud-based avatars CANDIDATO: RELATORE: Giacomo Gezzi Chiar.mo Prof. Ing. Antonio Corradi CORRELATORE: Chiar.mo Prof. Cristian Borcea Anno Accademico 2014/2015 Sessione III 2 Abstract L’obiettivo del progetto di tesi svolto e` quello di realizzare un servizio di livello middleware dedicato ai dispositivi mobili che sia in grado di fornire il supporto per l’offloading di codice verso una infrastruttura cloud. In particolare il progetto si concentra sulla migrazione di codice verso macchine virtuali dedicate al singolo utente. Il sistema operativo delle VMs e` lo stesso utilizzato dal device mobile. Come i precedenti lavori sul computation offloading, il progetto di tesi deve garantire migliori per- formance in termini di tempo di esecuzione e utilizzo della batteria del dispositivo. In particolare l’obiettivo piu` ampio e` quello di adattare il principio di computation offloading a un contesto di sistemi distribuiti mobili, miglio- rando non solo le performance del singolo device, ma l’esecuzione stessa dell’applicazione distribuita. Questo viene fatto tramite una gestione di- namica delle decisioni di offloading basata, non solo, sullo stato del de- vice, ma anche sulla volonta` e/o sullo stato degli altri utenti appartenenti allo stesso gruppo. Per esempio, un primo utente potrebbe influenzare le decisioni degli altri membri del gruppo specificando una determinata richiesta, come alta qualita` delle informazioni, risposta rapida o basata su altre informazioni di alto livello.
    [Show full text]
  • Design Pattern Implementation in Java and Aspectj
    Design Pattern Implementation in Java and AspectJ Jan Hannemann Gregor Kiczales University of British Columbia University of British Columbia 201-2366 Main Mall 201-2366 Main Mall Vancouver B.C. V6T 1Z4 Vancouver B.C. V6T 1Z4 jan [at] cs.ubc.ca gregor [at] cs.ubc.ca ABSTRACT successor in the chain. The event handling mechanism crosscuts the Handlers. AspectJ implementations of the GoF design patterns show modularity improvements in 17 of 23 cases. These improvements When the GoF patterns were first identified, the sample are manifested in terms of better code locality, reusability, implementations were geared to the current state of the art in composability, and (un)pluggability. object-oriented languages. Other work [19, 22] has shown that implementation language affects pattern implementation, so it seems The degree of improvement in implementation modularity varies, natural to explore the effect of aspect-oriented programming with the greatest improvement coming when the pattern solution techniques [11] on the implementation of the GoF patterns. structure involves crosscutting of some form, including one object As an initial experiment we chose to develop and compare Java playing multiple roles, many objects playing one role, or an object [27] and AspectJ [25] implementations of the 23 GoF patterns. playing roles in multiple pattern instances. AspectJ is a seamless aspect-oriented extension to Java, which means that programming in AspectJ is effectively programming in Categories and Subject Descriptors Java plus aspects. D.2.11 [Software Engineering]: Software Architectures – By focusing on the GoF patterns, we are keeping the purpose, patterns, information hiding, and languages; D.3.3 intent, and applicability of 23 well-known patterns, and only allowing [Programming Languages]: Language Constructs and Features – the solution structure and solution implementation to change.
    [Show full text]
  • Weaving Eclipse Applications
    Weaving Eclipse Applications Fabio Calefato, Filippo Lanubile, Mario Scalas, 1 Dipartimento di Informatica, Università di Bari, Italy {calefato, lanubile, scalas}@uniba.it Abstract. The Eclipse platform fully supports the ideas behind software components: in addition it also adds dynamic behavior allowing components to be added, replaced or removed at runtime without shutting the application down. While layered software architectures may be implemented by assembling components, the way these components are wired together differs. In this paper we present our solution of Dependecy Injection, which allows to build highly decoupled Eclipse applications in order to implement real separation of concerns by systemically applying Aspect Oriented Programming and the Model-View-Presenter pattern, a variant of the classic Model-View-Controller. Keywords: Eclipse, Aspect Oriented Programming, Dependency Injection. 1 Introduction The Dependency Inversion Principle [19] (DIP) states that (both high and low level) software parts should not depend on each other’s concrete implementation but, instead, be based on a common set of shared abstractions: one application of the DIP is the Dependency Injection, also called Inversion of Control (IoC) [11]. From an architectural perspective, DI allows to explicit the dependencies between software components and provides a way to break the normal coupling between a system under test and its dependencies during automated testing [25]. This is possible because the software is composed by aggregating simpler, loosely coupled objects that are more easily unit-testable [32]. Additionally, by separating the clients by their dependencies, we also make their code simpler because there is no need for them to search for their collaborators.
    [Show full text]
  • Static Versus Dynamic Polymorphism When Implementing Variability in C++
    Static Versus Dynamic Polymorphism When Implementing Variability in C++ by Samer AL Masri A thesis submitted in partial fulfillment of the requirements for the degree of Master of Science Department of Computing Science University of Alberta c Samer AL Masri, 2018 Abstract Software Product Line Engineering (SPLE) creates configurable platforms that can be used to efficiently produce similar, and yet different, product vari- ants. To implement SPLs, multiple variability implementation mechanisms have been suggested, including polymorphism. In this thesis, we talk about the trade-offs of using static versus dynamic polymorphism through a case study of IBM’s open-source Eclipse OMR project. Eclipse OMR is an open-source C++ framework for building robust lan- guage runtimes. To support the diverse languages and architectures targeted by the framework, OMR’s variability implementation uses a combination of build-system variability and static polymorphism. OMR developers now real- ize that their current static polymorphism implementation has its drawbacks and are considering using dynamic polymorphism instead. In order to study the trade-offs of using different kinds of polymorphism in OMR, it is crucial to collect function information and overload/override statistics about the current code base. Hence, we create OMRStatistics,a static analysis tool that collects such information about OMR’s source code. Using the information provided by OMRStatistics, OMR developers can make better design decisions on which variability extension points should be switched from static polymorphism to dynamic polymorphism. In addition, we report on our first hand experience of changing the poly- morphism used in OMR’s variability implementation mechanism from static to dynamic, the challenges we faced in the process, and how we overcame them.
    [Show full text]
  • Oracle FLEXCUBE Private Banking Release Notes
    Product Release Notes Oracle FLEXCUBE Private Banking Release 12.1.0.0.0 [April] [2016] Product Release Notes Table of Contents 1. INTRODUCTION ........................................................................................................................................... 1-1 1.1 PURPOSE ..................................................................................................................................................... 1-1 1.2 BACKGROUND/ENVIRONMENT ................................................................................................................... 1-1 1.3 THIRD PARTY SOFTWARE DETAILS ............................................................................................................ 1-2 1.4 RELEASE CONTENTS ................................................................................................................................... 1-4 1.5 PRODUCT DOCUMENTATION ....................................................................................................................... 1-5 2. COMPONENTS OF THE RELEASE ........................................................................................................... 2-1 2.1 DOCUMENTS ACCOMPANYING THE SOFTWARE ............................................................................................ 2-1 2.2 SOFTWARE COMPONENTS ........................................................................................................................... 2-1 1. Introduction 1.1 Purpose Purpose of this Release Note is to highlight the
    [Show full text]
  • Eclipse Governance Structure
    Eclipse Governance Structure Board of Directors A p p rov es S trateg y , P lans, P olicies E clip se M anag em ent O rg aniz ation E stab lish es th e R oadm ap , Bu ilds th e P latform , Deliv ers th e V ision R eq u irem ents C ou ncil P rop oses T h em es M em b ersh ip at L arg e & P riorities A p p rov es V ision, By law s Bu ilds th e E cosy stem P lanning C ou ncil A rch itectu re C ou ncil E stab lish es P latform Defines & M aintains R elease P lan A rch itectu re S u b com m ittee A S u b com m ittee B P M C 1 P M C 2 P M C 3 P M C 4 P M C 4 P M C 5 P M C 6 P M C 7 Project Management Committees Eclipse Foundation, Inc. Eclipse Development Roadmap ° http://www.eclipse.org/org/councils/roadmap.html ° Communicate the direction and timetable of the Eclipse projects ° Solicits for input from key stakeholders ° Create an open predictable environment to enable planning for commercial adoption ° Predictable schedule of new releases ° Understand technology direction ° Eclipse Roadmap consists of: ° Themes and Priorities ° Schedules ° Architecture Plan ° Will be update every 6 months ° First iteration done March 2005 Eclipse Foundation, Inc. Eclipse Roadmap: Development Councils Strategic Members PMC T&P’s Requirements Council Add-in Providers Market research T h P e r m io e ri s & ti s e & e s s e m ti e ri h o T ri P Platform Release Planning Architecture Council Architecture Plan Council P P M M C C P A l r a c n h s Eclipse Foundation, Inc.
    [Show full text]
  • Creating a Modular Aspectj Foundation for Simple and Rapid Extension Implementation By
    Creating a Modular AspectJ Foundation for Simple and Rapid Extension Implementation by Hristofor Mirche E!I FM" E#AMI$A"I%$ C%MMI""EE dr& C&M& 'oc(isch prof&dr&ir& M& A(sit )*&*+&,*-. Abstract "he current state of aspect/oriented programming 0A%1) has raised concerns regarding arious limitations that A%1 languages ha e& "he issue is that A%1 languages are not robust enough 3hen the basis program is changed& "here are many ne3 proposals for A%1 languages 3ith ne3 features that attempt to restrict or gi e more expressi eness to the programmer in order to force a ne3 context 3here the problems can be mitigated& Some of those languages are designed as extensions of AspectJ. Existing open AspectJ compilers can be used for implementing such an extension, but this can 5uic(ly become a complicated task of extending the complex processes of lexing4 parsing and 3ea ing4 of 3hich the compilers o6er lo3/le el abstractions& "hus4 there is a need for an easily extensible AspectJ foundation for a simpler and faster de elopment of language extensions& !e ha e de eloped such a foundation and in this thesis 3e describe the design of the implementation. !e pro ide an o er ie3 of a testing process to determine its alidity& Finally4 3e implement one proposal for an AspectJ extension and e aluate the extensibility and ease of use of our foundation in comparison to other existing AspectJ compilers& -& Introduction Moti ation& An easy approach to implement an aspect/oriented language 3ould be to extend an existing A%P compiler& "his is not al3ays the best approach4
    [Show full text]
  • Developing Java™ Web Applications
    ECLIPSE WEB TOOLS PLATFORM the eclipse series SERIES EDITORS Erich Gamma ■ Lee Nackman ■ John Wiegand Eclipse is a universal tool platform, an open extensible integrated development envi- ronment (IDE) for anything and nothing in particular. Eclipse represents one of the most exciting initiatives hatched from the world of application development in a long time, and it has the considerable support of the leading companies and organ- izations in the technology sector. Eclipse is gaining widespread acceptance in both the commercial and academic arenas. The Eclipse Series from Addison-Wesley is the definitive series of books dedicated to the Eclipse platform. Books in the series promise to bring you the key technical information you need to analyze Eclipse, high-quality insight into this powerful technology, and the practical advice you need to build tools to support this evolu- tionary Open Source platform. Leading experts Erich Gamma, Lee Nackman, and John Wiegand are the series editors. Titles in the Eclipse Series John Arthorne and Chris Laffra Official Eclipse 3.0 FAQs 0-321-26838-5 Frank Budinsky, David Steinberg, Ed Merks, Ray Ellersick, and Timothy J. Grose Eclipse Modeling Framework 0-131-42542-0 David Carlson Eclipse Distilled 0-321-28815-7 Eric Clayberg and Dan Rubel Eclipse: Building Commercial-Quality Plug-Ins, Second Edition 0-321-42672-X Adrian Colyer,Andy Clement, George Harley, and Matthew Webster Eclipse AspectJ:Aspect-Oriented Programming with AspectJ and the Eclipse AspectJ Development Tools 0-321-24587-3 Erich Gamma and
    [Show full text]
  • Flexibility at the Roots of Eclipse
    6°ÊÈ >ʽäÇ Dynamic Wizard Modeling with GMF Introduction to the Using GMF to Build a Dynamic Wizard Generic Eclipse Framework and a Graphical Editor Modeling System Developing a Deploying the BIRT Graphical Modeling Viewer to JBoss Tool for Eclipse Disseminate Report Content to an Application Server Subversive The Eclipse Enabling Plug-In for Integration and Subversion Interoperability for Eclipse based Development An Introduction to the Corona Project Flexibility at the Roots of Eclipse Solving the GUI Dilemma: SWTSwing and Eclipse on Swing 6°ÊÈ >ʽäÇ Vol.6 January 2007 Dynamic Wizard Modeling with GMF Introduction to the Using GMF to Build a Dynamic Wizard Generic Eclipse Table of Contents Framework and a Graphical Editor Modeling System Developing a Deploying the BIRT Graphical Modeling Viewer to JBoss Tool for Eclipse Disseminate Report Content to an Application Server Subversive The Eclipse Enabling Plug-In for Integration and Subversion FEATURES Interoperability for Eclipse based Development An Introduction to the Corona Project Flexibility at the Roots of Eclipse 29 Flexibility at the Roots of Eclipse Solving the GUI Dilemma: SWTSwing and Eclipse on Solving the GUI Dilemma: Swing SWTSwing and Eclipse on Swing No trench in the world of Java is deeper then that between SWT and Swing or Eclipse and Sun. Unity is only found in the knowledge that everybody suff ers from this argument. But how to end this almost religious battle over the righteous GUI-toolkit? How to bang their heads together if they only know DEPARTMENT one point of view—for them or against them! Th e sister projects SWTSwing and Eclipse on Swing News & Trends (EOS) achieve this trick.
    [Show full text]
  • Understanding and Characterizing Changes in Bugs Priority: the Practitioners’ Perceptive
    Understanding and Characterizing Changes in Bugs Priority: The Practitioners’ Perceptive Rafi Almhana Thiago Ferreira Marouane Kessentini Tushar Sharma Dept. of Computer Science Dept. of Computer Science Dept. Computer Science Research Scientist University of Michigan University of Michigan University of Michigan Siemens Corporate Technology [email protected] [email protected] [email protected] [email protected] Abstract—Assigning appropriate priority to bugs is critical for for automated validation of bug priority change requests, and timely addressing important software maintenance issues. An better documentation of these changes. The goal of this paper underlying aspect is the effectiveness of assigning priorities: if is to characterize the overall change process of bugs’ priority. the priorities of a fair number of bugs are changed, it indicates delays in fixing critical bugs. There has been little prior work We advocate that a critical and fundamental step in provid- on understanding the dynamics of changing bug priorities. In ing efficient support for managers and developers to enable this paper, we performed an empirical study to observe and them to validate bugs priority change is to understand the understand the changes in bugs’ priority to build a 3-W model bugs priority dynamics; it involves discover and characterize on Why and When bug priorities change, and Who performs the Why When Who change. We conducted interviews and a survey with practitioners and bug priorities change, and performs the as well as performed a quantitative analysis containing 225,000 change. Thus, the primary goal of this paper is to observe bug reports, developers’ comments, and source code changes and understand the changes in bugs priority to build a 3- from 24 open-source systems.
    [Show full text]
  • The Spring IDE Plug-In for Eclipse
    Minter_685-4App.fm Page 229 Wednesday, November 7, 2007 1:49 PM APPENDIX ■ ■ ■ The Spring IDE Plug-in for Eclipse The Spring IDE plug-in for Eclipse enhances the Eclipse environment by providing a variety of features that make it easier to work with Spring projects. The Spring IDE provides tools for creating, validating, viewing, and editing your Spring configuration files. A particu- larly attractive feature is the provision of autocompletion when editing bean definitions. Although the Spring IDE is a separate project from Spring itself, there are developers who participate in both projects, so there is excellent support for the latest Spring features. In this appendix, I discuss the installation of the Spring IDE and then briefly present the features related to editing and viewing bean and Spring Web Flow definitions. It is not possible to discuss all of the Spring IDE features in depth in this appendix. I would recommend installing and working with the plug-in initially as an aid to the creation of bean definition files. The autocompletion feature works in a manner nearly identical to the Java source autocompletion features. After you are familiar with these aspects of the plug-in, you should visit the Spring IDE website (http://springide.org/) to learn more about the tool. Installing the Plug-in Although it is possible to download the Spring IDE components and install them manually, by far the easiest way to install the Spring IDE into Eclipse is to use the built-in Software Updates feature of the Eclipse environment. Version 2 of the Spring IDE supports versions of Spring up to and including Spring 2.1 and up to version 1 of Spring Web Flow.
    [Show full text]
  • A Domain Specific Aspect Language for IDE Events Johan Fabry, Romain Robbes, Marcus Denker
    DIE: A Domain Specific Aspect Language for IDE Events Johan Fabry, Romain Robbes, Marcus Denker To cite this version: Johan Fabry, Romain Robbes, Marcus Denker. DIE: A Domain Specific Aspect Language for IDE Events. Journal of Universal Computer Science, Graz University of Technology, Institut für Informa- tionssysteme und Computer Medien, 2014, 20 (2), pp.135-168. hal-00936376 HAL Id: hal-00936376 https://hal.inria.fr/hal-00936376 Submitted on 25 Jan 2014 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. DIE: A Domain Specific Aspect Language for IDE Events Johan Fabry, Romain Robbes (PLEIAD Lab, Computer Science Department (DCC), University of Chile, Santiago, Chile {jfabry / rrobbes}@dcc.uchile.cl) Marcus Denker (RMoD, INRIA Lille Nord Europe Lille, France [email protected]) Abstract Integrated development environments (IDEs) have become the primary way to develop software. Besides just using the built-in features, it becomes more and more important to be able to extend the IDE with new features and extensions. Plugin architectures exist, but they show weaknesses related to unanticipated extensions and event handling. In this paper, we argue that a more general solution for extending IDEs is needed.
    [Show full text]