0% found this document useful (0 votes)
633 views2 pages

Technical Requirements Document Template

The document provides a template for outlining a project's technical requirements. It includes sections for hardware, software, functional and reporting technical requirements sourced from a business requirements document. Each technical requirement lists an ID number, the corresponding functional requirement ID from the business requirements document, and descriptions of how functional requirements will be implemented technically. Additional sections provide for security requirements, technical process flows, and addendums.

Uploaded by

judy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
633 views2 pages

Technical Requirements Document Template

The document provides a template for outlining a project's technical requirements. It includes sections for hardware, software, functional and reporting technical requirements sourced from a business requirements document. Each technical requirement lists an ID number, the corresponding functional requirement ID from the business requirements document, and descriptions of how functional requirements will be implemented technically. Additional sections provide for security requirements, technical process flows, and addendums.

Uploaded by

judy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Technical Requirements Template

Project Name:
Project Sponsor:
Service Owner:
Project Manager:
Document Date:

1. Hardware Requirements (If applicable)


ID Requirements
1.1 Hardware Requirement List the hardware requirements, if any. Example: 256 MB Ram

2. Software Requirements (If applicable)


ID Requirements
2.1 Software Requirement List the software requirements, if any. Example: Operating system: Windows 7

3. Technical Requirements
Technical requirements are giving information to the developers as to what the system must adhere to. These are guidelines that
can have implications over on the developer’s way of developing a code. For a successful development process identification of the
correlation between the functional requirements and corresponding technical requirements/constraints is essential. Best practice to
write technical requirements is to address each and every functional requirement mentioned in the business requirements document
(BRD). Use one table for each requirement identified from the BRD.
3.1. Functional Requirements
Functional Technical Req Technical Requirements
Req ID # ID #
(From
BRD)
3.1.1 Technical Requirement How is the functional requirement
implemented technically?
Example:
For a Registration/Login page,
 Required fields: first name, last name, phone number, email address, user
name, password
 Optional fields: company name, title, address1, address2, city, state, zip
code, country, fax number

3.2. Reporting Requirements (If applicable)


Reporting Technical Req Technical Requirements
Req ID # ID #
(From
BRD)
3.2.1 Reporting Requirement List the reporting requirements, if any.
Example: Select X, Y, Z from XXX table between date=YYY and date=ZZZ
Technical Requirements Template
Project Name:
Project Sponsor:
Service Owner:
Project Manager:
Document Date:

3.3. Security Requirements (If applicable)


Security Technical Req Requirements
Req ID # ID #
(From
BRD)
3.3.1 Security Requirement List the security requirements, if any. Example:
Use XXX algorithm for encryption.

4 Technical Process Flow


Insert process flows, if any.

5. Addendums & Appendices


Include any additional documents/ information.

You might also like