1. Foreword preface proposes the overview of the software demand specifications, which helps readers to read and understand this document. 1.1. Objective To describe the purpose of writing this demand specifications. Such as: the * software product is defined, and the software requirements of this product are defined in detail in this document. If this demand specification specification is described only for a part of the entire system, then the part or subsystem described in the document is defined. 1.2. Background to develop the name of the software product / project system; product / project task proposals, users, developers; the product is related to external systems or organizational structures. 1.3. Target 1.4. Reader and Reading recommendations List the different readers of the Software Demand Specification Specification, describing the organizational structure of the remainder of this document and reading recommendations for each type of reader. 1.5. Application ranges for a short description of the purpose of software products or projects to be developed, linking the software products or projects to the user's business scope and operational methods in the application environment. 1.6. Definition, abbreviation, omitted, agree to give the definition of some professional words in the document; explain some of the abbreviations and number of abbreviations in the document; some of the standards, typographic style, prompts, and special symbols used in documentation Description. 1.7. References list the information and other resources referenced when writing documents. It may include contracts, various specification standards, fast prototypes of user interfaces, other documents that have been released during project (product) development process. The information provided should be able to guide readers to read them for easy access to this information and resources, including title, authors, versions, dates, publishing units or sources of information. 2. System Overview of the functionality to which the system (module) to be implemented is a comprehensive description. The content to be described in this section may include: 1. User Type Description The final user range, type, and characteristics of the software product or project. 2. Product Features Overview Product The main function of the product, the detailed description will continue in the following sections. 3. Assuming and relying on some prerequisites for describing software runtime and some assumptions for various support environments for software runtime. 4. Other Macro descriptions of the product to be developed Depending on the actual structure of the system, you can specify the modules and sub-modules of the system in multiple sub-chapters. 3. The system structure fully describes the system's module structure and is attached to the corresponding chart (such as system module structure), each module should have a clear definition and scope detailed description. Each system module and the relationship between each system module are described by block diagram. If there is an external function module related to system characteristics, these external function modules should also be described in the block diagram. The function modules and interfaces between this section must have a detailed description in this document or other related documentation (such as independent system interface manual). 4. Extended Characteristics When there are some implicit demands in the system, the extension of the system implicit needs is described here. 5. System Software Demand This section describes the functional requirements of each functional module, and each module should have a corresponding tool of the software requirements specification. 5.1. 标 5 5.2. Identification 5.3. Specification Naming Number of identification number of system feature component assigned to the software. Name specification of identification number is: (Class) - {Field1 {-field2 {...}}} .seq. 1. Class represents the type, nature, importance, or priority of functional components, which can be defined according to the actual situation of the software. Such as: P: The primary function must be realized; i: important function, but do not have to be implemented immediately; S: Suggested function, not the customer proposed. 2. {Field1 {-field2 {- ...}}} According to the actual situation of the software. 3. SEQ demand function taste flow. Such as: p-secure.login.001, indicating the login function item in the system security module, the function item is the primary function, the water number is 001.5.4. {System Module Name 5.5. Name of the system function module name, identification number. This section describes the functional characteristics of software implementation in this module.
For different software products or projects, the development team can adjust the content of this section to establish its own document content structure and level. 6. System Interface Demand (Optional) The system interface consists of two parts, including external interface and internal module interface. If the interfaces in the system are more complicated, and more content can be formed as a separate system interface manual as this document. 6.1. System External Interface Description The interface requirements of the system and other other systems. 6.2. System Module Interface Description Interface between the internal modules within the system. 7. System Environmental Demand Description Software Running Environment Related Factors. Includes support for hardware platforms and software platforms. Describe the restrictions on the free choice of developers on the hardware platform and software platform, which may include: 1. It is necessary to use or avoid the techniques, tools, languages, software, etc .; 2. The development specification or standard 3 is required to comply. 4. Laws and regulations, industry standard 5. Quasi-wait; 6. Hardware restrictions (such as hardware integration is performed by other organizations) 7.1. Hardware platform description The hardware functional requirements of each module in the system, each module should have detailed hardware functional requirements, if the hardware requirements of all modules are the same, The hardware requirements of the entire system are required. Description of hardware requirements can be described as a functional feature that needs to be implemented by hardware, as well as hardware requirements for these features. 7.2. Software platform description system and operating system platforms, versions, other software components, applications, application services such as software components, applications, application services, etc. 8. Other non-functional requirements (optional) This section enumerates all non-functional needs in the system, including: 1. Performance requirements: Describe the requirements for software product performance in the target application. Such as: may exist, memory, or disk space requirements, capacity in the database, response time for user operation requests, etc. 2. Quality requirements: Describe the abnormalities in the system or will result in an unstable factors that will lead to an unusual factor, and define the necessary precautions and remedies. Determine the safety standards, strategies, or rules that software products must be observed. Such as: "When the number of users who have accessible exceeds 100, the busy information on the later user newspaper system is" " 3. Security requirements: Statement and systematic security, complete, confidential issues, which will affect the use of software and the protection of data created during use. Describe the security requirements that must meet in the system, define user identity confirmation or authorization requirements. Such as: "When the user accesses a table (or the data of a module, the data such as access, the data such as access, etc.) is written to the security log)." 4. Quality characteristics: Detailed description of the quality characteristics of users and developers. These features must be determined, quantitative, verifiable, and point out the side focus on these features. The following table lists some quality features considered from users and developers. For the user's important quality characteristics Important ValiTainAnability Flexibility (Reusability) Integrity (Integrity) Integrity (Integrity) ) Testability, Robustness, Different parts of the USABILITY, have different requirements for quality features. 5. Business rules: Describe the industry rules of user services to be complied with software products.
