Software demand manual
(Reprinted from National Computer Standards and File Templates)
The preparation of the software demand manual is to make the user and software developers have a common understanding of the initial provisions of the software, making it the basis of the entire development work. The content requirements for the preparation of the software demand manual are as follows: 1 Introduction 1.1 Writing Objectives Description Writing the purpose of this software requirements specification, pointing out the expected readers. 1.2 Background Description: a. The name of the software system to be developed; b. This item's task proposals, developers, users, and computing centers or computer networks that implement the software; C. The software system is based on the basic mutual processes of other systems or other agencies. 1.3 Definitions list the definitions of the specimen used in this document and the original phrase of the foreign letter group word. 1.4 References list the reference materials, such as: a. The approved planning task book or contract of the project, the approval of the superior authority; b. Other published files belonging to this item; c. The documents, materials, information, including the software development standards you want are included in this document. List the title, file number, publishing date, and publishing unit of these files, indicating that the source of these files can be obtained. 2 Task Overview 2.1 Target Describe the intention of the software development, application objectives, scope, and other background materials that should be explained to the reader. Explain the relationship between developed software and other related software. If this software product is a separate software, all content is self-contained, then this is described. If the defined product is a component of a larger system, the relationship between this product and other components in the system can be used to use a block diagram to explain the composition and this product. Contact and interfaces with other parts. | 2.2 User's characteristics list the characteristics of the end user of this software, fully illustrate the operational level and technical expertise of operators, maintenance personnel, and the intended frequency of this software. These are important constraints for software design 2.3 hypothesis and constraints list assumptions and constraints for the development of this software, such as funding restrictions, development periods, and more. 3 Requirements 3.1 Ways to the Functions (such as IPO table, processing, output table), quantitatively and qualitatively describe the functional requirements of the software, what is the amount of input, What is the processing, what is output, explaining the number of terminals that the software should support and the number of users that should be supported. 3.2 Provisions for Performance 3.2.1 Accuracy Description The input of the software, output data accuracy, may include the accuracy during transmission. 3.2.2 Time Features Requirements The time characteristic requirements for the software, such as: a. Response time; b. Update processing time; c. Data conversion and transmission time; D. Solution time; etc. 3.2.3 Flexibility Description Requirements for the flexibility of the software, that is, when certain changes in demand, such as adaptation capabilities, such as: a. Changes in operation methods; b. Change of operating environment; C. Changes to the interfaces of other software; d. Changes in precision and effective time limit; e. Plan changes or improvements. A specially designed part for providing these flexibility should be indicated. 3.3 Losing output requirements Interpret each input output data type and describe its media, format, numerical range, accuracy, etc. one by item. Interpretation of the data output of the software and the required control output, including a description of the hard copy report (normal result output, status output, and exception output) and graphics or display reports.
