原文地址:http://www.microtoolsinc.com/Howsrs.php
How to write a software requirements specification
如何編寫軟體需求規格書
by Robert Japenga
__________________________________________________________________________________________
What is the difference between a design requirement and software requirement?
設計需求和軟體需求有何區別?
In short, the SRS should not include any design requirements. However, this is a difficult discipline. For example, because of the partitioning and the particular RTOS you are using, and the particular hardware you are using, you may require
that no task use more than 1 ms of processing prior to releasing control back to the RTOS. Although that may be a true requirement and it involves software and should be tested, it is truly a design requirement and should be included in the Software Design
Document or in the Source code.
簡單來說,SRS不應該包含設計需求。然而,這個要求做起來比較難。例如,因為你使用了特殊的RTOS[譯者註:即時作業系統],使用了特殊的硬體,你可能需要每個任務的調度時間不超過1ms。儘管這是真正的需求,其包括軟體,並且應該被從測試,但這真的是一項設計需求,應該包含在軟體設計文檔中,或者在原始碼中。
Consider the target audience for each specification to identify what goes into what documents.
通過考慮每個規格書的閱讀對象來識別相應的文檔中應該有些什麼內容。
Marketing/Product Management
Creates a product specification and gives it to Systems. It should define everything Systems needs to specify the product
市場/產品管理
編寫產品規格書,給出系統。應該定義規範產品所需要的所有系統。
Systems
Creates a System Specification and gives it to Systems/Software and Mechanical and Electrical Design.
系統
建立系統規格書,給出系統/軟體和機械、電氣設計。
Systems/Software
Creates a Software Specification and gives it to Software. It should define everything Software needs to develop the software.
系統/軟體
常見軟體規格書,給出軟體。應定義開發軟體所需要的所有軟體內容。
Thus, the SRS should define everything explicitly or (preferably) by reference that software needs to develop the software. References should include the version number of the target document. Also, consider using master document tools which
allow you to include other documents and easily access the full requirements.
這樣,SRS應定義所有顯示或(可能)參考文獻來開發軟體所需的軟體。參考文獻應含有目的文件的版本號碼。此外,考慮使用文件管理工具,這樣可以方便的查看全部需求。
如何編寫軟體需求規格書(1)
如何編寫軟體需求規格書(2)
如何編寫軟體需求規格書(3)
如何編寫軟體需求規格書(4)
如何編寫軟體需求規格書(5)
如何編寫軟體需求規格書(6)
如何編寫軟體需求規格書(7)