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

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 .. 120 121 122 123 124 125 < 126 > 127 128 129 130 131 132 .. 142 >> Next

Attribute
Operation
Association
The refinement patterns suggest that responsibilities for Knowing are normally refined to attributes or associations, whereas responsibilities for Doing are refined to operations. A responsibility is refined by selecting it in the browser and using its Refine ^ <RefiningElement> context menu.
Refining the Account Business Object
Refine the responsibilities of the Account object as follows:
1. Refine the Know balance responsibility with an attribute,
accountNumber, of type string. Figure 8.6 shows the result of this procedure.
-235-
Convergent Architecture
Chapter 8: Tutorial Example
Figure 8.6: Refining the Know account number responsibility.
2. Similarly, refine the Know balance responsibility with an attribute,
balance, of type double. Figure 8.7 shows the result of this procedure.
-236-
Convergent Architecture
Chapter 8: Tutorial Example
Figure 8.7: Modeling the balance attribute.
3. Refine the Make deposit responsibility with an operation,
makeDeposit, with return type <none> and a parameter, amount, of type double and direction IN. Figure 8.8 shows the result of this procedure.
-237-
Convergent Architecture
Chapter 8: Tutorial Example
Figure 8.8: Modeling the makeDeposit() operation.
4. Similarly, refine the Make withdrawal responsibility with an operation,
make-Withdrawal, with return type <none> and a parameter, amount, of type double and direction IN.
Refining the Transfer Business Object
Now we refine the Transfer object.
1. Refine the Know source account with an attribute, source, of object
type Account. Figure 8.9 shows this procedure.
-238-
Convergent Architecture
Chapter 8: Tutorial Example
Figure 8.9: Modeling the source attribute.
2. Similarly, refine the Know destination account responsibility with an attribute, destination, of type Account.
3. Refine the Know amount to be transferred responsibility with an attribute, amount, of type double.
4. Refine the Execute transfer responsibility with an operation, execute, with return type <none> and no parameters.
Now the refinement of the business-model objects to UML convergent components has been completed, as indicated by the checkmark in the Figure 8.10. The checkmark indicates that the refinement of the model element is completed.
-239-
Convergent Architecture
Chapter 8: Tutorial Example
Figure 8.10: Refined to UML components.
Model Verification
The C-RAS module provides a model-verification mechanism to verify the structural correctness and completeness of the UML model. You can verify single model elements or the entire model using the element's Verify context menu.
The verifier notifies you as to the results of the validation. If the validation is not successful, you will get warnings or error messages. In the case of errors, the model must be fixed in order to maintain integrity as defined by the architectural style.
At this point, the UML convergent component model has been created.
J2EE/EJB Modeling with C-REF/UML
This section covers the technical refinement of the UML component model. This is the convergent refinement III (convergent UML refinement) activity of the analysis-by-design work flow, which is supported by the convergent EJB/UML refiner for Rational Rose (C-REF).
The C-REF module assists you in refining the UML model according to the UML modeling style and technology projection, as described in Chapter 7. The C-REF provides design assistants and defaults to technically refine all components and their relationships. This simplifies modeling while still permitting extensions and adjustments by experts.
This section contains the following subsections:
Starting the C-REF
Modeling the account component
-240-
Convergent Architecture
Chapter 8: Tutorial Example
Modeling the transfer component Modeling deployable components Model verification
Starting the C-REF
The C-REF module operates as an architectural shell around Rational Rose. Performance, compatibility, and ease of use from within the Rose environment are a high priority. To achieve this, the ArcStyler consolidates its open UML/XML repository (C-MOD) with the Rose internal repository. This consolidation is encapsulated properly and, as such, is transparent to all modules of the ArcStyler. The consolidated format is referred to as the Rose native format. The conversion between the Rose native format and the ArcStyler UML/XML repository is bidirectional and lossless. Also, it only needs to be carried out when you move back and forth between the C-RAS and C-REF modules. To move from the C-RAS module into the Rose-centric C-REF, you import the external C-MOD repository into its corresponding C-REF/Rose repository in Rose (Rose native format). Once in the C-REF/Rose environment, modeling proceeds using Rose within the ArcStyler shell. All modules use the C-REF/Rose native format. The ArcStyler C-MOD repository can be stored and reloaded in the Rose native format or exported to the external C-MOD at any time.
Previous << 1 .. 120 121 122 123 124 125 < 126 > 127 128 129 130 131 132 .. 142 >> Next