In view of the recent visit to the course design phase of software engineering courses, so we have more stringent requirements for the preparation of project documentation software engineering.
The record book about software engineering software requirements specification for the content of regulations to be written.
Software requirements specification, is an analyst in the requirements analysis phase needs to be done and asked Danone, the end result of software requirements analysis.
1 Scope
1.1 mark
1.2 System Overview
1.3 Document Overview
1.4 Baseline
2. references
3. Demand
State and direction desired 3.1
3.2 Demand Overview
3.2.1 target
3.2.2 Operating Environment
3.2.3 User features
3.2.4 Key points
3.2.5 Constraints
3.3 Requirements Specification
3.3.1 system software overall function / object structure
The overall function of the software system / object structure is described, including block diagrams, flowcharts or object in FIG.
3.3.2 software subsystem function / object structure
For each major subsystem basic function module described in / objects, including block diagrams, flowcharts or object in FIG.
3.3.3 Description conventions
Conventions described (mathematical symbols, units of measure, etc.) commonly used.
3.4 CSCI capacity needs
Paragraph shall be divided with a detailed description of the needs of each CSCI capability associated. "Capability" is defined as a group of related needs. You can use the "function", "Performance", "subject", "target" or other suitable word you need to replace the "capacity"
3.5 CSCI external interface requirements
This article shall hand side striping needs CSCI external interface. (If any) of this section may reference one or more Interface Requirements Specification (IRS) or documents containing these demands
3.5.1 Interface Interface logo and map
3.6 CSCI internal interface requirements
Article should indicate CSCI internal interface requirements (if slip). If all internal interfaces are left to define the design, we need to explain. To strengthen the demand, considering the card document gives a list of topics 3.5
3.7 CSCI internal data requirements
This article shall indicate on the demand CSCI internal data (if any), including the need for CSCI database and data files. If all decisions relating to internal data are pending, we need to explain
3.8 suitability requirements
3.9 confidentiality requirements
3.10 confidentiality and privacy requirements
3.11 CSCI environmental needs
3.12 computer resource requirements
3.12.1 computer hardware requirements
3.12.2 computer hardware resource utilization requirements
3.12.3 Computer Software Requirements
3.12.4 computer communication needs
3.13 software quality factors
3.14 Design and implementation constraints
3.15 Data
3.16 Operation
3.17 Troubleshooting
3.18 algorithm description
3.19 related to staffing requirements
3.20 related to the relevant training needs
3.21 related logistical requirements
3.22 Other requirements
3.23 packaging needs
Priorities and needs of the criticality of 3.24
4. Eligibility requirements
This chapter defines a set of eligibility method, for the first method in Chapter 3 in each needs to specify the use to ensure that needs are met. This information can be represented in tabular form, can also indicate the method to be used in each requirement in Chapter 3.
The demand for traceability
6. Unresolved Issues
7. Notes
This section shall contain general information helpful in understanding the document (eg, background information, glossary, rationale). This chapter contains terms and definitions for understanding the needs of this document, alphabetical list of all Abbreviations and their meanings in the document.
appendix
It is used to provide for convenience in document maintenance information (e.g., charts, classified data) two published separately.
Note: The above italicized selected according to actual demand.