Enterprise Architecture

Blueprint Development
Guidelines for GoR.

Prepared by:
Rwanda Information Society Authority / RISA
 I. INTRODUCTION

The purpose of these guidelines is to help public entities and GoR’s private partners
to have a common understanding of EA practice and to guide the systematic
mapping of the institution’s IT landscape (Blueprint) in clear steps namely: the AS-
IS situation, the To-Be situation, the Gap analysis and the Roadmap.

In order to bring alignment between business requirements and IT capabilities, the

blueprints are implemented through five (5) domains namely Business,
Information, Data, Application and Technology/Infrastructure Architectures. These
are commonly referred to as the BIDAT stack.
Depicted below are the domains that make up the BIDAT stack.
Business Architecture
This domain documents the business strategy, governance, business rules, goals,
structure, processes and services. Within this initiative, the business domain will
concern itself with the documentation of business services that IT supports.
Information Architecture
This domain is concerned with the transfer of information between different
business units using IT solutions
Data Architecture
This domain looks at how data sources are managed within an environment. It
concerns itself with the structuring of databases, defines the standards and models
for data collection, storage, use and management. All attributes for databases are
stored within the Information Resource Catalogue (IRC). It documents the physical
and conceptual data models, logical and physical data assets and data management
resources. In some cases, due to the close association between the two domains,
the Information and Data Architecture are combined and collectively referred to as
Information System Architecture.
Application Architecture
This domain documents the systems to be deployed, their interactions, and their
relationships to the core business processes of the organisation. The key
deliverables for this domain include the application models and an Application
Portfolio i.e. a catalogue of all applications within a given environment
Technology Architecture
This documents the hardware and software capabilities that are required to
support the deployment of business, data and application services. This includes
the documentation of the Enterprise Service Bus, IT Infrastructure, middleware,
networks and communications channels
 II. REFERENCE DOCUMENTS

For full guidance and overall context purpose, this document should be read in
conjunction with the following documents:
Government of Rwanda Enterprise Architecture Governance: This document
outlines the governance structure around enterprise architecture within
government of Rwanda.
Government of Rwanda Enterprise Architecture Framework: This outlines the
boundaries, approach and notation that is used to model the enterprise
architecture within Rwandan public entities
Government of Rwanda Enterprise Architecture Principles: This defines the
guiding principles for enterprise architecture that should be applied across all
public entities
Government of Rwanda Enterprise Architecture Standards: This document
defines the standards that should be adhered to in documenting enterprise
architecture artefacts

III. COMPLIANCE

One of the key benefits for establishing an institution’s blueprint is to ensure

the right selection and right scoping of IT projects, making clear the direct
linkage between the IT project and the institution’s business requirements. The
blueprint also serves as a framework to align with the integration and
interoperability standards at national level.

It is in this context that the development of institution’s blueprint will be

considered as the basic requirement for any IT project to be approved at RISA’s
level before a request for funds is sent to MINECOFIN.
IV. BLUEPRINT DEVELOPMENT GUIDELINES

For ease of consultation these guidelines are provided in the form of diagrams
organized in the following flow:

1. EA Development Value Chain

2. Business Requirements Analysis
2.1.Understand Business Requirements and Value Drivers
2.2.Confirm Scope and Approach
3. Baseline Blueprint Development
3.1.Prepare for Data Gathering
3.2.Gather Data
3.3.Develop Baseline Blueprint
4. Develop Target Recommendations
4.1.Develop Target Recommendations
4.2.Prioritise Target Recommendations
5. Target Blueprint Development
5.1.Define Target Blueprint
6. Gap Analysis
6.1.Conduct Gap Analysis
7. Create Roadmap for Target Blueprint Implementation
7.1.Create Road Map
 1. EA Development Value Chain
Develop Baseline (As Is) State Develop Target (To Be) State Conduct Gap Analysis Develop Roadmap
Analyse Baseline (As Is) assessment Develop Target Define Target (To Identify new initiatives Create Roadmap
Requirements Recommendations Be) Blueprint
3 11
6 13 Finalize Value Realization
Prepare for Data
Gathering Identify Target Identity List of Initiatives Plan & Governance
1 Understand 9
Objectives Approach
Business Prioritize
Requirements and Recommendations
Value Drivers 4
7 12 14
Gather Data, Score
and Map Applications Define Target Develop Target (To Be) Define Projects & Integrate
Recommendations Processes into Overall Program
2 10
Define Target (To
Confirm Scope 5 8 Be) 15
& Approach
Develop Baseline(As Determine Impact Blueprint Develop Implementation
Is) Blueprint and Benefits Plans

• Review business strategy • Gather application data • Define recommendations for • Develop high-level business • Identify gaps between Target and • Define Initiatives
• Conduct stakeholder • Map applications to business current environment case Baseline blueprints • Develop Transition Plans
Activities

assessment Services / functions • Analyze data/scores and • Prioritize recommendations, • Compare best practice implementation • Create value case appropriate for
Key

• Request/review existing • Analyze data and score disposition applications identifying interdependencies of desired solutions investment justification
documentation eg applications • Determine high-level impact • Identify additional opportunity • Identify optimization opportunities and • Create actionable roadmap
strategy, org structure etc • Validate Baseline (As Is) and benefits areas associated applications
• Review final deliverables with
• Confirm business Blueprint with the client • Identify ‘Quick Wins’ • Confirm business case and • Confirm opportunities with Stakeholders
services and stewards • Create Baseline (As Is) Models • Confirm recommendations prioritization with Stakeholders Stakeholders
• Confirm application in Sparx Enterprise Architect and dispositions with • Identify list of initiatives to close the
inventory and stewards • Export models and develop Stakeholders gap
• Finalize scope & Baseline (As Is) Blueprint • Map initiatives to target drivers and
approach business requirements

• Assessment scope and • Application inventory with • Recommendation Summary • Business Case • High Level Opportunity / Benefit • High Level Opportunity / Benefit
Deliverables

application inventory demographics • Application Disposition Matrix • Prioritized Recommendations Identification Identification
Key

• Data collection, analysis • Baseline (As Is) Blueprint • Pain Gain Analysis • Target (To Be) Blueprint • Heat maps • IT Roadmap
and scoring approach • Actionable quick win plans
• Quick Win Initiatives
• Communication Plan
2. Business Requirements Analysis
Liaise with RISA EA Team for alignment with project boundaries

Develop Baseline (As Is) State

Analyse Baseline (As Is) assessment
Requirements
3
Prepare for Data Key Objectives
Gathering
1 Understand
Business Work with the Project Sponsor to:
Requirements and
Value Drivers 4 • Understand the client’s strategic direction (IT and Business)
Gather Data, Score • Understand the assessment scope/boundaries (i.e. functional areas , geographic
and Map Applications
locations, business units, Business Services, number of applications etc)
2 • Determine assessment approach based on project objectives and goals
Confirm Scope 5
& Approach
Develop Baseline (As
• Understand the availability of data and the level to effort to collect
Is) Blueprint • Understand and agree on data collection techniques, tools, templates
• Identify key business and technology personnel to interview/gather required
information regarding people, process and technology

Key Activities Deliverables Exit Criteria

• Review business strategy, drivers and objectives • Application Inventory & Demographics • Scope and approach is confirmed
• Understand stakeholder requirements • Confirmed Scope • Strategic direction, business strategy is known
• Request/review existing documentation • Data collection and analysis approach • Application scoring method and participants are
• Confirm application inventory and stewards identified, and availability is confirmed

• Finalize scope & approach • Level of detail established for roadmap phase
deliverables
2.1 Understand Business Requirements and value
drivers
Review business strategy, government of Rwanda initiatives and goals

The RISA EA team to provide

clarity and guidance wherever
necessary No

Scope
Request Clarity
Clear? Review Existing
No Documentation
2
Request Yes
for EA Confirm Project Scope Yes
Project Scope Clear?
Received Schedule Meeting to Meeting /
Identify Source of Info Yes Validate / Gather Workshop
Yes Required Availa Information Scheduled
This will include the goals of Information ble?
the project and target audience
for the deliverables

Identify and Request

No Information from
Info No
Availab
Relevant le?
Stakeholders

Review all available and relevant documentations including strategy documents, Operating models,
Organisational structure, architecture models, government initiatives, mandates and drivers.
2.2 Confirm Scope and Approach

Establish project boundaries and familiarise oneself with the framework

The RISA EA team to provide The assets include :

clarity and guidance wherever Government of Rwanda Enterprise Architecture Framework
necessary
No Government of Rwanda Enterprise Architecture Governance
Government of Rwanda Enterprise Architecture Standards
Government of Rwanda Enterprise Architecture Principles
Government of Rwanda Enterprise Architecture Guidelines
Scope
Request Clarity
Clear?
No This also includes a complete understanding of project methods
and target deliverables
Request
Yes
for EA Confirm Project Scope
Review Scope
Project Scope Clear?
Received
Review and Understand
Align Scope to
understand Project Business Direction
Business Drivers
This will include the goals of
Yes approach and (Business Drivers
(objectives)
the project and target audience Assets and Strategy)
for the deliverables

Schedule Meeting to Meeting /

Validate / Gather Workshop
Information Scheduled

A clear understanding of both the scope of the project and framework will enable the architect to produce
deliverables that are seamlessly align to the goals of Government of Rwanda.
3. Baseline Blueprint Development
Gain deep understanding of available assets that guide the project

Develop Baseline (As Is) State

Analyse Baseline (As Is) assessment
Requirements
3
Prepare for Data Key Objectives
Gathering
1 Understand
Business • Align Business drivers to applications and technology
Requirements and
Value Drivers 4 • Determine technology strategic alignment
Gather Data, Score
and Map Applications • Identify business capabilities and map them to supporting technologies (applications,
infrastructure and data sources)
2
Confirm Scope 5 • Gain an understanding of the functional and technical health of applications
& Approach
Develop Baseline(As • Gain a high level understanding of the strategic alignment versus overall health of
Is) Blueprint
technologies
• Identify opportunities to optimize the application portfolio

Key Activities Deliverables Exit Criteria

• Gather Business services, processes, application • Baseline (As Is) models for all architecture • Data gathering templates completed completed
and technology data domains and returned
• Map applications to business functions • Baseline (As Is) Blueprint • Baseline interviews/meetings/workshops are
• Map applications to services complete

• All applications identified, inventoried • Optimization opportunities have been confirmed

3.1 Prepare for Data Gathering
Pre-work for the exercise should involve learning how to apply the assets

The RISA EA team to provide

clarity and guidance wherever No
necessary

Templ
Request Clarity ate
No Clear?

Update Template
Familiarise Oneself Templ Yes With Required
Scope Yes
with Data Gathering ate Information
Clear
Template Clear?

Assess Adequacy Prepare for

Adequ
Yes and Completeness
ate? workshop / Meeting
of Template

No Update Template Schedule Meeting to Meeting /

With Required Validate / Gather Workshop
Information Information Scheduled

Familiarity with the data gathering template will facilitate the running of the workshops and data gathering
proceses. The pre-work should also include familiarization with the deliverables and supporting assets.
3.2 Gather Data
Before the meeting, ensure that the stakeholder is aware of the project

Complete the template with one

service together with the client to
demonstrate the procedure

Meeting / Present Project

Present Project Show Sample Explain Data Capture Data for Distribute Template Workshop
Workshop Background and
Value Deliverables Collection Template One Service for Completion Complete
Starts Scope

Prior to the workshop, obtain Explain the role of the

sample deliverables from client in completing the
other Sectors – RISA EA template and timelines
Team to assist

During the workshop, take time to explain expectations and target deliverables, use of assets such as Data
Gathering Template, Framework, governance model etc.
3.3 Develop Baseline (As Is) Blueprint
Use guideline and template for blueprint development

The project team would have received training on

how to develop models in Sparx Enterprise
Architect facilitated by the RISA EA Team

Data Baseline
Create Architecture Export Models from
Gathering Understand Document Baseline (As Is)
Models in Sparx Sparx Enterprise
Template Blueprint Template (As Is) Blueprint Blueprint
Enterprise Architect Architect
Complete Complete

Export Models from

Sparx Enterprise
Architect

Yes
Schedule Meeting
No Update Models with
with Stakeholder to Validate Models with Validat
Inputs from
Validate Baseline the Stakeholder ed?
Stakeholder
Models

Use the structured template to complete the Baseline (As Is) Blueprint. The Blueprint must be developed
in close collaboration with all stakeholders to ensure its acceptability and alignment with overall goals.
4. Develop Target Blueprint
Use available assets to create deliverables that are understood across the board

Develop Target (To Be) State

Confirm Define Target (To
Recommendations Be)State
6
Identify Target 9 Key Objectives
Objectives
Prioritize
Recommendations Formalize optimization opportunities into recommendations:
7 • Gain an clear understanding of the technology scores/health
Define Target
Recommendations • Determine a high level technology strategy
10
Define Target (To • Understand the impact of the recommended Target (To Be) state
8 Be)
Determine Impact Blueprint • Identify ‘Quick-Wins’
and Benefits

Key Activities Deliverables Exit Criteria

• Define recommendations for current environment • Recommendation Summary • Recommendations confirmed
• Analyze data/scores and disposition technologies • Application Disposition Matrix • All applications dispositions identified an confirmed
• Determine high-level impact and benefits • Pain Gain Analysis • Impact /benefits of application dispositions are
• Identify ‘Quick Wins’ • Quick Win Initiatives determined and confirmed
• Confirm recommendations and dispositions with
Stakeholders
4.1 Develop Target (To Be) Recommendations
Recommendations must take into account overall government goals
Validate the models with:

1. IT Sector Working Group – to align on sector-wide IT initiatives

2. RISA EA Team – to align on Government-wide EA initiatives
3. Respective entity – to align on entity strategic goals

Review Government Refer to : Government of Rwanda Enterprise Architecture

Review Target (To Be) objectives of
of Rwanda Goals Governance.docx
the entity as well as the overall goals
of Government of Rwanda and
respective Sectors under which the
entity falls
Review Sector
Objectives
Baseline Schedule Meeting
Review Business Align Government Meeting /
(As Is) Define Target with Stakeholders to
Target (To Be) Goals to Business Workshop
Blueprint Recommendations Validate
Objectives Objectives Scheduled
Complete Recommendations
Review Entity
Objectives

Review Entity
Objectives

Standard procedure in determining in whether to Build, Buy or Enhance current solutions should apply.
This, however, should always take into account all stakeholder requirements and goals
4.2 Prioritise Target (To Be) Recommendations
Stakeholder would be best placed to set priorities
The recommendations need to be aligned to the Government of
Rwanda initiatives, Sector goals and objectives and entity
strategy
The validation to include IT Sector Working Group, RISA EA
Team and entity stakeholders

Refer to : Government of Rwanda Enterprise Architecture

Governance.docx Document New
Recommendations with
the Stakeholder

Review and Update

Proposed Changes
to Business
Draft Meet with client / Processes
No
Target Stakeholder to Agreed
Recomme validate Draft ?
dations Recommendations
Review and Update Prioritise Update Models in
Proposed Changes Prioritisati
Recommendations Sparx With Agreed
to Technology on
based on Recommendations
Yes Complete
Stakeholder Needs and Prioritisation

Document Additional
Recommendations
(if any)
5.Target Blueprint Development
Align with all stakeholders for completeness of the deliverables

Develop Target (To Be) State

Confirm Define Target (To
Recommendations Be)State
6
Identify Target 9 Key Objectives
Objectives
Prioritize
Recommendations • Derive a business case for each recommendation to provide economic
7
justification for execution
Define Target • Prioritize recommendations
Recommendations
10 • Develop Target (To Be) -state view of technology and business landscape
Define Target (To
8 Be)
Determine Impact Blueprint
and Benefits

Key Activities Deliverables Exit Criteria

• Develop high-level business case • Business Case • Target (To Be) state Business and technology
• Prioritize recommendations, identifying • Prioritized Recommendations landscape defined.
interdependencies • Target (To Be) Blueprint • Business cases for each recommendation
• Identify additional opportunity areas • Recommendations prioritized and confirmed
• Define Target (To Be) Business and technology
landscape
• Confirm business case and prioritization with
Stakeholders
5.1 Define Target (To Be) Blueprint
Use reference models to guide the development of Target Blueprints

These should be developed in close collaboration

with the stakeholders i.e. Respective government
entity, IT Sector Working Group and RISA EA
Team

Target
Target (To
State Update Target Develop Business Export Models from
Identify Additional Document Target Be)
Recomme Models in Sparx Case for Identified Sparx Enterprise
Opportunities (To Be) Blueprint Blueprint
ndations Enterprise Architect Initiatives Architect
Complete
Complete

Depending on the changes to the architecture, various reference models are available to assist in
developing Target Blueprints. Refer to RISA EA Team for assistance with overall strategic goals.
6. Gap Analysis
Recommended solutions to be aligned to Government of Rwanda capabilities

Conduct Gap Analysis

Identify new initiatives

11
Identity List of Initiatives
Key Objectives
• Run comparison of the Baseline (As Is) Landscape and Target (To Be) State
12
Develop Target (To Be) • Identify gaps between the two landscapes
Processes
• Benchmark recommendations against best practice implementation of the same
• Identify initiatives that need to be taken to close the gap

Key Activities Deliverables Exit Criteria

• Compare Baseline to Target Architecture • Gap analysis report • Gap analysis defined
• Identify gaps between the two architectures • List of initiatives
• Benchmark target architecture against best • Impact assessment report
practice
• Identify initiatives to bridge the gap
• Review list of initiatives with Stakeholders
6.1 Conduct Gap Analysis
New initiatives and mandates should be considered in conducting gap analysis

Document the Identify Initiatives to

Assess Variance
Variance Close Gap
Yes

Target Compare Baseline

Blueprint to Target Gap
State No
Analyse Each Blueprint Varian Review Initiatives Develop Gap Analysis
Recomme
Architecture Domain ce? with Stakeholders Analysis Report Report
ndations
Complete
Complete
Compare Target
Blueprint to Best
Practice This should be developed in close consultation
with the stakeholders taking into account all
requirements, drivers, stakeholder needs,
technology trends and government goals.

It is recommended that reference models be used to create ‘Heat Maps’ to depict highlight areas that need
attention and new initiatives. This should be undertaken in close collaboration with stakeholders.
7. Create Roadmap for Target Blueprint Implementation

In close collaboration with all stakeholders to ensure seamless alignment

Develop Roadmap
Create Roadmap

13 Finalize Value Realization

Plan & Governance
Approach
Key Objectives
• Develop roadmap or transition plan that defines the program necessary to implement the
14 Target (To Be) state business and technology landscape
Define Projects & Integrate
into Overall Program • Consolidate business cases for each recommendation into an overall value case for the
transformation program to provide economic justification for all planned activities

15 • Create program plans that will be required to startup, govern, and navigate the roadmap
Develop Implementation
Plans • Validate and gain consensus on Roadmap Deliverables with sponsors and stakeholders
• Transfer ownership of deliverables and roadmap to Sponsor that will drive the ensuing
implementation

Key Activities Deliverables Exit Criteria

• Define Initiatives • High Level Opportunity / Benefit Identification • Value Case and Roadmap Defined
• Develop Transition Plans • Roadmap • Next steps are defined/understood
• Create value case appropriate for investment • Actionable quick win plans • Deliverable sign-off
justification
• Create actionable roadmap
• Review final deliverables with Stakeholders
7.1 Create Roadmap
Roadmap development should be driven by the business case and
initiatives prioritisation

Gap Yes
Create Value Case Review Final
Analysis Develop Transition Create Actionable Approv Finalise Roadmap
Define Initiatives for Investment Roadmap with Sign-off
Report Plans Roadmap ed? and Project Sign-off
Justification Stakeholders
Complete

No
Based on the Prioritisation of
recommendations Update Based of
Stakeholder
Suggestions

Close collaboration with stakeholders in developing the roadmap will ensure ownership of the
implementation plans by the same.