White Papers
For technical white papers or to read the entire series of OptimalJ white papers and other Java-related topics, join JavaCentral, Compuware's Java Developer Community. One-time registration to our free community provides a forum to share application design and development strategies with professionals around the world, plus unlimited access to white papers, technical tips, tutorials, product downloads, and more.
OptimalJ and SOA
OptimalJ and Model Driven Architecture (MDA)
OptimalJ Integration
OptimalJ Cornerstones
More Optimal white papers and OptimalAdvisor
OptimalJ and SOA
Building an SOA as an Enterprise Business Foundation
This white paper presents the advantages of building an SOA as an enterprise business foundation and discusses how employing a pragmatic MDA development approach is the fastest way to achieve those goals. Development shops interested in building SOAs and increasing productivity should evaluate MDA-based tools, like Compuware OptimalJ, for their development projects.
Service Oriented Architecture and OptimalJ
SOA is important for enterprise IT because it provides the framework that unites the business model with the applications that provide the functionality required for efficient business. This CBDI Forum report looks at how OptimalJ supports SOA and examines how its model-driven approach complements Web Services to provide SOA.
OptimalJ and Model Driven Architecture (MDA)
Transforming Software Development with MDA and OptimalJ
University assistant professor Kurt Fenstermacher and doctoral student Thomas Meservy describe how MDA shifts the focus of software development from writing code to building models. They challenge the misconceptions and critics of MDA by outlining the advantages of modeling for long-term flexibility, increased productivity and lower costs. In a clear and concise manner, they walk through the MDA process with OptimalJ to solve a business example.
Middleware Company Productivity Analysis
The Middleware Company recently performed a study to compare developer productivity in two different development environments: traditional, code-centric IDEs, and the Model Driven Architecture (MDA) approach. Two teams–one using Compuware OptimalJ and another using a market-leading code-centric IDE–spent four weeks creating the same J2EE application with comparably skilled developers. The results are impressive.
Middleware Company Maintainability Analysis
This Middleware Company study extends the examination of TMC’s earlier productivity study into the realm of application maintenance. Two teams performed a set of typical and diverse enhancements to an existing application; one team used an MDA-based tool, the other used a code-centric approach. The MDA approach resulted in completion of enhancements 37% faster, reinforcing recommendations to use MDA-based development tools, such as Compuware OptimalJ, for powerful productivity gains.
Reflections on the MDA Productivity Study: a Perspective for Executives
Independent consultant David S. Frankel analyzes the results of the recent Middleware Company study, which compared developer productivity between Compuware OptimalJ’s approach using the Model Driven Architecture, and the traditional code-centric approach commonly used today. His outlook, summarized here, reviews the implications of the study for the IT executive.
An Evaluation of Compuware OptimalJ as an MDA Tool
King’s College of London and the University of York embarked on a study to discover the benefits of the Model Driven Architecture, create an MDA tools selection methodology, and assess OptimalJ using the new evaluation criteria. This white paper summarizes their findings.
Driving Business Agility with Model Driven Architecture
In this position paper, Steven Witkop, a Sun certified J2EE architect, developer and programmer for EDS, takes an objective look at the advantages of using Model Driven Architecture (MDA) and OptimalJ.
MDA Explained, the Model Driven Architecture: Practice and Promise
Chapter One of the book MDA Explained, the Model Driven Architecture: Practice and Promise, written by Anneke Kleppe and Jos Warmer from "Klasse Objecten http://www.klasse.nl/english/overig/index.html" and Wim Bast, Chief Architect of OptimalJ, from Compuware. Includes an OptimalJ demo edition to walk you through how to create a three-tier application with an MDA tool.
Governance and MDA through OptimalJ
Governance is the feature of MDA that ensures that the application architecture is never compromised by the development process. From the business perspective this means that you are not paying extra for architectural elegance, either in time or cost. This CBDI Forum report outlines the importance of proper governance, and reviews how OptimalJ addresses it.
Frequently Asked Questions about MDA
Model Driven Architecture (MDA) is not the next big thing. Instead, MDA enables organizations to leverage the next best thing. For example, a major problem that companies have faced in the last few years is the continual introduction of new infrastructure technologies. MDA’s key benefit is that it transcends the implementation infrastructure. Read how in this collection of Frequently Asked Questions that outline the basics of MDA, and explain how Compuware OptimalJ can facilitate its promises.
Implementing Sun Microsystems' Core J2EE Patterns
Distinguished engineer and chief Java architect John Crupi of Sun Microsystems, and Compuware director of software architecture Frank Baerveldt, provide an informed overview of OptimalJ and its use of Sun's core J2EE design patterns. This white paper describes patterns in general, how Model Driven Architecture (MDA) and OptimalJ incorporate patterns and models into development tasks, how patterns work within the OptimalJ application architecture, and Sun J2EE pattern implementation in OptimalJ.
Combining Models and Patterns: Delivering on the Promise of Increased IT Productivity
The future to attaining greater software development productivity is combining models with pattern-based development. This paper explains what patterns are, how they are used, and their future use within the Object Management Group's Model Driven Architecture (MDA).
MDA: The Proof is in Automating Transformations between Models
The Object Management Group's Model Driven Architecture (MDA) introduces a higher level of abstraction to traditional software design and development, enabling organizations to create models that are in essence application "blueprints." MDA has three cornerstones: multiple models at various abstraction levels, transformations between these models, and support for the MDA set of standards as defined by OMG. However, MDA will become a viable, long-term architecture only when MDA-compliant vendors automate otherwise labor-intensive transformations between models. This white paper discusses the need for automated transformations between models, and the importance of transformation patterns as the key to automation.
OptimalJ Integration
Accelerating SAP R/3 integration with OptimalJ and the iWay Intelligent Adaptor
OptimalJ, in conjunction with the iWay adapter for SAP, allows developers to easily read, write and enrich SAP transactions while shielding them from the complexities of the SAP and the J2EE computing environment. Download this white paper today and learn how IT organizations can significantly reduce the time, cost and skill level required for integration projects between SAP and J2EE.
OptimalJ Integration Mainframe Connectivity
Most large IT organizations view their mainframe applications as critical strategic assets, containing important functionality and data essential to ongoing business operations. Over 70% of the world's corporate data is stored on mainframes. Renewing and extending these applications is a critical task, posing the challenge of combining the proven power, reliability and security of the mainframe with new and emerging technologies. Compuware OptimalJ addresses this need with a model-driven and pattern-based Java/J2EE development environment that supports integration models based on Java, CORBA and Web services.
OptimalJ Cornerstones
OptimalJ features five critical cornerstones, as explained in the technical white paper series below. To fully appreciate the value of OptimalJ's model-driven, pattern-based development approach using the OMG's Model Driven Architecture, we encourage you to first review this introduction to OptimalJ, then read the white papers in sequential order.
- Model-Driven Development—How OptimalJ incorporates UML-based modeling techniques to make visual models a more productive part of the development process.
- Business Rules—How OptimalJ helps developers use business rules to simplify and enhance rapid J2EE development.
- Patterns—How OptimalJ uses patterns to transform UML models into high quality J2EE applications, increasing an application's development potential and encapsulate best practices for coding to J2EE specifications.
- Active Synchronization—How active synchronization with OptimalJ delivers highly productive modifications, regardless of the development cycle's stage.
- Integrated Deployment—How integrated deployment with OptimalJ offers flexible deployment solutions, and helps developers identify deployment solutions best suited to their application environment.
More Optimal white papers and OptimalAdvisor
OptimalJ Versus In-sync Modeling Tools
Is OptimalJ just like other modeling tools? Don't let the apparent similarities due to the use of UML diagrams fool you. In-sync modeling tools maintain a tightly coupled, one-to-one relationship between modeling diagrams and source-code—simply a manipulative user interface, if you will. OptimalJ, by contrast, embodies an essential set of best practices for development teams, enabling developers, designers and architects to work together at a higher level – the Domain Model. Manipulate the Domain Model, and see controlled changes propagate through the entire application (from persistence to presentation layers). Learn the advantages of model-driven, pattern-based development, in which the modeling effort leads directly to the generation of working applications.
Using Compuware OptimalJ in a Unified Software Development Process
See how OptimalJ can be implemented in the context of one of the most widely adopted formal processes. The Unified Software Development Process is a detailed procedure used by development teams to produce software. Developed by some of the pioneers of Object-Oriented programming, the Unified Process has gained in popularity and is now being adopted by many organizations that are developing enterprise software. For each phase of the Unified Process, this paper will show where and by whom OptimalJ is used, and the individual roles that are expected to use OptimalJ within this process.
Knowledge-driven Application Development - An introduction to OptimalAdvisor
To understand a software program, one has to first understand its general design and structure. In Java, code is structured in classes, which are organized in hierarchical packages. A top-down approach toward understanding Java programs means to discover the purpose and relationship of packages. OptimalAdvisor reengineers the application design from the actual source code and calculates metrics to evaluate the high-level architectural structure. Download this white paper today and learn how to quickly evaluate the internal quality of large software products.
|
