EA Roll Out – Silo v/s Goal-Oriented

EA Roll Out – Silo v/s Goal-Oriented

B: Single platform IT technology supporting various department requirements
D: Expel SILO approach
A: Optimization of IT Assets and resources
Click on the icons on the arrows to see assumptions and injections
C: Secure Resources or any other Assets such as IT infrastructure
D': Pursue with on-going SILO Approach to EA - lodge requirements of departments

In order to Optimization of IT Assets and resources we must Single platform IT technology supporting various department requirements and in order to Single platform IT technology supporting various department requirements we must Expel SILO approach. But, in order to Optimization of IT Assets and resources we must also Secure Resources or any other Assets such as IT infrastructure and in order to Secure Resources or any other Assets such as IT infrastructure we must Pursue with on-going SILO Approach to EA - lodge requirements of departments. we can't both Expel SILO approach and Pursue with on-going SILO Approach to EA - lodge requirements of departments.

RelationAssumption(s)Injection(s)
D-D'1. Continuing with the silo approach may not align the business and the IT logic.
2. Silo Approach to EA does not collaborate all the department requirements as it is a goal-oriented approach
3. EA Deployed is not mature with the existing silo approach method.
B-D1. Using silo approach, there will be fragmented system.
2. The existing Silo approach does not allow sharing or collaboration between departments.
3. Accessibility between departments
C-D'1.Easy to implement and operate department requirements.
2.Provide a common community of like minded individuals.
3.Establish credibility for members of the departments.
A-B1.It make easier for everyone in the university to access to university resources anytime and anywhere.
2.It improves user experience.
3.Improves IT security with the use of single platform.
A-C1. It is simpler to deal with different little departmental executions than expansive scale coordinated changes
2. It outcomes in worker fulfillment all the while influencing them to feel they are contributing their value to the projects
3. It keeps departments in charge, augments nearby efficiency which brings about a compelling EA usage(False Assumption)
1.Impart the estimation of EA usage to the clients and teach them its advantages which would be acknowledged by the departments, thus enhancing the efficiency of EA execution project.

2.Rather than SILO approach, the IT division should rehearse a more comprehensive approach by including the partners/stakeholders and different clients view-point ideal from the earliest starting point of the decision-making process.