Do we need an Architectural Body of Knowledge?

George Bagropoulos — Tue, 13 May 2008 17:33:00 +0000

I have recently read the article of Miha Kralj on the Architectural Journal about the need of an Architectural Body of Knowledge (ArcBOK). He has a facile model of knowledge areas of the ArcBOK:
Design management—Activities related to requirements gathering, modeling, visualization, and communication of IT designs
Analysis management—Activities related to analysis, deduction, innovation, creativity, and problem solving
Delivery management—Activities related to project, engagement, transformation, development, planning, coordinating, and quality management
People management—Activities related to leadership, organizational politics, stakeholder, and relationship management
Strategy management—Activities related to defining the business intent, enterprise strategy, and road maps
Financial and Legal management—Activities related to billing, sourcing, legislation, and procurement
Life-cycle management—Activities that focus on various stages of the IT life cycle, including envisioning, SLA management, change management, and IT decommissioning
(Kralj,2008)

Although in my opinion, many of the proposed areas are covered from the SWEBOK some areas are left uncovered. The role of an IT Architect is to understand the broader needs of the organization, to visualize the technological structure of the organization.

The IT Architect must know in relative depth the technologies she proposes. The IT Architect must also have training in management and in project management. These two areas are usually out of the job description of a Software Engineer.

The IT Architect will be responsible to communicate her architecture to both technical and non-technical stakeholders. I believe that an ArcBOK can complement the SWEBOK. It is easier that a Software Engineer becomes an Architect than a manager or a project manager becomes an IT Architect; because they have no technological training in depth .

We will see the results in the future.

References
IEEE Computer Society(2008). Guide to the Software Engineering Body of Knowledge . Available at: http://www.swebok.org/

Miha Kralj(2008). The Need for an Architectural Body of Knowledge. Available at: http://msdn.microsoft.com/en-us/arcjournal/cc505967.aspx

architecure – Tales from the bits

Do we need an Architectural Body of Knowledge?