{"id":779,"date":"2023-01-12T19:06:35","date_gmt":"2023-01-12T19:06:35","guid":{"rendered":"https:\/\/webresources-uat.com\/nchrp1918\/?page_id=779"},"modified":"2023-01-12T19:06:35","modified_gmt":"2023-01-12T19:06:35","slug":"38-technical-specification-documents","status":"publish","type":"page","link":"https:\/\/crp.trb.org\/nchrpwebresource2\/setup\/38-technical-specification-documents\/","title":{"rendered":"(38) Technical Specification Documents"},"content":{"rendered":"\n
\n
\n
\n
RESEARCH AND PLANNING<\/a>  |   SETUP<\/a><\/span>  |   ONGOING OPERATIONS<\/a>  | TRANSITIONING AND GROWING<\/a><\/div><\/div> \n
\n

Technical Specification Documents (38)<\/h1>\n

Description:<\/strong><\/h3> \n

\n \n \n<\/p>

This building block details specification about exactly how the technical system will operate. The system design documents\u2014which include the system requirement specifications, interface control document, and business rules (see System Design Documents<\/a><\/i><\/b> building block)\u2014should specify exactly how the system should work. Designing the technical system includes creating software specifications. It also may include developing hardware (i.e., circuit board) specifications. A technology vendor typically completes this building block. If separate RUC systems are needed for commercial and noncommercial vehicles, the specifications should be as consistent as possible between the two systems. \n <\/p>\n

\n \n
\n

Details:<\/strong><\/h3>\n

Based on the system design documents, use software and hardware engineering practices to develop detailed specifications documents that show exactly how the system works. Anything that is not described in the higher-level specification documents\u2014which include system design specifications, interface control document, business rules, and user-experience guidelines, if any\u2014is up for the engineer (vendor) to decide. If those requirements seem ambiguous, incomplete, or contradictory, then the vendor should ask the state for guidance, instead of simply deciding. State and vendor systems specifications will likely be different. \n <\/p>\n <\/div>\n

\n
\n

Primary Use:<\/strong><\/h3>\n

Specify the exact system to be built, including software and hardware details. \n <\/p>\n <\/div>\n \n

\n \n
\n

Best Practices\/Lessons Learned:<\/strong><\/h3>\n