Technical Specifications

Description

• 
  The identification of the specific technologies or class of technologies that will be used to implement the complete IT solution for the redesigned system in the organisation.  These specifications should identify technology standards and protocols for all pertinent IT components:
• Hardware (servers, workstations, personal computers, etc.)
• Network/communications (cabling, hubs/routers, network operating system, e-mail, etc.)
• Software (operating system, database, development tools, etc.).

Business Value

• The identification of technical specifications is a critical step in assuring the smooth integration in the organisation of the various technological components of the IT solution.
• If technology specifications are not identified at an early stage of the implementation, the interoperability of the IT system components can be put into question.  Furthermore, additional development work during future phases will be required, if formal technology specifications are not identified and adopted.

Approach

The technical specifications will continue from the work accomplished from the “To-Be” Technology Architecture, when high level technology requirements were identified for the solution.  For example, within the earlier deliverable cabling may be identified as needed for a wide area network.  Within this deliverable the precise type of cabling would be identified for use as a standard across the entire organisation.

1. Identify and understand technical configuration options for each IT component.
2. Determine interdependencies required among different IT component.
3. Develop draft technology standards for all components
1. These technology standards do not typically mandate a specific product or even specific vendors, but rather the technologies defined by a widely-recognised industry standard (e.g. Windows  or Intel workstations;  or Unix servers).  The primary values guiding these standards include  conformance to relevant technical and industry standards, scalability concerns, and vendor independence issues.
2. Although it is generally not necessary to select specific products or vendors at this stage, in some cases the selection of a given technology implies the selection of a vendor.  For example, Microsoft’s Windows NT operating system is both a technology and a product.  However, it is possible to specify a “Windows NT server” as a class of hardware products with selecting a particular vendor or model.
4. Review draft standards with appropriate client personnel.
5. Finalise and document standards.

Guidelines

Tactics/Helpful Hints

• Ensure that specifications are determined from substantiated data rather than by assumptions from project team and client IT staff.  The process of defining technical specifications will usually include some amount of research to confirm vendor claims about interoperability and other aspects of product performance.  It is important to utilize the reports of industry analysts (such as the Gartner Group) to obtain this type of information.
• If existing policies or contracts mandate the use of specific products, clearly identify and incorporate those products as part of the development of the draft standard.

Resources/Timing

• Consider bringing in specialised resources to provide the knowledge of typical standards for all IT components and the experience in analysis of interoperability between various components of IT solutions.