|
Sponsored Links
Resources
Enterprise Java
Research Library
Get Java white papers, product information, case studies and webcasts
|
J2EE patterns
J2EE patterns
J2EE patterns
|
Messages: 0
Messages: 0
Messages: 0
Printer friendly
Printer friendly
Printer friendly
Post reply
Post reply
Post reply
XML
XML
XML
|
 |
CBSE/COP pattern identical to design of physical products
This pattern outlines CBSE (Component based Software engineering) or Component Oriented programming (COP) process for building RIA, which is identical to component-based engineering for design and development of physical products such as automobile and computers.
To understand the pattern, it is important to understand
(i) Component Based Engineering (CBE for physical products) and
(ii) Essential characteristics of the components for physical products and building software components having properties comparable to physical components.
The following webpage briefly summarizes the two important stages of CBE (component-based engineering) for the physical products:
http://www.cbsdf.com/ps_blog/CBSE-and-CBE.htm
The following webpage provides a simple example for software components, which possess properties comparable to the properties of physical components:
http://www.cbsdf.com/misc_docs/Essential-complexity.htm
The following webpage defines couple of terms and unique meaning in the context of COP:
http://www.cbsdf.com/misc_docs/COP-Terminology.htm.
One must be cautious and notice that our definition for component is different than many other’s definition for software components. For example, most definitions for software component revolve around reusability (or distributed). But our components are custom designed (hence may not be reusable but loosely coupled objects), which must be easily replaceable (just like the components for physicals products).
A sample scenario for creating an RIA (Rich Internet Application) using COP:
http://www.cbsdf.com/ps_blog/WhyRepCom.htm
Please notice each of the component is custom designed for the application (hence likely not reusable) but very easily replaceable.
Almost every physical product satisfies 20% rule, if it is built using CBE. Hence any software application built using COP must satisfy 20% rule:
http://www.cbsdf.com/ps_blog/HSM-LC.htm
All such products offers outstanding “division of labor” to refine each component independently. Since there is very little accidental wasteful dependencies between the components, such products rarely require re-factoring at component assemble level.
Best Regards,
Raju
|
|
|
| EJB Design Patterns PDFEJB Design Patterns PDFEJB Design Patterns PDF |
|
|
EJB Design Patterns is now available for free download in PDF format. The book contains a catalog of twenty advanced EJB patterns and provides strategies for mapping application requirements to patterns-driven design, J2EE development best practices, and more. EJB Design Patterns was the #2 book at Java One 2002, and held the #1 Java book position on Amazon.com for weeks since the book was released in March. Download your PDF here.
|
| Useful patterns around the webUseful patterns around the webUseful patterns around the web |
|
|
This
essential pattern describes how to model your entity beans.
How to make an entity bean a facade to a set of dependent objects.
Every guru should use unit testing.
|
| Other Patterns sitesOther Patterns sitesOther Patterns sites |
|
|
|
The original reference
site for patterns. Frequented by the gang of 4 and their mentors (Kent Beck, Ward Cunningham).
A catalogue of J2EE design patterns from Suns Consulting Division.
A catalogue of
high level business, architectural and topological patterns for large scale systems.
Design Patterns from the J2EE Blueprints, Suns authoritative guide to J2EE development.
|
|
