Requirement Analysis


Published on

Published in: Technology, Business
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Requirement Analysis

  1. 1. Software Project Management Software Requirements Analysis & Specification
  2. 2. Requirement <ul><li>…A Condition or a capability that must be met or possessed by the system. </li></ul><ul><ul><ul><li>The basic goal of requirement phase is to generate SRS, which describes the complete external behavior of the software. </li></ul></ul></ul><ul><ul><ul><ul><li>However producing SRS is easier said than done! </li></ul></ul></ul></ul>
  3. 3. Software Requirements Specification <ul><li>…The SRS is a document that completely describes what the proposed software should do without describing how the software will do it. </li></ul>
  4. 4. Why we need SRS? <ul><li>The origin of most software systems is in the need of client. </li></ul><ul><li>The second party who is interested in the software is the user </li></ul><ul><li>The third party is developer </li></ul><ul><ul><li>SRS is the medium through which the client and user needs are accurately specified; indeed SRS forms the basis of software development. </li></ul></ul>
  5. 5. Advantages of SRS <ul><li>An SRS establishes the basis for agreement between the client and the supplier on what the software product will do. </li></ul><ul><li>An SRS provides a reference for validation of final product. </li></ul><ul><li>A High quality is a prerequisite to high quality software </li></ul><ul><li>A high quality SRS reduces the development cost. </li></ul>
  6. 6. Characteristics of an SRS <ul><li>Correct </li></ul><ul><li>Complete </li></ul><ul><li>Unambiguous </li></ul><ul><li>Verifiable </li></ul><ul><li>Consistent </li></ul><ul><li>Ranked for importance </li></ul><ul><li>Modifiable </li></ul><ul><li>Traceable </li></ul>
  7. 7. Components of an SRS <ul><li>Functionality </li></ul><ul><li>Performance </li></ul><ul><li>Design Constraints imposed on implementation </li></ul><ul><li>External interfaces </li></ul>
  8. 8. Function Requirements <ul><li>… It describes the relationship between input and output of the system. </li></ul><ul><ul><li>For each functional requirement, a detailed description of all the data inputs and their source, the units of measure, and the range of valid inputs must be specified. </li></ul></ul>
  9. 9. Performance Requirement <ul><li>… All the requirements relating to performance characteristics of the system must be clearly specified. There are two types of performance requirements. </li></ul><ul><ul><li>Dynamic ; that put constraints e.g. throughput, response time etc. </li></ul></ul><ul><ul><li>Static ; that do not impose constraints </li></ul></ul>
  10. 10. Design Constraints <ul><li>… There are number of factors in client’s environment that may restricts the choices of developer e.g. standards that must be followed. </li></ul>
  11. 11. External Interface Requirements <ul><li>All the possible interactions of the software with people, hardware and other softwares should be clearly specified </li></ul>
  12. 12. Contents of an SRS <ul><li>Introduction to the Organization </li></ul><ul><ul><li>Purpose of the system </li></ul></ul><ul><ul><li>Scope of the system </li></ul></ul><ul><ul><li>Definitions, Acronyms & abbreviations </li></ul></ul><ul><ul><li>References of data collection </li></ul></ul><ul><ul><li>Overview </li></ul></ul><ul><li>Overall System Description </li></ul><ul><ul><li>Product perspective </li></ul></ul><ul><ul><li>Product Functions </li></ul></ul><ul><ul><li>User Characteristics </li></ul></ul><ul><ul><li>General Constraints </li></ul></ul><ul><ul><li>Assumptions and dependencies </li></ul></ul>
  13. 13. Contents of an SRS Contd. <ul><li>Specific Requirements </li></ul><ul><ul><li>External Interface Requirements </li></ul></ul><ul><ul><ul><li>User Interfaces </li></ul></ul></ul><ul><ul><ul><li>Hardware Interfaces </li></ul></ul></ul><ul><ul><ul><li>Software Interfaces </li></ul></ul></ul><ul><ul><ul><li>Communication Interfaces </li></ul></ul></ul><ul><ul><li>Functional Requirements </li></ul></ul><ul><ul><li>Performance Requirements </li></ul></ul><ul><ul><li>Design Constraints </li></ul></ul><ul><ul><li>Other Requirements (Optional) </li></ul></ul><ul><li>Summary </li></ul>
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.