systemrequirementspecification系統(tǒng)需求分析模版(完整版)
【正文】 y of Southampton06/08/20116 / 8Table of ContentsTable of Contents iiRevision History ii1. Introduction 1 Purpose 1 Document Conventions 1 Intended Audience and Reading Suggestions 1 Project Scope 1 References 12. Overall Description 2 Product Perspective 2 Product Features 2 User Classes and Characteristics 2 Operating Environment 2 Design and Implementation Constraints 2 User Documentation 2 Assumptions and Dependencies 33. System Features 3 System Feature 1 3 System Feature 2 (and so on) 44. External Interface Requirements 4 User Interfaces 4 Hardware Interfaces 4 Software Interfaces 4 Communications Interfaces 45. Other Nonfunctional Requirements 5 Performance Requirements 5 Safety Requirements 5 Security Requirements 5 Software Quality Attributes 56. Other Requirements 5Appendix A: Glossary 5Appendix B: Analysis Models 6Appendix C: Issues List 6Revision HistoryNameDateReason For ChangesVersion1. Introduction Purpose Identify the product whose software requirements are specified in this document, including the revision or release number. Describe the scope of the product that is covered by this SRS, particularly if this SRS describes only part of the system or a single subsystem. Document ConventionsDescribe any standards or typographical conventions that were followed when writing this SRS, such as fonts or highlighting that have special significance. For example, state whether priorities for higherlevel requirements are assumed to be inherited by detailed requirements, or whether every requirement statement is to have its own priority. Intended Audience and Reading SuggestionsDescribe the different types of reader that the document is intended for, such as developers, project managers, marketing staff, users, testers, and documentation writers. Describe what the rest of this SRS contains and how it is organized. Suggest a sequence for reading the document, beginning with the overview sections and proceeding through the sections that are most pertinent to each reader type. Project ScopeProvide a short description of the software being specified and its purpose, including relevant benefits, objectives, and goals. Relate the software to corporate goals or business strategies. If a separate vision and scope document is available, refer to it rather than duplicating its contents here. An SRS that specifies the next release of an evolving product should contain its own scope statement as a subset of the longt
教學(xué)課件相關(guān)推薦
鄂ICP備17016276號(hào)-1