Literature and experience go hand in hand but, on the literature side I can recommend reading:
- Mastering Enterprise JavaBeans - Applied Java Patterns - Core J2EE Patterns - Patterns of Enterprise Application Architecture - J2EE Technology in Practise - Using UML - Distilled UML - UML 2.0 User Guide - SCEA Study Guide - "Any good OOA&D book" - Design Patterns [GoF] - learn definitions for part 1
Books that are not required as part of the SCEA but are highly recommend by architects in the trade:
- Pattern-orientated Software Architecture (all three books!) - Enterprise Integration Patterns - Large scale Software Architecture - Software Architect Boot Camp - very good introduction to architecture principles - Applied Software Architecture - Rational Unified Process Made Easy - Refactoring to Patterns - Developing Java Web Services - Practical Guide to Enterprise Architecture - Enterprise SOA - a must for any architect - Enterprise Service Architecture
These are but a few of the books on my bookshelf, I've probably another 100 or so sitting around either in the loft or in cupboards. Being an architect is about constantly being one step ahead in order to be able to provide that extra level of judgement and vision into proposed solutions. You are often looked upon as a source of information, which means that a large volume of books, courses, CBTs, Web courses etc., are consumed on a yearly basis. I personally read a book at least once a month in order to learn something new, upgrade or simply to refresh existing knowledge - obviously that is on top of my normal work hours, which can be quite excessive.
Good luck, :roll:
Ian Roberts<br />Application Architect<br />SCJP, SCJD, SCEA, OCUP Fundamental