Let's talk about Modernization! Call +1 (425) 284-2770 or send us a Message!

COBOL

Quickly Modernize Your Mainframe Technology for AWS

Migrate to the cloud faster with TSRI's reusable process and scalable solution

Image

Seamlessly Migrate Valuable Mainframe Technology with TSRI's AWS-Certified Engineers and Architects

As an AWS partner, TSRI's certified engineers and architects get mainframe software into the cloud quickly leveraging our automated refactoring technology. Our near-100% automation process transforms legacy applications to Cloud native applications ready for deployment on AWS. Our model-based solution transforms even very large (tens of millions of lines of code) legacy systems written in languages like COBOL, Fortran, PowerBuilder, Ada, MUMPS, VB6, and more than 25 other languages, into modern applications in cloud native target architectures. The output is a multi-tier application, taking advantage of cloud utilities and scalability.

TSRI's Migration to AWS Cloud

TSRI has extensive experience in all forms of legacy code transformation, including migration to cloud services and containerization. TSRI can move the currently-modernized applications to the cloud using cloud-specific refactorings – targeting services, micro-services, and containerization. Our migration services take a three-step approach:

ImageMIGRATE MONOLITHIC APPLICATIONS TO SERVICE-ORIENTED APPLICATIONS

Migration of legacy monolithic code to a service-oriented environment. This includes updating language from COBOL to Java or C#, changing databases, and refactoring to enable microservices. This step begins the process of abstracting underlying services from the application.

ImageMIGRATE SERVICE-ORIENTED TO NATIVE-CLOUD SERVICES

Integration of service-oriented applications with native cloud services. This could include re-orienting code from, for example, WebSphere DB2 legacy platforms to Apache Tomcat and Amazon RDS. Upgrading to incorporate the latest native architectural interfaces ensures that applications are tightly integrated with the new environment, and ensures easier updates in future.

ImageNATIVE-CLOUD, DOCKER, KUBERNETES AND CONTAINERS, LAMBDA/API GATEWAY - SERVERLESS FRAMEWORK

Transformation of native cloud to Docker Containers. The movement to containers provides additional architectural abstraction and improved integration of applications within the cloud.

LEARN MORE

AWS Sample Target Stack

TSRI has already modernized many Mainframe applications directly to the cloud for quite a few customers! Below you can find a sample target stack that we have modernized to and deployed in the cloud. Here the application was refactored to utilize a MVC style architecture, introduced a RESTful layer and modularized, as well as, containerize the application itself. While this is a sample technology stack that we can immediately go to, we are happy to adapt our solution to fit your needs and requirements.

AWS Sample Reference Architecture

Below you will find a sample architecture diagram for some of the modernizations we have undertaken going to AWS. Here you can see that we implemented REST endpoints to expose online programs for legacy interfaces, such as CICS. Such REST endpoints also expose batch to Python client job, XDML and ETF files. Our Database Access Object (DAO) injection supports data servers and the ability to talk to the source database & target database (for example, DB2 & SQL Server on AWS Aurora at the same time - this allows for step wise go-live for not only parts of the application but also parts of the database and even users. This solution helps reduce risks and makes the go-live easier for our customers. 

When one goes from a Mainframe single monolithic architecture & environment to a multi-tier architecture distributed environment, performance issues are exposed at the I/O via profilers and then remediated via TSRI's refactoring capabilities, high-performance modern environments and also other technologies such as caching capabilities in the new modern environment (here you can see that REDIS cache addressed rountripping data access and scalability.

AWS Cloud Case Studies

For over 25 years, TSRI has focused on modernizing the world's most critical technology. From retail and financial systems to mission-critical military applications, TSRI has completed over 250+ projects including modernizations targeting private and public cloud architectures. We are pleased to bring our experience to AWS cloud migrations, and have achieved success on every past project with references available.

ImageImageImageImage

GET STARTED!

Case Study

United States Air Force SBSS ILS-S COBOL to Java on AWS Modernization

A major component of the system is 54 years old, written in COBOL, and provides retail-level business logic. The component runs on mainframes that have proven to be extremely difficult to change and manage, and the DoD needed to modernize the component to drive down operating costs and move to an open platform, while retaining all functionality....

by Phil de Valence, AWS

On behalf of a U.S. Department of Defense (DoD) client, our multi-company team—comprised of staff from ARRAY, NTT Data, TSRI, and Datum—delivered a successful modernization of a COBOL-based system running on aged mainframes to a Java-based system running on x86 Red Hat Enterprise Linux (RHEL).

The goals were to introduce agility, reduce costs, modernize the technical stack, and enhance security by leveraging Amazon Web Services (AWS). We did this using automated code conversion tools and techniques while maintaining all functionality, screens, and reports.

The modernization target was AWS GovCloud (US) in order to address the DoD’s stringent security and compliance requirements such as U.S. citizenship.

The system we modernized is an ACAT III Major Defense Acquisition Program and mission-critical system used by more than 18,000 users at over 260 global locations. It provides daily supply chain and equipment support for DoD missions and is the accountable data system for over $30 billion in inventory.

AWS provides the system’s capabilities for reliability, scalability, and availability with features such as Availability Zones (AZs), Auto Scaling Groups, and Amazon Relational Database Service (Amazon RDS).

In this post, we describe the objectives, approach, solution, lessons, and customer benefits realized from this experience. ARRAY Information Technology is an AWS Partner Network (APN) Standard Consulting Partner.

Context and Objectives

A major component of the system is 54 years old, written in COBOL, and provides retail-level business logic. The component runs on mainframes that have proven to be extremely difficult to change and manage, and the DoD needed to modernize the component to drive down operating costs and move to an open platform, while retaining all functionality.

In the past, attempts made to modernize the component failed due to the massive size and complexity of the task. In fact, modernizing the component was regarded as such a difficult task that it was highlighted in the 2003 book Modernizing Legacy Systems: Software Technologies, Engineering Processes, and Business Practices.

After 54 years of operations, maintenance, and extensions, the component’s code had become poorly documented. The technical design of the existing system, which was needed to support the modernization effort, had to be derived from the existing system and code.

Key characteristics of this component included:

  • Annual operating costs over $30 million, largely attributable to mainframe hosting and maintenance costs.
  • 1.3 million lines of COBOL Source Lines of Code (SLOC).
  • A data management system, comprised of 1.2 million lines of COBOL code, supporting approximately 500,000 transactions per day.
  • Few remaining subject matter experts (SMEs).
  • Difficulty finding qualified, affordable COBOL programmers.

The component needed to be modernized and migrated to an affordable open system and hosting environment, with no down-time, data loss, functionality loss, performance loss, and minimal mission risk. The DoD had never done anything like this.

Modernization Approach and Solution

Our team developed a trusted relationship with the DoD’s Project Management Office over several years by delivering solutions that transformed and improved their supply mission. In 2015, the DoD contracted our team to modernize the component to become an integrated and sustainable part of the overall system.

We started the project by identifying and evaluating solution options:

  • A total manual rewrite and re-architecting solution failed to meet the program’s time constraints, had historically low success rates (high risk), and would have been too costly.
  • A replacement solution was not selected because the DoD needed to retain all the current business rules.
  • A COBOL emulator re-host solution was a stopgap measure that failed to reach the J2EE/RHEL/SQL DB architectural future state requirement.

This analysis led to our decision to use a COBOL-to-Java code automated refactoring solution. This option would take a low-risk, incremental approach and apply a blended agile/traditional methodology and tools to ensure rapid, high-quality software delivery.

Component Modernization Phases

Once the COBOL-to-Java code automated refactoring solution was selected, a three-phase approach emerged to meet the entirety of the DoD’s requirements and cost, schedule, and risk constraints.

  • Phase 1 (18 months): COBOL-to-Java code automated refactoring to x86/RHEL platform 
    This was the most complex and risky phase, as we automatically refactored COBOL code from mainframes to Java code on a virtualized x86 RHEL platform while not losing any functionality or performance. The resulting Java code contained design remnants of COBOL, and development and test environments were moved to the AWS Cloud.
  • Phase 2 (12 months): Code advanced refactoring to remove COBOL design overtones 
    We refactored the Java codebase even more to remove residual COBOL remnants, overtones, and design elements to improve maintainability.
  • Phase 3  (3 months): Infrastructure moved to AWS GovCloud (US)
    We moved all remaining environments to AWS GovCloud (US) including staging and production. AWS GovCloud (US) allowed us to meet the many cyberthreat security requirements for the DoD.

Figure 1 shows our three-phrase modernization approach. The two Java logos illustrate the different Java phases. At the end of Phase 1, the Java program is “dirty” with remaining COBOL coding practices. At the end of Phase 2, the Java program is “clean” without COBOL remnants.

Array-1.1

Figure 1 – ARRAY’s three-phase modernization approach met the DoD’s stringent requirements.

Phase 1: Automated Refactoring of COBOL to Java on x86

The modernization of the component involved a conversion of 1,260,679 lines of COBOL code and 10,078 lines of C code to Java to maintain current application capabilities, Graphical User Interface (GUI), and performance while migrating to an affordable and sustainable x86 RHEL platform.

The component’s COBOL online and batch applications were automatically refactored to run on a JEE platform using Java object-oriented software layers (data access, presentation, business logic) and patterns to enable migration to a standard x86 architecture.

The modernized Java software reused identifier names from the original COBOL application, allowing the component SMEs to read and understand the new Java code and routines more easily.

Rather than simply transliterating source COBOL code to target Java code, the tool executes a mature automated conversion and refactoring process by first constructing a comprehensive Intermediate Object Model of the legacy system in an intermediate translation language.

Once modeled within the tool engine, SMEs employ an iterative process of applying rules and tuning to output the transformed code into the target Java language.

We completed the work of reintegrating items like schedulers and other utilities, testing the initial construction iterations of the code, and providing defects. In response to each construction delivery evaluation, we adapted the transformation rules and regenerated improved construction iterations of the code according to internal evaluations.

During this phase, the COBOL Data Management System network database code was transformed to COBOL with SQL. This COBOL and SQL code was then transformed to Java and SQL code.

Array-2

Figure 2 – The component COBOL automated refactoring to Java.

Phase 2: Advanced Refactoring to Remove COBOL Design Overtones

After we completed Phase 1, the resulting converted Java code contained COBOL paradigm design remnants, or COBOL overtones, that required personnel to have specialized skills to maintain the codebase. A plan was developed to identify and correct COBOL overtones with standard Java solutions. This part of the effort was considered low-risk because we used approaches, processes, and techniques proven in Phase 1.

Our refactoring approach used the TSRI JANUS Studio tool and a semi-automated refactoring method that performs further code optimization, naming changes, and other enhancements to improve architecture, design, security, sustainability and performance.

We used an iterative approach consisting of tool-driven automated refactoring, regression testing, and customer review to address the four most significant COBOL overtones existing in the component’s Java codebase:

  • Refactoring the COBOL Memory Model to Java
  • Refactoring the COBOL data mapping layer to native Java and SQL
  • Removing COBOL-style control-flow/GOTO Logic
  • Identifying and removing redundant code sections

These techniques, along with the improved method synthesis algorithm, greatly improved the maintainability of the Java codebase.

Array-3

Figure 3 – The component refactored to maintainable Java.

Phase 3: Infrastructure Moved to AWS

After Phase 2 was completed, the entire component was moved to AWS GovCloud (US) including the staging, production, and all support environments.

AWS GovCloud (US) was selected because it aligned with the future technical direction of the system. This included cybersecurity, DevOps, and automated continuous integration (CI) and continuous delivery (CD) tools. The component’s architecture was installed in AWS GovCloud (US) and continues to evolve.

Array-4

Figure 4 – The component moved to Amazon Web Services (AWS).

Customer Benefits

For the DoD, the component has been transformed from an expensive mainframe COBOL legacy system to an affordable, modern maintainable Java-based system. All valuable existing business rules have been preserved in the modernized system, while development, test, and production environments were migrated to AWS providing flexibility at reduced cost.

The DoD’s projected cost savings is $25 million per year, and they are now able to use popular Java programmers to maintain and enhance the critical component.

Lessons Learned

This project taught the DoD that automated refactoring projects are a viable approach to modernize major legacy systems, including complex COBOL-based mainframes, to preserve the existing business rules within a cost-effective, open system.

We can highlight specific lessons learned during this project:

  • Code conversions via automated refactoring are a low-risk approach to modernize away from legacy platforms and migrate to the AWS Cloud.
  • Breaking efforts into phases (modernize, migrate, etc.) keeps risk low and ensures mission success.
  • Breaking away from legacy COBOL enable a completely new set of sustainment opportunities, such as labor and tooling.
  • Agile development models enable real-time course corrections and reduce delivery risk.
  • Maximum automation is crucial in order to transform millions of lines of code while preserving functional equivalence, reducing risks, and reducing the project timeline.
  • The Java language target allows choosing from a wide range of cost-efficient reliable compute options. In this case, it allowed the elasticity and scalability to meet the mission-critical DoD system needs.
  • Moving away from legacy proprietary mainframe and COBOL to an open Java platform allows access to a large pool of talented architects and specialists for design and operation.
  • Suppressing proprietary COBOL technologies allows more cost-efficient and reliable application servers and databases

If you want to learn more about this project or any of our other 200 successful major modernization projects, please give us a call at 425-284-2800 or send us an email at This email address is being protected from spambots. You need JavaScript enabled to view it.

 

Use Near 100% Automation to Transform PowerBuilder to Object-Oriented Java or C#. 

TSRI's automated model-based toolset, JANUS Studio®, transforms small, medium, and large (tens of millions of lines of code) PowerBuilder systems to modern languages with little to no manual intervention.  The resulting code is object-oriented, compiling, integration-ready, uniform, and native target language code, and is produced very quickly.  Ready to learn more?  Contact us to receive more information, see a demonstration, or have a conversation. 

PowerBuilder Modernization Past Performance 

TSRI has completed over 150+ major past projects in our 2 decades of operation, including PowerBuilder modernizations like the R-Supply portion of the NTCSS system for the US Navy (highly complex, transformed to multiple languages and target architectures for testing purposes), government tax systems for a European government project (part of a 29 million line of code modernization), and many others.  TSRI has achieved success on every past project, and offers references for all past projects completed, as well as case studies on many projects.  Ready to learn more?  Contact us to receive more information, see a demonstration, or have a conversation. 

Separate and Transform DataWindows and Screens Simultaneously

TSRI's toolset and process allows for the simultaneous modeling and automated transformation of Datawindows, including those generated dynamically, as part of our modernization process. Using our toolset, JANUS Studio, TSRI can isolate screen generation logic from the application logic, and demonstrate the 100% automated generation of modernized screens in a responsive web UI. These screens can then be regenerated using a customer's preferred style sheets--again, without any manual intervention on the code itself. Ready to learn more?  Contact us to receive more information, see a demonstration, or have a conversation. 

Eliminate Unecessary License Fees. 

Remove costly, proprietary runtime annual license fees by transforming to "license-fee free" Java or C# code.  TSRI's transformed code carries no costly proprietary runtime fees.   Ready to learn more?  Contact us to receive more information, see a demonstration, or have a conversation. 

Transform Monolithic PowerBuilder Systems to Multi-Tier / Thin-Client / Cloud Enabled / Microservices Architectures

TSRI's transformation and refactoring process produces, as a standard output, a multi-tier architecture with DAO layer, presentation (UI) layer, and application logic layer, and can target a variety of cloud architectures including Amazon Web Services (AWS), Azure, private & government cloud, and others.  With additional refactoring, TSRI can break monolithic PowerBuilder systems into microservices according to a customer's specifications. Ready to learn more?  Contact us to receive more information, see a demonstration, or have a conversation. 

Eliminate Vintage Hardware. 

Move off legacy hardware and reduce operational and maintenance (O&M) expenses, and eliminate a variety of associated license fees.  Reduce your hardware failure risk and footprint and move to high performance computing systems.  Ready to learn more?  Contact us to receive more information, see a demonstration, or have a conversation. 

Retarget Existing Databases or Transform Sybase (or other Databases) to New Targets

While modernizing the application logic, TSRI offers customers the options of retaining the existing database or moving your Sybase (or other database) to a new target, including SQL Server, Oracle, or open source databases.  Ready to learn more?  Contact us to receive more information, see a demonstration, or have a conversation. 

Generate "As-Is" PowerBuilder System Documentation, or "Bridge Documentation" with Side-By-Side Display of PowerBuilder and Modern Code

Either as a standalone project or part of a transformation project, TSRI produces fully automated code-level UML documentation of the structure and flow of the PowerBuilder logic, as well as "To-Be" or "Bridge Documentation" showing side-by-side, hyperlinking displays of the PowerBuilder and the Java or C#.  This documentation allows developers familiar with the PowerBuilder system to easily continue maintaining the modernized target system, and includes graphs like Control Flow, Cause Effect, Data Flow, State Transition Tables, Complexity Analysis, and more.  TSRI can demonstrate this documentation, for free, simply by receiving some of your code (under NDA).  Ready to learn more?  Contact us to receive more information, see a demonstration, or have a conversation. 

Refactor to Eliminate Dead and Redundant Code, and Consolidate Similar Code.

TSRI's model-based toolset allows for fully automated remediation of dead and redundant code, as well as the consolidation of similar statements and methods to improve maintainability.  Because this process operates on the model level, functional equivalence is preserved during all refactoring.   Ready to learn more?  Contact us to receive more information, see a demonstration, or have a conversation. 

Automated Test Support to Ensure Functional Equivalence.  

In addition to automated testing support, TSRI provides a comprehensive warranty on all PowerBuilder code transformed.  TSRI typically transforms to a functional equivalent, compiling, integration-ready target, and supports the testing process through the use of our automated tools.  Ready to learn more?  Contact us to receive more information, see a demonstration, or have a conversation. 

 

Use 100% Automation to Transform Ada to Object-Oriented Java, C++, or C#. 

TSRI's automated model-based toolset, JANUS Studio®, transforms systems of all sizes (even very large systems counting tens of millions of lines of code) from Ada to modern languages, without any manual intervention on the code.  The resulting code is object-oriented, compiling, integration-ready, uniform and native target language code, produced very quickly by automated technology.  Ready to learn more?  Contact us to receive more information, see a demonstration, or have a conversation. 

Extensive Ada Modernization Past Performance 

TSRI has completed over 150+ major past projects in our 2 decades of operation, including Ada modernizations like the European Air Traffic Management System (in use across Europe and Australia tracking commercial airliners), 5.5 million lines of Ada in the Advanced Field Artillery Tactical Data System (AFATDS) for the US Army, Aircraft avionics systems in multiple aircraft, and many others.  TSRI has achieved success on every past project, and offers references for all past projects completed, as well as case studies on many projects.  Ready to learn more?  Contact us to receive more information, see a demonstration, or have a conversation. 

Generate "As-Is" Ada System Documentation, or "Bridge Documentation" with Side-By-Side Display of Ada and Modern Code

Either as a standalone project or part of a transformation project, TSRI produces fully automated code-level UML documentation of the structure and flow of the Ada system, as well as "To-Be" or "Bridge Documentation" showing side-by-side, hyperlinking displays of the Ada and the Java, C++ or C#.  This documentation allows developers familiar with the Ada system to easily continue maintaining the modernized target system, and includes graphs like Control Flow, Cause Effect, Data Flow, State Transition Tables, Complexity Analysis, and more.   Ready to learn more?  Contact us to receive more information, see a demonstration, or have a conversation. 

Automated Test Support to Ensure Functional Equivalence.  

In addition to automated testing support, TSRI provides a comprehensive warranty on all Ada code transformed.  TSRI uses automation to transform to a functional equivalent, compiling, integration-ready target code, and supports the testing process through the use of our automated tools.  Ready to learn more?  Contact us to receive more information, see a demonstration, or have a conversation. 

Transition Ada Generics  

After dozens of projects modernizing Ada language systems, TSRI can inline Ada generics or convert them to Java generics or C++ templates.  In some cases, the Ada generic can become a non-generic/non-template depending on the original code.  TSRI also has existing libraries to support the Ada tasking and rendezvous constructs.  Ready to learn more?  Contact us to receive more information, see a demonstration, or have a conversation. 

Transition to New Hardware. 

Move off legacy platforms and reduce operational and maintenance (O&M) expenses, by moving to a language like Java, C++, or C# that can run on modern hardware.  Reduce your hardware failure risk and footprint and move to high performance computing systems.  Ready to learn more?  Contact us to receive more information, see a demonstration, or have a conversation. 

Retarget Existing Databases or Transform VSAM, ISAM, IMS, or Flat File Databases to New Targets

While modernizing the application logic, TSRI offers customers the options of retaining the existing database or moving your database to a new target, including SQL Server, Oracle, or open source databases.  Ready to learn more?  Contact us to receive more information, see a demonstration, or have a conversation. 

Refactor to Eliminate Dead and Redundant Code, and Consolidate Similar Code.

TSRI's model-based toolset allows for fully automated remediation of dead and redundant code, as well as the consolidation of similar statements and methods to improve maintainability.  Because this process operates on the model level, functional equivalence is preserved during all refactoring.   Ready to learn more?  Contact us to receive more information, see a demonstration, or have a conversation. 

 

Use 100% Automation to Transform Legacy Applications to Cloud Native Applications in AWS, Azure, OpenStack, BlueMix, DISA, or Other Cloud Architectures

TSRI's automated model-based toolset, JANUS Studio®, transforms even very large (tens of millions of lines of code) legacy systems written in languages like COBOL, Fortran, PowerBuilder, Ada, MUMPS, VB6, and more than 25 other languages, into modern applications in cloud native target architectures.  The output is a multi-tier application, taking advantage of cloud utilities and scalability.    Ready to learn more?  Contact us to receive more information, see a demonstration, or have a conversation. 

Extensive Modernization Past Performance Targeting New Architectures

TSRI has completed over 150+ major past projects in our 2 decades of operation, including modernizations targeting private and public cloud architectures.  TSRI has achieved success on every past project, and offers references for all past projects completed, as well as case studies on many projects.  Ready to learn more?  Contact us to receive more information, see a demonstration, or have a conversation. 

Achieve Scalability and Interoperability

TSRI can help bring legacy systems into highly scalable, flexible cloud platforms.   Ready to learn more?  Contact us to receive more information, see a demonstration, or have a conversation. 

Transform Sub & Related Languages (JCL, DCL, CICS, IMS, SQL, EasyTrieve, Assembly & others) Simultaneously

TSRI's toolset and process allows for the simultaneous modeling and automated transformation of other languages commonly present in legacy systems. Many of our clients have large systems which consist of many languages & sublanguages. Our process allows to target one single or multiple output languages with one uniform codebase. For example, a COBOL system can be modernized to Java, C#, C++ & others, including the JCL, which can be transformed to Python, C#, Java, or other scripting languages, per the customer requirements. Ready to learn more?  Contact us to receive more information, see a demonstration, or have a conversation. 

Eliminate Unnecessary License Fees. 

Remove costly, proprietary runtime annual license fees by transforming to "license-fee free" Java, C++, or C# code.  TSRI's transformed code carries no costly proprietary runtime fees.   Ready to learn more?  Contact us to receive more information, see a demonstration, or have a conversation. 

Transform Monolithic Legacy Systems to Multi-Tier / Thin-Client / Microservices Architectures

TSRI's transformation and refactoring process produces, as a standard output, a multi-tier architecture with DAO layer, presentation (UI) layer, and application logic layer, and enables a variety of cloud architectures including Amazon Web Services (AWS), Azure, private & government cloud, and others.  With additional refactoring, TSRI can break monolithic systems into microservices according to a customer's specifications. Many of these refactorings can be automated, reducing time and effort.   Ready to learn more?  Contact us to receive more information, see a demonstration, or have a conversation. 

Eliminate the Mainframe. 

Move off mainframe systems and reduce operational and maintenance (O&M) expenses, and eliminate a variety of associated license fees.  Reduce your hardware failure risk and footprint and move to high performance computing systems.  Ready to learn more?  Contact us to receive more information, see a demonstration, or have a conversation. 

Transform Green Screen MFS or BFS Screens Into Responsive HTML5 Web Displays

TSRI's past work has targeted a variety of modern web presentation layers, terminal emulators (perhaps to retain existing screen scrapers), or both.  Our customer-driven process allows you to decide the right target presentation layer for your modernized system.  Ready to learn more?  Contact us to receive more information, see a demonstration, or have a conversation. 

Retarget Existing Databases or Transform VSAM, ISAM, IMS, or Flat File Databases to New Targets

While modernizing the application logic, TSRI offers customers the options of retaining the existing database or moving your database to a new target, including SQL Server, Oracle, or open source databases.  Ready to learn more?  Contact us to receive more information, see a demonstration, or have a conversation. 

Generate "As-Is" Legacy System Documentation, or "Bridge Documentation" with Side-By-Side Display of Legacy and Modern Code

Either as a standalone project or part of a transformation project, TSRI produces fully automated code-level UML documentation of the structure and flow of the COBOL system, as well as "To-Be" or "Bridge Documentation" showing side-by-side, hyperlinking displays of the COBOL and the Java, C++ or C#.  This documentation allows developers familiar with the COBOL system to easily continue maintaining the modernized target system, and includes graphs like Control Flow, Cause Effect, Data Flow, State Transition Tables, Complexity Analysis, and more.   Ready to learn more?  Contact us to receive more information, see a demonstration, or have a conversation. 

Refactor to Eliminate Dead and Redundant Code, and Consolidate Similar Code.

TSRI's model-based toolset allows for fully automated remediation of dead and redundant code, as well as the consolidation of similar statements and methods to improve maintainability.  Because this process operates on the model level, functional equivalence is preserved during all refactoring.   Ready to learn more?  Contact us to receive more information, see a demonstration, or have a conversation. 

Thank you for your interest in TSRI's webinar series!

Please provide your information below to learn about our next webinar dates and to receive notifications about upcoming topics.

We look forward to answering your questions and hope you will enjoy our webinar series!

TSRI’s CEO, Mr. Philip Newcomb will be leading a complimentary special seminar on Architecture-Driven Modernization Best Practices on June 8th at the OMG Technical Meetings in Belgium. 
 

DATE: June 8, 2017

TIME: 1-4pm CEST

The ADM seminar is created for organizations looking for a way to reduce their burdensome O&M software and system operating costs and is a comprehensive introduction to the extensive body of practice, theory and standards developed by the ADM Task Force.  

Learn More About the Seminar

Mr. Newcomb will be your personal guide on how to migrate your applications to the Cloud.

Don’t miss out on this opportunity to learn from an expert.

This is a must-attend event for CIOs, CISOs, CTOs and other IT decision makers.

Register Today!

We look forward to seeing you in Belgium!

 

Sincerely,

The TSRI Team!

 

Eclipse Indigo

Acceleo can be downloaded and installed in a number of ways. If you have an existing Eclipse installation and simply wish to install Acceleo in it, Installing through the update site is the easiest way. If you'd rather install a new Eclipse with Acceleo, you may want to take a look at the facilities provided by the amalgamation project. Acceleo  Accessibility Tools Framework

EEF  The Extended Editing Framework aims at giving another way to improve the EMF model creation phase by providing new services dedicated to editing and using more appealing editing elements. The way to obtain these services and elements is based on a generative approach similar to the EMF.Edit one. The framework provides advanced editing components for the properties of EMF elements and a default generation based on standard metamodels using these components. The generic generators create a standard architecture with advanced graphical components to edit EMF model objects. These components are meant to leverage every aspects of the Eclipse Platform as for instance the Eclipse Dynamic Help. Agent Modeling Platform

The Amalgamation project provides improved packaging, integration, and usability of Modeling project components. The project is focused on providing a consumable and integrated Eclipse Modeling Tools package and ease the discovery of the modeling technologies through specific code and examples. Amalgamation ATL (ATL Transformation Language) is a model transformation language and toolkit. In the field of Model-Driven Engineering (MDE), ATL provides ways to produce a set of target models from a set of source models.  Developed on top of the Eclipse platform, the ATL Integrated Environnement (IDE) provides a number of standard development tools (syntax highlighting, debugger, etc.) that aims to ease development of ATL transformations. ATL BIRT is an open source Eclipse-based reporting system that integrates with your Java/Java EE application to produce compelling reports. BIRT Project  CDT Project
CDO is both a development-time model repository and a run-time persistence framework. Being highly optimized it supports object graphs of arbitrary size.  Model Repository

"Data Tools" is a vast domain, yet there are a fairly small number of foundational requirements when developing with or managing data-centric systems. A developer is interested in an environment that is easy to configure, one in which the challenges of application development are due to the problem domain, not the complexity of the tools employed. Data management, whether by a developer working on an application, or an administrator maintaining or monitoring a production system, should also provide a consistent, highly usable environment that works well with associated technologies. Data Tools Platform

The Amalgamation project provides improved packaging, integration, and usability of Modeling project components. The project is focused on providing a consumable and integrated Eclipse Modeling Tools package and ease the discovery of the modeling technologies through specific code and examples. Dynamic Languages Toolkit ECF is a framework for building distributed servers, applications, and tools. It provides a modular implementation of the OSGi 4.2 Remote Services standard, along with support for REST-based and SOAP-based remote services, and asynchronous messaging for remote services. Eclipse Communication Framework EGF: a Software Production Framework  A major concern in software engineering is to deliver on time with the expected level of quality, while requirements and development environments evolve and are more and more complex. In order to meet those needs, generation is a means which avoids wasting time and efforts. The purpose of EGF is to provide an extensible model-based generation framework and to support complex, customizable and integrated generations. Eclipse Generation Factories EGit is an Eclipse Team provider for the Git version control system. Git is a distributed SCM, which means every developer has a full copy of all history of every revision of the code, making queries against the history very fast and versatile.  EGit  Eclipse Gyrex Project

Create entry level downloads based on defined user profiles. The project defined and created the EPP downloads of Java Developer, Java EE Developer, C/C++ Developer and RCP Developer. These downloads are available from the main Eclipse download page. Please follow this description if you want to be a package maintainer. Eclipse Packaging Project

The EclipseLink project delivers a comprehensive open-source Java persistence solution addressing relational, XML, and database web services.  Eclipse Link Project The Ecore Tools component provides a complete environment to create, edit and maintain Ecore models. This component eases handling of Ecore models with a Graphical Ecore Editor and bridges to other existing Ecore tools (Validation, Search, Compare, Emfatic, generators...). The Graphical Ecore Editor implements multi-diagram support, a custom tabbed properties view, validation feedbacks, refactoring capabilities... The long-term goal is to provide the same level of services as does JDT for Java.  Ecore Tools EMF - The core EMF framework includes a meta model (Ecore) for describing models and runtime support for the models including change notification, persistence support with default XMI serialization, and a very efficient reflective API for manipulating EMF objects generically. EMF EMF Compare provides comparison and merge facility for any kind of EMF Model. It includes a generic comparison engine, the ability to export differences in a model patch and it is integrated with the Eclipse Team API meaning that it enable collaborative work on models using CVS, SVN and GIT EMF Compare  EMF Facet The query component provides capabilities to specify and execute queries against EMF model elements and their contents. EMF Query
The transaction component provides the following capabilities.     Multi-threading - Supports a protocol for clients to read and write EMF models on multiple threads.     Model Integrity - Semantic integrity is ensured by automatic validation to detect invalid changes and semantic procedures to proactively maintain correctness of semantic dependencies.     Batched Events - Clients are notified of groups of related changes in batches, rather than as a stream of EMF notifications. In particular, this allows applications to analyze change sets in their entirety.     Undo/Redo - For a simplified programming model, the API automatically tracks changes applied to models without the need for client code to use EMF edit Commands. These changes are encapsulated in transactions/operations that can undo and redo themselves.     Editing Domain - Support cooperative editing of models by multiple editors/applications. EMF resources can be shared amongst different editing domains.     Eclipse Workspace - The API provides traceability between EMF resources and workspace resources. Multi-threaded access is coordinated via the Eclipse jobs API and its integration with the workspace.     Eclipse Operations - The API supports the Eclipse operation history as an undo stack for undo/redo of resource changes. The API provides a framework for undoable operations that automatically capture undo/redo information, which can be interleaved on the same history with dependent operations that do not modify the EMF model.  The transaction component provides the following capabilities.      Multi-threading - Supports a protocol for clients to read and write EMF models on multiple threads.     Model Integrity - Semantic integrity is ensured by automatic validation to detect invalid changes and semantic procedures to proactively maintain correctness of semantic dependencies.     Batched Events - Clients are notified of groups of related changes in batches, rather than as a stream of EMF notifications. In particular, this allows applications to analyze change sets in their entirety.     Undo/Redo - For a simplified programming model, the API automatically tracks changes applied to models without the need for client code to use EMF edit Commands. These changes are encapsulated in transactions/operations that can undo and redo themselves.     Editing Domain - Support cooperative editing of models by multiple editors/applications. EMF resources can be shared amongst different editing domains.     Eclipse Workspace - The API provides traceability between EMF resources and workspace resources. Multi-threaded access is coordinated via the Eclipse jobs API and its integration with the workspace.     Eclipse Operations - The API supports the Eclipse operation history as an undo stack for undo/redo of resource changes. The API provides a framework for undoable operations that automatically capture undo/redo information, which can be interleaved on the same history with dependent operations that do not modify the EMF model. EMF Transaction

Validation Framework  The validation component provides the following capabilities.  	Constraint Definition - Provides API for defining constraints for any EMF meta-model (batch and live constraints). 	Customizable model traversal algorithms - Extensibility API to support meta-models that require custom strategies for model traversal. 	Constraint parsing for languages - Provides support for parsing the content of constraint elements defined in specific languages. The validation framework provides support for two languages: Java and OCL. 	Configurable constraint bindings to application contexts - API support to define "client contexts" that describe the objects that need to be validated and to bind them to constraints that need to be enforced on these objects. 	Validation listeners - Support for listening to validation events.   The validation component provides the following capabilities.      Constraint Definition - Provides API for defining constraints for any EMF meta-model (batch and live constraints).     Customizable model traversal algorithms - Extensibility API to support meta-models that require custom strategies for model traversal.     Constraint parsing for languages - Provides support for parsing the content of constraint elements defined in specific languages. The validation framework provides support for two languages: Java and OCL.     Configurable constraint bindings to application contexts - API support to define "client contexts" that describe the objects that need to be validated and to bind them to constraints that need to be enforced on these objects.     Validation listeners - Support for listening to validation events. EMF Validation

From a code point of view, Equinox is an implementation of the OSGi R4 core framework specification, a set of bundles that implement various optional OSGi services and other infrastructure for running OSGi-based systems.  More generally, the goal of the Equinox project is to be a first class OSGi community and foster the vision of Eclipse as a landscape of bundles. As part of this, it is responsible for developing and delivering the OSGi framework implementation used for all of Eclipse. In addition. the project is open to:  	Implementation of all aspects of the OSGi specification (including the EEG, MEG and VEG work) 	Investigation and research related to future versions of OSGi specifications and related runtime issues 	Development of non-standard infrastructure deemed to be essential to the running and management of OSGi-based systems 	Implementation of key framework services and extensions needed for running Eclipse (e.g., the Eclipse Adaptor, Extension registry) and deemed generally useful to people using OSGi. Equinox

EEF  The Extended Editing Framework aims at giving another way to improve the EMF model creation phase by providing new services dedicated to editing and using more appealing editing elements. The way to obtain these services and elements is based on a generative approach similar to the EMF.Edit one. The framework provides advanced editing components for the properties of EMF elements and a default generation based on standard metamodels using these components. The generic generators create a standard architecture with advanced graphical components to edit EMF model objects. These components are meant to leverage every aspects of the Eclipse Platform as for instance the Eclipse Dynamic Help. Extended Editing Framework

GEF (Graphical Editing Framework)  The Graphical Editing Framework (GEF) provides technology to create rich graphical editors and views for the Eclipse Workbench UI. It bundles three components:      Draw2d (org.eclipse.draw2d) - A layout and rendering toolkit for displaying graphics on an SWT Canvas.     GEF (MVC) (org.eclipse.gef) - An interactive model-view-controler (MVC) framework, which fosters the implementation of SWT-based tree and Draw2d-based graphical editors for the Eclipse Workbench UI.     Zest (org.eclipse.zest) - A visualization toolkit based on Draw2d, which enables implementation of graphical views for the Eclipse Workbench UI. Graphical Editing Framework

Graphiti - a Graphical Tooling Infrastructure  Eclipse provides a modeling infrastructure evolving around the Eclipse Modeling Framework (EMF) for which offering graphical representations and editing possibilities is essential. Graphiti

Java Workflow Tooling (JWT)  Eclipse SOA's Java Workflow Tooling project (JWT) provides design time, development time and runtime workflow tools. It also fosters interoperability between Business Process Management (BPM) platforms and integration in Information Systems thanks to Service Oriented Architecture (SOA).  Java Workflow Tooling

 Jetty

The Linux Tools project aims to bring a full-featured C and C++ IDE to Linux developers. We build on the source editing and debugging features of the CDT and integrate popular native development tools such as the GNU Autotools, Valgrind, OProfile, RPM, SystemTap, GCov, GProf, LTTng, etc. Current projects include LTTng trace viewers and analyzers, an RPM .spec editor, Autotools build integration, a Valgrind heap usage analysis tool, and OProfile call profiling tools.  The project also provides a place for Linux distributions to collaboratively overcome issues surrounding distribution packaging of Eclipse technology. The project produces both best practices and tools related to packaging. Since our 0.3.0 release, one of our features is a source archive of the Eclipse SDK that can be used by all Linux distributions building and distributing it.  Linux Tools

Introducing the Eclipse Marketplace Client What is the Eclipse Marketplace Client  Eclipse Marketplace Client (MPC) is a rich client interface for browsing and installing the Eclipse based solutions listed on the Eclipse Marketplace portal. It is a new feature that allows Eclipse users to discover and install Eclipse solutions directly into their Eclipse installation.  Marketplace Client Maven Integration (m2e)  The goal of the m2ec project is to provide a first-class Apache Maven support in the Eclipse IDE, making it easier to edit Maven's pom.xml, run a build from the IDE and much more. For Java developers, the very tight integration with JDT greatly simplifies the consumption of Java artifacts either being hosted on open source repositories such as Maven Central, or in your in-house Maven repository.  m2e is also a platform that let others provide better integration with additional Maven plugins (e.g. Android, web development, etc.), and facilitates the distribution of those extensions through the m2e marketplace. Maven Integration UML2 is an EMF-based implementation of the Unified Modeling Language (UMLTM) 2.x OMG metamodel for the Eclipse platform.  The objectives of the UML2 component are to provide      a useable implementation of the UML metamodel to support the development of modeling tools     a common XMI schema to facilitate interchange of semantic models     test cases as a means of validating the specification     validation rules as a means of defining and enforcing levels of compliance MDT UML2 UML2 is an EMF-based implementation of the Unified Modeling Language (UMLTM) 2.x OMG metamodel for the Eclipse platform.  The objectives of the UML2 component are to provide      a useable implementation of the UML metamodel to support the development of modeling tools     a common XMI schema to facilitate interchange of semantic models     test cases as a means of validating the specification     validation rules as a means of defining and enforcing levels of compliance MDT XSD

The goal of the Mobile Tools for JavaTM (MTJ) project is to extend existing Eclipse frameworks to support mobile device Java application development.  Mobile Tools for Java

Mylyn is the task and application lifecycle management (ALM) framework for Eclipse. It provides:      The revolutionary task-focused interface     Realigns the IDE around tasks so that you see only the code that's relevant           A task management tool for developers     Averaging 1 million downloads/month, Mylyn is the most popular IDE tool for ALM           A broad ecosystem of Agile and ALM integrations     Dozens of extensions integrate Mylyn with ALM and developer collaboration tools       Mylyn's task-focused interface reduces information overload and makes multitasking easy. Mylyn makes tasks a first class part of the IDE, integrates rich and offline editing for ALM tools, and monitors your programming activity to create a "task context" that focuses your workspace and automatically links all relevant artifacts to the task-at-hand. This puts the information you need at your fingertips and improves productivity by reducing information overload, facilitating multitasking and easing the sharing of expertise.  Mylyn

Eclipse OCL is an implementation of the Object Constraint Language (OCL) OMG standard for EMF-based models.  The core OCL component provides the following capabilities to support OCL integration:      Defines APIs for parsing and evaluating OCL constraints and queries on Ecore or UML models.     Defines Ecore and UML implementations of the OCL abstract syntax model, including support for serialization of parsed OCL expressions.     Provides a Visitor API for analyzing/transforming the AST model of OCL expressions.     Provides an extensibility API for clients to customize the parsing and evaluation environments used by the parser.  The accompanying examples provide:      A Console for interactive evaluation of OCL expression on models.     (Indigo) An Impact Analyzer to support analysis and optimised re-evaluation.  The additional OCL Examples and Editors component provides interactive support for OCL:      An Xtext editor for OCL expressions (used by Papyrus and the Console).     An Xtext editor for OCL expressions (used by Papyrus and the Console).     An Xtext editor for OCL documents complemementing meta-models (Complete OCL).     An Xtext editor for the OCL 'Standard' Library model.     (Indigo) A UML-aligned OCL meta-model supporting templates and reflection.     (Indigo) An OCL evaluator exploiting the extensible OCL library model.     (Indigo) An Xtext Console for interactive evaluation of OCL expression on models.  The core OCL parser is generated by the LALR Parser Generator, a SourceForge project, licensed under the EPL v1.0. Download it from the LPG home page. This site includes the generator executable required to regenerate the parser code. OCL Object Constraint Language

PHP Development Tools PHP Development Tools Model To Model (M2M) Model-to-model transformation is a key aspect of model-driven development (MDD). The M2M project will deliver a framework for model-to-model transformation languages. The core part is the transformation infrastructure. Transformations are executed by transformation engines that are plugged into the infrastructure. There are three transformation engines that are developed in the scope of this project. Each of the three represents a different category, which validates the functionality of the infrastructure from multiple contexts. M2M is a subproject of the top-level Eclipse Modeling Project. QVT Operational  Rich Ajax Platform The Riena platform is the foundation for building multi-tier enterprise client/server applications. As such Riena is broadening the usage of the service oriented architecture of OSGi/Equinox by providing access to local and remote services in a transparent way. Using this uniform programming model, the components of Riena and the business components of the enterprise application can be developed regardless of their target location. Components are later easily placed on client or server depending on the business requirements. Riena Platform Project Sequoyah project's purpose is to be focused on the needs of all mobile developers. Inheriting components from TmL, MTJ and Pulsar projects, Sequoyah intends to remove the artificial barriers of Linux and Java in order to provide a home for all Eclipse mobile developers.  Sequoyah

The Subversive project aims to provide Subversion (SVN) integration for Eclipse. The Subversive plug-in gives you the ability to work with this CVS successor version control system from the Eclipse workbench. You can work with Subversion repositories in almost exactly the same way you can now work with CVS repositories using the CVS plug-in bundled in the standard Eclipse distribution.  Subversive SVN

The Target Management project creates data models and frameworks to configure and manage remote (mainframe down to embedded) systems, their connections, and their services. Target Management  WindowBuilder Welcome to the Xpand wiki. Xpand is a language specialized on code generation based on EMF models. It supports the following main language features Xpand With Xtext you can easily create your own programming languages and domain-specific languages (DSLs). The framework supports the development of language infrastructures including compilers and interpreters as well as full blown Eclipse-based IDE integration. While Xtext equips you with sensible defaults, you can tweak every single aspect of your language with powerful APIs.  Xtext    

Eclipse Helios

Acceleo can be downloaded and installed in a number of ways. If you have an existing Eclipse installation and simply wish to install Acceleo in it, Installing through the update site is the easiest way. If you'd rather install a new Eclipse with Acceleo, you may want to take a look at the facilities provided by the amalgamation project. Acceleo  Accessibility Tools Framework The Amalgamation project provides improved packaging, integration, and usability of Modeling project components. The project is focused on providing a consumable and integrated Eclipse Modeling Tools package and ease the discovery of the modeling technologies through specific code and examples. Amalgamation ATL (ATL Transformation Language) is a model transformation language and toolkit. In the field of Model-Driven Engineering (MDE), ATL provides ways to produce a set of target models from a set of source models.  Developed on top of the Eclipse platform, the ATL Integrated Environnement (IDE) provides a number of standard development tools (syntax highlighting, debugger, etc.) that aims to ease development of ATL transformations. ATL Buckminster is a set of frameworks and tools for automating build, assemble & deploy (BA&D) development processes in complex or distributed component-based development. Buckminster allows development organizations to define fine-grained "production lines" for the various stages in software production - unit testing, integration testing, field deployment, staged migration, etc. - and to automate the execution of corresponding processes. BPMN Modeler Buckminster is a set of frameworks and tools for automating build, assemble & deploy (BA&D) development processes in complex or distributed component-based development. Buckminster allows development organizations to define fine-grained "production lines" for the various stages in software production - unit testing, integration testing, field deployment, staged migration, etc. - and to automate the execution of corresponding processes. Buckminster Component Assembly BIRT is an open source Eclipse-based reporting system that integrates with your Java/Java EE application to produce compelling reports. BIRT Project
 CDT Project

CDO is both a development-time model repository and a run-time persistence framework. Being highly optimized it supports object graphs of arbitrary size.  Model Repository

"Data Tools" is a vast domain, yet there are a fairly small number of foundational requirements when developing with or managing data-centric systems. A developer is interested in an environment that is easy to configure, one in which the challenges of application development are due to the problem domain, not the complexity of the tools employed. Data management, whether by a developer working on an application, or an administrator maintaining or monitoring a production system, should also provide a consistent, highly usable environment that works well with associated technologies. Data Tools Platform The Amalgamation project provides improved packaging, integration, and usability of Modeling project components. The project is focused on providing a consumable and integrated Eclipse Modeling Tools package and ease the discovery of the modeling technologies through specific code and examples. Dynamic Languages Toolkit ECF is a framework for building distributed servers, applications, and tools. It provides a modular implementation of the OSGi 4.2 Remote Services standard, along with support for REST-based and SOAP-based remote services, and asynchronous messaging for remote services. ECF Project EGit is an Eclipse Team provider for the Git version control system. Git is a distributed SCM, which means every developer has a full copy of all history of every revision of the code, making queries against the history very fast and versatile.  EGit The EMF project is a modeling framework and code generation facility for building tools and other applications based on a structured data model. From a model specification described in XMI, EMF provides tools and runtime support to produce a set of Java classes for the model, along with a set of adapter classes that enable viewing and command-based editing of the model, and a basic editor. Eclipse Modeling Framework

Create entry level downloads based on defined user profiles. The project defined and created the EPP downloads of Java Developer, Java EE Developer, C/C++ Developer and RCP Developer. These downloads are available from the main Eclipse download page. Please follow this description if you want to be a package maintainer. Eclipse Packaging Project

The EclipseLink project delivers a comprehensive open-source Java persistence solution addressing relational, XML, and database web services.  Eclipse Link Project

The Ecore Tools component provides a complete environment to create, edit and maintain Ecore models. This component eases handling of Ecore models with a Graphical Ecore Editor and bridges to other existing Ecore tools (Validation, Search, Compare, Emfatic, generators...). The Graphical Ecore Editor implements multi-diagram support, a custom tabbed properties view, validation feedbacks, refactoring capabilities... The long-term goal is to provide the same level of services as does JDT for Java.  Ecore Tools EMF - The core EMF framework includes a meta model (Ecore) for describing models and runtime support for the models including change notification, persistence support with default XMI serialization, and a very efficient reflective API for manipulating EMF objects generically. EMF EMF Compare provides comparison and merge facility for any kind of EMF Model. It includes a generic comparison engine, the ability to export differences in a model patch and it is integrated with the Eclipse Team API meaning that it enable collaborative work on models using CVS, SVN and GIT EMF Compare The query component provides capabilities to specify and execute queries against EMF model elements and their contents. EMF Query

 EMF Teneo Model Relational Mapping

 EMF Transaction

 EMF Validation

 Equinox

 Extended Editing Framework

GEF (Graphical Editing Framework)  The Graphical Editing Framework (GEF) provides technology to create rich graphical editors and views for the Eclipse Workbench UI. It bundles three components:      Draw2d (org.eclipse.draw2d) - A layout and rendering toolkit for displaying graphics on an SWT Canvas.     GEF (MVC) (org.eclipse.gef) - An interactive model-view-controler (MVC) framework, which fosters the implementation of SWT-based tree and Draw2d-based graphical editors for the Eclipse Workbench UI.     Zest (org.eclipse.zest) - A visualization toolkit based on Draw2d, which enables implementation of graphical views for the Eclipse Workbench UI. Graphical Editing Framework Model To Text (M2T)  The Model to Text (M2T) project focuses on the generation of textual artifacts from models. Its purpose is threefold:      Provide implementations of industry standard and defacto Eclipse standard model-to-text engines     Provide exemplary development tools for these languages     Provide common infrastructure for this languages. Java Emitter Templates

Java Workflow Tooling (JWT)  Eclipse SOA's Java Workflow Tooling project (JWT) provides design time, development time and runtime workflow tools. It also fosters interoperability between Business Process Management (BPM) platforms and integration in Information Systems thanks to Service Oriented Architecture (SOA).  Java Workflow Tooling

 Jetty

The Linux Tools project aims to bring a full-featured C and C++ IDE to Linux developers. We build on the source editing and debugging features of the CDT and integrate popular native development tools such as the GNU Autotools, Valgrind, OProfile, RPM, SystemTap, GCov, GProf, LTTng, etc. Current projects include LTTng trace viewers and analyzers, an RPM .spec editor, Autotools build integration, a Valgrind heap usage analysis tool, and OProfile call profiling tools.  The project also provides a place for Linux distributions to collaboratively overcome issues surrounding distribution packaging of Eclipse technology. The project produces both best practices and tools related to packaging. Since our 0.3.0 release, one of our features is a source archive of the Eclipse SDK that can be used by all Linux distributions building and distributing it.  Linux Tools

UML2 is an EMF-based implementation of the Unified Modeling Language (UMLTM) 2.x OMG metamodel for the Eclipse platform.  The objectives of the UML2 component are to provide      a useable implementation of the UML metamodel to support the development of modeling tools     a common XMI schema to facilitate interchange of semantic models     test cases as a means of validating the specification     validation rules as a means of defining and enforcing levels of compliance MDT UML2 UML2 is an EMF-based implementation of the Unified Modeling Language (UMLTM) 2.x OMG metamodel for the Eclipse platform.  The objectives of the UML2 component are to provide      a useable implementation of the UML metamodel to support the development of modeling tools     a common XMI schema to facilitate interchange of semantic models     test cases as a means of validating the specification     validation rules as a means of defining and enforcing levels of compliance MDT XSD Mint  Mint is a component in the Eclipse Modeling Framework Technology (EMFT) project whose goal is to improve out-of-the-box Java developer experience when writing EMF-based software. This is accomplished by extending Java Development Tools (JDT) with EMF-specific enhancements. The initial contribution consists of the following features: Mint The goal of the Mobile Tools for JavaTM (MTJ) project is to extend existing Eclipse frameworks to support mobile device Java application development.  Mobile Tools for Java

Mylyn is the task and application lifecycle management (ALM) framework for Eclipse. It provides:      The revolutionary task-focused interface     Realigns the IDE around tasks so that you see only the code that's relevant           A task management tool for developers     Averaging 1 million downloads/month, Mylyn is the most popular IDE tool for ALM           A broad ecosystem of Agile and ALM integrations     Dozens of extensions integrate Mylyn with ALM and developer collaboration tools       Mylyn's task-focused interface reduces information overload and makes multitasking easy. Mylyn makes tasks a first class part of the IDE, integrates rich and offline editing for ALM tools, and monitors your programming activity to create a "task context" that focuses your workspace and automatically links all relevant artifacts to the task-at-hand. This puts the information you need at your fingertips and improves productivity by reducing information overload, facilitating multitasking and easing the sharing of expertise.  Mylyn

PHP Development Tools PHP Development Tools

 Rich Ajax Platform

The Riena platform is the foundation for building multi-tier enterprise client/server applications. As such Riena is broadening the usage of the service oriented architecture of OSGi/Equinox by providing access to local and remote services in a transparent way. Using this uniform programming model, the components of Riena and the business components of the enterprise application can be developed regardless of their target location. Components are later easily placed on client or server depending on the business requirements. Riena Platform Project Sequoyah project's purpose is to be focused on the needs of all mobile developers. Inheriting components from TmL, MTJ and Pulsar projects, Sequoyah intends to remove the artificial barriers of Linux and Java in order to provide a home for all Eclipse mobile developers.  Sequoya The Subversive project aims to provide Subversion (SVN) integration for Eclipse. The Subversive plug-in gives you the ability to work with this CVS successor version control system from the Eclipse workbench. You can work with Subversion repositories in almost exactly the same way you can now work with CVS repositories using the CVS plug-in bundled in the standard Eclipse distribution.  Subversive SVN The goal of the Swordfish project is to provide an extensible SOA framework based on the proven Eclipse Equinox runtime technology. The framework is designed to be complemented by additional open source components such as a service registry, a messaging system, a process engine etc. to form a comprehensive open source SOA runtime environment based on both established and emerging open standards. Swordfish SOA Runtime Framework The Target Management project creates data models and frameworks to configure and manage remote (mainframe down to embedded) systems, their connections, and their services. Target Management

The Eclipse Test and Performance Tools Platform (TPTP) Project provides an open platform supplying powerful frameworks and services that allow software developers to build unique test and performance tools, both open source and commercial, that can be easily integrated with the platform and with other tools.  Eclipse Test & Performance Tools

Welcome to the Xpand wiki. Xpand is a language specialized on code generation based on EMF models. It supports the following main language features Xpand With Xtext you can easily create your own programming languages and domain-specific languages (DSLs). The framework supports the development of language infrastructures including compilers and interpreters as well as full blown Eclipse-based IDE integration. While Xtext equips you with sensible defaults, you can tweak every single aspect of your language with powerful APIs.  Xtext        
Page 1 of 2

                                                                                                               

Stay up to date on Architecture-Driven Modernization: