Thursday, January 31, 2008
Design Patterns Higer Level Diagram
Design pattern is a general repeatable solution to a commonly occurring problem in software design. A design pattern isn't a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations.
Thursday, January 24, 2008
Thursday, January 10, 2008
Prototype Pattern
Intent:
Specifies the kinds of objects to create using a prototypical instance and creates
new objects by copying this prototype.
Description:
The Prototype pattern allows an object to create customized objects without knowing
their exact class or the details of how to create them. The Prototype pattern gives
prototypical objects to an object and then initiates the creation of objects. The
creation-initiating object then creates objects by asking the prototypical objects to
make copies of them.
Benefits:
• Hides the concrete product classes from the client.
• Adding and removing products at runtime.
• Specifying new objects by varying values.
• Specifying new objects by varying structure.
• Reduced subclassing.
Monday, January 7, 2008
SCEA 5 Testing Objectives "DRAFT" -beta
SCEA 5 Multiple Choice Testing Objectives "DRAFT" -beta
Section 1: Application Design Concepts and Principles
1.1Explain the main advantages of an object oriented approach to system design including the effect of encapsulation, inheritance, delegation, and the use of interfaces, on architectural characteristics.
1.2Describe how the principle of “separation of concerns” has been applied to the main system tiers of a Java EE application. Tiers include client (both GUI and web), web (web container), business (EJB container), integration, and resource tiers.
1.3Describe how the principle of “separation of concerns” has been applied to the layers of a Java EE application. Layers include application, virtual platform (component APIs), application infrastructure (containers), enterprise services (operating system and virtualization), compute and storage, and the networking infrastructure layers.
Section 2:Common Architectures
2.1Explain the advantages and disadvantages of two tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security.
2.2Explain the advantages and disadvantages of three tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security
2.3Explain the advantages and disadvantages of multi-tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security.
2.4Explain the benefits and drawbacks of rich clients and browser-based clients as deployed in a typical Java EE application.
2.5Explain appropriate and inappropriate uses for Web Services in the Java EE Platform
Section 3:Integration and Messaging
3.1Explain possible approaches for communicating with an external system from a Java EE-based system given an outline description of those systems and outline the benefits and drawbacks of each approach.
3.2Explain typical uses of Web Services and XML over HTTP as mechanisms to integrate distinct software components.
3.3Explain how Java Connector Architecture and JMS are used to integrate distinct software components as part of an overall Java EE application.
Section 4: Business Tier Technologies
4.1Explain and contrast uses for Entity Beans, Entity Classes, Stateful and Stateless Session Beans, and Message Driven Beans and understand the advantages and disadvantages of each type.
4.2Explain and contrast the following persistence strategies: Container Managed Persistence (CMP) BMP, JDO, JPA, ORM and using DAOs (Data Access Objects) and direct JDBC-based persistence under the following headings: ease of development, performance, scalability, extensibility and security.
4.3Explain how Java EE supports the deployment of server-side components implemented as Web Services and the advantages and disadvantages of adopting such an approach.
4.4Explain the benefits of the EJB3 development model over previous EJB generations for ease of development including how the EJB container simplifies EJB development.
Section 5: Web Tier Technologies
5.1State the benefits and drawbacks of adopting a web framework in designing a Java EE application
5.2Explain standard uses for JSP and Servlet technologies in a typical Java EE application.
5.3Explain standard uses for JSF technology in a typical Java EE application.
5.4Given a system requirements definition, explain and justify your rationale for choosing a web-centric or EJB-centric implementation to solve the requirements. Web-centric means that you are providing a solution that does not use EJBs. EJB-centric solution will require an application server that supports EJBs.
Section 6: Applicability of Java EE Technology
6.1Given a specified business problem, design a modular solution implemented using Java EE which solves that business problem.
6.2Explain how the Java EE platform enables service oriented architecture (SOA) -based applications.
6.3Explain how you would design a Java EE application to repeatedly measure critical non-functional requirements and outline a standard process with specific strategies to refactor that application to improve on the results of the measurements.
Section 7: Patterns
7.1From a list, select the most appropriate pattern for a given scenario. Patterns are limited to those documented in the book - Alur, Crupi and Malks (2003). Core J2EE Patterns: Best Practices and Design Strategies 2nd Edition and named using the names given in that book.
7.2From a list, select the most appropriate pattern for a given scenario. Patterns are limited to those documented in the book - Gamma, Erich; Richard Helm, Ralph Johnson, and John Vlissides (1995). Design Patterns: Elements of Reusable Object-Oriented Software and are named using the names given in that book.
7.3Select from a list the benefits and drawbacks of a pattern drawn from the book - Gamma, Erich; Richard Helm, Ralph Johnson, and John Vlissides (1995). Design Patterns: Elements of Reusable Object-Oriented Software.
7.4Select from a list the benefits and drawbacks of a specified Core J2EE pattern drawn from the book – Alur, Crupi and Malks (2003). Core J2EE Patterns: Best Practices and Design Strategies 2nd Edition.
Section 8: Security
8.1Explain the client-side security model for the Java SE environment, including the Web Start and applet deployment modes.
8.2Given an architectural system specification, select appropriate locations for implementation of specified security features, and select suitable technologies for implementation of those features
8.3Identify and classify potential threats to a system and describe how a given architecture will address the threats.
8.4Describe the commonly used declarative and programmatic methods used to secure applications built on the Java EE platform, for example use of deployment descriptors and JAAS.
SCEA 5 Assignment Objectives "DRAFT"
Section 1: Application Design Concepts and Principles
1.1Document a given system architecture by creating UML diagrams for it.
1.2Explain the main advantages of an object oriented approach to system design including the effect of encapsulation, inheritance, delegation, and the use of interfaces, on architectural characteristics.
1.3Describe how the principle of “separation of concerns” has been applied to the main system tiers of a Java EE application. Tiers include client (both GUI and web), web (web container), business (EJB container), integration, and resource tiers.
1.4Describe how the principle of “separation of concerns” has been applied to the layers of a Java EE application. Layers include application, virtual platform (component APIs), application infrastructure (containers), enterprise services (operating system and virtualization), compute and storage, and the networking infrastructure layers.
Section 2:Common Architectures
2.1Explain the advantages and disadvantages of two tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security.
2.2Explain the advantages and disadvantages of three tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security
2.3Explain the advantages and disadvantages of multi-tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security.
2.4Explain the benefits and drawbacks of rich clients and browser-based clients as deployed in a typical Java EE application.
2.5Create a logical and physical model of a system infrastructure architecture
Section 3: Integration and Messaging
3.1Explain possible approaches for communicating with an external system from a Java EE-based system given an outline description of those systems and outline the benefits and drawbacks of each approach.
3.2Explain typical uses of Web Services and XML over HTTP as mechanisms to integrate distinct software components.
3.3Explain how Java Connector Architecture and JMS are used to integrate distinct software components as part of an overall Java EE application.
3.4Given a scenario, explain the appropriate messaging strategy to satisfy the requirements.
Section 4: Business Tier Technologies
4.1Explain and contrast uses for Entity Beans, Entity Classes, Stateful and Stateless Session Beans, and Message Driven Beans and understand the advantages and disadvantages of each type.
4.2Explain and contrast the following persistence strategies: Container Managed Persistence (CMP) BMP, JDO, JPA, ORM and using DAOs (Data Access Objects) and direct JDBC-based persistence under the following headings: ease of development, performance, scalability, extensibility and security.
Section 5: Web Tier Technologies
5.1Given a system requirements definition, explain and justify your rationale for choosing a web-centric or EJB-centric implementation to solve the requirements. Web-centric means that you are providing a solution that does not use EJBs. EJB-centric solution will require an application server that supports EJBs.
Section 6: Applicability of Java EE Technology
6.1Given a specified business problem, design a modular solution implemented using Java EE which solves that business problem.
6.2Given a specified business problem, identify and prioritize the main technology risk areas that must be addressed by the technical design and architecture.
6.3Explain how the Java EE platform enables service oriented architecture (SOA) -based applications.
6.4Identify how the Java SE and Java EE platform supports the internationalization and localization of applications.
6.5Explain your rationale for choosing build versus buy for a given Java EE component.
6.6Explain the typical challenges associated with the design and implementation of large scale enterprise software systems and how Java EE technology addresses those challenges.
6.7Explain how you would design a Java EE application to repeatedly measure critical non-functional requirements and outline a standard process with specific strategies to refactor that application to improve on the results of the measurements.
Section 7: Patterns
7.1From a list, select the most appropriate pattern for a given scenario. Patterns are limited to those documented in the book - Alur, Crupi and Malks (2003). Core J2EE Patterns: Best Practices and Design Strategies 2nd Edition and named using the names given in that book.
7.2From a list, select the most appropriate pattern for a given scenario. Patterns are limited to those documented in the book - Gamma, Erich; Richard Helm, Ralph Johnson, and John Vlissides (1995). Design Patterns: Elements of Reusable Object-Oriented Software and are named using the names given in that book.
7.3Select from a list the benefits and drawbacks of a pattern drawn from the book - Gamma, Erich; Richard Helm, Ralph Johnson, and John Vlissides (1995). Design Patterns: Elements of Reusable Object-Oriented Software.
7.4Select from a list the benefits and drawbacks of a specified Core J2EE pattern drawn from the book – Alur, Crupi and Malks (2003). Core J2EE Patterns: Best Practices and Design Strategies 2nd Edition.
Section 8: Security
8.1Given an architectural system specification, select appropriate locations for implementation of specified security features, and select suitable technologies for implementation of those features
8.2Identify and classify potential threats to a system and describe how a given architecture will address the threats.
Section 1: Application Design Concepts and Principles
1.1Explain the main advantages of an object oriented approach to system design including the effect of encapsulation, inheritance, delegation, and the use of interfaces, on architectural characteristics.
1.2Describe how the principle of “separation of concerns” has been applied to the main system tiers of a Java EE application. Tiers include client (both GUI and web), web (web container), business (EJB container), integration, and resource tiers.
1.3Describe how the principle of “separation of concerns” has been applied to the layers of a Java EE application. Layers include application, virtual platform (component APIs), application infrastructure (containers), enterprise services (operating system and virtualization), compute and storage, and the networking infrastructure layers.
Section 2:Common Architectures
2.1Explain the advantages and disadvantages of two tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security.
2.2Explain the advantages and disadvantages of three tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security
2.3Explain the advantages and disadvantages of multi-tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security.
2.4Explain the benefits and drawbacks of rich clients and browser-based clients as deployed in a typical Java EE application.
2.5Explain appropriate and inappropriate uses for Web Services in the Java EE Platform
Section 3:Integration and Messaging
3.1Explain possible approaches for communicating with an external system from a Java EE-based system given an outline description of those systems and outline the benefits and drawbacks of each approach.
3.2Explain typical uses of Web Services and XML over HTTP as mechanisms to integrate distinct software components.
3.3Explain how Java Connector Architecture and JMS are used to integrate distinct software components as part of an overall Java EE application.
Section 4: Business Tier Technologies
4.1Explain and contrast uses for Entity Beans, Entity Classes, Stateful and Stateless Session Beans, and Message Driven Beans and understand the advantages and disadvantages of each type.
4.2Explain and contrast the following persistence strategies: Container Managed Persistence (CMP) BMP, JDO, JPA, ORM and using DAOs (Data Access Objects) and direct JDBC-based persistence under the following headings: ease of development, performance, scalability, extensibility and security.
4.3Explain how Java EE supports the deployment of server-side components implemented as Web Services and the advantages and disadvantages of adopting such an approach.
4.4Explain the benefits of the EJB3 development model over previous EJB generations for ease of development including how the EJB container simplifies EJB development.
Section 5: Web Tier Technologies
5.1State the benefits and drawbacks of adopting a web framework in designing a Java EE application
5.2Explain standard uses for JSP and Servlet technologies in a typical Java EE application.
5.3Explain standard uses for JSF technology in a typical Java EE application.
5.4Given a system requirements definition, explain and justify your rationale for choosing a web-centric or EJB-centric implementation to solve the requirements. Web-centric means that you are providing a solution that does not use EJBs. EJB-centric solution will require an application server that supports EJBs.
Section 6: Applicability of Java EE Technology
6.1Given a specified business problem, design a modular solution implemented using Java EE which solves that business problem.
6.2Explain how the Java EE platform enables service oriented architecture (SOA) -based applications.
6.3Explain how you would design a Java EE application to repeatedly measure critical non-functional requirements and outline a standard process with specific strategies to refactor that application to improve on the results of the measurements.
Section 7: Patterns
7.1From a list, select the most appropriate pattern for a given scenario. Patterns are limited to those documented in the book - Alur, Crupi and Malks (2003). Core J2EE Patterns: Best Practices and Design Strategies 2nd Edition and named using the names given in that book.
7.2From a list, select the most appropriate pattern for a given scenario. Patterns are limited to those documented in the book - Gamma, Erich; Richard Helm, Ralph Johnson, and John Vlissides (1995). Design Patterns: Elements of Reusable Object-Oriented Software and are named using the names given in that book.
7.3Select from a list the benefits and drawbacks of a pattern drawn from the book - Gamma, Erich; Richard Helm, Ralph Johnson, and John Vlissides (1995). Design Patterns: Elements of Reusable Object-Oriented Software.
7.4Select from a list the benefits and drawbacks of a specified Core J2EE pattern drawn from the book – Alur, Crupi and Malks (2003). Core J2EE Patterns: Best Practices and Design Strategies 2nd Edition.
Section 8: Security
8.1Explain the client-side security model for the Java SE environment, including the Web Start and applet deployment modes.
8.2Given an architectural system specification, select appropriate locations for implementation of specified security features, and select suitable technologies for implementation of those features
8.3Identify and classify potential threats to a system and describe how a given architecture will address the threats.
8.4Describe the commonly used declarative and programmatic methods used to secure applications built on the Java EE platform, for example use of deployment descriptors and JAAS.
SCEA 5 Assignment Objectives "DRAFT"
Section 1: Application Design Concepts and Principles
1.1Document a given system architecture by creating UML diagrams for it.
1.2Explain the main advantages of an object oriented approach to system design including the effect of encapsulation, inheritance, delegation, and the use of interfaces, on architectural characteristics.
1.3Describe how the principle of “separation of concerns” has been applied to the main system tiers of a Java EE application. Tiers include client (both GUI and web), web (web container), business (EJB container), integration, and resource tiers.
1.4Describe how the principle of “separation of concerns” has been applied to the layers of a Java EE application. Layers include application, virtual platform (component APIs), application infrastructure (containers), enterprise services (operating system and virtualization), compute and storage, and the networking infrastructure layers.
Section 2:Common Architectures
2.1Explain the advantages and disadvantages of two tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security.
2.2Explain the advantages and disadvantages of three tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security
2.3Explain the advantages and disadvantages of multi-tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security.
2.4Explain the benefits and drawbacks of rich clients and browser-based clients as deployed in a typical Java EE application.
2.5Create a logical and physical model of a system infrastructure architecture
Section 3: Integration and Messaging
3.1Explain possible approaches for communicating with an external system from a Java EE-based system given an outline description of those systems and outline the benefits and drawbacks of each approach.
3.2Explain typical uses of Web Services and XML over HTTP as mechanisms to integrate distinct software components.
3.3Explain how Java Connector Architecture and JMS are used to integrate distinct software components as part of an overall Java EE application.
3.4Given a scenario, explain the appropriate messaging strategy to satisfy the requirements.
Section 4: Business Tier Technologies
4.1Explain and contrast uses for Entity Beans, Entity Classes, Stateful and Stateless Session Beans, and Message Driven Beans and understand the advantages and disadvantages of each type.
4.2Explain and contrast the following persistence strategies: Container Managed Persistence (CMP) BMP, JDO, JPA, ORM and using DAOs (Data Access Objects) and direct JDBC-based persistence under the following headings: ease of development, performance, scalability, extensibility and security.
Section 5: Web Tier Technologies
5.1Given a system requirements definition, explain and justify your rationale for choosing a web-centric or EJB-centric implementation to solve the requirements. Web-centric means that you are providing a solution that does not use EJBs. EJB-centric solution will require an application server that supports EJBs.
Section 6: Applicability of Java EE Technology
6.1Given a specified business problem, design a modular solution implemented using Java EE which solves that business problem.
6.2Given a specified business problem, identify and prioritize the main technology risk areas that must be addressed by the technical design and architecture.
6.3Explain how the Java EE platform enables service oriented architecture (SOA) -based applications.
6.4Identify how the Java SE and Java EE platform supports the internationalization and localization of applications.
6.5Explain your rationale for choosing build versus buy for a given Java EE component.
6.6Explain the typical challenges associated with the design and implementation of large scale enterprise software systems and how Java EE technology addresses those challenges.
6.7Explain how you would design a Java EE application to repeatedly measure critical non-functional requirements and outline a standard process with specific strategies to refactor that application to improve on the results of the measurements.
Section 7: Patterns
7.1From a list, select the most appropriate pattern for a given scenario. Patterns are limited to those documented in the book - Alur, Crupi and Malks (2003). Core J2EE Patterns: Best Practices and Design Strategies 2nd Edition and named using the names given in that book.
7.2From a list, select the most appropriate pattern for a given scenario. Patterns are limited to those documented in the book - Gamma, Erich; Richard Helm, Ralph Johnson, and John Vlissides (1995). Design Patterns: Elements of Reusable Object-Oriented Software and are named using the names given in that book.
7.3Select from a list the benefits and drawbacks of a pattern drawn from the book - Gamma, Erich; Richard Helm, Ralph Johnson, and John Vlissides (1995). Design Patterns: Elements of Reusable Object-Oriented Software.
7.4Select from a list the benefits and drawbacks of a specified Core J2EE pattern drawn from the book – Alur, Crupi and Malks (2003). Core J2EE Patterns: Best Practices and Design Strategies 2nd Edition.
Section 8: Security
8.1Given an architectural system specification, select appropriate locations for implementation of specified security features, and select suitable technologies for implementation of those features
8.2Identify and classify potential threats to a system and describe how a given architecture will address the threats.
Tuesday, January 1, 2008
Abstract Factory Pattern
Intent:
Provides an interface for creating families of related or dependent objects without
specifying their concrete classes.
Description:
The Abstract Factory pattern defines an abstract class that determines the
appropriate concrete class to instantiate to create a set of concrete classes that
implement a standard interface. The client interacts only with the interfaces and the
Abstract Factory class. The client is completely shielded from the concrete classes.
The Abstract Factory pattern is similar to the Factory Method pattern, except that it
creates families of related objects and can be considered as a factory of factories.
Benefits:
• Isolates concrete classes.
• Makes exchanging product families easy.
• Promotes consistency among products.
When to use?
You can use the Abstract Factory pattern when:
• The system should be independent of how its products are created,
composed, and represented.
• The system should be configured with one of the multiple families of
products.
• A family of related product objects is designed to be used together and
you need to enforce this constraint.
• You want to provide a class library of products and you want to reveal just
their interfaces, not their implementations.
GOF patterns: Creational
Creational patterns specialize in abstracting the instantiation process. They help in
isolating how objects are created, composed, and represented from the rest of the
system. There are five patterns defined in this category:
• Abstract Factory
• Builder
• Factory Method
• Prototype
• Singleton
isolating how objects are created, composed, and represented from the rest of the
system. There are five patterns defined in this category:
• Abstract Factory
• Builder
• Factory Method
• Prototype
• Singleton
Test 310-051 Testing objectives for the Sun Certified Enterprise Architect for J2EE Technology
Testing objectives for the Sun Certified Enterprise Architect for J2EE Technology include:
COMMON ARCHITECTURES
• Given an architecture described in terms of network layout, list benefits and potential weaknesses
associated with it
LEGACY CONNECTIVITY
• Distinguish appropriate from inappropriate techniques for providing access to a legacy system from Java
technology code given an outline description of that legacy system
ENTERPRISE JAVA \BEANS™
• List the required classes/interfaces that must be provided for an Enterprise JavaBean™ component
• Distinguish between stateful and stateless session beans
• Distinguish between session and entity beans
• Recognize appropriate uses for entity, stateful session, and stateless session beans
• State the benefits and costs of container-managed persistence
• State the transactional behavior in a given scenario for an enterprise bean method with a specified
transactional attributed as defined in the deployment descriptor
• Given a requirement specification detailing security and flexibility needs, identify architectures that would
fulfill those requirements
• Identify costs and benefits of using an intermediate data-access object between an entity bean and the
data resource
ENTERPRISE JAVABEANS™ CONTAINER MODEL:
• State the benefits of bean pooling in an Enterprise JavaBeans container
• Explain how the Enterprise JavaBeans container does lifecycle management and has the capability to
increase scalability
PROTOCOLS:
• Given a list of some of its features, identify a protocol that is one of the following: HTTP, HTTPS, IIOP,
or JRMP
• Given a scenario description, distinguish appropriate from inappropriate protocols to implement
that scenario
• Select common firewall features that might interfere with the normal operation of a given protocol
APPLICABILITY OF J2EE™ TECHNOLOGY:
• Identify application aspects that are suited to implementation using J2EE technology
• Identify application aspects that are suited to implementation using Enterprise Java Beans
• Identify suitable J2EE technologies for the implementation of specified application aspects
DESIGN PATTERNS:
• Identify the most appropriate design pattern for a given scenario
• Identify the benefits of using design patterns
• State the name of a Gamma et al. design pattern given the UML diagram and/or a brief description of the
pattern's functionality
• Identify benefits of a specified Gamma et al. design pattern
• Identify the Gamma et al. design pattern associated with a specified J2EE technology feature
MESSAGING:
• Identify scenarios that are appropriate to implementation using messaging, Enterprise JavaBeans
technology, or both
• List benefits of synchronous and asynchronous messaging
• Identify scenarios that are appropriate to implementation using messaging
• Identify scenarios that are more appropriate to implementation using asynchronous messaging, rather
than synchronous
• Identify scenarios that are more appropriate to implementation using synchronous messaging, rather
than asynchronous
INTERNATIONALIZATION:
• State three aspects of any application that might need to be varied or customized in different
deployment locales
• List three features of the Java programming language that can be used to create an
internationalizable/localizable application
SECURITY:
• Identify security restrictions that Java 2 technology environments normally impose on applets running
in a browser
• Given an architectural system specification, identify appropriate locations for implementation of specified
security features and select suitable technologies for implementation of those features
COMMON ARCHITECTURES
• Given an architecture described in terms of network layout, list benefits and potential weaknesses
associated with it
LEGACY CONNECTIVITY
• Distinguish appropriate from inappropriate techniques for providing access to a legacy system from Java
technology code given an outline description of that legacy system
ENTERPRISE JAVA \BEANS™
• List the required classes/interfaces that must be provided for an Enterprise JavaBean™ component
• Distinguish between stateful and stateless session beans
• Distinguish between session and entity beans
• Recognize appropriate uses for entity, stateful session, and stateless session beans
• State the benefits and costs of container-managed persistence
• State the transactional behavior in a given scenario for an enterprise bean method with a specified
transactional attributed as defined in the deployment descriptor
• Given a requirement specification detailing security and flexibility needs, identify architectures that would
fulfill those requirements
• Identify costs and benefits of using an intermediate data-access object between an entity bean and the
data resource
ENTERPRISE JAVABEANS™ CONTAINER MODEL:
• State the benefits of bean pooling in an Enterprise JavaBeans container
• Explain how the Enterprise JavaBeans container does lifecycle management and has the capability to
increase scalability
PROTOCOLS:
• Given a list of some of its features, identify a protocol that is one of the following: HTTP, HTTPS, IIOP,
or JRMP
• Given a scenario description, distinguish appropriate from inappropriate protocols to implement
that scenario
• Select common firewall features that might interfere with the normal operation of a given protocol
APPLICABILITY OF J2EE™ TECHNOLOGY:
• Identify application aspects that are suited to implementation using J2EE technology
• Identify application aspects that are suited to implementation using Enterprise Java Beans
• Identify suitable J2EE technologies for the implementation of specified application aspects
DESIGN PATTERNS:
• Identify the most appropriate design pattern for a given scenario
• Identify the benefits of using design patterns
• State the name of a Gamma et al. design pattern given the UML diagram and/or a brief description of the
pattern's functionality
• Identify benefits of a specified Gamma et al. design pattern
• Identify the Gamma et al. design pattern associated with a specified J2EE technology feature
MESSAGING:
• Identify scenarios that are appropriate to implementation using messaging, Enterprise JavaBeans
technology, or both
• List benefits of synchronous and asynchronous messaging
• Identify scenarios that are appropriate to implementation using messaging
• Identify scenarios that are more appropriate to implementation using asynchronous messaging, rather
than synchronous
• Identify scenarios that are more appropriate to implementation using synchronous messaging, rather
than asynchronous
INTERNATIONALIZATION:
• State three aspects of any application that might need to be varied or customized in different
deployment locales
• List three features of the Java programming language that can be used to create an
internationalizable/localizable application
SECURITY:
• Identify security restrictions that Java 2 technology environments normally impose on applets running
in a browser
• Given an architectural system specification, identify appropriate locations for implementation of specified
security features and select suitable technologies for implementation of those features
Subscribe to:
Posts (Atom)