O GoConqr está de visual novo! Conte para nós o que você achou.

Mapa mental

Software Requirements Specification

Carlos Aguilar Teacher Aidaa. Espanhol

Conteúdo do mapa

Software Requirements Specification

  1. Introduction (Section 1 of the SRS)

    • Purpose
      • Specify the intended audience for the SRS.
    • Definitions, acronyms, and abbreviations
      • This subsection should provide the definitions of all terms, acronyms, and abbreviations required to properly interpret the SRS. This information may be provided by reference to one or more appendixes in the SRS or by reference to other documents.
    • Scope
      • A) Identify the software products to be produced by name
        • B) Explain what the software products will and if necessary will not do.
          • C) Describe the application of the software being specified, including relevant benefits, objectives, and goals.
            • D) Be consistent with similar statements in higher-level specifications
              • Scope
  2. Overall description

    • Product perspective
      • Software interfaces
      • Hardware interfaces
      • Communications interfaces
    • Product functions
      • This subsection of the SRS should provide a summary of the major functions that the software will perform.
    • User characteristics
      • This subsection of the SRS should describe those general characteristics of the intended users of the product
  3. Specific requirements

    • This section of the SRS should contain all of the software requirements to a level of detail sufficient to enable designers to design a system.
      • External interfaces
        • This should be a detailed 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.
      • Logical database requirements
        • This should specify the logical requirements for any information that is to be placed into a database.
      • Software system attributes
        • Security
        • Portability
        • Maintainability
      • System mode
        • Some systems behave quite differently depending on the mode of operation. may have different sets of functions depending on its mode
          • Training
            • The performance are dependent on mode.
              • Normal
              • Emergency
          • Normal
  4. Supporting information

    • Table of contents and index
      • The table of contents and index are quite important and should follow general compositional practices.

Informações

Descrição
Teacher Aidaa. Mapa Mental sobre Software Requirements Specification, criado por Carlos Aguilar em 15-05-2019.
Criado por
Carlos Aguilar
Visualizações
10
Avaliação

Mais sobre Software Requirements Types and Specification

Fale Conosco

Sobre o que é sua mensagem?

O que você acha do novo visual?

Você gostou?