# Reference Models

Application Reference Model

It is acknowledged that public entities fall within different industries and therefore have different and unique requirements.<span style="letter-spacing: 2.0pt;"> </span>These requirements inform the structure and arrangement of some of the attributes that respective entities have. As such, therefore, there will be different reference models for each industry / cluster.

One of the important reference models that will need to be developed for each cluster will be the application Reference Model.

The application reference model presents a structure view of the applications that each entity uses in relation to the business requirements.<span style="letter-spacing: 2.0pt;"> </span>The model reflects core capabilities and the applications that are

<span style="font-size: 11.0pt; 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;">used within and organization as well as the enterprise wide application needs which are viewed as organization enablers.<span style="letter-spacing: 2.0pt;"> </span>Below is a diagram of a sample application reference model.</span>

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

[![image.png](https://guidelines.risa.gov.rw/uploads/images/gallery/2025-10/scaled-1680-/VFGimage.png)](https://guidelines.risa.gov.rw/uploads/images/gallery/2025-10/VFGimage.png)The top-level view of the model merely depicts the capabilities of respective applications per business / functional areas.<span style="letter-spacing: 2.0pt;"> </span>Concealed within the top level view are the actual names of applications.<span style="letter-spacing: 2.0pt;"> </span>While this diagram<span style="letter-spacing: -.6pt;"> </span>is<span style="letter-spacing: -.6pt;"> </span>important<span style="letter-spacing: -.55pt;"> </span>and<span style="letter-spacing: -.6pt;"> </span>conveys<span style="letter-spacing: -.55pt;"> </span>important<span style="letter-spacing: -.55pt;"> </span>information,<span style="letter-spacing: -.55pt;"> </span>the<span style="letter-spacing: -.55pt;"> </span>real<span style="letter-spacing: -.65pt;"> </span>value<span style="letter-spacing: -.55pt;"> </span>comes<span style="letter-spacing: -.55pt;"> </span>from<span style="letter-spacing: -.5pt;"> </span>the<span style="letter-spacing: -.55pt;"> </span>ability<span style="letter-spacing: -.55pt;"> </span>to<span style="letter-spacing: -.5pt;"> </span>conduct impact assessment for each application.<span style="letter-spacing: 2.0pt;"> </span>This view provides a strong foundation for determining the extent at which an application is used within the environment.

Within<span style="letter-spacing: -.1pt;"> </span>*Sparx Enterprise Architect* and<span style="letter-spacing: -.05pt;"> </span>indeed<span style="letter-spacing: -.05pt;"> </span>any other<span style="letter-spacing: -.05pt;"> </span>repository-based<span style="letter-spacing: -.15pt;"> </span>enterprise architecture<span style="letter-spacing: -.15pt;"> </span>toolset, it<span style="letter-spacing: -.45pt;"> </span>is<span style="letter-spacing: -.45pt;"> </span>possible<span style="letter-spacing: -.55pt;"> </span>to<span style="letter-spacing: -.4pt;"> </span>select<span style="letter-spacing: -.55pt;"> </span>an<span style="letter-spacing: -.5pt;"> </span>artefact<span style="letter-spacing: -.55pt;"> </span>such<span style="letter-spacing: -.5pt;"> </span>as<span style="letter-spacing: -.55pt;"> </span>an<span style="letter-spacing: -.5pt;"> </span>application<span style="letter-spacing: -.6pt;"> </span>and<span style="letter-spacing: -.5pt;"> </span>view<span style="letter-spacing: -.5pt;"> </span>all<span style="letter-spacing: -.6pt;"> </span>other<span style="letter-spacing: -.55pt;"> </span>entities<span style="letter-spacing: -.55pt;"> </span>that<span style="letter-spacing: -.45pt;"> </span>are<span style="letter-spacing: -.55pt;"> </span>associated<span style="letter-spacing: -.45pt;"> </span>with it.<span style="letter-spacing: 1.9pt;"> </span>In<span style="letter-spacing: -.35pt;"> </span>this<span style="letter-spacing: -.3pt;"> </span>case,<span style="letter-spacing: -.25pt;"> </span>the<span style="letter-spacing: -.25pt;"> </span>application<span style="letter-spacing: -.3pt;"> </span>reference<span style="letter-spacing: -.4pt;"> </span>model<span style="letter-spacing: -.25pt;"> </span>will<span style="letter-spacing: -.3pt;"> </span>enable<span style="letter-spacing: -.25pt;"> </span>decision<span style="letter-spacing: -.35pt;"> </span>makers<span style="letter-spacing: -.25pt;"> </span>to<span style="letter-spacing: -.2pt;"> </span>see<span style="letter-spacing: -.35pt;"> </span>the<span style="letter-spacing: -.25pt;"> </span>business<span style="letter-spacing: -.25pt;"> </span>areas<span style="letter-spacing: -.3pt;"> </span>and services that utilize a specific application.<span style="letter-spacing: 2.0pt;"> </span>In that way, when change is being considered for any given application,<span style="letter-spacing: -.2pt;"> </span>decision<span style="letter-spacing: -.35pt;"> </span>makers<span style="letter-spacing: -.2pt;"> </span>are<span style="letter-spacing: -.2pt;"> </span>able<span style="letter-spacing: -.3pt;"> </span>to<span style="letter-spacing: -.25pt;"> </span>see<span style="letter-spacing: -.3pt;"> </span>the<span style="letter-spacing: -.2pt;"> </span>impact<span style="letter-spacing: -.3pt;"> </span>that<span style="letter-spacing: -.2pt;"> </span>change<span style="letter-spacing: -.3pt;"> </span>will<span style="letter-spacing: -.25pt;"> </span>have<span style="letter-spacing: -.2pt;"> </span>on<span style="letter-spacing: -.35pt;"> </span>all<span style="letter-spacing: -.2pt;"> </span>related<span style="letter-spacing: -.25pt;"> </span>business<span style="letter-spacing: -.2pt;"> </span>units and services.

##### **ESB**

<p class="callout info">Refer<span style="letter-spacing: -.5pt;"> </span>to<span style="letter-spacing: -.3pt;"> </span>the<span style="letter-spacing: -.25pt;"> </span>document<span style="letter-spacing: -.35pt;"> </span>*Government<span style="letter-spacing: -.25pt;"> </span>of<span style="letter-spacing: -.25pt;"> </span>Rwanda<span style="letter-spacing: -.35pt;"> </span>Enterprise<span style="letter-spacing: -.25pt;"> </span>Architecture<span style="letter-spacing: -.1pt;"> </span>ESB<span style="letter-spacing: -.35pt;"> </span>Reference<span style="letter-spacing: -.25pt;"> </span><span style="letter-spacing: -.1pt;">Model.DOCX</span>*</p>

##### ***<span style="letter-spacing: -.1pt;">Security</span>***

<p class="callout info">Refer<span style="letter-spacing: -.5pt;"> </span>to<span style="letter-spacing: -.3pt;"> </span>the<span style="letter-spacing: -.3pt;"> </span>document<span style="letter-spacing: -.3pt;"> </span>*Government<span style="letter-spacing: -.3pt;"> </span>of<span style="letter-spacing: -.3pt;"> </span>Rwanda<span style="letter-spacing: -.3pt;"> </span>Enterprise<span style="letter-spacing: -.3pt;"> </span>Architecture<span style="letter-spacing: -.25pt;"> </span>Security<span style="letter-spacing: -.25pt;"> </span>Reference<span style="letter-spacing: -.35pt;"> </span><span style="letter-spacing: -.1pt;">Model.DOCX</span>*</p>