|
|
Tim O'Neill, University of Technology, Sydney, Australia |
|
|
Dr Tim O'Neill holds a Bachelor of Engineering degree in Computer Systems and a PhD from the University of Technology, Sydney (UTS). Currently he is a Research Fellow in the UTS Institute for Information and Communication Technologies (IICT) and for the last 3 years has been the CEO of Avolution Pty Ltd, a UTS spin-off company. In
the last 15 years Dr O'Neill has published over 40 internationally
refereed papers and consulted on large commercial projects
in all sectors in Australia and overseas. He is currently
undertaking multi-disciplinary, qualitative and quantitative
research and consulting for large-scale, complex enterprises
and systems on behalf of UTS and Avolution Pty Ltd |
|
|
|
Presentation CASE STUDY: Enterprise Architecture Modelling at Birmingham City Council
Birmingham City Council (BCC) is one of the largest local authorities in the world and is 1 year into a visionary 10 year / £450M business transformation programme. One of the first initiatives undertaken has been to construct the "Council in a Box" enterprise model as a single-point-of-truth for the Council. This presentation will briefly cover the Enterprise Modelling (EM) Method used to build this model, aspects of the resulting Framework and the structure and connectedness of the Repository using the ABACUS solution from Avolution. We will also introduce some revolutionary techniques (including descendant architectures, capability space charts and trade-off diagrams) used by BCC to analyse and communicate the trade-offs and benefits of various enterprise-wide initiatives, alternatives or solutions across people, processes and technology.
Key questions explored:
- Is traditional Enterprise Architecture just "Art for Art's Sake"?
- Why passive modeling to develop "just enough architecture" was the only way forward
- Are all architectures and architecture-models equal?
- The difference between "Impact Observation" and real Trade-off and Impact Analysis
- Managing non-functional requirements like TCO, Performance, Availability and Security
return
to program
|
|
|
|
|
|