GoConqr has a new look! Let us know what you think.

Flowchart

Untitled

Ana Ruth Spanish

Flowchart content

  1. SRS

  2. Introduction

  3. Overview

  4. Specific Requirements

  5. (1.1) Purpose

  6. Specify the intented audience.

  7. (1.2) Scope

  8. (1.3) Definition

  9. Identify the software products, explain the software and describe application include objetives and system requieremts

  10. Provide definitions of all terms, acronys and abbreviations to interpret.

  11. Specify, identify and provide the found of where we can obtend the information SRS.

  12. (1.4) References

  13. (2.1) Product Perspective

  14. (2.2) Product Funtions

  15. (2.3) User Characterics

  16. (2.4) Constrains

  17. Describe how the sofware operates inside various constrains.

  18. System, user, hardware, software and communications.

  19. Memory constrains, operations and site adaption requieremts.

  20. Provide a summary of the major funtions.

  21. Isn't used for requirements only for describe characteristics of the intended of the product.

  22. (2.5) Assumptions And Dependencies

  23. (2.6) Apporting Of Requirements

  24. Provide a general description of any other iterms.

  25. Isn't about software only the factors that affect the requirements.

  26. Identify requirements of future versions systems.

  27. (3.1) External Interfaces

  28. (3.2) Funtions

  29. (3.3) Performance Requirements

  30. Description of all inputs into and outputs from the software system.

  31. Define the fundamental actions that must take place in the software in accepting and processing.

  32. Specify both the static and the dynamic numerical requirements placed on the software or human interaction.

  33. (3.4) Logical Database Requirements

  34. (3.5) Desing Contraints

  35. (3.6) Software System Atributes

  36. (3.7) Organizing The Specific Requirements

  37. Specify the logical requirements for any information that is to be placed into a database.

  38. Can be imposed by other standdars and hardware limitations.

  39. Standards compliance include report formal, data naming, accounting procedures and audit tracing

  40. Has the concepts like reliability, availability, security, maintainability and portability

  41. Has system mode, user class, objects, feature, stimulus, response and funtionals hierachy.

  42. Are quite important and should follow general compositional practices.

  43. Notations, methods and automated support.

  44. Aren't always considered part of the actual SRS and aren't always necessary.

  45. (3.8) Additional Comments

  46. (4.1) Table Of Contents And Index

  47. Supporting Information

  48. (4.2) Appendixes

Information

Description
Flowchart on Untitled, created by Ana Ruth on 15/05/2019.
Created by
Ana Ruth
Views
0
Rating

Feedback

What is it about?

What do you think of the new look?

How do you like it?