H2: SOFTWARE TECHNICAL SPECIFICATION TEMPLATE

YOUR LOGO

PROJECT NAME

AUTHOR

DATE

Version 0.0.0

REVISION HISTORY
DATE	VERSION	DESCRIPTION	AUTHOR

Table of Contents

INTRODUCTION	3

PURPOSE	3

INTENDED AUDIENCE AND PERTINENT SECTIONS	3

PROJECT SCOPE	3

DOCUMENT CONVENTIONS	3

REFERENCES	3

DESCRIPTION	3

PRODUCT PERSPECTIVE	3

FEATURES	3

USER OVERVIEW	3

OPERATING ENVIRONMENT	3

CONTRAINTS: IMPLEMENTATION / DESIGN	3

DOCUMENTATION	3

ASSUMPTIONS / DEPENDENCIES	3

SYSTEM FEATURES	3

SYSTEM FEATURE 1	3

SYSTEM FEATURE 2	3

SYSTEM FEATURE 3	3

REQUIREMENTS OF EXTERNAL INTERFACE	3

USER INTERFACES	3

HARDWARE INTERFACES	3

SOFTWARE INTERFACES	3

COMMUNICATION INTERFACES	3

ADDITIONAL NONFUNCTIONAL REQUIREMENTS	3

PERFORMANCE	3

SAFETY	3

SECURITY	3

SOFTWARE QUALITY	3

APPENDICES	3

APPENDIX A: GLOSSARY OF TERMS	3

APPENDIX B: ANALYSIS DOCUMENTATION	3

APPENDIX C: ISSUES	3

INTRODUCTION

PURPOSE

Identify and describe scope of product whose technical specifications are being documented, and describe desired outcome.

INTENDED AUDIENCE AND PERTINENT SECTIONS

Describe each type of reader, including developers, users, testers, writers, marketing, etc., and outline which portions of document are crucial to their department.

PROJECT SCOPE

Describe relevant benefits, objectives, and goals and how they relate to corporate goals and strategies.

DOCUMENT CONVENTIONS

Describe any naming or structural conventions employed throughout document and how they benefit reader.

REFERENCES

List any referenced document names or links.

DESCRIPTION

PRODUCT PERSPECTIVE

Provide context and origin of product, along with expected functionality.

FEATURES

List main features with brief description.

USER OVERVIEW

Define groups, and describe user characteristics.

OPERATING ENVIRONMENT

Illustrate where software will function: hardware platform, operating systems, and other software components or applications with which it must work in conjunction.

CONTRAINTS: IMPLEMENTATION / DESIGN

Describe limitations impacting development.

DOCUMENTATION

Describe content, mode of delivery, and standards.

ASSUMPTIONS / DEPENDENCIES

Detail all assumed factors (not known facts) that could potentially impact technical specifications set forth. Include external factors.

SYSTEM FEATURES

SYSTEM FEATURE 1

DESCRIPTION AND PRIORITY
STIMULUS / RESPONSE SEQUENCES
FUNCTIONAL REQUIREMENTS

SYSTEM FEATURE 2

DESCRIPTION AND PRIORITY
STIMULUS / RESPONSE SEQUENCES
FUNCTIONAL REQUIREMENTS

SYSTEM FEATURE 3

DESCRIPTION AND PRIORITY
STIMULUS / RESPONSE SEQUENCES
FUNCTIONAL REQUIREMENTS

REQUIREMENTS OF EXTERNAL INTERFACE

USER INTERFACES

Describe product / user interface characteristics, including standards, style guides, constraints, functionality, and sample screens if applicable.

HARDWARE INTERFACES

Describe product / hardware interface characteristics, nature of interactions, and communication protocols.

SOFTWARE INTERFACES

Describe product / other software interface characteristics, including component names and versions, databases, operating systems, libraries, tools, etc. Specify any constraints, along with nature of communications and what data is coming in and being disseminated.

COMMUNICATION INTERFACES

List requirements of communication functions: email, browsers, servers, forms, etc. Describe standards employed, security or encryption measures, data transfer rates, and synching.

ADDITIONAL NONFUNCTIONAL REQUIREMENTS

PERFORMANCE

Specify performance requirements. For additional clarity, provide rationale.

SAFETY

Specify safety requirements. Define safeguards and systems employed. Identify external policies and regulations impacting safety requirements.

SECURITY

Specify security requirements. Define safeguards and systems employed. Identify external policies and regulations impacting safety requirements.

SOFTWARE QUALITY

List other characteristics crucial to success of product. List each by describing its relation to product, being quantitative, specific, and verifiable.

APPENDICES

APPENDIX A: GLOSSARY OF TERMS

Define all terms and unique acronyms employed throughout document and specific to project.

APPENDIX B: ANALYSIS DOCUMENTATION

List file / document names / provided links to all diagrams, models, additional findings pertinent to technical specification development.

APPENDIX C: ISSUES

List all unresolved issues, TBDs, pending decisions, findings required, conflicts, etc.

ISSUES
ID	DESCRIPTION	PARTY RESPONSIBLE