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

Post a Comment

Popular posts from this blog

Webinar: Powering your business with Cloud Computing

On October 14th, I will be hosting a Grid Computing Now! web seminar on the topic of Cloud Computing. We have lined up two very interesting speakers who are using Cloud now to make businesses work. Ross Cooney had a good technological solution to sell but couldn't make it economic until Cloud Computing allowed him to pay for his computation only when he needed it. He will discuss the instant benefits and long term impact of cloud computing to the development, competitiveness and scalability of your application. Alan Williamson created the BlueDragon Java CFML runtime engine that powers MySpace.com. He advises several businesses and will give an overview of the different types of services available and how to avoid being locked-in to a single supplier. You can register for this event here .
Post a Comment
Read more

Business Model Canvas

A Business Model Canvas is a tool for mapping the core functions and capabilities of an organisation.  Compared to the Core Diagrams that I described in an earlier post , the business model canvas attempts to present more aspects of the business, starting with the value proposition – a statement of what the organisation offers to its users (in the business world, to its customers).  It shows the activities and resources, as Core Diagrams do, but also shows user relationships & channels, and also benefits and costs.  I’m not aware of any universities that have used this tool but you can find examples from elsewhere on the web. We are considering business model canvases as a tool for mapping the strategic capabilities of units at the University of Edinburgh.  Phil Taylor, our EA contractor, sketched an outline of what a business model canvas might begin to look like for HR: This is only intended to be suggestive: the real canvas would need to result from in-de...
2 comments
Read more

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...
1 comment
Read more