Michael Platt's WebLog

Computer Engineering

Blogs

Architecture and Architects

  • Comments 1
  • Likes
  • What is architecture?

IT architecture is the use of models, levels of abstraction and relationships in IT systems and processes to manage complexity and simplify communication.

 

http://standards.ieee.org/reading/ieee/std_public/description/se/1471-2000_desc.html

http://www.bredemeyer.com/whatis.htm

http://www.architecture.external.hp.com/Overview/arch_what_architect.htm

http://www.sei.cmu.edu/architecture/

http://www.sei.cmu.edu/architecture/definitions.html

http://en.wikipedia.org/wiki/Software_architecture

 

 

  • Why do we need architecture?

 

Over the years IT projects have grown in size, scope, complexity, expense and criticality. Ad hoc approaches to building these large projects have been consistently shown to fail by cost or time overrun, incorrect or missing functionality, inability to scale or be reliable and in the worst cases the inability to even finish the system.

Other disciplines than IT also have large and complex critical projects and these have been much more successful than IT in completing on time and budget systems. Examining these projects a common theme has been the use of abstraction and modeling to simply the overwhelming complexity and communicate common views to all the stakeholders. This use of abstraction is commonly called architecture and it would appear that architecture is the solution to many of IT’s ills.

A well architected solution is simple, clear, flexible, adaptable, scalable, reliable, highly available and easily understood. Above all it works!

 

http://www.bredemeyer.com/why.htm

http://www.sei.cmu.edu/architecture/

http://www.wwisa.org/wwisamain/phil.htm

 

  • What are architects?

 

Architects are people who can take large and complex problems distill them into models with the appropriate layers of abstraction and then provide multiple views into these models to facilitate communication between all stakeholders.

 

http://www.bredemeyer.com/who.htm

http://www.architecture.external.hp.com/Overview/arch_who_architect.htm

http://www.sei.cmu.edu/architecture/arch_duties.html

http://www.softwaretechnews.com/technews2-3/profession.html

http://www.wwisa.org/wwisamain/role.htm

 

  • What skills do architects have?

 

Architects are able to take complex problems and simplify them by using models and the communicate the elements of the problem to a wide rang eo people. The specific skills that they have are are:

 

Leadership: Architects can develop partnerships with stakeholders across the organization on their projects; that they can mentor others; that they develop and form strong teams; and that they achieve successful results.

Technology Depth: Architects demonstrate that they have a deep understanding of the concepts and application of a number of core technologies (for example, messaging, storage, Windows, networks, etc.) plus the ability to quickly assimilate information about new technologies.

Technology Breadth: Architects understand architectural best practices and are able to apply them across a breadth of technologies to orchestrate a solution. They also have views on the future development of a technology and how it might influence current solutions. Finally, they understand the interaction between infrastructure, solution, and enterprise architecture and practices.

Strategy: Architects demonstrate understanding of enterprise architectural frameworks such as Zachmann and operational frameworks such as ITIL and be able to use these frameworks in their projects. They also understand project management principals and how architects interact with project managers to deliver projects. In addition, they understand the economic dimension of projects and how costs influence the available choices for technology.

Organization Dynamics: Architects show that they are able to recognize the key stakeholders in a project and that they can work with those stakeholders to drive a project to a successful conclusion. They present the ability to pick the right battles at the right time and then recognize the political landscape that influences a project within an organization and then influence organizational politics for the success of their projects.

Tactical/Process: Architects can gather and refine project requirements from both a technical and business perspective. They understand how to effectively prototype and test a solution and also showcase the talent to create effective project artifacts. Lastly, they exhibit the ability to refine project goals and the tactics necessary to achieve those goals as the project develops.

Communication: Architects can maintain well-written and accurate project documentation; they are able to present information on a technical subject in a concise and measured manner; they have the ability to influence others; they have the ability to manage conflicts effectively; and to tailor their communication to the needs of the target audience.

 

http://www.sei.cmu.edu/architecture/arch_duties.html

http://www.softwaretechnews.com/technews2-3/profession.html

http://www.wwisa.org/wwisamain/role.htm

http://www.digital-web.com/articles/soft_skills_for_information_architecture/

http://www.opengroup.org/architecture/togaf8-doc/arch/p4/skills/skills.htm

http://www.from9till2.com/CommentView.aspx?guid=0f47a7aa-66d8-4229-989f-afbe3ae7d8bf

 

 

  • What are the types of architect?

Whilst architects need all of the above skills the technical depth skills and experience level that they have make them fall into one of three architectural categories:

  1. Enterprise

Enterprise Architects work on the architecture of the whole organization, including business, technical, software, infrastructure, security etc. They are concerned in bringing together the organizations IT architectures as a homogenous whole and matching it to the business needs and culture

http://apps.adcom.uci.edu/EnterpriseArch/EARole.html

http://www.bredemeyer.com/who.htm

http://www.zapthink.com/report.html?id=ZAPFLASH-09182003

http://www.martinfowler.com/ieeeSoftware/enterpriseArchitects.pdf

http://www.ftponline.com/ea/magazine/spring/columns/businesscase/

http://www.intelligententerprise.com/020308/505e_business1_1.jhtml

http://www.ewita.com/EA_Overview/ArchitectRole.htm

 

  1. Technical

Technical architects work across a broad architectural domain such as infrastructure or software. They have both breadth and depth expertise in that domain and an understanding of the other domains. Typical technical architecture domains are solutions, applications, infrastructure, integration, security, messaging, information etc.

http://www.bredemeyer.com/pdf_files/role.pdf

http://www.artima.com/intv/architect.html

http://www.developer.com/mgmt/article.php/3504496

http://www.agilearchitect.org/agile/role.htm

http://www.certmag.com/articles/templates/CM_gen_Article_template.asp?articleid=1406&zoneid=225

 

  1. Product

Product level architects have an in depth understanding of the use of a specific product in a technical architecture domain such as Lotus notes in the messaging domain. Typical product architects are Exchange, SQL Server (normally as a DBA), Windows, and Networking etc.

Comments
  • original post on October 26th, 2005
    Just some links for future reference:

    Enterprise Architecture,...