Technical Requirements Document

A Technical Requirements Document is a requirements document that contains technical requirements.

• Context:
  • It can be the output of a Technical Requirements Analysis Task.
• Example(s):
  • …
• Counter-Example(s):
  • Product Requirements Document (for a product requirements analysis).
  • Market Requirements Document (for a market requirements analysis).
  • Functional Specifications Document.
  • SWOT Analysis Document (for a SWOT analysis).
  • Product Roadmap.
• See: Product Management, Requirements Analysis, Corporate Stakeholder, System Requirements, Usage Analysis, Use Case.

---

---

References

2011

• https://docs.oracle.com/cd/E19199-01/817-5759/scenario_techreqs.html
  • QUOTE: This chapter discusses some of the processes and procedures that occur during technical requirements analysis.

     Technical requirements analysis begins with the business requirements documents created during the business analysis phase. Using the business requirements as a basis, you perform the following steps:

    • Perform a usage analysis to aid in determining expected load on the deployment
    • Create a set of use cases that model typical user interaction with the deployment
    • Create a set of system requirements that are derived from the business requirements, use cases, and usage analysis.
  • The use cases are also the basis for designing the logical architecture in the design phase. The logical architecture and the system requirements together form the deployment scenario, which later is an input to the deployment design phase.
  • The following figure shows the technical requirements phase in relation to the business analysis, logical design, and deployment design phases.

---