[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-detail-166083-en":3,"doc-seo-166083-105":30,"detail-sidebar-cat-1-en-105":96},{"code":4,"msg":5,"data":6},0,"success",{"doc_id":7,"user_id":8,"nickname":9,"user_avatar":10,"doc_module":11,"category_id":12,"category_name":13,"doc_title":14,"doc_description":15,"doc_content":16,"file_id":17,"file_url":18,"file_type":19,"file_size":20,"view_count":11,"is_deleted":4,"is_public":11,"is_downloadable":11,"audit_status":11,"page_count":21,"language":22,"language_code":23,"site_id":24,"html_lang":23,"table_of_contents":25,"faqs":26,"seo_title":27,"seo_description":15,"update_tm":28,"read_time":29},166083,1374402524268,"Berry Peter","https://ap-avatar.wpscdn.com/davatar_3d24733baf745e90a7e4bdd5f77d97b2",1,11,"Presentations","Space Shuttle Upgrades Project Program Requirements Document (PRD) - Template","Template and guidance for producing a Space Shuttle Program Requirements Document (PRD) to be baselined by the Space Shuttle Program Requirement Control Board. The PRD defines program level requirements, objectives, and goals that direct subsequent life-cycle phases, and it is referenced throughout development to confirm that requirements and design align with program office intent. In addition, it captures top-level operational concepts and upgrade project interfaces, while clarifying scope, verifiability, traceability, rationale, and referencing requirements from NSTS program level documents.","Space Shuttle Upgrades Project\u000bProgram Requirements Document (PRD) \u000bTemplate\nThis document provides a template and guidance for generating a Program Requirements Document (PRD) to be baselined by the Space Shuttle Program Requirement Control Board.  The need to produce a PRD, to be controlled by the Manager of the Space Shuttle Program, is established in NSTS 37400, Space Shuttle Upgrades Program Management Plan.  The PRD is essential to upgrade development activities because it establishes key requirements, objectives and goals that drive all subsequent life-cycle phases.  It is continually referenced during the development phase to ensure that requirements and design meet the program office intent.  In addition to the key program level requirements, the PRD also captures top-level operational concepts and program level interfaces of the upgrade project.\nThe following are some reminders as you create your document.\nA quality requirement document will contain certain key characteristics. Each requirement will be verifiable and traceable.  Each requirement will be properly written in terms of format, form, terms, and grammar.  Each requirement will be accompanied by rationale that provides the reason for the requirement and any assumptions that were made at the time the requirement was written and approved.  This information will provide essential data for development, verification, maintenance, and future upgrades.\nOnly program level requirements to the upgrade project are to be included in this document.  Further expansion of these requirements and derivation of requirements from NSTS-07700 will be included in the project’s System Requirements Document (SRD).  The PRD requirements are those controlled by the PRCB.  Key program requirements already documented in NSTS 07700 may be referenced in the PRD and shall contain the exact paragraph number being referenced.\nEXAMPLE:\u000bNSTS 07700\tProgram Definition and Requirements\u000b(Current Issue)\tRef. Preface, Para. 3.2.1\nReferences to specific requirements in STS-07700 and other program level documents, must site the specific paragraph(s) that are being referenced, not the entire document(s).\n\u000fInstructions for using the PRD template:\nWhen you open this template document, it will be read-only.  The following steps will result in a write-enabled version for you to use for your specific project.\nDelete the top pages of this document that contain instructions and the revision record for the template itself.  There is a heavy line and a statement “Delete all text above this line” marking the position where the reference information for this document ends and the PRD template begins.\nChange the title to reflect the upgrade project name and date.  In the footer of each section, change the date before distributing the document for review.\nDo a “Save As” under the File menu, specifying the directory you want to store your project PRD.\nBegin modifications to the saved version of the PRD template.  You will need to take other steps, listed here, to make the document conform to your project and to remove unneeded information and instructions from the template.\nThis template is designed as a skeleton document to be completed by each project.  It includes imbedded instructions and examples.\nTo view the instructions embedded in this document, specific view and print options must be selected.  Under Tools/Options/View, “Screen Tips” must be checked but “Field Codes” and “Hidden Text” should not be checked.\nInstructions on section content are provided as MSWord comments that display on-screen when the cursor is positioned over words highlighted in yellow.\nTo print only the comments in the document, select the File/Print menu, and highlight “Comments” from the “Print What” pull-down menu.  After the comments are printed, the “Print What” option will automatically default to printing the entire document.\nTo print the location of comments within document text, select the Tools/Options/Print menu, and check t","cbCaivoWhwuBf9Zo","https://ap.wps.com/l/cbCaivoWhwuBf9Zo","doc",192000,27,"English","en",105,"# Instructions for using the PRD template\n## Quality requirement characteristics\n## Scope and referencing rules\n## Creating a writable project version\n## Using Word comments and embedded instructions\n## Acronyms and placeholders","[{\"question\":\"What is the purpose of the Space Shuttle PRD template?\",\"answer\":\"It provides a template and guidance for generating a PRD to be baselined by the Space Shuttle Program Requirement Control Board, ensuring upgrade program requirements are documented and controlled.\"},{\"question\":\"What requirements must each PRD entry satisfy?\",\"answer\":\"Each requirement should be verifiable and traceable, be properly written in clear format and grammar, and include rationale covering the reason and any assumptions made at approval time.\"},{\"question\":\"What scope should be included in this PRD document?\",\"answer\":\"Only program level requirements for the upgrade project should be included; expansions and derivations from NSTS-07700 are handled in the project’s System Requirements Document (SRD).\"},{\"question\":\"How should references to NSTS 07700 be handled in the PRD?\",\"answer\":\"References must cite the specific paragraph(s) being referenced, including exact paragraph numbers, rather than referencing entire documents.\"}]","Space Shuttle Upgrades Project Program Requirements Document (PRD) - Template | DOC",1788182844,9,{"code":4,"msg":31,"data":32},"ok",{"site_id":24,"language":23,"slug":33,"title":14,"keywords":34,"description":15,"schema_data":35,"social_meta":91,"head_meta":93,"extra_data":95,"updated_unix":28},"space-shuttle-upgrades-project-program-requirements-document-prd-template","",{"@graph":36,"@context":90},[37,54,69],{"@type":38,"itemListElement":39},"BreadcrumbList",[40,44,48,51],{"item":41,"name":42,"@type":43,"position":11},"https://docshare.wps.com","Home","ListItem",{"item":45,"name":46,"@type":43,"position":47},"https://docshare.wps.com/template/","Template",2,{"item":49,"name":13,"@type":43,"position":50},"https://docshare.wps.com/template/presentations/",3,{"item":52,"name":14,"@type":43,"position":53},"https://docshare.wps.com/template/space-shuttle-upgrades-project-program-requirements-document-prd-template/166083/",4,{"url":52,"name":14,"@type":55,"author":56,"headline":14,"publisher":58,"fileFormat":61,"inLanguage":23,"description":15,"dateModified":62,"datePublished":63,"encodingFormat":61,"isAccessibleForFree":64,"interactionStatistic":65},"DigitalDocument",{"name":9,"@type":57},"Person",{"url":41,"name":59,"@type":60},"DocShare","Organization","application/octet-stream","2026-09-05","2026-08-31",true,{"@type":66,"interactionType":67,"userInteractionCount":53},"InteractionCounter",{"@type":68},"ViewAction",{"@type":70,"mainEntity":71},"FAQPage",[72,78,82,86],{"name":73,"@type":74,"acceptedAnswer":75},"What is the purpose of the Space Shuttle PRD template?","Question",{"text":76,"@type":77},"It provides a template and guidance for generating a PRD to be baselined by the Space Shuttle Program Requirement Control Board, ensuring upgrade program requirements are documented and controlled.","Answer",{"name":79,"@type":74,"acceptedAnswer":80},"What requirements must each PRD entry satisfy?",{"text":81,"@type":77},"Each requirement should be verifiable and traceable, be properly written in clear format and grammar, and include rationale covering the reason and any assumptions made at approval time.",{"name":83,"@type":74,"acceptedAnswer":84},"What scope should be included in this PRD document?",{"text":85,"@type":77},"Only program level requirements for the upgrade project should be included; expansions and derivations from NSTS-07700 are handled in the project’s System Requirements Document (SRD).",{"name":87,"@type":74,"acceptedAnswer":88},"How should references to NSTS 07700 be handled in the PRD?",{"text":89,"@type":77},"References must cite the specific paragraph(s) being referenced, including exact paragraph numbers, rather than referencing entire documents.","https://schema.org",{"og:url":52,"og:type":92,"og:title":14,"og:site_name":59,"og:description":15},"article",{"robots":94,"canonical":52},"index,follow",{"doc_id":7,"site_id":24},{"code":4,"msg":5,"data":97},[98,101,106,111,116,121,126,131,136],{"id":12,"doc_module":11,"doc_module_name":46,"category_name":13,"show_sort_weight":99,"slug":100},90,"presentations",{"id":102,"doc_module":11,"doc_module_name":46,"category_name":103,"show_sort_weight":104,"slug":105},12,"Resumes",80,"resumes",{"id":107,"doc_module":11,"doc_module_name":46,"category_name":108,"show_sort_weight":109,"slug":110},14,"Invoices",70,"invoices",{"id":112,"doc_module":11,"doc_module_name":46,"category_name":113,"show_sort_weight":114,"slug":115},15,"Posters",60,"posters",{"id":117,"doc_module":11,"doc_module_name":46,"category_name":118,"show_sort_weight":119,"slug":120},16,"Social Media",50,"social-media",{"id":122,"doc_module":11,"doc_module_name":46,"category_name":123,"show_sort_weight":124,"slug":125},17,"Forms",40,"forms",{"id":127,"doc_module":11,"doc_module_name":46,"category_name":128,"show_sort_weight":129,"slug":130},18,"Letters",30,"letters",{"id":132,"doc_module":11,"doc_module_name":46,"category_name":133,"show_sort_weight":134,"slug":135},21,"Paper Templates",5,"papers-templates",{"id":137,"doc_module":11,"doc_module_name":46,"category_name":138,"show_sort_weight":4,"slug":139},158,"General","general-158"]