513
edits
Changes
Jump to navigation
Jump to search
mLine 29:
Line 29: − + + + + + + + + +
GC Enterprise Architecture/Playbook (view source)
Revision as of 16:26, 20 January 2020
, 16:26, 20 January 2020no edit summary
<h2> The Plays </h2> <br>
<h2> The Plays </h2> <br>
<h3><span style="font-size: 1.5em;"> 1. Business Architecture</span></h3> <br><br>
<h3><span style="font-size: 1.5em;"> How to start </span></h3> <br>
When department has an idea, a problem or an issue that needs to be addressed, the <b>main</b> question that needs to be answered is that <b><u>"Is it worth it ?"</b></u>.
To answer this question, department has to:
1. Identify the end goal - what it is that the department wants to achieve at the end; what problem is the department trying to solve; how would the new solution fit in the whole IT landscape within the department and the GC,
2. Determine options - if we use this solution how would it affect the outcome, the existing process, the other system and find the best solution that will fit departmental needs as well as align with the GC Direction. <br><br>
<h3><span style="font-size: 1.5em;"> 1. Business Architecture</span></h3> <br>
Business Architecture is where an organization identifies the various services that it needs to provide externally, as well as the various functions it owns or needs to own internally to support their services to the public. In the context of GC Enterprise Business Architecture, this is where the Government of Canada identifies the various departments, the services they provide to Canadians and the functions they owns. <br><br>
Business Architecture is where an organization identifies the various services that it needs to provide externally, as well as the various functions it owns or needs to own internally to support their services to the public. In the context of GC Enterprise Business Architecture, this is where the Government of Canada identifies the various departments, the services they provide to Canadians and the functions they owns. <br><br>
