Myth: Architects only create Diagrams

Leave a comment

23 Apr 2017 by mallyanitin

Like it or not. Diagrams (visual) are a great communication tool. If one of the responsibility of architects is communication, there is no better way than visual communication. Contextual communication requires that the same information to be represented differently for effective communication.

Architects (titled or not) have a responsibility to analyze data from various sources:

  1. Requirements coming from customer or product manager.
  2. Complaints coming from customer or product manager.
  3. Constraints coming from customer or product manager.
  4. Constraints and opportunities from operational leaders.
  5. Technology advances in industry.
  6. Patterns and practices in architecture.
  7. Feedback from development teams.
  8. Feedback from independent consultants (peers, stakeholders).
  9. Inputs from security teams.
  10. Inputs from operational teams.

All this data needs to be analyzed to produce conceptual and detailed sketches (as required) for construction. Today, most of these sketches are conceptual. Teams are very skilled to develop the detailed sketches right in code.

The architect is like a data scientist working on all this data to determine the function that ‘fits’. This function is represented as a diagram – a view, or a perspective. The diagram could even be a simple table.

Stating that ‘architects only create diagrams’, however, is a poor critique of the effort. Creating conceptual clarity is important for the architect. But the architect’s job does not end at diagrams. They have to communicate, plan, and code. Unless, the diagram is realized, it’s useless.

Just like code and configuration should be treated like ‘code’; documentation and diagrams also need to be treated like ‘code’. This means – reviewed, maintained, tested, critiqued, destroyed, re-factored, …

Only treating ‘code’ like ‘code’ is bad ‘coding’. Code, configuration and concepts need to be treated like ‘code’.

Dismissing concepts (usually the work of an architect) is immature.

The best representation of ‘architecture’ is ‘code’. The first draft’s of ‘code’ are ‘concepts’. ‘Concepts’ are represented as ‘diagrams’ for communication. AND. communication is a good thing.

Enough said.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

mallyanitin

mallyanitin

A leader! Attracted to creativity and innovation. Inspired by simplicity.

View Full Profile →

Architecture Quotes

"Practicing Architects are consultants. Empower them to make them Architects"

"Architecture is the art of keeping things simple. This can get complex"

"Good architecture can be seen, great architecture does not even get in the way of eyes"

"Sometimes a great architecture choice, is not to do anything"

"A good architecture, is great enough, if simple enough to build"

Archives

%d bloggers like this: