Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

It seems that the role of architect varies in between software companies. What does the role of a standard architect include?


  1. Draw high level diagrams and explain to the team why this is a reasonable architecture.

  2. Write documents for managers or customers.

  3. Write the infrastructure of a software upon to which others add more features.

  4. Write various prototypes and run performance tests.

  5. Conceive additional features and improvement to existing features and guide the team towards them.

  6. Other responsibilities.

share|improve this question

closed as not constructive by Oded, gnat, jmquigley, Otávio Décio, Walter Apr 27 '12 at 14:32

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

There is no standard. Every place does something different. There are also different types of "architect" - technical, enterprise, database... –  Oded Apr 27 '12 at 13:28

1 Answer 1

up vote 4 down vote accepted

There are many types of software architects and companies expect them to play different roles based on the company and the projects. But I do believe the following bullet points are necessary for any software architect.

  1. An architect maintains control over the architecture lifecycle parallel to the project’s software development lifecycle.

  2. An architect stays on course in line with the long term vision. When project's scope creep attempts to manipulate software architecture in a certain way in order to satisfy the desires of myriad stakeholders the architect must know when to say "NO" to select requests in order to say "YES" to others.

  3. An architect progressively makes critical decisions that define a specific direction for a system in terms of implementation, operations, and maintenance.

  4. An architect works closely with executives to explain the benefits and justify the investment in software architecture of a solution.

  5. An architect inspires, mentors, and encourages colleagues to apply intelligently customized industry’s best practices.

  6. An architect fights entropy that threatens architect’s structural approach to problem solving.

  7. An architect creates and distributes tailored views of software architectures to appropriate stakeholders at appropriate intervals.

  8. An architect acts as an agent of change in organizations where process maturity is not sufficient for creating and maintaining architecture centric development.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.