50 likes | 167 Vues
Title of the function. Names of authors. Figure about your Function. Introduction & Motivation. Basic Idea and Purpose of the function Scope Identify the software product(s) to be produced by name Explain what the software product(s) will, and, if necessary, will not do
E N D
Title of the function Names of authors
Figure about your Function RACE Praktikum
Introduction & Motivation • Basic Idea and Purpose of the function • Scope • Identify the software product(s) to be produced by name • Explain what the software product(s) will, and, if necessary, will not do • Describe the application of the software being specified, including relevant benefits, objectives, and goals • Definitions, acronyms, abbreviations • provide the definitions of all terms, acronyms, and abbreviations required to properly interpret this document Source: IEEE-830-1998 (Recommended Practice for Software Requirements Specifications) RACE Praktikum
Overall description • Product perspective • If the product is a component of a larger system, then this subsection should relate the requirements of that larger system to functionality of the software and should identify interfaces between that system and the software. • System Interfaces, User Interfaces, HW Interfaces, SW Interfaces • Product functions • summary of the major functions that the software will perform • User characteristics • general characteristics of the intended users of the product • Constraints • HW limitations, interfaces to other applications, protocols, reliability requirements, criticality of the application • Assumptions and dependencies RACE Praktikum
Specific requirements • External interfaces • Description of all inputs into and outputs from the software system. • Functions • Functional requirements should define the fundamental actions that must take place in the software in accepting and processing the inputs and in processing and generating the outputs. These are generally listed as “shall” statements starting with “The system shall...” • Performance requirements • specify the static and the dynamic numerical requirements placed on the software or on human interaction with the software as a whole. Static numerical requirements may include the following • a) The number of terminals to be supported; • b) The number of simultaneous users to be supported; • c) Amount and type of information to be handled. RACE Praktikum