Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.
Non Functional
Requirements
Where Do Requirements
Come From?
Stakeholders
• Product user group
• Project customer
• An analyst/requirement engineer
• ...
REQUIREMENT TYPES
Functional
• Describe the behaviors (functions or services) of
the system
• Support user goals, tasks or activities
• F(in...
Non Functional
• Non functional requirement – in software system engineering is, a
software requirement that describes not...
Cont.
• Involves
• ilities: understandability, usability, modifiability, reliability, portability,
dependability, flexibil...
Non Functional vs. Functional
FR
Verbs
Mandatory
Captured in use case
Product feature
Easy to capture
NFR
Attributes
Not m...
Furps +
Requirements
Packaging
+
Boehm’s NFR list
Classification of NFR’s
Continuing with FURPS + model
Usability
How easy is it for the user to accomplish a desired task?
• Learning system features
• Using system effectively
...
General Scenario
• Source – User
• Stimulus – What the user wants to do
• Artifact – System
• Environment – Runtime or con...
Cont.
• Measureable criteria:
Time taken to learn how to use.
• Realization of the metrics:
Minutes taken for some user’s ...
Reliability
• Reliability measures the level of risk and the likelihood of potential
application failures.
• It is the pro...
Reliability measures
• Reliability of software is measured in terms of Mean Time Between
Failure (MTBF). For eg if MTBF = ...
Cont.
Reliability is measured to find
• The performance of software
• Life of the software
• Cause of failure
• No. of fai...
PERFORMANCE
USER’S CONCERN
• Proper resource utilization
• Efficiency
• Security
• Ease-of-use
EXAMPLE
TYPES OF PERFORMANCE REQUIREMENTS:
A.Response Requirements
B. Throughput Requirements
C. Availability requirements
FACTORS AFFECTING PERFOMANCE:
• CPU speed
• Type of graphics card
• RAM size
• The number of applications running.
HOW TO INCREASE
PERFORMANCE:
Performance of a computer can be increased
by proper care of hardware maintenance.
SUPPORTABILITY
CONCERN
• Adaptability
• Maintainability
• Internationalization
• Portability
• Tailorability
• Replaceability
ADAPTABILITY
To adapt the changes after
deployment efficiently
MAINTAINABILITY:
To deal with new technology
or to fix the defects
INTERNATIONALIZATION:
Ability to deal with deal with
international conventions
PORTABILITY
Can easily be transferred from one
environment to another
TAILORABILITY:
Changing aspects of an
application’s functionality
REPLACEABILITY:
Replacing another system that
performs the same functionality
Implementation
requirements
Physical
requirements
Interface
requirements
Packaging
requirements
Operation
requirements.
Le...
1.Implementation requirements:
Examples:
• Direct changing.
• Parallel running of coding.
• Third party component involvin...
2.Interface Requirements:
•Buttons
•Images
•Colors
•Labels
•Panels
•Icons
•Short cut keys.
3. Physical requirements:
A physical requirement specifies a physical constraint imposed
on the hardwaresuse for a softwar...
4. Packaging requirements:
These tools cover every aspect of
building, installing and maintaining
software packages and in...
Operation Requirements.
6. Legal requirements.
• Piracy Control
• Copyright laws
• Privacy Laws
• Safety Instructions
Non Functional Requirement.
Nächste SlideShare
Wird geladen in …5
×

Non Functional Requirement.

13.490 Aufrufe

Veröffentlicht am

Non-functional details.

Veröffentlicht in: Software
  • Enough is a enough! Is this going to be the day you finally do something about your health? It is a lot easier than you think to be able to shed off unwanted weight. See how you can get started today with 1 minute weight loss routines! ◆◆◆ https://tinyurl.com/1minweight
       Antworten 
    Sind Sie sicher, dass Sie …  Ja  Nein
    Ihre Nachricht erscheint hier

Non Functional Requirement.

  1. 1. Non Functional Requirements
  2. 2. Where Do Requirements Come From? Stakeholders • Product user group • Project customer • An analyst/requirement engineer • Project leader • Project team members • Upper management • Project testers • Licensing entities • Outside vendors or suppliers • Government entities
  3. 3. REQUIREMENT TYPES
  4. 4. Functional • Describe the behaviors (functions or services) of the system • Support user goals, tasks or activities • F(input, system state) (output, new state) Output, new state Input, initial state
  5. 5. Non Functional • Non functional requirement – in software system engineering is, a software requirement that describes not what the software will do, but how the software will do it, for example, software performance requirements, software external interface requirements, design constraints, and software quality attributes. Nonfunctional requirements are difficult to test; therefore, they are usually evaluated subjectively.”
  6. 6. Cont. • Involves • ilities: understandability, usability, modifiability, reliability, portability, dependability, flexibility, availability, maintainability, scalability etc. • ities: security, safety etc. • ness: user-friendliness, robustness, timeliness, responsiveness, correctness, completeness, conciseness etc. • Others like: convenience, comfort, performance, efficiency, accuracy, consistency, cost, development time, time-to-market etc.
  7. 7. Non Functional vs. Functional FR Verbs Mandatory Captured in use case Product feature Easy to capture NFR Attributes Not mandatory Captured in quality attribute scenario Product properties Difficult to capure
  8. 8. Furps +
  9. 9. Requirements Packaging +
  10. 10. Boehm’s NFR list
  11. 11. Classification of NFR’s
  12. 12. Continuing with FURPS + model
  13. 13. Usability How easy is it for the user to accomplish a desired task? • Learning system features • Using system effectively • Minimizing impact of errors • Adapting to user needs • Increasing confidence • Performing the tasks quickly • Re-establishing the proficiency while using a system after a long time.
  14. 14. General Scenario • Source – User • Stimulus – What the user wants to do • Artifact – System • Environment – Runtime or configuration time (compiled at deployment time ) • Response – What the system does • Response Measure – time, tries, number of errors or solutions,
  15. 15. Cont. • Measureable criteria: Time taken to learn how to use. • Realization of the metrics: Minutes taken for some user’s task
  16. 16. Reliability • Reliability measures the level of risk and the likelihood of potential application failures. • It is the probability that software will work without failure for a specified period of time in a specified environment. • Technically reliability is the ability of a system to behave consistently in the user-acceptable environment. • Reliability is based on the probability that a system will break i.e., the more likely it is to break, the less reliable it is
  17. 17. Reliability measures • Reliability of software is measured in terms of Mean Time Between Failure (MTBF). For eg if MTBF = 10000 hours for an average software, then it should not fail for 10000 hours of continuous operation. • Failure Rate (λ), which is defined as: number of failures / total time in service. • Realization of metrics: Run it and count no. of crashes per hour.
  18. 18. Cont. Reliability is measured to find • The performance of software • Life of the software • Cause of failure • No. of failures occurring in a particular time of a software. • Reliability is considered important because it eliminates the failure mode of the software.
  19. 19. PERFORMANCE
  20. 20. USER’S CONCERN • Proper resource utilization • Efficiency • Security • Ease-of-use
  21. 21. EXAMPLE
  22. 22. TYPES OF PERFORMANCE REQUIREMENTS: A.Response Requirements B. Throughput Requirements C. Availability requirements
  23. 23. FACTORS AFFECTING PERFOMANCE: • CPU speed • Type of graphics card • RAM size • The number of applications running.
  24. 24. HOW TO INCREASE PERFORMANCE: Performance of a computer can be increased by proper care of hardware maintenance.
  25. 25. SUPPORTABILITY
  26. 26. CONCERN • Adaptability • Maintainability • Internationalization • Portability • Tailorability • Replaceability
  27. 27. ADAPTABILITY To adapt the changes after deployment efficiently
  28. 28. MAINTAINABILITY: To deal with new technology or to fix the defects
  29. 29. INTERNATIONALIZATION: Ability to deal with deal with international conventions
  30. 30. PORTABILITY Can easily be transferred from one environment to another
  31. 31. TAILORABILITY: Changing aspects of an application’s functionality
  32. 32. REPLACEABILITY: Replacing another system that performs the same functionality
  33. 33. Implementation requirements Physical requirements Interface requirements Packaging requirements Operation requirements. Legal requirements. Furps +:
  34. 34. 1.Implementation requirements: Examples: • Direct changing. • Parallel running of coding. • Third party component involving. • Implementation languages. • Platform support. • Limited resources. • Required standards • Rights for database integrity. • Operation environments. Operation environments. Implementation languages. Required standards Parallel running of coding. Direct changing.
  35. 35. 2.Interface Requirements: •Buttons •Images •Colors •Labels •Panels •Icons •Short cut keys.
  36. 36. 3. Physical requirements: A physical requirement specifies a physical constraint imposed on the hardwaresuse for a software. Example: • Material • Shape • Size • Weight
  37. 37. 4. Packaging requirements: These tools cover every aspect of building, installing and maintaining software packages and include the ability of having multiple versions of a single software package installed concurrently. Example: Windows vista. Windows 7,8 and 8.1.
  38. 38. Operation Requirements.
  39. 39. 6. Legal requirements. • Piracy Control • Copyright laws • Privacy Laws • Safety Instructions

×