Enterprise Architecture

The role of the Enterprise Architecture (EA) is to harmonise, clarify and describe the structures and operations of an organisation. It also aims to describe the interdependencies between functions and requirements. It can be used, for example, for information system or technology upgrades, tendering, business change and strategy work.

A Entreprise Architecture helps organisations make strategic decisions, such as investing in new technologies, information systems or business processes. It also facilitates collaboration and communication between different departments by providing a common language and understanding of the organisation's activities and goals.

The Enterprise Architecture is not limited to technology alone, but encompasses a wide range of aspects of the organisation and the relationships between them. It can help an organisation to improve its efficiency, innovation and ability to respond to change quickly and flexibly.

What is the Enterprise Architecture alignment process?

The Enterprise Architecture alignment process aims to standardise the systems and technologies that deliver an organisation's system services. The alignment process helps to identify the functional, technological and information needs for change. The alignment process also includes an assessment of the security and safety of the system or technology.

The systems used by the University require an alignment process if the conditions are met, but the applications do not. This is how you distinguish between an application and a system:

Software

  • Installed on a user's computer and controlled by the user.
  • The application is installed on the user's computer and is controlled by the user and runs from the user's computer cache.
  • Examples of applications: Photoshop, Microsoft Office, SPSS, GIMP, Pro Tools, AutoCAD, Visual Studio, PyCharm.
  • Often colloquially referred to as a "desktop application" or "program"

System (Application Component)

  • Delivered centrally to the user in an Internet browser or mobile interface.
  • Access rights and system management are managed centrally from a data centre.
  • Examples of systems: ROTI, SISU, Facebook, Microsoft O365, Optima, SOLE
  • Often referred to as a "service" in colloquial language.

The alignment process ends with an alignment decision by the Enterprise Architecture Steering Group or the University Board. According to the alignment decision, a system or technology can be:

  • Mandatory
    The mandatory system may be used for a specific purpose, but no other system may be used for the same purpose. For example, accounting is done only in SAP Financial System.
  • Recommended
    The recommended system is the one supported by Digital Services. The system is secure and in good data protection condition. The system is integrated with other JYU systems. For example, Moodle is a recommended learning environment. Other systems may be used alongside the recommended system for the same purpose. 
  • Allowed
    The approved system may be used, but it is not supported by Digital Services. The system may not have been checked for security and protection and may not be integrated with other JYU systems. An example of an authorised system is Pedanet.
  • Not recommended
    A system that is not recommended for use may, for example, be technologically obsolete. The system may have security or protection shortcomings, or its use may cause other problems for the organisation's operations. Digital Services is not responsible for the functionality of the system. 
  • Disallowed
    The system must not be used.

When should a technology or system be brought into the Enterprise Architecture alignment process?

The steering group of the Ä¢¹½Ö±²¥'s overall architecture has decided on 1.9.2019 that a system or technology must be included in the alignment process if one or more of the following conditions are met: 

Technology:

  • The technology is not in use at the Ä¢¹½Ö±²¥ or does not comply with current architecture recommendations.
  • The technology affects the operation of several university systems.

System:

  • A system is already in place or aligned for the system service implemented by the system.
  • The purchase price of the system exceeds the University's procurement competitive threshold.
  • The implementation of the system will result in significant changes to the University's core activities (research and education).
  • The system generates, processes or archives personal data or sensitive information.
  • The system will affect the work of more than 300 employees.
  • The system will affect the studies of more than 1000 students.

Note: The Ä¢¹½Ö±²¥'s technology and system acquisitions are approved by Ari Hirvonen, Digital Director. The Digital Director and the Chief Enterprise Architect of the University should be informed in connection with the procurement. Unaligned systems and technologies must also be entered into the university's Enterprise Architecture System.

Contact information

Ari Lehtiö

Ari Lehtiö

Head of Development
Ari Hirvonen

Ari Hirvonen

Digital Director

See also

Services provided by Digital Services

Digital Services offer a variety of services, for students, staff and visitors.

Software Distribution

Where can I get the licence or right to use the software I want? How much would the software cost?

Guides offered by the Digital Services

User guides for the different applications offered by the Digital Services.