Sei sulla pagina 1di 8

<Project Name> Technical Specification

Client Name (insert)


Project Title (insert)
Technical Specification
Version:
Author:
Date:

X.X
Ashley Friedlein
XX.XX.XX

This document provides a detailed description of the technical


design of the (insert Project Title)

Document Review and Sign off


I hereby agree to having read and fully understood the contents and implications of the
attached document.
For & on behalf of:
Date:
(Insert client name)
For & on behalf of:
Date:
(Insert supplier name)

Econsultancy.com

Page 1 of 8

<Project Name> Technical Specification

1. Version Control
The following is a list all changes made to this document, the person making the change, the new
version number and the reason why the change was necessary.

Date

Author

Econsultancy.com

Version

Change Description

Page 2 of 8

<Project Name> Technical Specification

2. Distribution List
The following list contains the names and organisational details of the people to whom this
document has been distributed.

Name

Econsultancy.com

Organisation

Position

Page 3 of 8

<Project Name> Technical Specification

3. Terms and Abbreviations


3.1. Abbreviations
The following table contains a list of the terms and abbreviation specific to the project

Abbreviation

Definition

3.2. Reference Documents


This functional specification should be read in association with the following:

Document

Econsultancy.com

Purpose

Version

Date

Status

Author

Page 4 of 8

<Project Name> Technical Specification

3.3. Assumptions
List any assumptions that are specific to this technical specification document

Assumption 1
Assumption 2
Assumption 3

Econsultancy.com

Page 5 of 8

<Project Name> Technical Specification

4. Table of Contents
1.

VERSION CONTROL

2.

DISTRIBUTION LIST

3.

TERMS AND ABBREVIATIONS

3.1.

Abbreviations

3.2.

Reference Documents

3.3.

Assumptions

4.

TABLE OF CONTENTS

5.

INTRODUCTION

6.

SYSTEM SPECIFICATION

6.4.

System Architecture Diagram

6.5.

Hardware Specification and Server Configuration

6.6.

Other Platforms

6.7.

Software Specification

6.8.

System Interfaces or 3rd Party Products

6.9.

Security

6.10.

Development Standards & Compliance

6.11.

Configuration Management

6.12.

Backup & Recovery

7.

USER INTERFACE SPECIFICATION

7.13.

User Agent specification

7.14.

User Interface Design and Development

8.

TECHNICAL DESIGN

9.

INTEGRATION

10.

APPENDICES

Econsultancy.com

Page 6 of 8

<Project Name> Technical Specification

5. Introduction
Contains:
Description of the purpose of the document (i.e. to describe the underlying technology of the
application to be delivered to the client):
Setting the scope for the technical responsibilities of the individuals on the project
including any disclaimers with regard to the information or processes mentioned in the
document
This should contain a high level overview of the project's technical design, which will be
outlined in further detail in subsequent sections.

6. System Specification
Contains:
Detailed technical analysis of the proposed solution relating to the overall web site and any
server side components:

6.1. System Architecture Diagram


6.2. Hardware Specification and Server Configuration
(including the development, staging & live environments)

6.3. Other Platforms


(if applicable, WAP and iTV (set top configuration) should be documented in this section)

6.4. Software Specification


(including application languages, web server, operating system)

6.5. System Interfaces or 3rd Party Products


(including content management system, payment providers, XML links, data transfer
processes, COM objects, log analysis tools)

6.6. Security
(including data storage requirements, sensitivities particular to the project, commitment, or
non-commitment to, comply with the data protection legislation (country specific),
public/private key infrastructure, SSL certificates, version control and release procedures
details, directory structure standards)

6.7. Development Standards & Compliance


(including file types being used, file naming standards, content and application directory
structures and naming conventions to be used (for both client and server side together))

6.8. Configuration Management


(including the process to maintain version control of the software from the development,
staging and through to the production environment)

Econsultancy.com

Page 7 of 8

<Project Name> Technical Specification

6.9. Backup & Recovery

7. User Interface Specification


Contains:
Detailed technical analysis of the user interface relating back to the Functional Specification:
Validation
Identification of dynamic content
Style sheets
Application objects
Functions
Database objects
Template include files and frameset definitions
Screen grabs/access to assets, give examples
Screen resolutions/display properties
Page weights
Any other multimedia objects used

7.1. User Agent specification

including browsers (versions to be supported and the applications limitations) & operating
systems)

7.2. User Interface Design and Development

(including information on JavaScript and client side validation, server page integration & style
sheets)

8. Technical Design
Contains:
Details how the environment for the application will be produced:
Application Design and Development (including application layer coding, database
design and development (including entity-relationship diagram, entity definitions, stored
procedures (pseudo code)), class diagrams
Special Notes (details of any unusual requirements or aspects to the application
environment)

9. Integration
Contains:
A description of how the various technical service teams and third parties involved in the project
will work together co-ordinating their work and integrating it into the overall solution:
Third Party relationships

10. Appendices
Contains:

Technical RAID document (listing the Risks, Issues, Assumptions and Dependencies
that are being made when scoping the technical elements of the project)

Econsultancy.com

Page 8 of 8

Potrebbero piacerti anche