Fig 4 - uploaded by João Saraiva
Content may be subject to copyright.
Source publication
![Fig. 4. Major components in the Eclipse Platform (extracted from [4]).](profile/Joao-Saraiva-16/publication/235656071/figure/fig2/AS:669538370715659@1536641795793/Major-components-in-the-Eclipse-Platform-extracted-from-4_Q320.jpg)
The development of information systems is a complex task, involving technical, human and organizational issues. The results of this task are not always successful, which are apparent in the lack of software quality and in costs and schedules overruns. The ProjectIT research program addresses this specific task, however, taking different approaches...
Context in source publication
Context 1
... aside from the ones that developers can create. Figure 4 shows the major components in Eclipse. As an example of component usage, all Eclipse application that feature a graphical user in- terface will have dependencies to the WorkBench plug-in, which will also depend on the SWT (Standard Widget Toolkit) and on the JFace plug-ins. ...
Similar publications
The organizations dedicated to the development of software face a competitive scenario that constantly evaluates the success of the developed projects and the quality of the processes that are implemented in them. Several studies indicate that most software development projects fail mainly due to poor project management and the dissatisfaction of t...
Citations
... In addition, and because it promotes productivity, ProjectIT-Studio provides innovative features, such as requirements-to-models, models-to-models, models-to-code transformation techniques, template managing and UML profile definition. ProjectIT-Studio consists of an orchestration of plugins for Eclipse.NET as illustrated in Fig. 5. Eclipse.NET is an integration platform with a plugin-based architecture that provides an elegant and efficient mechanism to allow plugins to communicate, without making them depend on each other [27]. The ProjectIT-Studio tool provides three main plugins, which are discussed in the following subsections. ...
The suggestion that in software development projects the emphasis must be on the project management (RE), requirements engineering, and design activities, and consequently efforts in production activities - such as traditional software programming and testing - should be minimised and performed as automatically as possible is discussed. The Project IT approach that integrates contributions from the RE and model-driven engineering communities is also discussed. The goal with requirement specification is not just in managing textual specifications, but also to obtain a consistent requirements document that is in conformance with a domain-specific language, and that can be re-used to increase the design and development activities in the context of model driven and code generation techniques. Furthermore, the feasibility and benefits of this approach by presenting a proof-of-concept case study are discussed, in which the orchestration of the concepts and concrete components related with the Project IT approach, the PIT-RSL, XIS and PIT-TSL languages and the Project lT-Studio CASE tool is emphasised. A practical demonstration of the approach including the description of the system requirements, the design of the system, the use of code generation techniques, and how they integrate to improve and accelerate the software engineering lifecycle is presented.
... The generation's process is described onFigure 4 and has three main transformations: (1) T1 transforms conceptual model into XMI format. Several tools perform this transformation; (2) T2 transforms XMI into XML format based on scripts developed; (3) T3 produces automatically several artifacts from model specified in XML and with appropriate templates created in an inverse engineering process, we generate the modules of the IR system, which are linked the Eclipse Platform [12], a well-known and stable platform with widespread support in the Java community. Although commonly known to software developer community as an open-source IDE (Integrated Development Environment) for Java software development, Eclipse should be best described as " an open universal framework for building developer tools " [12]. ...
... Several tools perform this transformation; (2) T2 transforms XMI into XML format based on scripts developed; (3) T3 produces automatically several artifacts from model specified in XML and with appropriate templates created in an inverse engineering process, we generate the modules of the IR system, which are linked the Eclipse Platform [12], a well-known and stable platform with widespread support in the Java community. Although commonly known to software developer community as an open-source IDE (Integrated Development Environment) for Java software development, Eclipse should be best described as " an open universal framework for building developer tools " [12]. Consequently, programmers are involved to produce specific components, typically helper source code, such as facades, adapters, controllers and business logic. ...
MDIRS is methodology to define the actors and the steps to build efficiently information retrieval (IR) System. MDRIS main mission is to analyze, develop and evaluate mechanisms and tools to produce IR systems from a more abstract, high level, efficient and productive way than it is done currently. MDIRS project is influenced by MDA reference model, and is mainly based on three principles: namely, high-level models specification; generative programming techniques; and it is component-based architecture-centric. In this paper we detail the methodology generative programming techniques used to produce IR Systems and the work that will be handled in the near future.
... This same approach, but according to another perspective, can be applied having as its main goal the creation of a templates repository, thus supporting the concept of develop-for-reuse [28], whose main objective is to define a requirements documents templates catalog/library. These later templates, " architectural templates " , are based on re-factored requirements, hence improving their range of possible application, assuring simultaneously that they incorporate the best practices of requirements documents and use cases writing patterns [29] ...
We propose a new approach based on a methodology assisted by a IR-Case tool for the creation of IR (Information Retrieval) systems inspired on a set of best practices or principles: it is based on high-level models or specifications; it is component-based architecture centric; it is based on generative programming techniques. This approach follows in essence the MDA (Model Driven Architecture) philosophy with some specific characteristics. We propose a repository that keeps related information, such as models, applications, software architectures, generated artifacts and even information concerning the software process itself (e.g., generation steps, tests and integration milestones). Generically, this methodology receives system requirements (e.g., functional, non-functional and development requirements) as its main input, and produces a set of artifacts (e.g., source code, configuration scripts or data scripts) as its main output, that will be linked in the IR-Case tool proposed, generating the IR-System. These aspects are implemented in a tool (IR-Case tool), providing a roadmap where designers can follow as well as model-to-model transformation templates in order to accelerate their system development tasks. This step facilitates the construction and consequently will contribute for the personalized IR-Systems and also a test platform for IR-Algorithms and IR-Process.
... started an initiative in the area of requirements engineering and model-driven development named ProjectIT [6]. The main results of this project are: (1) a new requirements specification language, called ProjectIT-RSL ([7] and [8]); (2) a UML profile, called XIS (short name for " eXtreme modeling Interactive Systems " ), which was proposed and validated in previous work [9,10] and is now in its second version; and (3) a set of integrated tools, called ProjectIT-Studio [11], that supports the activities of the software development life cycle, from requirements specification to the application of generative programming techniques. Interactive systems are a sub-class of information systems that provide a large number of common features and functionalities, such as user-interfaces to drive the human-machine interaction, databases to keep the involved information consistent, and role-based access control to manage end-users and related permissions [25]. ...
... Besides minor issues, these versions showed that we lacked a common base platform for all our research: the work-around for this issue was accomplished with the port of the Eclipse platform to the .NET environment, called Eclipse.NET (at http://www.sourceforge.net/projects/eclipsedotnet ) [11,13]. Eclipse.NET is an integration platform with a plugin-based architecture that provides an elegant and efficient mechanism to allow plugins to communicate, without making them depend on each other [11]. ...
... ) [11,13]. Eclipse.NET is an integration platform with a plugin-based architecture that provides an elegant and efficient mechanism to allow plugins to communicate, without making them depend on each other [11]. Plugins can have two kinds of relations: (1) " imports " and (2) extension points. ...
Despite the efforts made to overcome the problems associated with the development of information systems, it is still an immature activity with negative consequences in time, budget and quality. One of the main causes for this situation is the fact that many projects do not follow a structured, standard and systematic approach, like the methodologies and best practices proposed by the Software Engineering community. In this paper, we overview an innovative approach for the development of information systems, called ProjectIT, and how it is supported by an integrated set of tools, called “ProjectIT-Studio”. This approach benefits from the ideas of some of the most referred initiatives, such as the Microsoft’s Dynamic Systems Initiative (DSI) or OMG’s Model Driven Architecture (MDA).
(Dissertation, in Portuguese, available at http://www.scribd.com/doc/103740062/ )
O ProjectIT é um programa de investigação do Grupo de Sistemas de Informação (GSI) do INESC-ID, que pretende tornar a utilização de boas práticas nos projectos de TI (Tecnologias de Informação) uma tarefa automática e transparente para a equipa de desenvolvimento. Este programa visa produzir duas ferramentas, o ProjectIT-Studio e o ProjectIT-Enterprise.
Uma das vertentes do ProjectIT consiste no ProjectIT-MDD, que se baseia no conceito de desenvolvimento baseado em modelos (MDD – Model Driven Development). O ProjectIT-MDD vem no seguimento de dois TFCs anteriores, que tiveram como resultado a ferramenta XIS-Tool.
Contudo, tem surgido no contexto do ProjectIT-Studio um grande problema: os seus sistemas (ProjectIT-MDD, ProjectIT-RSL, etc.) conseguem comunicar, mas não conseguem “trabalhar” juntas, i.e., o nível de integração destas ferramentas está muito abaixo do que seria desejável.
Neste TFC, foi proposta uma solução: uma conversão da plataforma Eclipse (disponível em Java) para .NET. Esta plataforma oferece um mecanismo de extensibilidade poderoso, mas incentiva ao mesmo tempo a modularidade e ao encapsulamento. A plataforma foi convertida, adaptada para a ferramenta ProjectIT-Studio, e a ferramenta XIS-Tool (agora designada “ProjectIT-MDD Tool”) foi integrada no ProjectIT-Studio.
Espera-se que este trabalho contribua significativamente para o esforço de desenvolvimento do ProjectIT e para a comunidade .NET. Caso a plataforma Eclipse.NET seja aceite pela comunidade .NET, pode mesmo evoluir para se tornar um standard no desenvolvimento de aplicações em .NET.
(Dissertation at http://www.scribd.com/doc/103738694/ )
ProjectIT is a collaborative research project, developed in the context of the Information Systems Group of INESC-ID, that integrates several final graduation works, MSc and PhD thesis. Its main objective is to provide a complete software development workbench, with support for activities such as project management, requirements engineering, analysis, design, and code generation. This objective is achieved through the implementation of a CASE tool, called ProjectIT-Studio, that covers all the stages of an IT product’s life-cycle.
The context of this work is ProjectIT-MDD, a functional component of ProjectIT that allows the visual specification of models and the automatic generation of artifacts from these models. After the previous work (which resulted in ”Eclipse.NET, an integration platform for ProjectIT-Studio”), this work focuses on the creation of an UML 2.0 visual modeling plugin for ProjectIT-Studio, fully integrated with the requirements and code-generation capabilities of ProjectIT-Studio, that allows the seamless transition from requirements specification to source-code generation according to current MDE approaches.
The main goals of this work are: (1) the development of an UML graphical modeling plugin for ProjectIT-Studio that provides features of a flexible UML modeling tool; (2) the complete integration of this plugin with the other plugins of ProjectIT-Studio; (3) the support of the UML Profile mechanism, in a way that is both simple and powerful; (4) the development of a mechanism that constantly monitors the syntactic and semantic consistency of a model, according to the UML Profiles applied to it; and (5) the preliminary development of a mechanism that allows the application of user-defined model-to-model transformations. Thus, the results of this work will allow ProjectIT-Studio users to quickly create visual models of information systems, and then supply these models as input to an automatic code generator.
