Page 307 - PowerPoint Presentation
P. 307

CAVITE STATE UNIVERSITY
                               T3 CAMPUS
                               Department of Information Technology             ITEC 75 – System Integration and Architecture 1

                       Risk  identification  and  mitigation  is  not  a  one-time  activity,  it  is  an  ongoing
               management review item that will assist in making an EA program successful.

               Quantifying EA Program Value
                       How to translate value to the bottom line is one of the biggest questions executives
               and Line of Business (LOB) managers have about EA programs. Building a business case
               that includes an alternative analysis, cost-benefit analysis and return on investment calculation
               is the primary measure for evaluating the contribution to profitability and/or mission success.
               Many aspects of Enterprise Architecture value can be quantified, including the following areas:

               Shortening Planning Cycles
                       Enterprise  Architecture  can  help  shorten  planning  cycles  by  providing  a  robust
               repository of online information regarding current and future processes and resources. While
               Enterprise Architecture does not replace strategic planning or business process improvement
               activities, it does enhance them through contribution of useful information that would otherwise
               be gathered separately.

               More Effective Planning Meetings
                       Enterprise Architecture allows for the presentation of a common baseline of planning
               and  reference  information.  IT  reduces  ambiguity  and  increases  levels  of  common
               understanding.

               Shorter Decision-Making Cycles
                       The  time  it  takes  to  gather  and  crosswalk  strategy,  business  and  technology
               information is greatly reduced by having a repository of EA information that was developed
               through the use of a logical framework and archiving method. Decision-making processes can
               be streamlined to reflect the availability of this new resource of integrated baseline information.

               Improved Reference Information
                       By  using  an  EA  documentation  framework  and  implementation  methodology,
               information on processes and resources is gathered in a standardized method using the same
               tools  and  applications.  Additionally,  the  method  for  storing  the  information  is  coordinated
               through the use of the online EA repository, which requires the use of standardized data and
               document formats. This in turn creates the ability to perform queries for information across
               otherwise disparate activities and resources. It also supports a more robust data mining and
               business analysis capability.

               Reduction of Duplicative Resources
                       One  of  the  greatest  contributions  an  EA  makes  to  an  enterprise  is  aiding  the
               visualization of the value that current resources provide, where those value areas overlap, and
               where  performance  gap  exist.  For  example,  duplicative  data  represents  low-hanging  fruit
               ready  for  elimination  through  the  implementation  of  the  future  architecture.  Subsequent
               improvements might then focus on the introduction of new technologies and improvements in
               efficiency.

               Reduced Re-work
                       By approaching the planning and execution of new resources in a holistic manner,
               potential  re-work  that  might  have  been  created  through  individual  program  level  initiatives
               (containing duplicative and/or conflicting capabilities) can be avoided. Also, rework is reduced
               through  the  use  of  a  step-by-step  EA  methodology  and  framework  that  call  for  standard
               approaches to documentation that are based on mature modeling and analysis techniques.







                                                                                                 Page | 19
   302   303   304   305   306   307   308   309   310   311   312