NYCJAVA-Wiki: Part 1 Objectives Notes

At line 2 changed 3 lines.

* [1.1|SCEA 5 Pt.1 1.1] Explain 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.2|SCEA 5 Pt.1 1.2] Describe 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.3|SCEA 5 Pt.1 1.3] Describe 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.

* [1.1|SCEA 5 Pt.1-1.1] Explain 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.2|SCEA 5 Pt.1-1.2] Describe 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.3|SCEA 5 Pt.1-1.3] Describe 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.

At line 7 changed 5 lines.

* [2.1|SCEA 5 Pt.1 2.1] Explain the advantages and disadvantages of two tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security.

* [2.2|SCEA 5 Pt.1 2.2] Explain the advantages and disadvantages of three tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security.

* [2.3|SCEA 5 Pt.1 2.3] Explain the advantages and disadvantages of multi-tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security.

* [2.4|SCEA 5 Pt.1 2.4] Explain the benefits and drawbacks of rich clients and browser-based clients as deployed in a typical Java EE application.

* [2.5|SCEA 5 Pt.1 2.5] Explain appropriate and inappropriate uses for Web Services in the Java EE Platform.

* [2.1|SCEA 5 Pt.1-2.1] Explain the advantages and disadvantages of two tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security.

* [2.2|SCEA 5 Pt.1-2.2] Explain the advantages and disadvantages of three tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security.

* [2.3|SCEA 5 Pt.1-2.3] Explain the advantages and disadvantages of multi-tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security.

* [2.4|SCEA 5 Pt.1-2.4] Explain the benefits and drawbacks of rich clients and browser-based clients as deployed in a typical Java EE application.

* [2.5|SCEA 5 Pt.1-2.5] Explain appropriate and inappropriate uses for Web Services in the Java EE Platform.

At line 14 changed 3 lines.

* [3.1|SCEA 5 Pt.1 3.1] Explain 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.2|SCEA 5 Pt.1 3.2] Explain typical uses of Web Services and XML over HTTP as mechanisms to integrate distinct software components.

* [3.3|SCEA 5 Pt.1 3.3] Explain how Java Connector Architecture and JMS are used to integrate distinct software components as part of an overall Java EE application.

* [3.1|SCEA 5 Pt.1-3.1] Explain 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.2|SCEA 5 Pt.1-3.2] Explain typical uses of Web Services and XML over HTTP as mechanisms to integrate distinct software components.

* [3.3|SCEA 5 Pt.1-3.3] Explain how Java Connector Architecture and JMS are used to integrate distinct software components as part of an overall Java EE application.

At line 20 changed 4 lines.

* [4.1|SCEA 5 Pt.1 4.1] Explain 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.2|SCEA 5 Pt.1 4.2] Explain 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.3|SCEA 5 Pt.1 4.3] Explain 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.4|SCEA 5 Pt.1 4.4] Explain the benefits of the EJB3 development model over previous EJB generations for ease of development including how the EJB container simplifies EJB development.

* [4.1|SCEA 5 Pt.1-4.1] Explain 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.2|SCEA 5 Pt.1-4.2] Explain 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.3|SCEA 5 Pt.1-4.3] Explain 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.4|SCEA 5 Pt.1-4.4] Explain the benefits of the EJB3 development model over previous EJB generations for ease of development including how the EJB container simplifies EJB development.

At line 26 changed 4 lines.

* [5.1|SCEA 5 Pt.1 5.1] State the benefits and drawbacks of adopting a web framework in designing a Java EE application.

* [5.2|SCEA 5 Pt.1 5.2] Explain standard uses for JSP and Servlet technologies in a typical Java EE application.

* [5.3|SCEA 5 Pt.1 5.3] Explain standard uses for JSF technology in a typical Java EE application.

* [5.4|SCEA 5 Pt.1 5.4] Given 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.

* [5.1|SCEA 5 Pt.1-5.1] State the benefits and drawbacks of adopting a web framework in designing a Java EE application.

* [5.2|SCEA 5 Pt.1-5.2] Explain standard uses for JSP and Servlet technologies in a typical Java EE application.

* [5.3|SCEA 5 Pt.1-5.3] Explain standard uses for JSF technology in a typical Java EE application.

* [5.4|SCEA 5 Pt.1-5.4] Given 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.

At line 34 changed 3 lines.

* [6.1|SCEA 5 Pt.1 6.1] Given a specified business problem, design a modular solution implemented using Java EE which solves that business problem.

* [6.2|SCEA 5 Pt.1 6.2] Explain how the Java EE platform enables service oriented architecture (SOA) -based applications.

* [6.3|SCEA 5 Pt.1 6.3] Explain 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.

* [6.1|SCEA 5 Pt.1-6.1] Given a specified business problem, design a modular solution implemented using Java EE which solves that business problem.

* [6.2|SCEA 5 Pt.1-6.2] Explain how the Java EE platform enables service oriented architecture (SOA) -based applications.

* [6.3|SCEA 5 Pt.1-6.3] Explain 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.

At line 40 changed 4 lines.

* [7.1|SCEA 5 Pt.1 7.1] From 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.2|SCEA 5 Pt.1 7.2] From 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.3|SCEA 5 Pt.1 7.3] Select 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.4|SCEA 5 Pt.1 7.4] Select 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.

* [7.1|SCEA 5 Pt.1-7.1] From 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.2|SCEA 5 Pt.1-7.2] From 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.3|SCEA 5 Pt.1-7.3] Select 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.4|SCEA 5 Pt.1-7.4] Select 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.

At line 46 changed 4 lines.

* [8.1|SCEA 5 Pt.1 8.1] Explain the client-side security model for the Java SE environment, including the Web Start and applet deployment modes.

* [8.2|SCEA 5 Pt.1 8.2] Given an architectural system specification, select appropriate locations for implementation of specified security features, and select suitable technologies for implementation of those features.

* [8.3|SCEA 5 Pt.1 8.3] Identify and classify potential threats to a system and describe how a given architecture will address the threats.

* [8.4|SCEA 5 Pt.1 8.4] Describe 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.

* [8.1|SCEA 5 Pt.1-8.1] Explain the client-side security model for the Java SE environment, including the Web Start and applet deployment modes.

* [8.2|SCEA 5 Pt.1-8.2] Given an architectural system specification, select appropriate locations for implementation of specified security features, and select suitable technologies for implementation of those features.

* [8.3|SCEA 5 Pt.1-8.3] Identify and classify potential threats to a system and describe how a given architecture will address the threats.

* [8.4|SCEA 5 Pt.1-8.4] Describe 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.