Pattern in Software Industry (Week 3)

The second task of our lecture in week 3 was to identify a design pattern example other than the ones listed in handouts, I came across following example of design pattern;J2EE Design Patterns.


J2EE-specific design patterns identify the minimal set of known problems that application architecture should solve. These patterns are based on experiences of the J2EE community and use J2EE technologies to solve problems. The advantages of applying a design pattern are: proven solutions to the problems, reusability, improved performance, increased maintainability, and so on. [11]

It has a total of 13 patterns. J2EE Design Pattern Catalogue [2]

Business Delegate – Reduce coupling between web and enterprise JavaBeans tiers

Composite Entity – Model a network of related business entities

Composite View – Separately manage layout and content of multiple composed views

Data Access Object – Abstract and encapsulate data access mechanisms

Fast Lane Reader – Improve read performance of tabular data

Front Controller – Centralize application request processing

Intercepting Filter – Pre- and post-process application requests

Model View Controller – Decouple data representation, application behavior, and presentation

Service Locator – Simplify client access to enterprise business services

Session Façade – Coordinate operations between multiple business objects in a workflow

Transfer Object – Transfer business data between tiersValue List Handler – Efficiently iterate a virtual list

Value List handler - Efficiently Iterates a virtual List

View Helper – Simplify access to model state and data access logic


References

[1] J2EE Design Pattern Examples
Available from URL
http://www.oracle.com/technology/sample_code/tech/java/j2ee/designpattern/index.html

[2] J2EE Design Pattern – Design Pattern Catalogue
Available from URL
http://java.sun.com/blueprints/patterns/catalog.html