It Architects And Engineers

1,031 views

Published on

A short comparison and description of the roles of IT Architecture and Engineer. These are loose terms often misused and not well defined.

Published in: Technology, Design, Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,031
On SlideShare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
29
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

It Architects And Engineers

  1. 1. IT Architects and Engineers<br />12/30/2009<br />David Champeau - ECM Consultant<br />
  2. 2. IT Architects and Engineers<br />Different roles and responsibilities<br />Different backgrounds, education, thought processes<br />Work together and overlap knowledge bases<br />Introduction<br />
  3. 3. There are many flavors<br />Enterprise Architect<br />Solution Architect<br />System Architect<br />Application Architect<br />Software Architect<br />IT Architects<br />
  4. 4. Then there are more specialized architects<br />Network Architect<br />Storage Architect<br />Security Architect<br />Infrastructure Architect<br />Portal Architect<br />IT Architects<br />
  5. 5. Now there are new, emerging disciplines<br />Process Architect<br />Information Architect<br />IT Architects<br />
  6. 6. The term “architect” was borrowed from the building trades<br />It describes the “design” aspect of the job<br />The word “architect” is regulated in many US states<br />Architect defined<br />
  7. 7. The architect (working with other SMEs like plumbers and electricians) designs a house<br />A lot of detail is put into the design<br />There are many different views that make up the overall design<br />The design is done before any nail is pounded or cement poured<br />If new techniques (technologies) are to be used then tests are run, prototypes built<br />But the house is not started without the design completed and signed off<br />Designing a house<br />
  8. 8. My builder once told me “he (the architect) never pounded a nail.”<br />The design can change as the house is built<br />Some things are missed<br />Details are added or changed<br />Walls are moved<br />Building a house<br />
  9. 9. Even thought the builder is required to change some of the details because something is missed or added, the details are put on paper by the architect before the foundation is poured<br />It is the architects job to think things through as much as possible<br />And this can only be done on “paper” (or Visio, etc.)<br />Details<br />
  10. 10. The Enterprise Architect works with stakeholders, both leadership and SMEs, to build a holistic view of the organization’s strategy, process, information and information technology assets<br />The role is to take this knowledge and ensure that the business and IT are in alignment<br />Enterprise Architect<br />
  11. 11. Strategic Thinking<br />Across projects<br />System Interactions<br />Highly Abstracted<br />Communication<br />Across Organization<br />Design<br />Minimal, High Level<br />Enterprise Architect<br />
  12. 12. Delivered successfully, an enterprise architecture has the potential to allow both the business and IT strategies to enable and drive each other<br />Enterprise Architecture<br />
  13. 13. Responsibilities<br />Alignment of IT strategy and planning with business goals<br />Optimization of information management approaches <br />Work with other architects, SMEs, engineers<br />Enterprise Architect<br />
  14. 14. In today’s complex, specialized, interconnected world, IT projects require a team of architects to design a complex system<br />IT Architects<br />
  15. 15. Enterprise Architect<br />Like a city planner<br />Provide the roadmaps and regulations used to manage city growth and services<br />System Architect<br />Plans one or more buildings<br />Software Architect<br />Plans Heating, Ventilation and A/C<br />Network Architect<br />Plans plumbing, electricity, water and sewer<br />IT Architects<br />
  16. 16. There are many flavors<br />Software Engineer<br />Security Engineer<br />Network Engineer<br />Performance Engineer<br />Release Deployer<br />IT Administrator<br />System Tester<br />Front End Java Script Engineer<br />IT Engineers<br />
  17. 17. Design and Build things<br />Software engineer will design a program for a specific task or function and then write the code<br />IT Administrator will write scripts to monitor a component of a system<br />System tester will write scripts or configure a tool to test a system<br />IT Engineers<br />
  18. 18. Architects design<br />Engineers build<br />Architects would do well to have spent some time as engineers<br />Confusing<br />
  19. 19. Architect<br />Sees a bigger picture<br />Able to communicate the future state<br />Works and communicates well with others<br />Comprehensive knowledge of many areas<br />Uses multiple methodologies<br />Skills and Knowledge<br />Engineer<br />More detail focused<br />Able to work alone or in a team<br />Detailed knowledge of a few select areas<br />Understands how to build and test<br />Uses methodoligies<br />
  20. 20. Architects design before anything is built<br />Engineers take the design and determine how to build (or if it can be built)<br />The more effort put into the design, the greater the chance for success<br />The better the communication, the greater the chance for success<br />Summary<br />

×