Peruse Muse Infuse

Home | Site Map | Site Index
Subscribe To This Blog
Atom Feed
RSS 2.0 Feed
Tags
Agile (9)  Architecture (25)  ASP.NET MVC (1)  Aspiring Architects (13)  Bio-Diversity (1)  Business (4)  Business Architecture (1)  Cheat Sheets (8)  CodePlex (4)  Dalek (1)  Data Architecture (1)  Enterprise Architecture (3)  Formula One (1)  Garfield (1)  Ghostbuster (1)  Hello Cruel World (1)  History (2)  iGovt (1)  Inter-Personal (1)  Modeling (5)  Morphfolia (1)  Off Topic (3)  open source (7)  podcast (3)  Political Architecture (1)  Politics (1)  Security (7)  Solution Architecture (1)  SqlAzure (1)  Strategy (4)  Tech-Ed 2009 (3)  The Cloud (4)  Thinking (6)  Web Development (7)  Wellington (12)  WSAF (12) 
Recent Posts
Base-Line of Usability NFRs
RoboMojo
Hitchhikers Guide to NFRs - the System Quality Attributes Map
Backlog Depression
At the Coal-Face - Solution Architecture in the Public Sector
Security Guidance - Practical Non-Functional Requirements
Career Direction - What and How
10 Years in IT - 6 Lessons Learnt
I Blame the Superficialites
Free Un-Evil Options Analysis Template
Available Blogs
Morphfolia Code Log
Peruse Muse Infuse
At the Coal-Face - Solution Architecture in the Public Sector
Posted at 29/06/2010 10:05:15 p.m. by AdrianK (68 days, 5 hours and 55 minutes ago)
Tagged under: Aspiring Architects, Wellington, WSAF, Solution Architecture

At the Coal-Face - Solution Architecture in the Public Sector

I'll be speaking at the next WSAF meeting, my topic being what I do every day.

When: Thursday 8th July 2010, Networking from 12:00 noon, Formal session from 12:30 - 1:30pm 
Where: Equinox (level 5, Equinox House), 111 The Terrace, Wellington

RSVP to me via email or LinkedIn: http://events.linkedin.com/Coal-Face-Solution-Architecture-Public/pub/354587

What (I think) I'll be talking about - I can't promise to cover it all, but these are the lines I'm thinking along:  

The Merger: NZTA = Transit NZ (Java, Novell) + LTNZ (.Net, Microsoft and Mainframes), different cultures, 2-into-1, and so on.

  • Setting the scene: size and physical dispersion of the agency, different core business of ex-Transit / ex-LTNZ, high level technology being used.
  • Technical diversity - high level overview.
  • Absence of in-house development capability - which gives us greater latitude as we don't have to maintain development teams that cover two major back-end platforms.
  • The influences of technology on development / project approaches (iterative / waterfall).

What I do, what others think I do and what actually happens.

  • What I do: technical assistance (in the absence of developers), conceptual kite flying, helping research and making decisions.
  • "Selling" architecture.  Walking the balance of the Enterprise view and the Project view.
  • How there's not so much actual technical design work as I thought there would be - more of a consultative role supporting others, providing support through discussions.
  • Non-functional Requirements: comment on how I support the BA's; how we cross-pollinate with other govt agencies.
  • Use of Sparx EA for modelling.

Differences between working in the public and private sectors.

  • Working with legislative drivers (why we can't be late)
  • Trust: public information - how we work with public information / provide public services - the fact that everyone takes this responsibility very seriously.
  • Government shared services: leveraging these.

 

 Some rights reserved.
Last Modified 15/04/2010 11:34:08 a.m. by AdrianK (adriank [at] morphological [dot] geek [dot] nz)