Layers of Architecture

There are tons of architects out there today. It seems when you’ve spent enough time as a developer, you end up becoming an architect.  Architecture is not just the next step in a developers career. There are whole new disciplines and methodologies applicable to architecture. That said here are the common levels of architecture.

Enterprise Architecture (planner)

Enterprise architecture is a high level field that concentrates on how the various domains or subject areas interact. This layer spends even more time focusing on how technology will be utilized in the future, and governing how it is used today. Enterprise architects work to create technology roadmaps and work with the business to plan for the implementation. Enterprise architects create technology projects. It is at this layer where frameworks like TOGAF and taxonomies like Zachman come into play. This layer view the enterprise as a holistic entity.

 

Solution Architecture (designer)

A solution is an answer to a question. The question in this case is typically an IT project. The solution architect’s primary objective is to design a solution that meets the projects requirements and also falls in line with the domain and enterprise architecture guidelines. The solution architect is responsible for coordinating with multiple domain architects to design the most appropriate solution. A solution architect may interact with domain architects in infrastructure, web services, data management, and so on. During the course of the project a solution architect will typically create many work products either for communicating the solution to a governance board, to explain the implantation to a developer and various other uses. These work products are eventually owned by the domain architect as codified knowledge of the system after the project implementation.

 

Domain Architecture (owner)

A domain is an area of focus. Domain architects are primarily focused on maintain a specific area of technology or a specific application. These architects are the owners and gatekeepers for a specific area. The work in this area is primarily concerned with the current state of the system. These architects are charged with managing the knowledge for their area. These architects are also responsible for keeping up to date on future projects related to the domain and guiding the designs to meet the overall objectives of the domain. A successful domain architect will know that a future project will require x functionality. When an active project is debating between two possible implementations, the domain architect will be able to guide solution toward the best of the two solutions that meet the future goals.

 

Application or System Architecture(builder)

The application or system architect is primarily focused on the implementation at hand. This is the most detailed level of architecture. An application architect, for instance, would be concerned with the most appropriate design pattern to use in a certain programming situations. These tend to evolve from the most advance developers and engineers. The primary focus here is to implement the best solution for a specific task. Work products that may be produced during this layer are primarily used to communicate to the developers or implementers. In many co-located environments a lead developer often fills this role and very few work products are actually produced. Instead the team may utilized whiteboards or code stubs to communicate the implementation. For larger more dispersed projects, or for outsourced solutions, the application or system architect has a more demanding role for providing detailed implantation instructions. 

 

Conclusion

The various layers of architecture are not meant to be isolated entities. In most situations one architect will fill multiple roles at various levels. Each layer has a unique focus. Understanding the layers helps clarify responsibilities, activates and deliverables. From a career development standpoint individuals can use the layers as the basis for a personal gap analysis and learning plan.

 

I look forward to reading your thoughts and comments.

 

Best of luck in all your endeavors.

Types of presentations

An effective way to prepare a presentation is to begin with a clear understanding of the purpose of the presentation. Generally there are three main types of presentation, each with a different goal. Depending on which type you’re targeting, your content and focus may change.

Discussion Presentation

The primary goal of a discussion presentation is to gather input and feedback from the audience. Discussion presentations are most effective when one or more discussion questions are clearly defined and communicated to the audience. Supporting background information is typically provided to provide context before opening up for discussion. A typical audience for a discussion presentation would include subject matter experts and other core individuals. Multiple discussion presentations may occur in order to include all facets and aspects of a discussion. For example an initial discussion may present a challenge and solicit possible options. A second discussion may present the proposed solution to all impacted parties to solicit feedback from those individuals.

Inform Presentation

Informational presentations are typically geared to larger more general audiences. The focus of an informational presentation is more “matter of fact” in nature, discussing the facts of a situation. Presentations of the Inform type don’t typically ask questions of the audience. Ideally those questions that do surface would look to clarify points within the presentation. Inform presentations can also be thought of as training presentations. The objective is to communicate information clearly from one group to another.

Approval Presentation

Once various alternatives have been considered and evaluated, the Approval presentation provides the opportunity to explain the problem and proposed solution for acceptance by leadership or governing entities before moving forward. Effective approval presentations typically frame the problem, as well as process that led to the solution. With the objective of this presentation type concluding with a yes or no decision, all efforts should be made to answer potential questions well before the actual presentation. This type of presentation should avoid debates about the correct way to accomplish something. Those discussions should occur before this in discussion presentations. The result of those debates and discussion should be summarized in the approval presentation.
Effective approval presentations provide a clear explanation of the problem faced, summary of findings and options reviewed, as well as a brief overview of the steps taken that led to the proposed solution. Most importantly the presentation should clearly communicate what the audience is being asked to approve. At the conclusion of the presentation the audience should have a solid understanding of their task at hand and information required to accomplish the task and approve or deny the proposal.

Conclusion

Regardless of your situation, beginning with a clear understanding of your objective is critical for achieving success, and presentations are no exception. Clearly identifying your presentation type enables you to guide and focus the discussion to meet the real objectives of your presentation. Utilizing the Discuss, Approve, and Inform concepts will help you succeed in your future presentations.

What is Architecture

The word architect, and architecture are thrown around a lot and are frequently misused. There a frameworks, methodologies, classifications that get into extreme detail on what architecture is.  Understanding what architecture means is valuable to excel in a current architect role or for use in career planning and development. The following distills a variety of sources such as Zachman and TOGAF into a more pragmatic summary of architecture.

Architecture (noun)

Units of technology have defined sets of architectural elements. These elements can be applied at any level from a macro / enterprise perspective, down to the view of a simple utility. All technology units contain the following architectural elements.

• Scope Vision Mission Purpose
• Business Process and Models
• Information Architecture (Applications)
• Technologies
• Operation

Architecture (verb)

The practice of architecture is applied with multiple perspectives. Each perspective takes into account the elements from the others, yet has a unique focus and function.

• Enterprise Architecture
  • Strategy & Direction
    • Mission / Vision
  • Guidance & Governance
    • Architectural Principles
    • Architectural Processes
• Domain Architecture
  • Knowledge Management
  • Run Time / Operation
• Solution Architecture
  • Tactical
  • Project

Success in the Corporate World – Part 1 the Basics

There seems to be a lot of people looking for tips on getting ahead in the corporate world. While I may not be a Stephen Covey, I have picked up a few things over the years that may help you.

Confidence

I really think the most important thing you can do is to project confidence at work. Be careful not to be arrogant though. Speak loudly without yelling. Apparently people who talk loud are perceived better than those who talk quietly. I’m sure there’s some psychology behind this but I don’t have it handy. Watch your posture sit and walk as if you were being pulled up by a chain hooked right under your breast bone. This will lift your chest and head up and put your shoulders back.

No one is an expert

This one has two points. First if you think you are an expert, think again, there is always more to learn. Second if you’re talking with someone smarter than you, good, there’s nothing wrong with not having all the answers.

Ask Questions

Don’t just sit there and act like you know what’s going on. Ask what something means. Too many times people just sit there and nod their heads. Asking questions won’t make you look dumb, but acting like you understand something you don’t sure will.  You would be surprised how many people would be asking the same question if they were brave enough. Getting the answer out in public helps get everyone on the same page. Asking questions also shows you’re engaged in the discussion.

Listen

This is important and has many aspects to it. Listening is a lot harder than is sounds. A lot of us want to show people we’re smart so we talk more than we listen. Stop talking! Here’s a really odd thing, you will gain more respect and support by listening than by talking. This is such an important thing I’ll be writing more about it later.

Expand on the conversation

This is a great technique for looking smarter than you are. When you’re in a meeting listen to everyone, then expand on what someone else said. “I think Bob had a great point, by doing X and Y we can see more results, what about adding Z to that, can we get even more results?” The key here is to mention the other persons contribution, it show’s you’re listening. Following it up with a little more info shows you’re providing value.

These a just a few of the basics, I’ll be adding more tips soon. Please feel free to comment with your own tips or questions. More to come.