Architecting and Designing J2EE Applications (Applying SOA)

Beskrivelse:
Participants will gain an understanding of the strategies needed to create application blueprints that work well when implementing J2EE technologies. These strategies include effective decision making through the use of systemic qualities (such as scalability and flexibility), J2EE technology blueprints and design patterns, and iterative and incremental development.

Målgruppe:
J2EE Architects, System Designers and Developers

Forkunnskaper:
Students should be able to describe the different J2EE components. Students shoud also have a working knowledge of UML.

Throughout this course, students will explore a practical case study using the HighView’s "Borrow and Fly" System example. Students will build the systems from the ground up, from requirements gathering through architecturally correct implementation of a few selected use cases.

Working within this environment, students will capture the requirements, investigate systematic qualities and then establish the business Architecture in terms of Business Components and the services. Students will also learn how to (and will) define the technical architecture based in the non-functional requirements (systematic qualities), map their Business Architecture to the Technical Architecture, and design and build a few components based on that architecture (this will include EJB 2.1 development).

Throughout the course, students will explore the overall software architecture (including the presentation tier) and best practices for development. This will give the students the possibility to design, implement and assemble a solution for three use cases (using the components developed earlier)

Workshop overview

This is an overview of the course. For a detailed description with objectives per topic, we refer to the detailed workshop overview, listed further below in this document.

Session: The Business Architecture: Service and Component Based Design/Development (sCBD)

• Lesson: Introduction to Service Orientation and CBD
• Lesson: Describing a Service Oriented Process (SOP)

Session: Applying sCBD’s Component Modeling

• Lesson: The Requirements Capture Phase
• Lesson: Defining the Service Architecture

Session: Enterprise Architectures and a Justification for using J2EE

• Lesson: The Technical Enterprise Architecture
• Lesson: J2EE as a Candidate Framework for your Architecture
• Lesson: J2EE vendors and market

Session: Technical overview of J2EE

• Lesson: Overview of the Complete architecture
• Lesson: Presentation Tier
• Lesson: Application Tier
• Lesson: EIS Tier
• Lesson: Security

Session: Mapping to the Technical Architecture

• Lesson: (J2EE) Design Patterns summary
• Lesson: Mapping Components to a (distributed) J2EE Environment
• Lesson: The Internal Design Phase (Component Delivery)
• Lesson: Overall (Web-Based) J2EE Architectures

Appendix: Introduction to UML 2.0

• Lesson: Introduction
• Lesson: Use-Case Models in UML 2.0
• Lesson: Structural and Implementation models
• Lesson: Dynamic models

Appendix: Model Driven Architecture overview

• Lesson: Overview of MDA
• Lesson: MDA applied in an actual design

Appendix: Introduction to Design Patterns

• Lesson: Introduction to Design Patterns

Appendix: Exploring (GoF) Patterns

• Lesson: Exploring Creational Design Patterns
• Lesson: Exploring Behavioral Design Patterns
• Lesson: Exploring Structural Design Patterns