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

Presentation: Putting IT all together

This is a presentation I gave to an audience of University staff: 

In this seminar, I invite you to consider what the University’s online services would be like, if we worked together to design them from the perspective of the student or member of staff who will use them, instead of designing them around the organisational units that provide them. I’ll start with how the services might appear to that student or member of staff, then work back from there to show what this implies for how we work, how we manage our data, and how we integrate our IT systems. It might even lead to changes in our organisational structure.

Our online services make a vital and valued contribution to the work of our students and staff. I argue that with better integration, more consistent user interfaces, and shared data, this contribution could be significantly enhanced.

This practice is called “Enterprise Architecture”. I’ll describe how it consults multiple organisational units and defines a framework …

Not so simple...

A common approach to explaining the benefits of Enterprise Architecture is to draw two diagrams: one that shows a complicated mess of interconnections, and one that shows a nicely layered set of blocks. Something like this one, which came from some consultants:


I've never felt entirely happy with this approach.  Yes, we do want to remove as much of the needless complexity and ad-hoc design that litters the existing architecture.  Yes, we do want to simplify the architecture and make it more consistent and intelligible.  But the simplicity of the block diagram shown here is unobtainable in the vast majority of real enterprises.  We have a mixture of in-house development and different third-party systems, some hosted in-house, some on cloud infrastructure and some accessed as software-as-a-service.  For all the talk of standards, vendors use different authentication systems, different integration systems, and different user interfaces.

So the simple block diagram is, basically, a l…

2016 has been a good year

So much has happened over the last year with our Enterprise Architecture practice that it's hard to write a succinct summary.  For my day-to-day experience as enterprise architect, the biggest change is that I now have a team to work with.  This time last year, I was in the middle of a 12-month secondment to create the EA practice, working mainly on my own.  Now my post has been made permanent and I have recruited two members of staff to help meet the University's architectural needs.

I have spent a lot of the year meeting people, listening to their concerns and explaining how architecture can help them.  This communication remains vital, the absolute core of what we do and we will continue to meet people in this way.  We also talk to people in other Universities in order to learn from what they are doing and to share our own experience back.  A highlight in this regard was my trip to the USA last January.

Our biggest deliverable for the past year was the design of the data wa…