Skip to main content

Applications Architecture

For a change, I had a week with very few meetings, which allowed me to progress some of the items on my long list of outstanding actions.  One of the things I spent some time on was the reorganisation of our Applications Architecture wiki pages, which have been ably improved over recent weeks by   Richard Good.

This work has had rather a long gestation and remains a work in progress but we have reached the stage where we have circulated the link and asked our colleagues for feedback on the formats.   At the current time we are particularly looking to confirm the format for the Data and Service Registry, and for the list of External Standards.

We have simplified the top level page, which now links to the following sub-pages:
  • Introduction: What is an “Applications Architecture”, and information about the Governance Group.
  • Principles and Patterns: The core principles of the group and “patterns” of how interfaces should be designed.
  • Data and Service Registry:  In some sense the core of the architecture, this will be a list of definitions of the common data or entity types which are key to the core business of the University, together with the interfaces that should be used to access them.  This includes some initial examples, such as Identity, Activity (from Timetabling), Fault and Group.
  • Specific Areas of the Architecture: High-level overviews of how components work together in specific areas, such as the student record (EUGEX), Provisioning, the interface between SITS and Finance, or Calendar systems.
  • External Standards: This will be a list of the external standards for data schemas used in our definitions, such as eduPerson, iCalendar & LTI.
  • Annual planning: Results of the group’s review of annual planning projects from last year; this year’s review will be added in due course.
 My aim is to get agreement on the basic layout so that we have a resource that we can grow over the months and years.

For readers within the University, you can see the pages at the following link.

Appplications Architecture Wiki pages

Comments

Popular posts from this blog

Changing Principles

In EA, architecture principles set a framework for making architectural decisions.  They help to establish a common understanding across different groups of stakeholders, and provide guidance for portfolios and projects.  Michael Durso of the LSE gave a good introduction to the idea in a webinar last week for the UCISA EA community.

Many organisations take the TOGAF architecture principles as a starting point.  These are based on the four architectural domains of TOGAF: business, information/data, applications, technology/infrastructure.  These principles tend to describe what should be done, e.g. re-use applications, buy in software rather than build it, keep data secure.  See for example the principles adopted at Plymouth University and the University of Birmingham.

Recently though, I encountered a different way of looking at principles.  The user experience design community tend to focus more on how we should do things.  E.g. we should start with user needs, use iterative developm…

Why the UCISA Capability Model is useful

What do Universities do?

This may seem a strange question to ask and the answer may seem obvious.  Universities educate students and undertake research.  And perhaps they work with industrial partners and create spin-off companies of their worn.  And they may work with local communities, and affiliation bodies for certain degress, and they definitely report on their activities to government bodies such as HEFCE.  They provide student services and support.  The longeryou think about it, the more things you can think of that a University does.

In business, the things that an organisation does are called "capabilities", which is a slightly strange term.  I think it is linked to the HR idea of a combination of the CAPacity and ABILITY to do a task.  Whatever the name, it is a useful concept.  A capability is more basic than a process: a University may change the way it educates students but as long as it remains a University it will educate them one way or another.

A capability …

A new EA Repository

One of my goals since starting this job two years ago has always been to create a repository for architecture documents.  The idea is to have a central store where people can find information about the University's applications, data sources, business processes, and other architectural information.  This store will make it easier for us to explain our plans, to show the current state of the University's information systems, and to explain what Enterprise Architecture is all about.

It's taken a long time to reach this goal, mainly because we're often had more pressing and immediate work to be done.  The creation of a repository is one of those tasks that is very important but never quite urgent.  So I'm now very happy to say that we are in the process of deploying a repository and modelling tool.


This is the culmination of a careful process to select the most appropriate tool for our needs.  We began by organising several workshops to gather requirements from a rang…