Minor glitch I think, but the AAF site was back online this morning. Register away - only a few days to go before we kick off in Melbourne!
Got a report this evening (thanks, Michael) that the Australian Architecture Forum site is down. It'll be back online asap, so hold tight if you are trying to register, and keep checking back in with us.
In the meantime, check this little fella out:
We were on the road between Traralgon and Woodside this weekend, on our way to visit P's mum, and came around a corner to discover an 'ex-Roo' laying in the middle of the road. Being a moderately blind corner, it wasn't a great place to suddenly come accross for a large amount of animal at 100Kph, so after a bit of discussion we decided to turn around and move it off the road. Lucky we did, as this little guy was still in it's mum's pouch.
Although sadly it's mum hadn't survived, the Joey seemed to have escaped trauma. We gently pulled it out of it's mum's pouch, wrapped it up nice and warm and called Wildlife Victoria when we got to P's mum's place.
They were amazing, and had a local carer over within the hour to pick it up for fostering. The carer said that it's very common for Joey's to be found alive in their pouches days after their mum's have been hit by vehicles. It just goes to to show - if you hit something, it's really important you stop and check whether it had any young that might have survived (as well as assessing whether the animial you hit can be saved and/or isn't suffering, and doesn't represent a risk to other people on the road).
We're in the final countdown to this year's Australian Architecture Forum, which I'm very proud of being a part of again this year. The AAF - in case you didn't know - is a unique conference designed to maximise opportunities for IT architects to (a) network with other architects and (b) learn how other architects practice architecture, and what they think. The idea is that rather than spend most of the day listening to presenters talk about their topic, AAF attendees split up into smaller round-tables to discuss specific topics with a subject matter expert but mostly with each other.
This is a great opportunity to get with other architects from similar (or dissimilar) backgrounds and industries to learn how they approach architecture, to find areas of common interest and practice, and to get to know others in the industry. It's also a great opportunity to get into a room in order to disagree with what everyone else is saying, which is always entertaining (and educational) if last year's forum is anything to go by :)
This year is shaping up to be very interesting, with Microsoft, IBM, SalesForce and Thoughtworks and Object Consulting working in unison to produce a single-day event that addresses multiple industry points of view. We're at an inflection point in the industry, with traditional on-premise models of software delivery being transformed by the availability of new services provided in the 'cloud'. What does this mean for architecture? How do the traditional concepts of SOA apply to this new model, and what does the future look like. I can't think of many forums where you could get the major players at the same event debating and discussing this topic on neutral ground, which for me is what makes the AAF model compelling.
Some particularly interesting (at least for me) sessions on the agenda:
- Ron Todd, Worldwide Solutions Architect delivering the AAF keynote on SOA and business agility.
- Peter Coffee, SalesForce Director of Platform Intelligence busting some myths about SaaS.
- David Lemphers, newly minted MS corp Cloud Services Product Manager talking about SOA strategies designed to leverage the best of on-premise as well as cloud services.
- Chris Seymour from Object Consulting talking about key SOA drivers for Smart Client applications
- Ron Jacobs, Microsoft Corp WCF/WF evangelist talking about RESTful services co-existing with traditional SOA web services.
- Gianpaolo Carrao, Microsoft Corp, discussing some of the implications of the consumerisation of IT services.
- The Thoughtworks team - Jim Webber, Joshua Graham and Richard Durnall delivering what I think will be an extremely interesting (and knowing Jim) quite possibly very entertaining locknote on how the enterprise is responding to pressures in the modern computing environment (and hopefully it's not all about enterprise computing being backward ;) ).
There's only nine days to go before the first event kicks off in Melbourne on Friday 16th May, while the second event is on in Sydney on Monday 19th May. If you don't have your ticket yet, don't despair - there is still time to register at the AAF site to secure your spot. This is one architecture community event you don't want to miss!
Just got a note from Deeps that the TechEd 2008 site is now live. I'm looking after the Aussie and Kiwi Architecture tracks at TechEd again this year, so I've been thinking about the sort of sessions that we'll have in the track. The official Architecture track summary is as follows:
You already know a lot about different products and technologies, but how do you make them work together to solve business problems? How can you create applications and infrastructures that solve today’s challenges-without just choosing technology for technology’s sake? The Architecture track offers broad architectural perspectives that span many products, technologies and solutions. We can help you further or begin your career as an architect by providing the background, patterns, and real-world guidance you need.
This year, we're focusing on three broad areas:
- Persona: What is the role of an architect? How do I become an architect? What skills does an architect need?
- Patterns: Architectural patterns and practices, considerations like user experience and distributed applications, and current trends like software-plus-services and composite applications.
- Practice: Real-world case studies, best practices, recommendations, and other architecture-related guidance.
The purpose of this track is to help you coordinate your knowledge of multiple products, technologies, and solutions to meet the business needs of your organisation. Further your career and solve tomorrow's architectural problems today with the knowledge you'll gain from the Architecture track.
The general idea of the architecture track is to step up a level of abstraction and look at some of the higher order bits of the topics that are being addressed in the other other parts of TechEd. The track is less about the technology per-say, and more about the considerations and practices raised by the adoption and use of the platform.
So, with that in mind, what do YOU want to see in the track? Who would you like to see presenting from MS corp (or elsewhere) this year? I've got a few speakers in mind, but I'm interested in your feedback about what would be of interest. What topics are going to spin your wheels? Should we be talking more about Live? About S+S? About patterns&practices? Methodologies? Something else?
Let me know your thoughts. As we develop the track, I'll start posting ideas and topics here so you can follow along.
PS: Check out the TechEd Australia and NZ sites. Note the use of Silverlight on the Aussie site. Very pretty. I voted for "Gladiator" :)
Dave recently pinged me on this little meme that's going around that lets you inflict random factoids about yourself on unsuspecting visitors to your blog. I'm up for it. The ground rules are as follows:
- Each player starts with eight random facts/habits about themselves.
- People who are tagged need to write a post on their own blog (about their eight things) and post these rules.
- At the end of your blog, you need to choose eight people to get tagged and list their names.
- Don’t forget to leave them a comment telling them they’re tagged, and to read your blog.
Little-known facts about Nigel
- I'm half-Maori. My Dad was from Taranaki, on the west coast of the North Island of New Zealand. On my mother's side, it's all Scottish and German from the deep south.
- I worked on a shearing gang when I was a student. I was the guy who scraped the dags away
from the fleece during shearing, and then gatherered the shorn fleece
to be transferred to the classing table. I always held jealous
aspirations of working the wool press, which was the most advanced
piece of technology in the shearing shed at the time.
- I am addicted to an online world-war-II combat flight simulator called Aces High. My call-sign is 'whisk' and I'm in a squad called the "Airborne Kitchen Utensil Assault Group", along with several other kitchen implements. My preferred ride is the Pony.
- I once played drums in a progressive country punk power trio called 'The Hyphen-Ears', with Steve Watson and the late Kevin Smith. Kevin went onto become an actor of some repute, most notably as 'Ares, God of War' on 'Xena, Warrior Princess'. Kev was an amazing guy, who's sorely missed by all who were lucky enough to have known him.
- I studied computer science at the University of Canterbury, in Christchurch. My undergrad degree was a B.Sc, and my master's degree was (somewhat bizarrely when I think about it) a M.Com. Really, the post-grad degree thing was all about avoiding getting a job in the real-world.
- Most of my work prior to joining Microsoft was on un*x based platforms. I have worked for Microsoft for 6.5 years now, and I still spend quite a bit of time fiddling with various flavours of Linux.
- My partner's name is Princess. No really, it is.
- I'm a cat person, but allergic to cats. So we have a dog.
So, onto the viral part of the meme - the tagging:
Taking my lead from Greg, I've finally gotten off my derrier and set up my skydrive account so I've got a convenient place to post Melbourne Architecture Council Decks. I've placed the deck from Dr Bohdan Szymanik's excellent session on KiwiBank on the share. Kiwibank's story is very impressive - in seven short years they have built an online bank from (literally) nothing to an operation that now has in excess of 600,000 customers. Not bad for the size of the market in NZ. It was great to hear about how Kiwibank achieved this bootstrapping feat - which was as much about a clear business imperative and overcoming organisational obstacles as it was about technology. Great session, and I'm glad we were lucky enough to have Bodhan come over.
Following all of the excitement around Silverlight 2 at MIX last week, last night we quietly released the source code for the Silverlight Retail Financial Services Demonstrator onto an unsuspecting interweb. This is a technology demonstrator that shows how you can build a rich, immersive online banking experience in Silverlight, and it's got some really shmik features that I wish MY bank had. These include interactive 'what-if' games you can play with your mortgage, being able to schedule payments and model how these affect your account balance through the month, and navigating your stock portfolio, amongst lots of other cool things.
If you are interested in getting a quick overview, there's videoed session from MIX posted up at the VisitMix OpenSpace blog. However, if you're like me, you'll probably just want to download the source and start playing with it, which is what I did :) Here it is, running in (ahem) another browser.
Note, I followed the instructions in the distribution to get this up and running, which are pretty good. However, this is one small change you might need to make in order to get it working on your system. Initially, once I had it all set up, I ran the application, and was rewarded with... a blank browser page. A bit of investigation revealed the cause: in the file TestPage.html.js, you'll find a Javascript function createSilverlight. The first thing this function does is make a call to SilverLight.createObjectEx(), passing a source parameter for the SL xap of "BankingDemo.xap". However, this xap actually lives in the ClientBin subdirectory, and so my browser couldn't find it. Quite simply, the call to createObjectEx never returned a functioning silverlight object to the browser. The fix was simple: just qualify the name in the source parameter as "ClientBin/BankingDemo.xap", as shown below, and all should run fine.
Happy Retail Financial Service Demonstrator Code Tinkering :)
This week, I've been helping host my good friend and colleague Gianpaolo Carraro at a number of round-tables discussing Software + Services. We're half-way through; yesterday we conducted a session in Melbourne, and this morning we were in Canberra. As I write this, I'm at Canberra Airport waiting for our flight to Sydney, where we're on again tomorrow morning.
I have to say it's always fascinating to observe how differently architects in the private sector see the world compared with architects from the public sector. With regard to Software + Services, in Melbourne much of the discussion centred on the practicalities of integrating internal with external systems. In particular, authR/N got a fair bit of attention - i.e. how are you going to do SSO between your internal systems and stuff that's hosted by a cloud provider? Obviously you want your users to have as good an experience as possible, and this doesn't include having to type credentials into every app you access (or incorporate into a mash-up of some kind). Moreover, what about authorisation? It's important that you can map internal user auth groups onto the roles that are (presumably) provided by the service running in the cloud. Very interesting conversation, and to me the entire session was an implicit validation of the model that enterprises will increasingly start to consider externally hosted and run software as well as software that will continue to run on-premise.
On the other hand, at this morning's session in Canberra - to predominantly public sector architects - the focus was much more on the cultural and legaslative aspects of consuming services that are provided by outsiders. As you'd expect, for some federal agencies, relinquishing control over citizen or national data is simply not an option. Think tax, or defence. One of the major concerns is privacy - in the private sector, if someone inadvertantly discloses your financial details, you could probably redress this with some kind of monetary compensation. In the public sector, if someone inadvertantly discloses something about your - say - health records, then it could potentially ruin your life. Because of this you could argue the stakes are considerably higher for this sort of information, and the agencies take the custodianship of this information very seriously.
However, having said this, it was also clear that even in the public sector there are lots of commodotised capabilities that dont necessarily hold personal information, or information of concern to national security, that may be very good candidates for externalising. One example given was ERP - many government purchases are a matter of public record - i.e. department X spent $Y with provider Z. The financial transaction is already in the public domain, and therefore could be hosted/executed by a third-party provider. The details of the transaction i.e. exactly what was purchased, may not be, and could be retained on internal ERP systems that are in some way linked with the external application provider. This to my mind is one of the best aspects of the S+S vision - you can concentrate on what's important for your business (tracking the inventory of what you've bought), and factor out the stuff that's not that interesting (the fiscal details of that purchase).
Anyway - I'm looking forward to the session in Sydney tomorrow morning. I've attached GP's deck to this post - enjoy!
Last week Glenn Smyth, Chief Architect from the Adelaide Bank presented for us at the Melbourne Architect Council.
Ostensibly, this was a talk about SOA, and how you can use capability modelling (ala Motion, now called MSBA) to guide some of your decisions about implementing service oriented architectures. But really, the talk was about good old fashioned organisational politics.
Want IT architecture to have an impact on the business? Get the role out of IT, and _into_ the business. What does this mean? In the case of Adelaide Bank, it means that architecture is a strategic group that reports directly to the CEO. They have a voice with the business, and are seen as adding strategic direction and business value to the organisation rather than simply being seen as 'governance' and 'standards'.
This also means that to be truly effective, enterprise architects MUST understand the business, which further implies that the business itself must be able to articulate what their actual business strategy is. This might seem trite, but quite often it's the case that the business has trouble with this. It's not enough to say "increase market share" or "improve customer retention and monetisation" or even "maximise profits through improved execution and reduced costs". The strategy needs to be more specific than this, and include a clear view of the business intent of the organisation as well as some clear thoughts on the business operating model (ala the thinking from Enterprise Architecture as Strategy: Creating a Foundation for Business Execution).
The upshot is that if, as an enterprise architect, you aren't armed with a clear view of the business intent, strategy and operating model, you are more or less working in the dark as you try to align your architecture (and services) to the business.
It was a great session, with plenty of food for thought. I've attached Glenn's very useful annotated deck to this post - feel free to grab it and have a look at how capability mapping can help your thinking around SOA and working more closely with the business.
The newly (and most likely temporarily) facially hirsuite Dave, the ever-analytical Graham and I spent an intimate evening a few weeks ago with 20 of our closest MOSSIG friends discussing "The Platform". Tim has posted a podcast (and summary) of this session, which I have to admit I haven't had a chance to listen to yet... but from memory it was one of those very interesting chats where everyone is either in vehemant agreement or arguing bitterly about semantcs :)
FWIW - I still maintain (looking furtively at CodeJedi here) that the .NET framework, as well as the SCSF, SSF and the WCSF are all platforms by my admittedly arbitrary definition: "any code artifact that accelerates your time to value is a platform".
Thanks Tim for giving us an opportunity to be part of a really interesting discussion!
It's hard to believe that it's only a few days until the inaugural Australian Architecture Forum. But don't despair, there's still time to register for the event if you haven't had a chance to yet. I've been looking at the agenda today, and it looks like it'll be a really interesting conference. Some highlights - at least for me - are:
Dr Paul Ashley from IBM talking about IBM's take on e-Business patterns
The IBM Patterns for e-Business (p4eb) have been used by architects and specialists in sales and delivery situations for a number of years. They can be used to provide a step by step approach to designing a solution for a client, by partitioning the problem into logical business patterns. These patterns are then refined through application, runtime and deployment patterns. The advantage of using p4eb is that they are a great productivity tool in designing systems and also express the design in a common language that is easily understood. With the advent of SOAs and Web 2.0, the p4eb are evolving to make use of these new technologies. Significant work is underway to update the patterns so they reflect the current thinking in both these areas, providing new solution approaches.
It's clear to me that - at the moment - there's a dearth of good architectural guidance for enterprises looking at how best to incorporate Web 2.0 concepts into their architectures, so it'll be interesting to get IBM's perspective on this.
Phil Argy, ACS president hosting a roundtable discusing IP, and ramifications for software development
As a partner of Mallesons Stephen Jaques for over 20 years and President of ACS and on World Intellectual Property Organisation (WIPO) panel of arbitrators for the resolution of intellectual property disputes Philip Argy is uniquely qualified to lead this discussion on the discussion on the legal ramifications and challenges of writing software in Australia.
This is a really interesting topic. Do we pay enough attention to the legal side of the systems we architect? In my experience, I'm not sure we do...
Evan Bottcher from Thoughtworks discussing legacy application extension
The project team faced a tough challenge. The business wanted to build some major new features for their resource planning application, but the existing code was a bit of a mess. Serious design problems were immediately apparent which would make it difficult to deliver the new features required, and the current functionality could not be clearly understood. There was almost no automated test coverage to give confidence. Surely it would be best to start from a clean sheet of paper?
Instead the team embraced the legacy and carefully renovated the application while delivering new functionality. This enabled us to make earlier and more frequent releases and reduce risk dramatically. This session will share the approach used by the team to quickly and safely extend and improve the application.
IMHO War stories are probably one of the best ways to learn more about the practice of architecture, so this session and other similar case studies from the community are going to be really valuable parts of the conference
Brett McDowell from Object Consulting talking about the practice of Architecture
What skills, experiences and other attributes are needed to be an Architect? What levels and types of Architects are out there and what exactly do they do?
'Architecture' in IT can mean a range of things. Typically it is a poorly structured discipline within the software industry as a whole and within the software engineering fraternity in particular. One of the reasons is the number of 'soft' aspects to architecture which have proven difficult to formularise, codify and document.
Most Architects work in an ad hoc manner and will have a range of tricks and techniques and some shortcuts and preconceived ideas of what works and what doesn’t. But very few Architects can actually describe how to actually architect a system clearly, which makes it very difficult for people wishing to become architects.
'Architecture' is such a broad term that it's often hard to figure out what it actually means to be an 'architect'. Should be a fascinating round-table.
On that same topic, it's also good to note that IASA international president Paul Preiss will be in Australia especially for the Architecture Forum to talk about how the IASA are working with the international community to address some of the concerns the industry has regarding legitimising the role of 'architect'
Join Paul Preiss, President of the International Association of Software Architects, as he guides you through the knowledge required in today’s software architects. This knowledge base comes from the official IASA skills taxonomy (http://www.iasahome.org/web/home/skillset) which represents a revolutionary step in the development of the architecture profession. For the first time real architects detail the knowledge and capabilities which have taken them to the top of the field. The knowledge was taken from over 85 of the world’s top architects, each with over 10 years experience in IT architecture. It has been compiled into a powerful set of materials which describe the skills you need to be successful. In this exclusive session Paul will show you how to increase your existing skill set using this powerful knowledge base.
There's lots of other great sessions - the entire agenda is online for you to have a look at on the forum site. So, if you haven't registered to come along already there's still time! Hope to see you there!
I couldn't resist it.
Check out Frank's blog for more TechEd LOLCATs madness.
Just a reminder, for those of you that haven't seen an invitation yet - time is ticking away to get yourself registered for the Australian Architecture Forum, which runs in Sydney and Melbourne in a couple of weeks time.
This is a truly unique event; IBM, Microsoft, Object Consulting, ThoughtWorks, EDS, SDM, and WDG, along with the IASA and ACS all working in unison to bring together some of our local community's brightest to discuss and share solution architecture practices.
Top five reasons why you should consider coming along:
- Meet and network with your peers in the industry. What do architects at other organisations do? How does this compare to what you do, and what can you learn from others?
- Discuss and share experiences. The majority of the day is made up of round-tables, hosted by subject matter experts from the community. This is YOUR opportunity to learn directly from someone with an architectural speciality while at the same time having a chance to voice your own thoughts.
- Find out how you can progress your career as an architect. What certifications are available? How do you get onto these programs? What sort of mentoring is available?
- Learn about the latest best practices in architecture in some of the breakout sessions. The keynote will be delivered by none other than Don Ferguson, otherwise known as the 'Father of Websphere'. This is a very, very special chance to hear his thoughts on how SOA, ESBs, Web Services and Web 2.0 technologies are harmonising in the industry.
- The event is a single-day, in either Sydney or Melbourne. No need to block out 2-3 days for a long, drawn out conference. AND it's incredible value for money - less than $300.00 to participate in a unique forum in which you can help set the agenda for the day.
Hope to see you there!
I'm an Industry Track paper reviewer for the 2007 Australian Software Engineering Conference, being held in Melbourne in April this year. The venue is booked... the track committees and chairs selected... sponsors are being charmed... and now all we need are people to share war stories, ideas, and experiences in the Industry track.
This is a great opportunity to talk about your favourite (or not so favourite) project in front of your peers. Some of the topic areas you might consider are:
- Architecting Software as a Service solutions
- Large-scale information systems development
- Enterprise application integration
- Building interoperable applications
- Building secure systems
- Novel development method experiences (eg. Agile, Aspect Oriented)
- Adopting new technologies
- Model driven development experience
- Service oriented architecture case studies
- Advanced web services projects
- Patterns and practices
- Measuring ROI
- Software project management challenges
- Enterprise architecture and governance issues
- Technology acquisition methods and experiences
- Outsourcing experiences
- Local product development success stories
- Vertical industry project case studies
... or create your own topic. You'll have to hurry, though - abstracts (200 words or thereabouts) need to be submitted by the 4th Feb.
Chuck and I - in conjunction with Object Consulting and the ACS - are working on catalysing a community architecture event for next year, which he blogged about last week here and here. I wanted to chime in on some of the underlying thinking behind why we think this event will be important, and what you should expect from it.
The overall goal for the Australian Architecture Forum is to create a vendor and community neutral space in which architects - and budding architects - can engage in dialogue with subject matter experts from the community. With that in mind, the top-level objectives for the forum are that it should be:
- Inclusive. The forum format and topics need to appeal to a broad range of solution architects. While we intend that practicing architects from the community will find it desirable to come along, we also believe it's equally important to reach out to the 'next generation' of architects - i.e. those in lead developer roles - to get them to participate in the discussion and learn about how solution architecture is practiced in the industry. Platform neutrality is essential.
- Relevant. It's important that the forum incorporates topics that are relevant to the architecture challenges of today; in addition to technology topics, it'd be great to address the softer side of solution architecture. This might include issues such as organisational politics, project funding and management, intellectual property law, pragmatic approaches to architecture, working with project teams - amongst many other possible topics. ** see below for more on topics.
- Interactive. Rather than show-up-throw-up 1:many presentations, we are aiming to encourage discussion and idea sharing amongst attendees. Our experience suggests that round-table discussion groups facilitate this well - and these types of interactions are seen by participants as much, much more valuable than traditional group presentation breakouts, and provide opportunities for networking. I mean, anyone can sit in a room listening to a presentation, or download a web-cast, but how many opportunities to you get to have a structured conversation with a subject matter expert AND a room full of your industry peers?
- Accessible. In short, let's have as few barriers to participation as possible. This means keeping registration costs affordable (we're aiming at around $250 per person), and limiting the duration of the event to a single day (to avoid participants from out of town having to set aside multiple days to attend, as well as potentially avoiding the need for them to book accommodation etc).
- Ongoing. This is really important. Rather than simply conducting a point-in-time conference, it'd be great to capture ideas, thoughts and best-practices from each moderated round-table, and then publish these on a publically accessible WIKI. The idea is that - over time, and over several of these events - the WIKI will gradually become a community resource of ideas and guidance on the pragmatic practice of architecture. We're initially aiming at running this event in Sydney and Melbourne. However, provided the recipe works well there's no reason why this same event can't be run in other places around Australia, giving everyone an opportunity to contribute to the community dialogue.
The format of the day is going to look something like this:
|
08.30-09.45 |
Breakfast Keynote |
|
10.00-10.50 |
Breakout A1 |
Breakout B1 |
|
10.50-11.10 |
Morning Tea |
|
11.10-12.00 |
RT1,1 |
RT2,1 |
RT3,1 |
RT4,1 |
RT5,1 |
RT6,1 |
RT7,1 |
RT8,1 |
RT9,1 |
RT10,1 |
|
12.10-13.00 |
RT1,2 |
RT2,2 |
RT3,2 |
RT4,2 |
RT5,2 |
RT6,2 |
RT7,2 |
RT8,2 |
RT9,2 |
RT10,2 |
|
13.00-14.00 |
Working Lunch |
|
14.10-15.00 |
RT1,3 |
RT2,3 |
RT3,3 |
RT4,3 |
RT5,3 |
RT6,3 |
RT7,3 |
RT8,3 |
RT9,3 |
RT10,3 |
|
15.10-16.00 |
RT1,4 |
RT2,4 |
RT3,4 |
RT4,4 |
RT5,4 |
RT6,4 |
RT7,4 |
RT8,4 |
RT9,4 |
RT10,4 |
|
16.10-17.00 |
RT1,5 |
RT2,5 |
RT3,5 |
RT4,5 |
RT5,5 |
RT6,5 |
RT7,5 |
RT8,5 |
RT9,5 |
RT10,5 |
|
17.05-17.30 |
Closing/Summary |
Each of those slots marked RT is an individual round-table session. We plan on allocating topics to slots, balancing the number of times a particular topic is run according to demand. For example, let's say that we had a topic that 50% of attendees in Sydney were interested in participating in: assuming we had 200 or so people at the forum, and we're limiting to 20 the number of individuals in a round table, we'd need to run this topic in five of the slots. Make sense?
Chuck has posted a list of possible topics for discussion. There are probably many more sub-topics in each of these broad areas that we could drill down into. If you have thoughts on what these might be, and what you'd be interested in seeing that's not in the list below - please drop either Chuck or myself a line via our blogs.
Here's the straw-person list:
- Architectural Strategies for Portals.
- Legal and Intellectual Property issues for Architects.
- Project Management/Team dynamics
- The Architecture of Middleware - SOA and ESB considerations.
- SaaS - what is it, and what does it mean for architecting software?
- Web vNext. Business AND Technology considerations
- Business Intelligence Strategies
- Virtualisation/Physical consolidation.
- Data Architectures.
- Modelling tools, Model driven development, methodologies, tools, factories.
- ... what have we missed?
Interested to hear from you if you've got ideas on how we should run this, additional topics to consider, or if you want to be involved as a Subject Matter Expert (and your organisation is willing to become a stakeholder in the event).