Case Study: GovDept's Enterprise Architecture Implementation

CASE STUDY

TABLE OF CONTENTS
INTRODUCTION...........................................................................................................................1
MAIN BODY..................................................................................................................................1
1. Develop a comprehensive road map that helps in specifying what kind of projects should be
executed in future........................................................................................................................1
2. 5 key roles that IT will be playing in GovDept.......................................................................2
3. 5 key EA artefacts that would be delivered in 2 to 3 months..................................................2
4. Taxonomy of documentations that will be implemented and reason because of which it is
important for government............................................................................................................3
5. Discussion of operating model that will be implemented and reason because of which that
model has been chosen................................................................................................................3
6. Role of standard and landscape in implementation of GovDept’s EA....................................4
7. 5 types of IT initiatives that are required to be considered and are extremely important for
GovDept’s EA.............................................................................................................................4
8. Explanation of considerations that would be delivered in GovDept’s EA..............................5
9. 5 subtype of visions that were used in EA artefacts implementation......................................5
CONCLUSION................................................................................................................................6
REREFENCES................................................................................................................................7

INTRODUCTION
EA or enterprise architecture can be defined as a well- defined practise for conducting
enterprise IT design (Hinkelmann and et al., 2016). One of the main purposes of EA is to
maintain alignment between IT and business concerns. It helps the organization to guide the
process of planning and designing IT capabilities of an enterprise in order to meet their desired
objectives. This assignment will focus on a case study of GovDept which is a mid-sized
government department who is focusing on developing and supporting information system for all
of their business units. They are taking initiative to evolve EA practises and focusing on
developing all kinds of EA artefacts in a specified time period. This assignment will help in
identification of key aspects of information system.
MAIN BODY
1. Develop a comprehensive road map that helps in specifying what kind of projects should be
executed in future
Road map is a high- level strategic document that helps in mapping out all the important
general stages of implementing all kinds of important projects in future (Safari, Faraji and
Majidian, 2016). It helps in explaining all the important project goals and deliverables in a better
manner. Road map for future projects are as follows:
 Goals and objectives: To ensure EA in business and align IT strategies with business
 Timeline to indicate schedule: Main defined goal is required to be achieved within 2 years.
 Important milestones and deliverables:
 Engage all the important stakeholders in order to identify important projects that are
required to be focused on- within 2 months
 Analyse current trends, need of IT within the business- within 6 months.
 Implement advance IT systems in order to centralise all the operations of the GovDept-
within 8 months
 Test the system and resolve any kind of issues or problems associated with it- within 4
months
 Possible risk: Possible risk associated with this road map is that if any milestone is missed or
is not completed within time period then it can affect future milestones such as if current
trends are not analysed within time period then there is a possibility that IT needs and
requirements might change.
1