Work Product Descriptor (Artifact): IT Services Detailed Design
This artifact shows the detailed flow of work through a services-based solution.
Purpose

This work product is created to completely define the IT Services for the solution. It is the final level of detail created during the design of the solution. It will be used as input into the development of the solution, especially in the writing of procedures, the customization of applications and data and the writing of user guides.

This work product can be used to communicate the final detailed specifications of the capability solution to the stakeholders.

Relationships
Input ToMandatory: Optional:
  • None
External:
  • None
Description
Main Description

This artifact include the tasks executed, the job function that performs the task, and the technology (both applications (or tool) and data) that is used to perform the task. In addition, the work product clearly describes the relationship of the tasks to the job functions and the technology. This work product has the following characteristics:

  • The job functions are shown using the defined job names of those jobs participating in the execution of the tasks.
  • The tools/applications are named and, ideally, specific functions and/or user interfaces are referenced.
  • The data fields used for each task are named and their source is identified.
  • The flow of information from one task to another is identified.
  • The tasks are shown in time sequence.
  • Optionally, time estimates for the completion of each task are indicated.
Brief Outline

The work product will normally consist of two components:

  1. Documentation of the specific tasks, tools, jobs and data associated to each other. It is recommended to gather this data in a table.
  2. Workflow charts to visualize the flow of the tasks in time sequence and associate the jobs and tools. There are several methods how to develop the charts (flowcharts, IDEF0, LOVEM, etc.). What to choose will depend on:
    • reuse of intellectual capital.
    • experience of the project team members.
    • standard method use by the client.
Properties
Optional
Planned
Key Considerations

The review of the high-level service design at the beginning of the development of this work product provides the opportunity to educate new project team members and have them understand the solution as designed.

Depending on how the IT Services Detailed Design work product output is going to be used, it may not be necessary to develop the workflow charts (e.g. LOVEM charts).  The narratives and task/job/data/tool table may be sufficient to meet the requirements of the engagement.

Tailoring
Impact of not havingWithout this work product, the details of the solution may be left unclear. As the development proceeds unnecessary time may be spent in rework, because the solution development may not be meeting the required specifications.
Reasons for not needingThis work product may not be needed if the solution being developed requires only a small degree of customization, or if capability will be executed in an informal fashion.