J2EE
Common Architectures and Protocols

■ Given an architecture described in terms of network layout, list benefits and
potential weaknesses associated with it.


■ Role of an architect
■ Architecture defined
■ Architectural terms
■ Architecture versus design
■ Fundamentals of architecture
■ Capabilities of an architecture
■ Design goals of architecture
■ Architecture tiers and layers
■ Benefits and weaknesses of architecture
■ Protocols: HTTP, HTTPS, IIOP
Types of Architecture
System Architecture >>>> 60%
Reference Architecture >>>> 50%
Flexible Reference Architecture >>>> 50%

Architectural Design and Principles
Where Architecture Fits in Analysis, Design, and Development >>>> 50%
Architecture vs. Design >>>> first 50%
■ A system architecture document to describe your existing hardware, software, network topology, and other components.
■ An application architecture document to describe the application’s major structure, including a logical view of all architecturally significant components, use case components, and legacy components.
■ A components design guideline to describe all design guidelines and architectural decisions, explain all those decisions, and describe possible consequences if an alternative option is used. These guidelines should capture all-important base determinants that the new component design must respect to maintain the system’s architectural integrity.
■ An architectural prototype to evaluate new technologies, gain experience developing and deploying J2EE applications, build architectural frameworks, and address risks by measuring performance and scalability, as well as proof of concept for the project stakeholders.
Steps in Software Development >>>> 50%
Requirement Analysis/Problem Statement
Object-Oriented Analysis
Architectural Analysis
design guideline(User Case, Sequence, Class, Collaboration Diagrams)
Object-Oriented Design
Architectural Design
Ultimately the object creation
■ Develop package dependency diagrams.
■ Decide how the classes in different package interact.
■ Develop deployment diagrams.
■ Decide where the software components will reside in deployment.

Architectural Terminology >>>> 50%
Abstraction >>>>
Surface Area >>>>
Boundaries >>>>
Brittleness >>>>
Capabilities, Friction, and Layering >>>>

Principles of Architecture
Layering >>>>
Tiers >>>>
Basic Three-Tier Java Technology Architecture >>>>
Capabilities of an Architecture >>>>

Creating an Architecture
Using Distributed Services and J2EE
Enterprise JavaBeans >>>>
Distributed Application Lifecycle >>>>
Iterative Development/MVC >>>>
Simplified Architecture and Development >>>>
Component-Based Application Models >>>>
Support for Client Components >>>>
Support for Business Logic Components >>>>

J2EE API’s and Certification
J2EE Specification >>>>
J2EE Reference Implementation >>>>
Sun BluePrint Design Guidelines for J2EE >>>>

XML and J2EE
Why Use XML? >>>>
Electronic Data Exchange and E-Commerce >>>>
Electronic Data Interchange (EDI) >>>>
Enterprise Application Integration (EAI) >>>>
Software Development and XML >>>>
XML Technology and the Java Platform >>>>

Distributed Programming Services
Naming and Registration >>>>
Remote Method Invocation (RMI) >>>>
Protocols >>>>
Distributed Object Frameworks >>>>