1.2.1 Providing better returns on technology investment
Applications can be developed or acquired
as needed, which means that only those
parts of the system that really need to be changed are replaced retaining the rest of the
systems so reducing both purchasing and implementation costs, particularly in terms of
staff development and training.
1.2.2 Enabling faster deployment of technology
As components are independent it will
often be easier to deploy new components so
long as the needs of the new components are compatible with the existing interfaces.
Even where this is not the case it may still be simpler to alter or replace other
components to supply the requirements of new systems.
1.2.3 Providing a modular and flexible technology base.
The rationale for the framework is specifically
to enable the development of modular and
flexible systems, where the individual components can be added or replaced more easily
than in traditional models
1.2.4 Making collaboration between institutions easier
Through a common framework and thus a
common service oriented architecture it
becomes easier to define the application interfaces which are needed and thus to share
information between institutions (for instance to support student progression). It may
also make sharing of applications easier, as it will be simpler to define small applications
which are needed in common and can be developed to meet the needs of each
institution.
