|
A complement to Rational XDE™ and
Together ControlCenter™
From a code
ownership point of view
Codagen Architect lets architects own the code associated with
their architecture through an automated process that can transform a
whole Platform Independent Model (PIM) into working
code with one click of the mouse. Conversely, Rational XDE and
Together ControlCenter are better suited for developers because each
model-to-code transformation requires manual intervention. With XDE
and ControlCenter, developers can efficiently implement the domain
logic of the application.
From a traceability point of view
Codagen Architect is the only offering that can guarantee the
enforcement of a layered architecture through the code because developers cannot change the templates once they are stored in binary
form. In a typical organization, you might find five senior software
architects and 500 developers. It is not feasible to rely only on code
reviews to achieve consistent results. Codagen Architect has a unique
trace feature that shows architects—in a tree view—how the
information captured in UML is used inside a template.
From a UML point of view
Codagen Architect’s easy-to-produce UML profile significantly
increases the amount of code produced. The UML profile captures
The different layers of an application.
The architecture issues for each layer that must be addressed in order to get the best
implementation practices using the technologies of that layer.
The design decisions that must be made in order to resolve each architectural issue. A UML profile created with Codagen Architect
supports UML 1.4, although XDE and ControlCenter support UML 1.3.
From an interoperability point of view
Codagen Architect enables the creation and evolution of an Enterprise
Architecture Blueprint that is technology-neutral in many of the
layers. It provides flexibility to target the appropriate platform whether it be J2EE or .NET.
From an XML point of view
Codagen Architect provides a UML solution for generating XML schemas
from a business model (PIM), like the IBM IAA or ACORD insurance
business model.
From a development process point of view
Codagen Architect supports any formal methodology, like the Rational
Unified Process. When software architecture is modeled in UML with XDE
and ControlCenter, its evolution and maintenance require tedious,
repetitive, manual intervention because all the details of the
infrastructure are contained in the UML model. For example, to change
an architecture pattern, you have to reflect that change in every
occurrence where it is used to realize a Platform Specific Model (PSM)
for a given PIM.
A preferred approach is to use Codagen Architect to
automatically derive the PSM from the PIM, taking advantage of a UML
profile to annotate the UML elements found in the PIM with mapping
rules that will be used to selectively apply architecture patterns as
transformation rules. A change in an architecture pattern will then be
automatically propagated in the PSM. This preferred approach precludes
the manual process of creating a design model; XDE and
ControlCenter are the perfect tools to derive the design model from
the code generated by Codagen Architect.
From a software engineering point of view
Codagen Architect supports the notion of extreme programming and
aspect oriented programming. It enforces and eases the deployment of
an organization's programming standards and allows dissemination of
development best practices.
From our product roadmap point of view
Codagen Architect will further complement XDE and ControlCenter by
enabling companies to reverse engineer code into a PIM. Today, XDE and
ControlCenter provide only the synchronization between the code and a
PSM.
[
Back to Codagen Architect ] |
