Skip to main content
Institute of Advanced Technological and Commercial Studies

Careers

Enterprise architect

The architect designs coherence: which systems exist, how they exchange data, which to replace and in what order. They decide what will structure the organisation for the next ten years.

Designing the coherence of a whole

Work starts from an honest map: what really exists, including shared files and manual routines nobody documents. The architect then defines landscaping rules — which application owns which reference data, how exchanges happen, what duplication is accepted. They build a transformation roadmap in fundable stages, each delivering its own benefit. Every new project is tested against that frame before it starts.

  • Map an application estate and its real data flows
  • Define reference data and which application owns it
  • Design a transformation roadmap in fundable stages
  • Appraise a solution choice and argue it before an executive team

The estates to be landscaped

  • Banks and insurers with systems inherited across generations
  • Telecom operators with complex billing chains
  • Administrations embarking on digitising their procedures
  • Industrial groups linking management and production systems
  • Consulting firms working on transformation programmes

The figures to keep in mind before deciding

A candidate compares four things first: duration, taught hours, credits and target level. Here they are, in the order that matters. Level sets the responsibility the qualification recognises; hours state the real work asked of you; credits make comparison possible with any other programme, here or elsewhere in the region.

Expert and executive

qualification level
7
months of programme
9

Led by an instructor.

taught hours
700 h

1 credit = 25 h of work, 10 of them taught.

credits
70

Framework of the « Enterprise Architect » qualification, code TP34.

competency blocks
5

The validated skills, one by one

Each block matches a capability the role demands and the assessment verifies. The breakdown comes from the filed framework: it describes an occupation as it is practised, not a subject as it is taught. A block once obtained stays obtained, which makes the path resumable if working life calls for a pause.

Enterprise architecture
190 (27 %)
Technical and data architecture
200 (29 %)
Security, sovereignty and reversibility
170 (24 %)
The economics of architecture
90 (13 %)
Expert conduct
50 (7 %)
Total: 700 taught hours
  • Enterprise architecture · 190 h — Mapping, urbanisation, master plan, technical debt, roadmap
  • Technical and data architecture · 200 h — Distributed systems, integration, data, cloud, agent-based systems
  • Security, sovereignty and reversibility · 170 h — Security by design, hosting, supplier dependency, exit clauses
  • The economics of architecture · 90 h — Total cost of ownership, build-versus-buy, inference cost
  • Expert conduct · 50 h — Convincing without line authority, defending a technical trade-off before leadership

Building an architect's skill set

Here are the paths open to this occupation, with their real cost and duration. A long programme installs the full base; a certificate targets a precise function and can be taken while keeping your job. Both strategies work, and the table gives what you need to choose between them.

ProgrammeDurationCreditsTaught hoursFees
Computer Science programme — Bac+3 level · Bachelor's degree3 years1801800 h5 400 000 GNF per year
Networks and Cloud · Bachelor's degree2 years1201200 h5 600 000 GNF per year
Enterprise architect — Careers | IHETC — IHETC