in black and white
Main menu
Share a book About us Home
Biology Business Chemistry Computers Culture Economics Fiction Games Guide History Management Mathematical Medicine Mental Fitnes Physics Psychology Scince Sport Technics

convergent architecture Building model driven J2EE Systems with UML - Hubert R.

Hubert R. convergent architecture Building model driven J2EE Systems with UML - Wiley publishing , 2002. - 289 p.
ISBN: 0-471-10560-0
Download (direct link): convergentarchitecturebu2002.pdf
Previous << 1 .. 107 108 109 110 111 112 < 113 > 114 115 116 117 118 119 .. 142 >> Next

Concerning implementation, build, deployment, and test artifacts. Significant portions of these artifacts can be generated automatically from any UML design models that conform to the modeling style.
This generation occurs according to a technology projection that has been designed to map a style-conform UML model to a particular technology. Thus, the IDE must support the pragmatic, flexible configuration of technology projections and their automatic use in an incremental development process.
Lastly, the tools must help developers create new technology projections or modify and extend existing technology projections.
The rest of this chapter shows how an architectural IDE meets or exceeds these high-level requirements. It also illustrates the individual features of the architectural IDE that were referred to in previous chapters on the development model. First, however, we need to see how the basic categories and requirements from Figure 7.1 are mapped to concrete modules of a real-world architectural IDE. This is done in Figure 7.2, which introduces the main modules of the ArcStyler, an architectural IDE as defined by the Convergent Architecture. The figure positions these modules of the IDE with respect to the critical-path workflows and the supporting workflows of the CA process. It also shows some of the major tools that are currently encapsulated or explicitly coordinated by the IDE: Rational Rose and JBuilder, J2EE/EBJ application servers, Web infrastructure, and so on.
Convergent Architecture
Chapter 7: The Architectural IDE
Figure 7.2: The modules and environment of the architectural IDE.
The following sections describe each of these modules, one module per section:
■ The convergent business object modeler (C-BOM)
■ The federated UML/XML model repository (C-MOD)
■ The convergent pattern refinement assistant (C-RAS)
■ The convergent UML refinement assistant (C-REF) with Rational Rose
■ The convergent translative generator (C-GEN)
■ The convergent generator IDE (C-GEN-IDE)
■ The convergent implement, deploy, and test environment (C-IX) with JBuilder and a J2EE application server
Since the architectural IDE covers a whole lot of ground, the overview will be some-what selective. To maintain the focus, each section is limited to one or two screenshots that exhibit several of the most style-relevant features of the module. Based on the screenshot, I explain how the module supports the development model of the architectural style. Only the highlights and the most critical features are explained; many features of the tool modules are not covered. Additional information at the user's guide or a user's reference level is available on the Convergent Architecture Web site.
The architectural IDE leverages a specific set of best-of-breed tools in its standard constellation (in particular, Rational Rose and JBuilder). These tools were selected to enable the most effective overall platform. However, as a pure Java component environment itself, the IDE is not inextricably coupled with these technologies. Alternatives to this particular set of embedded tools are conceivable.
The Convergent Business Object Modeler (C-BOM)
The C-BOM module (see Figure 7.3) supports both the T-bar and analysis-by-design workflows. It is used to capture and organize the business requirements and the business model. Figures 7.4 and 7.5 show its two primary views, first the CRC modeling view to capture the business components and then the
Convergent Architecture
Chapter 7: The Architectural IDE
corresponding scenario modeling view to capture the business dynamics. Together these views constitute a contract-based design.
Figure 7.3: Orientation of the C-BOM module.
Figure 7.4: Business object modeling.
Convergent Architecture
Chapter 7: The Architectural IDE
Figure 7.5: Use-case scenario modeling.
The teams in the T-bar and analysis-by-design sessions record convergent components in the form of CRC cards, as shown in the figures. The CRC cards are used to record the business responsibilities, collaborators, private ownership, and inheritance relationships of the components. The tabs of each card are designed to hold the information on both documentation and special requirements in areas such as security, migration, coordination with other components, and so on.
The hierarchy browser to the left of the figure serves to organize the design into logical groupings corresponding to organizations and assemblies. In addition, the scenario models and recorded run-throughs are organized in the hierarchy browser. The hierarchy browser remains visible throughout the entire development cycle in all tool modules. Each module of the IDE will show the hierarchy containing the artifacts from the previous module plus the additional, module-specific artifacts.
This allows convergence to be tracked in both directions along the development path.
Figure 7.5 shows the scenario model view of the C-BOM module. It is used by the teams to investigate and record the business dynamics in terms of component message flow, conditional transitions, and visual run-throughs.
Previous << 1 .. 107 108 109 110 111 112 < 113 > 114 115 116 117 118 119 .. 142 >> Next