4.1.11: SDLC
Use a Service-Based SDLC with Incremental Development Practices Other Information:
The service-based solution model is characterized by two primary roles: provider and consumer. Because the lifecycles, skills,
and responsibilities for these two roles are significantly different, SOA methodologies separate the solution development
lifecycle (SDLC) into two tracks (known as “twin track” development): service provisioning and solution assembly. An important
step for agencies to take is to revise their SDLC to incorporate twin track development and recognize the different life cycles
for services and (composite) applications. SOA implementations are by design, continuously improving environments that deliberately
feed on the innovation of the various participants. Therefore, SOA implementations should not be designed with a single deliverable
and a firm deadline. That is, SOA should not be fielded as a traditional major acquisition program via a long waterfall process.
Rather, it should be fielded as the service-oriented capability via the lifecycle maintenance model, i.e., as a continuous
and innovative technology refresh. Lifecycle maintenance of a modern computer network requires incremental innovation on a
time scale consistent with Moore’s law and aimed at specific operational issues and opportunities. Agencies should define
their services environment as a major resource that is already in place and that requires continuous improvement. The task
is to enhance business agility through incremental re-capitalization. Think of SOA lifecycle maintenance as an innovative
and evolving technology refresh rather than as a major acquisition.
Indicator(s):
|
