Skip to main content

Towards automated deployment

Currently, whenever we deploy a new application on the university's IT infrastructure, we follow a detailed quality assurance process.  This involves several different teams.  The actual deployment is performed by the database/system adminstration team.  If we developed the application ourselves, or if it needed significant integration with other university systems, then the software development or software configuration teams will be involved.  The corresponding support teams will check that they have the documentation and knowledge that they need to start supporting the application once it is "live".  The project mangers co-ordinate everything.  And this is just the teams in Applications Division; our colleagues for whom we are implementing the system will be doing their own checks and making their own arrangements.  So deployment takes quite a bit of effort and time.

What we would like to do is to make this process easier, quicker and more reliable.  To this end, we have run software development project in which we tried using a continuous integration tool.  Rather than having one big deployment with everyone involved, we wrote scripts to automate the process and had deployed the application (to a test server) every time the software changed during development.  Automated tests ensured that we didn't introduce any bugs as we wrote new code.  The result was a much smoother deployment process, and the assurance from much greater testing (the equivalent of 60 days of a human tester).

We're now looking to make this a standard approach for our software development projects.  At least on of our developers is wondering why management (that's me) doesn't just make this happen immediately. Well, as is often the case, the technical solution is simple, but we need to change the "people" part of the process to make it possible.  All the teams need to understand how the new process works and what it means for them.  We need to understand what value the different teams currently bring to the process and make sure that we don't lose these contributions.  We also have to adapt the other parts of the process, such as writing support documentation, to work with the new deployment process.  All this takes time, and has to be done while we're under pressure to deliver a large number of systems during the year.

Although it will take some work to make this happen, I'm quite excited by this development.  It promises to make our deployments much easier for everyone and to provide a consistently reliable service to our colleagues. I'll post news of progress here as it happens.

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…

A brief summary of our major initiatives

I notice that in 2016 I wrote 34 posts on this blog.  This is only my fifth post in 2017 and we're already three-quarters of the way through the year.  Either I've suddenly got lazier, or else I've had less time to spend writing here.  As I'm not inclined to think of myself as especially lazy, I'm plumping for the latter explanation.

There really is a lot going on.  The University has several major initiatives under way, many of which need input from the Enterprise Architecture section.

The Service Excellence programme is overhauling (the buzzword is "transforming") our administrative processes for HR, Finance, and Student Administration.  Linked to this is a programme to procure an integrated ERP system to replace the adminstrative IT systems. 

Enabling Digital Transformation is a programme to put the middleware and architecture in place so that we can make our processes "digital first".  We're implementing an API framework, a notification…