Enterprise Architecture at Austral University
Enterprise Architecture at Austral University
Enterprise Architecture
Systems Architecture
Members:
Pedro Ojeda
Javier Subiabre
José Villalón
Cristian Zumelzu
Content
Introduction 2
Theoretical Framework................................................................................................................. 3
Software Architecture
SOA ..................................................................................................................................................... 3
Enterprise Architecture
Zachman Framework .......................................................................................................................... 4
Context ...
History of the UACh Computer Center................................................................................................. 5
Mission of the Computer Center ............................................................................................................ 5
Vision of the UACh IT Center ................................................................. 6
Organizational Chart ....................................................................................................................................... 6
Services .............................................................................................................................................. 6
Areas of the Computer Center .............................................................................................................. 7
Analysis and comparison
Reality .............................................................................................................................................. 10
IT Committee
10
Technologies ....................................................................................................................................... 11
Comparison
12
Tools or methodologies for designing an Enterprise Architecture ..................................... 12
Conclusions
14
References ............................................................................................................................................... 16
Appendices ...................................................................................................................................................... 17
Introduction
The application of the content covered in the subject will be presented next.
example from real life, visiting a real-world company, gathering information to later be
analyzed and compared, in terms of its Enterprise Architecture.
It is vitally important to mention and describe some key concepts necessary for
the present research.
Software Architecture
The software architecture of a program or computer system is the structure of that system.
which includes software components, the external visible properties of those components, and the
relationships between these. The term may also include documentation on the architecture
system software.
SOA
In software engineering, a service-oriented architecture corresponds to one of the
main methodologies for designing and developing software as interoperable services.
It is also necessary to mention the differences between model, architecture, and methodology. To
hello we cite the following:
Zachman Framework
Provide the architecture for the information infrastructure of an organization, the
Marco contains six rows and six columns that make up thirty-six cells or distinct aspects. Not
there is a set direction in the sequence or process for the application of the architecture. The objective is
ensure that all aspects of a company are covered and shows the relationships that
they will ensure a complete system regardless of the order in which they are established. [AEN]
Context
History of the UACh Computer Center
The Computing Center was established in May 1996, continuing what was the Directorate.
of Computing. This unit, dependent on the Rector's Office, was formed with the idea of providing support
computer scientist and encourage its use in academic and administrative financial tasks, in order to achieve
corporate objective of raising teaching quality.
At that moment, it was stipulated that the Computer Center would be made up of a Board of Directors.
of Computer Science and by the Computer Science Directorate. The latter was organized based on two divisions,
which grouped functional areas characterized by the orientation and scope of their results.
The first of these was the Operational Services Division, which grouped the following.
areas:
· Operations Area
· User Support Area
· Projects Area in Systems Maintenance
The second was called Project Development Division and included the
areas:
On the other hand, given the supportive nature of IT services, it was intended
that, through partnerships with internal and external entities of the Corporation, create ties with
different entities of the X region to also be a service company for the community
external.
This area of the University is responsible for shaping its architecture as a Company,
Identifying the different components that make it up and being able to describe them correctly
both how they communicate with each other and the communication with the outside.
Support, promote, and facilitate the education and research objectives of the corporation
through the implementation and delivery of information and communication services for our
students and academics.
Promote the modernization of the corporation through the integration of technology, in accordance
with strategic planning, providing operational continuity and first-level support to
all corporate [Link]
Vision of the UACh Computer Center
Deliver the best university technological environment in the southern austral zone, seeking
essentially contribute to the teaching and research activities of the corporation.
[Vci]
Organization chart
The UACh is made up of three main parts: Rector's Office, Vice Rectories, and Faculties.
The Vice-Rectorate has two Macro Units, the Academic Vice-Rectorate and the Vice-Rectorate of
Management
Economic and Administrative. The Computer Center of the University depends on this last one.
Services
The computer center has only internal clients, that is, from the same University, and it was established as
the needs of these. There are three main areas of users to whom it provides services: Finance,
HR and Academic, from this the Teachers area as well as students derives. Just as their
mission indicates, the computer center offers the following services, necessary to understand how
Each of them allows the proper functioning of the University in all its breadth.
Open access:
Corporate website
Telephone Directory
TvAustral
Service Portal
WiFi Connectivity
Help desk
Email (Outsourced Service to Microsoft)
WiFi Connectivity
Connectivity and Networks
Video Conferences
Classified Ads
Management Systems
Computer Lab
Site Administration System
Intranet
Easy Procedure
For academics:
Training
Video tutorials
Academic System
Administrative System
Employee Information
SIVEDUC
Directory of Academics
Easy Procedure
For students:
Student Info
Job Board
Computer Laboratory
SIVEDUC
Easy Process
To maintain and develop all the mentioned services, the computer center of the
Austrian University of Chile is distributed into sections or areas, each with different
tasks and staff arranged in the following manner:
Development Area
It is the largest team, which has a Head of Development and Systems Maintenance and
various Analyst Programmers. They are responsible for developing and maintaining systems that provide support
both to the networking and operations areas of the University and to the rest of the sectors that use the
current computer system. The Development area is a fundamental pillar for the University
function correctly and stay at the forefront of technology.
The area aims, among other things, to keep the following systems and processes running:
Compensation System.
Billing.
Accounting processes.
Curricular management systems.
Changes are made to these systems that allow for updates on the changes that occur day by day.
day occur at the university and affect these systems, as well as projects
adicionales que busquen brindar nuevas funcionalidades a la empresa, a través de plugins o mejoras
additional.
Area of Exploitation
This area includes Operations and Networks, the person responsible is the Head of Operations.
responsible for operating, supervising, and maintaining information systems in operation
corporate, the institutional network platform and its local, national, and international connectivity,
projecting and implementing the necessary technological tools to always maintain
the availability of the network and its services. There is also a Network Engineer and an Engineer working.
in systems, alongside two operators.
This platform was created due to the progressive increase in institutional need for
occupy a space on the internet and thereby improve the services provided to the general community. In
the
In the IT center, there is a person in charge of this platform, who is responsible for the Corporate Website.
Principal and the positioning of the University on the Web.
Generate and execute projects for improvement, updating, and technological integration for
the various services.
Computer Committee
This committee is composed of members from the Vice Rectory; Vice Rectors, Head of Planning.
who judge from the strategic and economic point of view of the University. The understood part
en la materia es la Directora del centro quien también es miembro del comité, el cualfnalmente es
who is marking the technological and development path. The Director logically presents the
trends and best options to take technologically, suggested by the whole team of
development. Where the Director meets weekly with the committee to review progress, new ideas,
projects, etc. Therefore, there is always space and the need to provide information and explanation about
technological changes to those who are not knowledgeable in the field. Here the concept of
Government of Information Technologies, a new concept that explains and defines how it is given
communication between the IT department and managerial and executive positions. Helping with the
IT evangelization of specialists in measuring return on investment ROI and nothing more.
Here you can see how the different parts of the company are related and have a
degree of dependence between them. IT decisions are not made purely by experts.
in technology. The committee gives different priorities to each project, postponing or carrying out each one.
from them, always subject to the words 'Limited Resources'.
After talking with the heads of development and operations, it was made clear to us that
enterprise architecture and the software architecture that UACh seeks to implement. It is worth mentioning
again, in December 2011, the Center underwent changes at the organizational and strategic levels that
they are currently generating a scenario with a few months of practice. From this starting point the
the architecture that is intended to have is SOA. Currently, everything that is developed is oriented towards
services, focusing on implementing a SOA architecture that allows for faster implementation of
new services through others that already exist. SOA is not fully implemented as only
it has been about 4 months of implementation. In the same words of Mr. Milton Muñoz, "If
You ask me what architecture we have, I can't tell you SOA, but that's how it is.
how we want to be.
The main factor affecting this implementation is the lack of clarity that exists within it.
company regarding the processes it carries out. The organization of the University and exceptions
requested by different authorities often leads to breaking rules and not respecting the channels
regular. For example, the hiring process for a Professor must follow a series of steps;
bureaucratically speaking; where the last step, once the previous ones are approved, is to add a
report to the teacher in the SIVEDUC system. However, since this bureaucratic part has 'diversions' or
"delays", the teacher is already conducting classes and it is requested that the center integrate the new one.
Professor to the system without following the previous steps. This is a clear example that there is no flow.
suitable work or simply does not exist. The business process is not well defined and is
It is necessary for each of the processes to be well defined and structured.
The associated technologies, ad-hoc development tools with this architecture will be
detailed in the following point. One of the problems they have faced in
implementar esta arquitectura es que no todos los sistemas son propios, es decir, existen algunos
acquired systems (many of them old; inherited systems) which the IT center
seeks to integrate these systems into the SOA architecture (that is, they can be reusable as
services). The same development was hindered by the technologies that the computer center had.
In the past (the teams did not allow to implement a service-oriented architecture).
However, all new systems are being designed with SOA, using
SOA tools such as Web-service.
Technologies
The computer center works with different technologies to meet the demand of the
Austral University of Chile. The databases are Sybase under Red Hat on Dell machines, however
the services run on a Microsoft corporate development platform. This was a decision of
equipment renewal from a couple of years ago.
For the development area as well as in the testing and production areas mainly, there
they use Microsoft's .NET frameworks, however depending on the conditions that are required
Other programming languages such as Visual Basic, C, C#, PHP, JAVA are also used for the system.
among others. Since the goal of the IT center is to be able to use SOA in its entirety, they must have
all the services very well defined, and they are carrying out that process gradually, creating new ones
systems under these technologies, but with their processes well defined in order to be used as
SOA.
Comparison
The Computer Center does not use any tool that serves to define or design a
enterprise architecture, such as the Zachman framework or The Open Group Architecture
framework, however they stated that they have a structure that manages the information, that
obeys its own needs and defined by themselves. It has no name nor follows others.
examples, it's simply the way they work. Don Milton mentioned knowledge about these
concepts but stated that at the University level and the IT department they do not have an infrastructure.
clear for the information. However, we have some diagrams and information with which
we could compare and try to define the Zachman matrix (shown below). Each of the cells
will be indicated by its location [row, column].
We will consider an example to fill the cells with the artifacts that we have. The list of
The objectives of the university are publicly known, one of them could be:
Those were some of the artifacts provided by the computer center, making it clear that
they do not have the infrastructure to manage the information.
Conclusiones
1. The computer committee only serves to demonstrate how difficult it is to make decisions for
invest in technologies. As exemplified in the article: 'Service-oriented architecture,
Practical guide to quantifying return on investment from IBM, where the economic part and
This committee's strategy expects arguments for investment with numbers, ideally a
indicator, such as ROI. For those who worked at the center, led by their director.
The mission was to explain the benefits of implementing this architecture, understanding the difficulty.
What will they have to understand for those who await purely economic indicators. It is inferred
also the importance of the more "political" skills that the Director must have
center to achieve their goals.
3. The communication between the IT department and senior management such as managers and directors.
no IT experts, has generated a new and profound concept called Governance of
IT, being fundamental for the success of the company.
Today the focus is on integrating business processes and NOT as it was in previous years.
redesign by parts, through reengineering processes, redesign each part separately or
each area separately. Today it is about integrating the different services of each area.
5. According to the words of the head of the development area, the computer center, the way to generate and
llevar a cabo proyectos es por iniciativa propia proponiendo mejoras al negocio, al contrario de
as is generally the case in other companies where they decide such lines of business and
They ask the department how this is supported. For this reason, the computer science department of the University
take on a role more in processes and business than in actual development.
7. Despite the absence of an information infrastructure like the one proposed by John Zachman, they
they pointed out having their own means and ways for this. Models like the Zachman matrix come
to clarify what information is necessary, at the moment and to the indicated people, providing
a robust and clear information infrastructure.
8. SOA ultimately seeks for each development to be a new service and a musical note.
most learned, thus having a series of musical notes we can develop a multitude of
songs for different tastes and needs, using and rearranging each note; service;
composing increasingly complex songs that sound better, with lower cost and greater
efficiency.
9. Finally, enterprise architecture plays a fundamental role in the success of the company. In the
measure achieved by aligning the company's strategic plan with its IT department, through
from a complete information infrastructure like the Zachman framework, relying on
a software architecture that follows these guidelines will ultimately benefit the company
will be much closer to success.
References
[AdS] Software Architecture. Available at
[Link] Cconsulted on March 7, 2012
History of the Computer Center UACh. 'History' section of the website of the Computer Center.
UACh. Available at[Link] Consulted on March 8
2012.
Mission of the UACh Computer Center. 'Mission' section of the website of the Computer Center.
UACh. Available at[Link] on March 8
2012.
Email form
Of Requirements with a Copy
Development Boss Receive notice of
step to production
Develop the
Analyze and complete successful
solution
form
Requirement
Verify
Requirement
NO
Involves changes
of Objects
NO
Yes
You must send a plan
deTesting
YES NO
YES