Based on the consensus reached the demo we
are focusing on is a line-of-business integration between HR, Finance and
program management to track human resources costs for projects. The
consensus is to get this basic functionality up and running. Once done
there are various additional capabilities and scenarios that could be put against
it – for example one where an LOB service center is wiped out or one
where project resources had to be reallocated due to an emergency. Other
examples could be bringing a new service on line that utilizes the existing ones
(perhaps an emergent or dynamically defined service) – the options are
endless. From the perspective on enabling the federal transition
framework the current direction shows a lot of value – the integration of
loosely coupled organizations to achieve shared business services. The way
to actually do a LOB architecture is still up in the air, so we think it is a
very viable starting point to showcase SOA.
As far as I know there is no further
development being done on Rex’s emergency response demo – but perhaps
you should contact that group to find out.
soa-demo-bounces@xxxxxxxxxxxxxx [mailto:soa-demo-bounces@xxxxxxxxxxxxxx] On Behalf Of Paul S Prueitt
Sent: Saturday, September 23, 2006
To: [planning for soa-demo]
Cc: Thomas Erl; David RR Webber
(XML); Niemann. Brand
Subject: Re: [soa-demo] Ourcome
metics on the SOA demos
Is there a wiki page for the Emergency
Response Demo, particularily a page or number of pages that gives the kind of
detail that one would expect eventually would be developed?
In particular, there may be a detailed
scenario description and the list of all services, with standard formate for
convaying specificdata objects between processes.
There may be a published standard for core
data objects, a registry and repository of service definitions, as well as
demonstration of service discovery and the orchestration of service responses.
I have to admit that I have not followed
the demo development for months. The demo discussions and processes
started (May, 2006?)
What I was interested in was how
service discovery would be developed. If, in an emergency,
required services are not available from a standard set of data objects and
interfaces, how would a required service (one that was not in the standard core
but absolutely necessary in the emergery response) be identified/measured.
The OASIS BCM (business centric methdology)
and SOA Blueprints specifications have a process model for the aggregation of
new service defintion in real time. Was this process model used in the
Emergency Response demo, and if not how are the issue of novelty addressed?
I approach the modeling of event space
using the notion of natural category. As recently suggested, there are
two types of natural category, natural category that is stable and natural
category that emerges as part of natural processes.
Services may be defined as transactions in
a natural category space, where the transactions have charaterisitic event
chains. Web-services and "natural services" then are
reflections of each other; sometimes these reflections have high fidality and
sometimes they do not.
Does any of the demos specifically address
the issue of fidality, or of outcome metrics on the usefulness of a service
soa-demo-bounces@xxxxxxxxxxxxxx [mailto:soa-demo-bounces@xxxxxxxxxxxxxx]On Behalf Of Cory Casanave
Sent: Saturday, September 23, 2006
Subject: [soa-demo] Writing the
SOA demo spec
SOA Demo Team,
I have started writing into the SOA demo spec located here: http://colab.cim3.net/cgi-bin/wiki.pl?SoaLobDemoSpec
Please take a look at it and consider contributing along the
lines we have discussed. We should be able to develop a good deal of the
specification on the Wiki – all you need do is register for the wiki and
make updates. If there are open questions or controversial parts please
discuss it on the mail list prior to changing the spec.
We also need to start work on the technical considerations
– registry and web service details. Lets try and get “hello
world” running very soon.