[模板]需求管理檢查列表

1、SRS檢查列表Version 0.1項(xiàng)目名稱:會議日期:工作制品:主持人:版本:內(nèi)部 / UAT / 最終記錄人:完全性Completeness (CP)1. Are required attributes, assumptions, and constraints of the program set completely listed?是否列出了程序所要求的特征，假設(shè)前提以及約束條件？2. Have all requirements and constraints been assigned a priority?是否對所有的需求及約束條件賦予了相應(yīng)的優(yōu)先級3. Have the crit

2、eria for assigning requirement priority levels been defined?是否定義了對需求優(yōu)先級賦值的標(biāo)準(zhǔn)4. Have the requirements been stated for each delivery or staged implementation?是否對每一個(gè)交付或是階段性實(shí)施的需求進(jìn)行了描述5. Have requirements for installation (packaging, site preparation, operator training) been specified?是否對安裝需求（打包、網(wǎng)站設(shè)置、操作員

3、培訓(xùn)）進(jìn)行了描述6. Have the target language, development environment, and run-time environment been chosen?是否選擇了目標(biāo)語言，開發(fā)環(huán)境和運(yùn)行環(huán)境一致性Consistency (CS)7. Are the requirements consistent with each other?各個(gè)需求是否保持一致8. Are the requirements consistent with the requirements in related documents?相關(guān)文檔之間的需求是否一致9. Are the

4、requirements consistent with the actual operating environment (e.g., check hardware timing, precision, event sequencing, data rates, bandwidth)?需求是否與實(shí)際的操作環(huán)境一致（例如：檢查硬件延時(shí)、精確度、事件序列、數(shù)據(jù)率、帶寬）10. Do the requirements stay within the capability of the requirements allocated by higher level documentation? 需求是

5、否與從上一級文檔分派出來的需求容量一致數(shù)據(jù)使用Data Usage (DA)11. Have the data type, rate, units, accuracy, resolution, limits, range, and critical values for all internal data items been specified?是否指明了所有內(nèi)部數(shù)據(jù)項(xiàng)的類型、比率、單位、精確度、分辨率、限制、范圍以及關(guān)鍵值12. Have the data objects and their component parts been specified?是否指明了所有的數(shù)據(jù)對象以及它們的組

6、成部分13. Has the mapping between local views of data and global data been shown?是否指明了本地?cái)?shù)據(jù)和全局?jǐn)?shù)據(jù)的意義對應(yīng)關(guān)系14. Has the management of stored and shared data been provided?是否提供了存儲和共享數(shù)據(jù)的管理方式15. Has a list of functions that set and/or use stored and shared data been provided?是否提供了對存儲及共享數(shù)據(jù)的賦值和使用功能的相關(guān)列表16. Are th

7、ere any special integrity requirements on the stored data?是否對存儲的數(shù)據(jù)有特殊的完整性要求17. Have the types and frequency of occurrence of operations on stored data (e.g., retrieve, store, modify, delete) been specified?是否指明了對存儲數(shù)據(jù)的操作類型（獲取、存儲、修改、刪除）及發(fā)生頻率18. Have the modes of access (e.g., random, sequential) for t

8、he shared data been specified?是否指明了對共享數(shù)據(jù)的訪問方式（例如：隨機(jī)訪問，順序訪問）文檔/清晰Documentation/ Clarity (DC)19. Are the goals of the subsystem defined?是否定義了子系統(tǒng)的目標(biāo)20. Is the terminology consistent with the users and /clients terminology?所用術(shù)語是否與使用者/客戶的術(shù)語一致21. Are the requirements clear and unambiguous?需求是否清晰不存在二義性22.

9、Is a functional overview of the program set provided?是否提供了程序集的功能概述23. Is an overview of the operational modes, states, and concept described?是否提供了運(yùn)作模式、狀態(tài)和概念的概述24. Have the software environment (co-resident program sets) and hardware environment (specific configuration(s) been specified?是否指明了軟件環(huán)境（常駐程

10、序集）和硬件環(huán)境（特定配置）25. If assumptions that affect implementation have been made, are they stated?是否存在影響系統(tǒng)實(shí)現(xiàn)的假設(shè)情況？是否對這些假設(shè)情況進(jìn)行了描述26. Have the requirements been stated in terms of inputs, outputs, and processing for each function?需求是否指明了對每個(gè)功能都以輸入、處理、輸出的方式進(jìn)行處理功能性Functionality (FN)27. Are all described functi

11、ons necessary and sufficient to meet the clients/system objectives?是否所有描述的功能是必需且能足夠滿足的客戶或是系統(tǒng)目標(biāo)28. Are all inputs to a function necessary and sufficient to perform the required operation?是否為 實(shí)現(xiàn)了某個(gè)必要操作的功能 提供了必需且足夠的條件29. Does each function clearly describe how outputs (and shared data) are generated fr

12、om inputs (and shared data)?是否每個(gè)功能都清晰地描述了怎樣從輸入數(shù)據(jù)（共享數(shù)據(jù)）得到輸出數(shù)據(jù)（共享數(shù)據(jù)）30. Are all function states defined?是否對所有的功能狀態(tài)進(jìn)行了定義界面接口Interface (IF)31. Are all external and internal interfaces sufficient and necessary?是否定義了充分且必要的內(nèi)部和外部接口32. Are all of the outputs produced by a function used by another function or

13、 transferred across an external interface?是否所有的功能產(chǎn)生的輸出結(jié)果都被其他功能使用，或是通過外部接口被傳遞到系統(tǒng)外部33. Are the interface requirements between hardware, software, personnel and procedures included?是否包含了硬件、軟件、人和程序之間的接口需求34. Have the contents, formats, and constraints of all the displays been adequately documented and d

14、escribed?是否對所有顯示所要求的內(nèi)容、格式和約束限制進(jìn)行了充分的記錄和描述35. Are all of the data elements adequately described?是否對所有的數(shù)據(jù)元素進(jìn)行了充分的描述36. Has the data flow between internal software functions been represented?是否提供了所用軟件內(nèi)部功能之間的數(shù)據(jù)流程圖37. Are all data elements crossing program set boundaries identified?是否對所有的跨程序集（模塊）的數(shù)據(jù)元素進(jìn)行了

15、定義詳細(xì)的級別Level of Detail (LD)38. Are the software requirements free of unwarranted design detail?軟件需求是否已經(jīng)不含有不需要的設(shè)計(jì)細(xì)節(jié)39. Have all “To Be Determines” (TBDs) been resolved?是否解決了所有的未確定項(xiàng)40. Have the interfaces been described to enough detail for design work to begin?對所要求的接口是否進(jìn)行了足夠詳細(xì)的描述，可以開始設(shè)計(jì)工作41. Have the

16、 functional requirements been described in enough detail for design work to begin?對功能需求是否進(jìn)行了足夠詳細(xì)的描述以便可以開始設(shè)計(jì)工作？42. Have the performance requirements been described to enough detail for design work to begin?對性能需求是否進(jìn)行了足夠詳細(xì)的描述可以，開始設(shè)計(jì)工作？43. Have the accuracy, precision, range, type, rate, units, frequenc

17、y and volume of inputs and outputs been specified for each function?是否對每個(gè)功能的輸入輸出項(xiàng)的準(zhǔn)確度、精確度、范圍、類型、比率、單位、使用頻率和使用量進(jìn)行了聲明可維護(hù)性Maintainability (MN)44. Are the requirements weakly coupled (i.e., changing a function will not have adverse and unexpected effects throughout the subsystem)？需求之間的關(guān)系是否是弱耦合的？（例如：改變一個(gè)

18、功能不會在子系統(tǒng)中出現(xiàn)不利或是不可預(yù)見的影響）45. Will the requirements minimize the complexity of the design?需求是否能夠做到最小化設(shè)計(jì)的復(fù)雜性46. Have the documented maintainability requirements been levied to functions?被記錄在文檔中的可維護(hù)性需求是否被分派到功能級別？47. Are reusable parts of other designs being considered? Has their effects on design and int

19、egration been stated?是否考慮到了其他設(shè)計(jì)的可重用部分？是否對可重用部分對設(shè)計(jì)和集成上的影響進(jìn)行了描述？48. Are the documented portability requirements been levied to functions被記錄在文檔中可移植性需求是否被分派到功能級別？49. Has the use of inherited design or code or pre-selected tools been specified?是否對使用繼承的設(shè)計(jì)和代碼以及預(yù)先選擇的工具進(jìn)行了說明(d)項(xiàng)強(qiáng)調(diào)的是現(xiàn)成的組件）)性能Performance (PF)5

20、0. Have all documented performance requirements been allocated to functions?被記錄在文檔中的性能需求是否被分派到功能級別？51. Have the resource and performance margin requirements been stated along with the means for managing them?是否對資源和性能邊界需求以及管理它們的方式進(jìn)行了描述可靠性Reliability (RL)52. Have quality factors been specified as meas

21、urable requirements and prioritized design goals?可靠性這一質(zhì)量要素是否被描述成可測量需求并且作為已設(shè)定優(yōu)先級的設(shè)計(jì)目標(biāo)53. Have documented reliability requirements been levied to functions?被文檔化的可靠性需求是否被分派到功能級別？54. Have documented availability requirements been levied to functions?被文檔化的可用性需求是否被分派到功能級別？55. Have documented security/safe

22、ty requirements been levied to functions?被文檔化的安全性/保密性需求是否被分派到功能級別？56. Are undesired events considered and their required responses specified?是否考慮到了可能的意外事件以及對他們的處理方式進(jìn)行了說明57. Are initial or special states considered (e.g., cold starts, abnormal termination, etc.)?是否考慮到了初始或者特殊狀態(tài)（冷啟動(dòng)、異常中斷）58. Have assum

23、ptions about intended sequences of functions been stated? Are these sequences required?是否對系統(tǒng)功能按預(yù)期順序執(zhí)行的假設(shè)進(jìn)行了描述？是否這些順序是必需的？59. Is error checking and recovery required?錯(cuò)誤檢查和恢復(fù)是否是必需的？標(biāo)準(zhǔn)Standards (ST)60. Does this document follow the projects documentation standards?文檔是否遵循了項(xiàng)目文檔標(biāo)準(zhǔn)？易測性Testability (TL)61. C

24、an the program set be tested, demonstrated, analyzed, or inspected to show that it satisfies requirements?程序能否通過測試、論證、分析和檢查以表明滿足需求62. Are individual requirements stated so that they are discrete, unambiguous, and testable?每個(gè)需求是否都已被單獨(dú)的申明以保證他們是離散，無二義性，具有可測試性63. Have the overall program set acceptance

25、criteria been established?是否制定了整個(gè)程序的驗(yàn)收標(biāo)準(zhǔn)64. Have clear pass/fail acceptance criteria been established?是否制定了明確的通過或者不通過驗(yàn)收的標(biāo)準(zhǔn)65. Have the test methods (test, demonstration, analysis, or inspection) been stated for each requirement?是否描述了每個(gè)需求的測試方法（測試、論證、分析或檢查）可追蹤性Traceability (TR)66. Are all functions, structures, and constraints traced to requirements, and vice versa