Solution Architecture

I was recently asked to provide a description of Solution Architecture and define what a Solution Architect actually does. A quick search of the Internet yielded disappointing results. Most articles describe a Solution Architect as assisting in the translation of requirements into a coherent vision or operating at a high design level to create a roadmap for future implementation.

That may be accurate from an outsider’s perspective, but the true goal of the Solution Architect is to assist in process of Solution Selling. Wait… What is Solution Selling?

Rather than just promote an existing product, Solution Sellingfocuses on a customer’s problems and addresses the issue with a variety of products and services. A Solution Architect is a technical pre-sales resource that works closely with sales and the customer to identify the problem, gather requirements and provide a workable solution that all can agree upon. The solution is not just a high-level abstraction of ideas, but is often results in the creation of demos and proof-of-concepts to validate these concepts in the customer’s mind. At the conclusion of the sales cycle, the Solution Architect often works with professional services or the customer’s development staff for a smooth transition from requirements gathering to the implementation phase of the project. This could result in a one-on-one knowledge transfer with a senior developer or through hands-on, group training sessions with the entire development team.

In summary, Solution Architecture is not defined by the nature of its deliverables, it is defined by a specific moment during the sales cycle. It is temporal in nature. No doubt this is why it is term is difficult to quantify, but also why it provides such a unique and richly rewarding atmosphere for those who decide to work in it.

First blog post

This is your wiki's blog first post. Its goal is to provide a short description of your blog's main features.

  • You can create new blog posts through the input field located on your Blog's homepage. The status of a blog post may be any one of the following:
    • Unpublished: your post is still a draft. It can be seen by its creator and by administrators. Once you have clicked publish, you cannot unpublish a post. However, you can choose to hide it.
    • Published: your post can be read by every user that has access to your blog.
    • Published & hidden: your post is published but only its creator and admins can see it. This is useful if you need to make modifications on a post that has already been published by mistake.
  • Every blog article can be tagged and/or categorized:
    • You will be able to browse posts by category using the panel located on the left of the page
    • You can create new categories and subcategories when creating a new post
    • The use of tags allows your article to be found by browsing your wiki's tags, along with any other wiki document
  • Blog-specific panels are available on the left of your blog page:
    • The recent posts lists the most recent entries to any visitor of the blog
    • The unpublished panel lists the blog posts you created, but didn't yet publish
    • The categories panel lets you browse blog posts listed by category and subcategory
    • The archive panel lets you browse blog posts by publication date

Happy blogging!

Created by admin on 2005/01/28 15:50

Blog Archive

All Blogs