systemrequirementspecification系統(tǒng)需求分析模版-閱讀頁
2025-07-11 00:01本頁面
【正文】 subset of the longterm strategic product vision. ReferencesList any other documents or Web addresses to which this SRS refers. These may include user interface style guides, contracts, standards, system requirements specifications, use case documents, or a vision and scope document. Provide enough information so that the reader could access a copy of each reference, including title, author, version number, date, and source or location.2. Overall Description Product PerspectiveDescribe the context and origin of the product being specified in this SRS. For example, state whether this product is a followon member of a product family, a replacement for certain existing systems, or a new, selfcontained product. If the SRS defines a ponent of a larger system, relate the requirements of the larger system to the functionality of this software and identify interfaces between the two. A simple diagram that shows the major ponents of the overall system, subsystem interconnections, and external interfaces can be helpful. Product FeaturesSummarize the major features the product contains or the significant functions that it performs or lets the user perform. Details will be provided in Section 3, so only a high level summary is needed here. Organize the functions to make them understandable to any reader of the SRS. A picture of the major groups of related requirements and how they relate, such as a top level data flow diagram or a class diagram, is often effective. User Classes and CharacteristicsIdentify the various user classes that you anticipate will use this product. User classes may be differentiated based on frequency of use, subset of product functions used, technical expertise, security or privilege levels, educational level, or experience. Describe the pertinent characteristics of each user class. Certain requirements may pertain only to certain user classes. Distinguish the favored user classes from those who are less important to satisfy. Operating EnvironmentDescribe the environment in which the software will operate, including the hardware platform, operating system and versions, and any other software ponents or applications with which it must peacefully coexist. Design and Implementation ConstraintsDescribe any items or issues that will limit the options available to the developers. These might include: corporate or regulatory policies。 hardware limitations (timing requirements, memory requirements)。 specific technologies, tools, and databases to be used。 language requirements。 security considerations
教學(xué)課件相關(guān)推薦
鄂ICP備17016276號-1