# Background

The<span style="letter-spacing: -.65pt;"> </span>government<span style="letter-spacing: -.6pt;"> </span>of<span style="letter-spacing: -.65pt;"> </span>Rwanda<span style="letter-spacing: -.6pt;"> </span>has<span style="letter-spacing: -.65pt;"> </span>embarked<span style="letter-spacing: -.6pt;"> </span>on<span style="letter-spacing: -.65pt;"> </span>a<span style="letter-spacing: -.6pt;"> </span>project<span style="letter-spacing: -.6pt;"> </span>to<span style="letter-spacing: -.65pt;"> </span>establish<span style="letter-spacing: -.6pt;"> </span>and<span style="letter-spacing: -.65pt;"> </span>implement<span style="letter-spacing: -.6pt;"> </span>enterprise<span style="letter-spacing: -.65pt;"> </span>architecture (EA) in public entities with the end goal of establishing common architecture standards across all ICT functional units.

This will in turn assist the government in fostering synergies between entities within and across defined clusters. The government has identified the following as some of the topical issues that enterprise architecture will seek to resolve.

1. **Poor support for business needs** – in some sectors, the ICT function has been found to be misaligned with the needs<span style="letter-spacing: -.1pt;"> </span>of the business.<span style="letter-spacing: 2.0pt;"> </span>This is largely because the ICT capabilities have been developed without direct reference to the business requirements
2. **Lack of coordination** – Projects undertaken within some of the entities are not properly coordinated resulting in wasteful expenditure when some resources could have been re-used or <span style="letter-spacing: -.1pt;">shared</span>
3. **Inaccurate scoping of projects** – without a reference point on the ICT and business landscape, projects<span style="letter-spacing: -.45pt;"> </span>are<span style="letter-spacing: -.55pt;"> </span>scoped<span style="letter-spacing: -.45pt;"> </span>based<span style="letter-spacing: -.6pt;"> </span>on<span style="letter-spacing: -.5pt;"> </span>assumption<span style="letter-spacing: -.6pt;"> </span>of<span style="letter-spacing: -.45pt;"> </span>the<span style="letter-spacing: -.4pt;"> </span>impact<span style="letter-spacing: -.4pt;"> </span>and<span style="letter-spacing: -.5pt;"> </span>resources<span style="letter-spacing: -.55pt;"> </span>needed<span style="letter-spacing: -.6pt;"> </span>to<span style="letter-spacing: -.5pt;"> </span>deliver.<span style="letter-spacing: 1.5pt;"> </span>This<span style="letter-spacing: -.5pt;"> </span>has in some cases let to inaccurate project scoping.
4. **Lack of integration and interoperability** – although there are some shared services across some of<span style="letter-spacing: -.65pt;"> </span>the<span style="letter-spacing: -.6pt;"> </span>public<span style="letter-spacing: -.5pt;"> </span>entities,<span style="letter-spacing: -.65pt;"> </span>it<span style="letter-spacing: -.5pt;"> </span>has<span style="letter-spacing: -.65pt;"> </span>been<span style="letter-spacing: -.55pt;"> </span>found<span style="letter-spacing: -.6pt;"> </span>that<span style="letter-spacing: -.65pt;"> </span>their<span style="letter-spacing: -.55pt;"> </span>respective<span style="letter-spacing: -.65pt;"> </span>ICT<span style="letter-spacing: -.5pt;"> </span>functional<span style="letter-spacing: -.6pt;"> </span>units<span style="letter-spacing: -.55pt;"> </span>have<span style="letter-spacing: -.55pt;"> </span>had<span style="letter-spacing: -.65pt;"> </span>minimal collaboration.<span style="letter-spacing: .45pt;"> </span>The<span style="letter-spacing: -.7pt;"> </span>close<span style="letter-spacing: -.6pt;"> </span>association<span style="letter-spacing: -.65pt;"> </span>between<span style="letter-spacing: -.65pt;"> </span>some<span style="letter-spacing: -.7pt;"> </span>of<span style="letter-spacing: -.7pt;"> </span>the<span style="letter-spacing: -.6pt;"> </span>public<span style="letter-spacing: -.6pt;"> </span>entities<span style="letter-spacing: -.65pt;"> </span>calls<span style="letter-spacing: -.7pt;"> </span>for<span style="letter-spacing: -.85pt;"> </span>more<span style="letter-spacing: -.6pt;"> </span>integration
5. **Low<span style="letter-spacing: -.2pt;"> </span>quality<span style="letter-spacing: -.25pt;"> </span>service<span style="letter-spacing: -.3pt;"> </span>delivery<span style="letter-spacing: -.05pt;"> </span>**–<span style="letter-spacing: -.25pt;"> </span>some<span style="letter-spacing: -.25pt;"> </span>complaints<span style="letter-spacing: -.25pt;"> </span>around<span style="letter-spacing: -.3pt;"> </span>quality<span style="letter-spacing: -.2pt;"> </span>of<span style="letter-spacing: -.25pt;"> </span>service<span style="letter-spacing: -.25pt;"> </span>delivery<span style="letter-spacing: -.35pt;"> </span>is<span style="letter-spacing: -.3pt;"> </span>attributed<span style="letter-spacing: -.3pt;"> </span>to lack<span style="letter-spacing: -.2pt;"> </span>of<span style="letter-spacing: -.25pt;"> </span>coordinated<span style="letter-spacing: -.1pt;"> </span>planning<span style="letter-spacing: -.15pt;"> </span>due<span style="letter-spacing: -.1pt;"> </span>to<span style="letter-spacing: -.2pt;"> </span>the<span style="letter-spacing: -.2pt;"> </span>absence<span style="letter-spacing: -.2pt;"> </span>of<span style="letter-spacing: -.25pt;"> </span>reference<span style="letter-spacing: -.2pt;"> </span>point<span style="letter-spacing: -.3pt;"> </span>of<span style="letter-spacing: -.2pt;"> </span>the<span style="letter-spacing: -.2pt;"> </span>current<span style="letter-spacing: -.25pt;"> </span>business<span style="letter-spacing: -.2pt;"> </span>or<span style="letter-spacing: -.25pt;"> </span>ICT landscape.<span style="letter-spacing: 2.0pt;"> </span>This is the gap the enterprise architecture seeks to fill.

It is acknowledged that within each government entity, some of the building blocks that make up enterprise architecture are in existence.<span style="letter-spacing: 2.0pt;"> </span>The challenge, however, is that their development and arrangement has<span style="letter-spacing: -.1pt;"> </span>not<span style="letter-spacing: -.1pt;"> </span>been<span style="letter-spacing: -.3pt;"> </span>properly<span style="letter-spacing: -.05pt;"> </span>coordinated<span style="letter-spacing: -.15pt;"> </span>with<span style="letter-spacing: -.3pt;"> </span>the use<span style="letter-spacing: -.1pt;"> </span>of<span style="letter-spacing: -.1pt;"> </span>common standards and therefore<span style="letter-spacing: -.1pt;"> </span>fail<span style="letter-spacing: -.1pt;"> </span>to provide the added value that the business should be deriving from them.

<span style="font-size: 11.0pt; line-height: 150%; font-family: 'Calibri',sans-serif; mso-fareast-font-family: Calibri; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;">  
</span>

<span style="font-size: 10.0pt; mso-bidi-font-size: 11.0pt;"> </span>

<span style="font-size: 10.0pt; mso-bidi-font-size: 11.0pt; mso-no-proof: yes;">![](https://guidelines.risa.gov.rw/uploads/images/gallery/2025-10/embedded-image-kwxaoeiu.png)</span>

<span style="font-size: 8.0pt; mso-bidi-font-size: 11.0pt;"> </span>Addressing the abovementioned challenges requires a structured approach.<span style="letter-spacing: 2.0pt;"> </span>Within the Enterprise Architecture<span style="letter-spacing: -.65pt;"> </span>practice,<span style="letter-spacing: -.6pt;"> </span>both<span style="letter-spacing: -.65pt;"> </span>methodologies,<span style="letter-spacing: -.5pt;"> </span>standards,<span style="letter-spacing: -.6pt;"> </span>principles,<span style="letter-spacing: -.5pt;"> </span>governance<span style="letter-spacing: -.6pt;"> </span>and<span style="letter-spacing: -.65pt;"> </span>EA<span style="letter-spacing: -.45pt;"> </span>framework<span style="letter-spacing: -.5pt;"> </span>drive<span style="letter-spacing: -.6pt;"> </span>the structured approach.<span style="letter-spacing: 2.0pt;"> </span>The selection of<span style="letter-spacing: -.1pt;"> </span>each of these requirements is important as care must be taken to ensure<span style="letter-spacing: -.2pt;"> </span>that<span style="letter-spacing: -.2pt;"> </span>the<span style="letter-spacing: -.2pt;"> </span>asset<span style="letter-spacing: -.2pt;"> </span>that<span style="letter-spacing: -.2pt;"> </span>is<span style="letter-spacing: -.2pt;"> </span>selected<span style="letter-spacing: -.25pt;"> </span>meets<span style="letter-spacing: -.2pt;"> </span>the<span style="letter-spacing: -.2pt;"> </span>requirements<span style="letter-spacing: -.2pt;"> </span>and<span style="letter-spacing: -.25pt;"> </span>capabilities<span style="letter-spacing: -.35pt;"> </span>of<span style="letter-spacing: -.35pt;"> </span>government<span style="letter-spacing: -.2pt;"> </span>of<span style="letter-spacing: -.2pt;"> </span>Rwanda.

There<span style="letter-spacing: -.65pt;"> </span>are<span style="letter-spacing: -.6pt;"> </span>a<span style="letter-spacing: -.65pt;"> </span>number<span style="letter-spacing: -.6pt;"> </span>of<span style="letter-spacing: -.65pt;"> </span>frameworks<span style="letter-spacing: -.6pt;"> </span>available<span style="letter-spacing: -.65pt;"> </span>that<span style="letter-spacing: -.6pt;"> </span>could<span style="letter-spacing: -.6pt;"> </span>have<span style="letter-spacing: -.65pt;"> </span>been<span style="letter-spacing: -.6pt;"> </span>chosen<span style="letter-spacing: -.65pt;"> </span>to<span style="letter-spacing: -.6pt;"> </span>drive<span style="letter-spacing: -.65pt;"> </span>this<span style="letter-spacing: -.6pt;"> </span>initiative.<span style="letter-spacing: .4pt;"> </span>However, not<span style="letter-spacing: -.15pt;"> </span>all<span style="letter-spacing: -.45pt;"> </span>of<span style="letter-spacing: -.3pt;"> </span>them<span style="letter-spacing: -.25pt;"> </span>meet<span style="letter-spacing: -.25pt;"> </span>the<span style="letter-spacing: -.25pt;"> </span>requirements<span style="letter-spacing: -.4pt;"> </span>of<span style="letter-spacing: -.3pt;"> </span>Rwandan<span style="letter-spacing: -.3pt;"> </span>Government.<span style="letter-spacing: 1.9pt;"> </span>The<span style="letter-spacing: -.15pt;"> </span>framework<span style="letter-spacing: -.4pt;"> </span>that<span style="letter-spacing: -.15pt;"> </span>has<span style="letter-spacing: -.3pt;"> </span>been<span style="letter-spacing: -.3pt;"> </span>chosen<span style="letter-spacing: -.3pt;"> </span>is The Open Group Architecture Framework (TOGAF) because its completeness and applicability.

The selection of TOGAF is based on the appreciation that the framework not only covers are all the required architecture domains but also presents an iterative approach to implementation of enterprise <span style="letter-spacing: -.1pt;">architecture.</span>

<span style="font-size: 11.0pt; line-height: 150%; font-family: 'Calibri',sans-serif; mso-fareast-font-family: Calibri; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;">  
</span>

<span style="font-size: 10.0pt; mso-bidi-font-size: 11.0pt;"> </span>

<span style="font-size: 10.0pt; mso-bidi-font-size: 11.0pt; mso-no-proof: yes;">![](https://guidelines.risa.gov.rw/uploads/images/gallery/2025-10/embedded-image-uhzkgfon.jpeg)</span>

However,<span style="letter-spacing: -.3pt;"> </span>although<span style="letter-spacing: -.5pt;"> </span>TOGAF<span style="letter-spacing: -.6pt;"> </span>is<span style="letter-spacing: -.35pt;"> </span>robust,<span style="letter-spacing: -.3pt;"> </span>it<span style="letter-spacing: -.3pt;"> </span>is<span style="letter-spacing: -.45pt;"> </span>still<span style="letter-spacing: -.35pt;"> </span>too<span style="letter-spacing: -.4pt;"> </span>complex.<span style="letter-spacing: 1.7pt;"> </span>The<span style="letter-spacing: -.45pt;"> </span>decision<span style="letter-spacing: -.5pt;"> </span>was<span style="letter-spacing: -.45pt;"> </span>therefore<span style="letter-spacing: -.45pt;"> </span>taken<span style="letter-spacing: -.3pt;"> </span>to<span style="letter-spacing: -.35pt;"> </span>customize the framework to meet the requirements of Rwanda.<span style="letter-spacing: 2.0pt;"> </span>This decision resulted in the development of the Rwanda Government Enterprise Architecture Framework (RGEA).

[![image.png](https://guidelines.risa.gov.rw/uploads/images/gallery/2025-10/scaled-1680-/ZWMimage.png)](https://guidelines.risa.gov.rw/uploads/images/gallery/2025-10/ZWMimage.png)

Through this modified framework, the core artifacts that are needed to develop enterprise architecture for Government of Rwanda entities are organized per architecture domain to show the horizontal and vertical alignment with other domains.