I received an excellent question from the entry What is a Systems Architect? about what classes and training can help to develop an experienced IT person into a "Systems Architect."

First, to be considered for a Systems Architect position, it typically requires several (usually 8-10+) years of IT experience with an established reputation as an expert within a specific area. For example, many of my fellow architects have deep knowledge in at least one of more areas including security, collaboration, middleware, networking, mobile devices, governance, Service Oriented Architecture and messaging, mainframe development, open systems development, Windows development, web development, storage, database, and specific vertical business applications.

Once you have had proven success and a solid background in a few technology areas, it may be time to consider working with the broader picture for design and planning - which is why many consider the Systems Architect role.

To answer what training is best, I'd like to look at what skills are most needed:

1. Soft Skills

Probably the most overlooked and yet probably the most important skill that differentiates those that choose this path. Most companies consider the Systems Architect role as equivalent to a middle manager role and also expect the soft skills to be on par with this "peer group." This role requires a significant amount of selling the ideas, concepts, plans, direction, and evaluations to both developers and IT people as well as to business and technology management teams.

Top soft skills to consider:

Verbal Communication Skills. Consider courses on making and delivering presentations, becoming more influential (think sales types of courses), and any improvement in language. A good option may also be Toastmasters to allow for practice in making presentations in front of groups.

Written Communication Skills. Start reading the documentation that is produced internally by the architecture groups. There are also many classes that can assist that range from email to full evaluation documentation and architecture drawings. See what the current group is producing today and start working on creating similar documentation for your own group or area.

Interpersonal Communication Skills. Get an honest assessment of your own interpersonal skills and be aware of them as you work with others. Learn how to become more flexible and adjust to a given situation is extremely important. A Systems Architect has to work with a wide variety of people that include upper management, middle management, technology developers, support groups, project managers, vendors, and customers. Look for courses in areas that you feel you need some help.

2. Functional Skills

A Systems Architect role is ever changing depending on the current strategy and priorities of the company. It is important to be always in the mode of continuous learning. I usually aim for at least 2-3 new training classes or seminars every year in addition to regular reading on new technologies or architecture best practices and background. There are a few Systems Architecture and Enterprise Architecture courses or conferences that can help to provide many of the concepts shown below.

Some of the required reading or classes should include the following:

Enterprise Architecture Frameworks . It is important to have an understanding of the main architectural frameworks which includes POSIX, TOGAF, Zachmann, DoDAF, and FEAF. Determine which one that you and your company have adopted - or more likely what variation or combination of framework.

Architecture Diagram Examples. There is no standard format for these but an investigation of the ones internal to the organization as well as the various examples of Conceptual, Logical, and Physical diagrams. It is best to have an understanding of the differences of each of these diagrams along with various techniques for modeling dependent on the type of project and solution.

Unified Modeling Language or UML . This will provide a background understanding and good foundation for many diagrams and documentation. UML is a method of defining an abstract or complex solution using a standardized visual model.

Business Strategy Development. Understand the current strategies, how they were developed, and who developed them. Understand the impact based upon business, applications, and infrastructure.

Technology Lifecycle and Evaluation. Evaluation of current and new technologies and products and their lifecycle to include emerging technologies to retired technologies. This includes making choices of when to introduce these new technologies and when they should be replaced.

Architecture Principles and Policies. Architecture decisions need to be made based upon a common direction. Review your company's or other company's written principles and policies.

Governance and Policies. This will depend on your given vertical marketplace but include different organizations such as SOX or ISO.

Vendor Management. Related classes could include ethics and legal courses in addition to understanding how to develop Request for Information and Request for Proposals.

Project Management. Many Systems Architects may also be required to lead the technology portion of a project.

I look forward to any comments on other recommended areas for building your Systems Architect portfolio.

"With the current economic situation, it wasn’t even really a surprise that my former company was downsizing, and that included my termination. With the amount of experience I had, I felt that finding a new job wouldn’t be as difficult as it turned out to be. With the bills piling up and still no job, a friend referred me to www.careersuccessions.com . On the site, I was able to find the job that I have today, which I can honestly say has been the most fulfilling company I have every worked for. When you are looking for career guidance that doesn’t waste your time or money, seriously consider www.careersuccessions.com .