05 nonfunctional requirements


Published on

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

05 nonfunctional requirements

  1. 1. Nonfunctional Requirements
  2. 2. There are several differenttypes of requirements¡  Business Requirements¡  Business Rules¡  System Functional Requirements¡  Non-Functional Requirements¡  Data Requirements¡  User Interface Requirements¡  Enterprise Requirements
  3. 3. No, theyre not requirementsthat dont work
  4. 4. Nonfunctional requirements describe the characteristics of the system Functional Requirements Nonfunctional RequirementWhat the system shall do What the system shall beWhat the system does How well the system does itThe things it should do Measurements of how it does it
  5. 5. Lets look at an exampleWindows LinuxA computer operating system for A computer operating system forrunning personal computers and running personal computers andenterprises enterprisesVery simple to use Purposely difficult to useExpensive FreeSecretive OpenTakes huge amounts of disk space Very conservative in disk usageMemory hog Very conservative in memory usage
  6. 6. Users have expectationsabout how well our softwareworks¡  How easy the software is to use,¡  how quickly it executes,¡  how reliable it is, and¡  how well it behaves when unexpected conditions arise.
  7. 7. Specify as precisely aspossible by using numbers¡  Max seconds it must take to perform some task¡  Min concurrent users supported¡  Max minutes per year a system may be down¡  Max size of database¡  Max millisecond response time
  8. 8. But whatkinds ofthingsshould bemeasured?
  9. 9. Capacity¡  Throughput – how many transactions per hour does the system need to be able to handle?¡  Storage – how much data does the system need to be able to store?¡  Predictions of growth
  10. 10. Flexibility¡  If the organization intends to increase or extend the functionality of the software after it is deployed, that should be planned from the beginning¡  It influences choices made during the design, development, testing, and deployment of the system.
  11. 11. Recoverability¡ Recovery process¡ Recovery time scales¡ Backup frequencies¡ Backup generations
  12. 12. Auditability¡  Audited elements – what business elements will be audited?¡  Audited fields – which data fields will be audited?¡  Audit file characteristics - before image, after image, user and time stamp, etc.
  13. 13. Reliability¡ Reliability¡ Mean Time Between Failures¡ Mean Time To Recovery
  14. 14. Compatibility¡  Portability specifies the ease with which the software can be installed on all necessary platforms, and the platforms on which it is expected to run.¡  Compatibility with shared applications – What other systems does it need to talk to?¡  Compatibility with 3rd party applications – What other systems does it have to live with amicably?¡  Compatibility on different operating systems – What does it have to be able to run on?
  15. 15. Scalability¡  Software that is scalable has the ability to handle a wide variety of system configuration sizes. The nonfunctional requirements should specify the ways in which the system may be expected to scale up (by increasing hardware capacity, adding machines, etc.)¡  How many more users can it handle?¡  Can we easily add capacity when it slows down?¡  Can we add additional servers easily?¡  Can we upgrade the current hardware easily?
  16. 16. Security/Integrity¡  Integrity: Integrity requirements define the security attributes of the system, restricting access to features or data to certain users and protecting the privacy of data entered into the software¡  Login requirements - access levels, CRUD levels¡  Password requirements - length, special characters, expiry, recycling policies¡  Inactivity timeouts – durations, actions
  17. 17. Performance¡  The performance constraints specify the timing characteristics of the software. Certain tasks or features are more time-sensitive than others; the nonfunctional requirements should identify those software functions that have constraints on their performance.¡  Response times - application loading, screen open and refresh times, etc¡  Processing times – functions, calculations, imports, exports¡  Query and Reporting times – initial loads and subsequent loads
  18. 18. Efficiency¡  How well the software utilizes scarce resources: CPU cycles, disk space, memory, bandwidth, etc.
  19. 19. Availability¡  Availability: A systems availability, or "uptime," is the amount of time that it is operational and available for use. This is specified because some systems are designed with expected downtime for activities like database upgrades and backups.¡  Hours of operation – when is it available? Consider weekends, holidays, maintenance times, etc¡  Locations of operation – where should it be available from, what are the connection requirements?
  20. 20. Robustness andIntegrity¡  A robust system is able to handle error conditions gracefully, without failure. This includes a tolerance of invalid data, software defects, and unexpected operating conditions.¡  Fault trapping (I/O) – how to handle electronic interface failures, etc¡  Bad data trapping - data imports, flag- and-continue or stop the import policies, etc¡  Data integrity – referential integrity in database tables and interfaces¡  Image compression and decompression standards
  21. 21. Maintainability¡  Conformance to architecture standards – What are the standards it needs to conform to or have exclusions from?¡  Conformance to design standards – What design standards must be adhered to or exclusions created?¡  Conformance to coding standards – What coding standards must be adhered to or exclusions created?
  22. 22. Usability¡  Usability: Ease-of-use requirements address the factors that constitute the capacity of the software to be understood, learned, and used by its intended users.¡  Look and feel standards - screen element density, layout and flow, colors, UI metaphors, keyboard shortcuts¡  Internationalization / localization requirements – languages, spellings, keyboards, paper sizes, etc
  23. 23. Documentation¡  Required documentation items and audiences for each item
  24. 24. Reusability¡  Many systems are developed with the ability to leverage common components across multiple products. ¡  Reusability indicates the extent to which software components should be designed in such a way that they can be used in applications other than the ones for which they were initially developed.
  25. 25. You maywant to putthem oncards torecord them
  26. 26. Conclusion¡  Software can work as designed but still be unusable¡  Nonfunctional requirements tell how the software should do its job¡  They should be quantified to make them precise¡  Some of the things we require may be: ¡  Scalability ¡  Documentation ¡  Efficiency ¡  Security ¡  Maintainability ¡  Capacity ¡  Integrity ¡  Flexibility ¡  Availability ¡  Robustness ¡  Reliability ¡  Recoverability ¡  Auditability ¡  Usability ¡  Performance