|
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
|
 |
Few important facts about CBE & True Components
I feel it is extremely important one must know facts about the original components (in the physical world) and component based engineering (or CBE) of physical components, if he wishes to discover true software components (in the virtual world of software engineering). http://www.cbsdf.com/PS-Info/CBE-facts.htm
Imagine if you were an Alien from far away galaxy and send to the earth to get DNA (e.g. Blood sample) of an elephant. If you never seen an picture of an elephant but have description, such as, big, fat, black creature having 4 legs like cylinders, large ears and an elongated nose called trunk.
If he first finds a pig and if it fits 60% description, can he assume it is 60% elephant? If he finds rhino to satisfy 70% description, can he assume it is 70% elephant? Almost every animal having 4-legs can be called certain percent elephant, but it would not serve the purpose.
This is the situation in the software engineering. Software experts have been struggling to discover true software components for over 40 years by referring against general properties of certain physicals components. This long struggle led them into various wrong directions. Software experts calling almost any part of a application a component, such as, a function, a variable, a class or object, a data structure - just because each have some properties of components. Just like 60% elephants don’t serve purpose 60% components can’t serve purpose.
To discover true software components and component based engineering one must know the absolute truth about the physical components and the CBE. The software researchers also must learn huge benefits have been gained by the true components and division of labor.
Also the software experts and researchers must strive to comprehend why they are struggling to find true components in the first place. They must find the components that serve their purpose, which requires comprehending why components are required and how they secure huge benefits to designers of physical products. http://www.cbsdf.com/PS-Info/CBE-facts.htm
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.
|
|
