Duchess
Globally Connecting Women in Java Technology

It’s been a year since I attended a bootcamp for Sun Certified Enterprise Architect and I noticed that I never published these study tips. The course went from fundamental architectural concepts to using current Java technology to design software.

I really liked learning the SunTone Architecture Methodology – specifically the SunTone cube, which helped me visualize and make connections to infrastructure. What I liked less is the focus on Java design patterns, some of which are outdated, and a focus on (although a little understandably) Sun technology. The problem is these days – knowing the Sun way of doing things (EJB3, JSF, etc) is not the only choice. There is definitely a gap there for a more comprehensive Java Architecture course that comprises of all mainstream Java technology and help make the choices between them. Overall, I found that it was a good opportunity to focus and learn for a week on architecture and design. I’m glad to find that UML is still relevant in the face of agile development, although people haven’t talked about it much in more than 10 years.

SunTone Architecture Methodology
To aid in the development of enterprise applications, Sun Java Center formulated the SunTone Architecture Methodology (SunTone AM) in the late 90′s. Enhancing RUP with the SunTone cube, it has now evolved to have more agile influences. SunTone AM introduced the SunTone cube to describe primary concerns in enterprise applications. The three faces on the cube represented layers, tiers, and systemic qualities.

Layers
Layers are usually in the domain of infrastructure architects, where the application sits on top of infrastructure components.

• Application – software
• Virtual Platform – interfaces to the middleware for decoupling
• Application Infrastructure – middleware
• Enterprise Services – OS
• Compute & Storage – hardware
• Network Infrastructure – network

Tiers
Tiers are well-known to application architects. They describe how an application is decomposed into modules to reduce coupling and enhance system flexibility. Annoyingly, tiers are sometimes called layers, when not in the context of SunTone.

• Client Tier – browsers, standalone clients
• Web Presentation Tier – HTTP requests
• Business Tier
• Integration Tier – interfaces with resources
• Resource Tier – DBMS, mainframe, EIS

Systemic Qualities
Systemic qualities help establish the quality of service that a system can deliver. Different systemic qualities impose different constraints on the design of a system. This list correlates to Non-Functional Requirements (NFR) that when prioritized help make choices in system design that take quality, time, and costs into consideration.

• Manifest Qualities
  • Performance
  • Reliability
  • Availability
  • Usability
• Operational Qualities
  • Throughput
  • Manageability
  • Security
  • Serviceability
  • Testability
• Developmental Qualities
  • Realizability
  • Planability
• Evolutionary Qualities
  • Scability
  • Maintainability
  • Extensibility
  • Flexibility

The Multiple Choice Exam
A lot of passing the exam has to do with learning the terminology.
The multiple choice exam tests knowledge from roughly 8 areas:

1. Application Design Concepts + Principles
   • encapsulation, inheritance, separation of concerns
2. Common Architectures
   • 2-tier, 3-tier, multi-tier, rich clients vs. browser/thin clients, web services
3. Integration + Messaging
   • communication w/ external systems, WS+XML over HTTP, JCA, JMS
4. Business Tier Technology
   • Enterprise Beans, Enterprise Classes, Stateful/Stateless Session Beans, Message Driven Beans
   • CMP/BMP, JDO, JPA, ORM, DAO, JDBC, JAX WS, EJB 3.0
5. Web Tier
   • Web Framework, JSPs, Servlets , JSF
6. Applicability of J2EE Technology
   • Designing modular solutions, SOA, measuring NFR, refactoring
7. Design Patterns
   • GoF Design Patterns
   • Core J2EE Design Patterns
8. Security
   • Client-side security: WebStart, applet deployment
   • potential threats
   • encryption, hash, SHA, asymmetric vs symmetric
   • JAAS

Resources

• SunTone Architecture Methodology
• The Java EE 5 Tutorial
• Gang of Four Design Patterns
• Core J2EE Design Patterns

Agile Open Holland is the conference by and for you! Organized by Agile Holland, it is an Open Space conference, where the program is made by the participants at the start of each conference day. You can propose discussions, workshops, simulations, games, coding dojos, whatever topics and formats you are passionate about and want to take responsibility for.

Since the conference is what you make it, you’ll come back to work re-energized, filled with fresh ideas to make your work more fun, more productive and more profitable.

Find out the details and register!

Coding Dojos are inspired by the Socratic Circle, a learning method that involves questions and debate between participants and teacher, illuminating different points of views.

Come learn and practice TDD (Test-Driven Development) with FitNesse, an acceptance testing framework that enables you to communicate progress with business and customers, while improving your programming skills.

You are welcomed to join us on Friday evening, June 18, in the Amsterdam Public Library (Openbaar Bibliotheek Amsterdam) – next to Amsterdam Central Station – for a coding dojo with a focus on TDD with FitNesse.

We are very happy to have Marc Evers from QWAN and Agile Holland lead us through this dojo.

We will start at the La Place upstairs (7th floor) for food at 18:00 and will move to the meeting room (6th floor) to start at 19:00 and go until 22:00 at the latest.

We ask a voluntary 10 Euro participation fee to cover expenses.
Please sign up each attendee individually so we can track attendance.

Space is limited to 20 participants – so first come first serve!

The Amsterdam Public Library is easily accessible by public transport or car.
For those who want to drive, Parkeergarage Oosterdok is the closest parking garage.