DETAILED TECHNICAL SPECIFICATION (DTS)

Contents:

A DTS is a functional specification, and refers to technical details of the system.

a. Objectives

The objectives of a DTS are to:

Spell out how to modify the system to implement a business requirement already described in a DBS

  • Provide direction and detail that will reduce errors and reduce the need for later clarification
  • Pass on knowledge about the system from LIFEfit experts to as many others as possible as a learning experience (through the review process)
  • Help ensure that ongoing development of LIFEfit proceeds in a coordinated manner so that the integrity of the overall conceptual framework is retained
  • Provide an opportunity for several people to consider a matter at a measured pace so as to give the best chance of getting the most effective solution
  • Document what was done
  • Document existing and proposed LIFEfit functions, thus creating seed points for future documentation efforts

b. Initiate DTS

i. Who:

  • Project Manager (or person as nominated by PM who knows most about the issue)

ii. When:

  • For development that is estimated at more than three days, but not usually for software corrections (no more than one DTS per DBS)
  • After confirming work is to go ahead and before any development on the matter is started

iii. How:

  • Demonstrate existing functionality to the person responsible for the technical specification, the reviewer for that DTS, the project manager if different, and the person who will be doing the work if already selected
  • Describe to this group the new functionality in terms of changes required
  • Confirm with them that a DTS is required

c. Complete the initial analysis

i. Who:

  • Person responsible for the technical specification (a developer, not a business analyst)

ii. When:

  • As soon as possible after the walkthrough is completed

iii. How:

  • Assess how the work is to be done; keeping it brief – i.e., for complicated work, spending no more than 2 hours; and if desired, note this under Initial Analysis in the DTS
  • Describe the proposal to a reviewer and the project manager, and to the person who will be doing the work if already selected
  • On approval, note the group’s various initials and the date on the DTS
  • If there are problems, revise and check with the reviewer and project manager again, etc.

d. Complete the remainder of the DTS

i. Who:

  • Person writing the DTS

ii. When:

  • After the initial analysis is agreed Within two days of the walkthrough, though usually this takes less time

e. Coordinate sign off of the DTS

i. Who:

  • Person writing the DTS

ii. When:

  • As soon as possible after the DTS is complete

iii. How:

  • Secure approval from the reviewer, the person who provided the walkthrough, and the project manager (if different) and note their initials and the date on the DTS
  • Provide the DTS to the person who will be doing the work
  • NB: The work must be implemented as specified in the latest version of the DTS.
  • If the person doing the work discovers that the DTS is not clear or feels it is incorrect, that person must go back to the DTS author, and they must clarify it together.  Once this is done the DTS author secures approval of the revised DTS from the reviewer and the project manager and notes version and review details as before, and then work can proceed.
  • If difficulties arise the author or the reviewer can refer the matter to an account executive for resolution.  The author or the reviewer can also refer the DTS to the Delivery Manager for problems with style, format, or clarity.  An unacceptable outcome is to implement the work in a manner not specified in the DTS.
  • This process will be explained in more detail in the Work Instruction (forthcoming) for Development.

> Top <