Lists Home |
Date Index |
Regarding item #1 below:
1.The impact of XML
-How it effects the life cycle of a project?
-In all the phases such as design,implementation etc.
-an example of such implementation
You may wish to tackle this in terms of service-oriented architectures
(SOA), whose foundation is XML (webservices.org is one of many good
resources for SOA). Thinking in terms of the SLDC, here are some phases
and an example of how one benefits from SOA. This assumes that there are
existing services (perhaps within a single organization, or out there on
the Web) that one can leverage. Any issues regarding service quality,
trust, etc. are outside the scope of the example below (they are
extremely important issues, but I don't think you want me to write all
day on this :):
Less time spent in detailed requirements, due to the availability of
existing services that can be discovered (in a registry) and leveraged.
High-level requirements may be same, given that you have to determine at
least your high-level requirements to determine what you are searching
Less time spent here, as you have less designing to do given that you
have discovered one or more services that you can leverage. You may
decide that you need to enhance a discovered service for your purposes,
so there may be design in that regard.
Same general ideas as for Design Phase, but in terms of less development
required. Although not depicted here, one can also insert a "DISCOVERY
PHASE" after high-level requirements and before detailed requirements.
Less development means less testing (please note that normally one would
break this out into unit testing, system testing, etc. - I'm keeping it
So in general, SOA tends to compress the SDLC given that an increased
number of services available can (stress "can", not "will" because it
depends on their suitability for the requirements at hand) lead to
shortened phases as discussed above.
INTEGRATION PHASE (some do not consider this a "truely separate" SLDC
SOA's foundation of open standards means easier integration between
components of an architecture.
SOA's notion of shared services means less instances of a service to
deploy (perhaps only one to deploy), which means lower licensing fees,
lower maintenance fees, etc.
Additionally, for those parts of a SOA that are Web Service-enabled
(because SOA does not have to equal Web Services 100%), use of the WWW
for communications rather than "private" networks means lower
Further additionally, rehosting costs can be dramatically less in that
with a Web Service within a SOA, a change to an address within a WSDL
document (and awareness of that change by service consumers, be this
out-of-band, pub/sub, or other) is much more efficient than "rewiring"
Hope that helps.
Booz Allen Hamilton
Strategy and Technology Consultants to the World