You can keep up with news about the projects that we are working on at the University of Edinburgh by subscribing to the RSS feed on our projects website.
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…
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…
Comments