What analogues of technical specifications are there in the West?

Question

Preparation of terms of reference

Who knows what documents over the hill correspond to our TK (task) and TP (project)? Has anyone seen examples?
This refers to the system, software package, device.

Answer 1

1. User (organization) requirements according to GOST 34 ±= Stakeholder Requirements Specification (StRS) according to IEEE 29148-2011, can also be informally called Customer Requirements (Specification) (BRS), Business Requirements (Specification) (BRS).
2. TK for speakers according to GOST 34 ±= System Requirements Specification (SyRS) according to IEEE 29148-2011, can also be informally called Functional (Requirements) Specification. But the word functional implies that these are pure functional requirements, without restrictions and quality attributes (which is sometimes bad).
3. Specification for software according to GOST 19.201-78 ±= Software Requirements Specification (SRS) according to IEEE 830-1998 and IEEE 29148-2011, can also be informally called Functional (Requirements) Specification (FRS), Technical Requirements.
4. The set of documents of the Technical Project according to GOST 34 / RD 50 does not fully comply, but there is:
- Architecture Description document according to ISO IEC IEEE 42010-2011
- Software Architecture Document (SAD) in RUP
- Informal document High Level Design (HLD)
- Informal document (Software) Design Specification
- There is some international standard for describing data structures, such as Database Design Document
I can also tell you about analogues of concepts, marketing requirements and product requirements :)

Answer 2

most often write
specs