On 07/01/07, Gervas Douglas <[EMAIL PROTECTED]> wrote:
[snip]
> 2007 Prediction #2: Enterprise Architect Drought
> One dire prediction for 2007 is that there simply won't be enough qualified
> and SOA experienced enterprise architects (EA) around. Sure, there might be
> many "paper architects" – that is, those that claim EA and/or SOA skills on
> their resumes or in their career history, but much of that experience will be
> attendance at a few vendor-heavy SOA courses, the development of Web
> Services-centric interfaces, and a sore lack of any methodology, modeling,
> Service lifecycle, or governance experience to speak of. Yes, it might just
> be that the biggest force gating widespread adoption of SOA is not the
> technical complexity of SOA projects (one can actually say that the
> technology part is relatively trivial), but rather the organizational,
> architectural, and skill gap that most companies have in making this
> architectural change a reality.
>
[snip]
Putting the Zapthink certification to one side, this is the biggest
issue I face out there right now. Namely people who have actually
"done" SOA in the wild and delivered real systems and understand the
organisation and cultural benefits and don't start a slide deck with
"Harness the power of the internet" - REST
"Web Services to solve our integration challenge" - WS
"Enterprise Strategy to deliver Business Agility" - PPT only.
There are however lots and lots of people, often encouraged by a
paticular software vendor, who are embarking on large SOA Technology
projects, without considering the consequences.
So as a question to everyone, what are your top five questions that
you ask to separate the wheat from the chaff mine are
1) What is a service
2) What is the most important thing to consider when starting an SOA engagement
3) What is your approach for defining services and managing service
based projects
4) If there were three things you would mandate and three things you'd
ban, what would they be?
5) What will be the key changes in the SOA market from now until 2012?
There are others, including the "explain the difference between the
specification created by the WS-Reliability specification created by
the WS-RM group and the WS-RM standard created by the WS-RX group"
which is always good for a giggle.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/service-orientated-architecture/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
