General Guidelines [1] This technical requirement document (TRD) describes the technical aspects that TG3d standard must fulfill, such as performance-related issues, reliability issues and availability issues. These types of requirements are often called quality of service (QoS) requirements; other requirements are usually maintenance-level requirements or external constraints, sometimes called compliance. Technical requirements are summarized as any other specifications; they have a name and a unique identifier. Technical requirements are documented in the same manner as any specifications, including a description, an example, a source or references to related technical requirements and a revision history. TG3d to effectively define and manage requirements to ensure they are meeting needs of the applications, while proving compliance. Ideally, requirements are: Correct (technically and legally possible) • Complete (express a whole idea or statement) • Clear (unambiguous and not confusing) • Consistent (not in conflict with other requirements) • Verifiable (it can be determined that the system meets the requirement) • Traceable (uniquely identified and trackable) • Feasible (can be accomplished within cost and schedule) • Modular (can be changed without excessive impact) • Design-independent (does not pose a specific solution on design) •
General Guidelines [1] This technical requirement document (TRD) describes the technical aspects that TG3d standard must fulfill, such as performance-related issues, reliability issues and availability issues. These types of requirements are often called quality of service (QoS) requirements; other requirements are usually maintenance-level requirements or external constraints, sometimes called compliance. Technical requirements are summarized as any other specifications; they have a name and a unique identifier. Technical requirements are documented in the same manner as any specifications, including a description, an example, a source or references to related technical requirements and a revision history. TG3d to effectively define and manage requirements to ensure they are meeting needs of the applications, while proving compliance. Ideally, requirements are: • Correct (technically and legally possible) • Complete (express a whole idea or statement) • Clear (unambiguous and not confusing) • Consistent (not in conflict with other requirements) • Verifiable (it can be determined that the system meets the requirement) • Traceable (uniquely identified and trackable) • Feasible (can be accomplished within cost and schedule) • Modular (can be changed without excessive impact) • Design-independent (does not pose a specific solution on design)
15-14-0309-02-003d-technical-requirements-document.docx