Skip to main content

Views from the schools

This week I had several meetings with computing and e-Learning staff from the academic schools.  I find these meetings really useful to learn what matters to people who are using (or in some cases not using) IS systems in conjunction with their own applications. 

First up was the Technical Peer Group for the university web site.  Here I gave a short summary of our preliminary investigation of whetheer Drupal would be a suitable CMS for the university's central web presence.  I'll write more about that another time.   We also had a presentation about how the university is adapting to the new law on cookies and privacy.  The meeting finished with a short discussion about getting central university data in order to create staff profile pages on school web sites.  We have yet to provide a supported API for this, so some enterprising school staff have found their own way to access the data they need.  This illustrates why a centrally supported interface is a food idea - it would mean a single, guaranteed way of accessing data, rather then multiple ad-hoc approaches that might break if IS change the central system.

Then I had two requirements gathering workshops for the Data Hub project that I blogged about recently.  Several useful strands of discussion suggested ideas to explore in more detail.  Several people were keen to access information about enrolment on tutorial groups, which is something we are just beginning to investigate.  In addition to the technical discussions, I also got some good recommendations of other people who I should talk to, including some of the academic staff who are making good use of e-learning technologies.

Finally I attended a meeting of the Computing Professionals Advisory Group in the College of Science and Engineering, as the IS Applications rep. I gave them an update on various projects and they asked a number of questions.  We were interested in each other's work with Drupal.  They are looking at the possibility of a college shared Drupal service and are wrestling with several of the same issues that we encountered with our preliminary investigations.  I'll be joining their mailing list on the topic, which should be a good opportunity for us to share ideas and experiences.


Comments

Popular posts from this blog

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…

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…

New staff for the EA team

I'm delighted to welcome Jason Murphy, who joins us as our CRM Architect, and Wilbert Kraan, our new Data Architect.  Both Jason and Wilbert have worked as consultants for several years and bring new skills and considerable experience to IS.  They both know more than I do about their respective fields, which is how I like to hire people.

So the Enterprise Architecture practice now comprises the three of us, instead of me working on my won, which means we have more capacty to guide the University's IT architecture.  We can offer a greater range of skills and can bring a wider range of experience to bear.  I'm really excited about the opportunities this presents.

As his job title implies, Jason will focus on contact relationship management, working to build a user community and to create a strategy for managing and improving the University's relationships with prospective students, research partners, community organisations, and other parties - to give them all a better …