The term “Architect” is used as a metaphor to describe numerous disciplines. It sometimes seems as if a new job can be defined simply by adding an adjective to it! For this reason, it is important to specify: functional architect, technical architect, enterprise architect, etc.
The common feature shared by all architecture disciplines, a feature borrowed from the primary meaning of architecture, is the following:
An architect will consider the system in its entirety; taking decisions about the overall structure.
This is what differentiates an architect from a designer. Both draw up a solution, design something to build, but, while the designer examines the details, the architect decides on the broad outline.
It can also be expressed in terms of Reach?. The architect is responsible for the global reach of the system in question.
We could use the definition that each architecture discipline has provided for itself: Business Architecture in BABoK?, Enterprise Architecture in TOGAF, etc.
However, Praxeme first lays the overall framework – the Enterprise System Topology – and from there defines the disciplines. The definition therefore comes from its positioning. In addition to the notion of reach, the aspect(s) for which the architect is responsible are specified. This means of proceeding – positioning upon a common framework – has the advantage of clarifying, from the outset, the responsibilities and articulations, as demonstrated in the following schema.
<< to do: EST with the actors (names in French) linked to the aspects that they are responsible for; links to the corresponding pages >>