non functional requirement
DESCRIPTION
Non-functional details.TRANSCRIPT
![Page 1: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/1.jpg)
Non Functional Requirements
![Page 2: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/2.jpg)
Where Do RequirementsCome 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
![Page 3: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/3.jpg)
REQUIREMENT TYPES
![Page 4: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/4.jpg)
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
![Page 5: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/5.jpg)
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.”
![Page 6: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/6.jpg)
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.
![Page 7: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/7.jpg)
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
![Page 8: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/8.jpg)
Furps +
![Page 9: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/9.jpg)
Requirements
Packaging
+
![Page 10: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/10.jpg)
Boehm’s NFR list
![Page 11: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/11.jpg)
Classification of NFR’s
![Page 12: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/12.jpg)
Continuing with FURPS + model
![Page 13: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/13.jpg)
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.
![Page 14: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/14.jpg)
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,
![Page 15: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/15.jpg)
Cont.
• Measureable criteria:
Time taken to learn how to use.
• Realization of the metrics:
Minutes taken for some user’s task
![Page 16: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/16.jpg)
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
![Page 17: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/17.jpg)
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.
![Page 18: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/18.jpg)
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.
![Page 19: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/19.jpg)
PERFORMANCE
![Page 20: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/20.jpg)
USER’S CONCERN
• Proper resource utilization
• Efficiency
• Security
• Ease-of-use
![Page 21: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/21.jpg)
EXAMPLE
![Page 22: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/22.jpg)
TYPES OF PERFORMANCE REQUIREMENTS:
A. Response Requirements
B. Throughput Requirements
C. Availability requirements
![Page 23: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/23.jpg)
FACTORS AFFECTING PERFOMANCE:
• CPU speed
• Type of graphics card
• RAM size
• The number of applications running.
![Page 24: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/24.jpg)
HOW TO INCREASE PERFORMANCE:
Performance of a computer can be increased by proper care of hardware maintenance.
![Page 25: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/25.jpg)
SUPPORTABILITY
![Page 26: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/26.jpg)
CONCERN
• Adaptability
• Maintainability
• Internationalization
• Portability
• Tailorability
• Replaceability
![Page 27: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/27.jpg)
ADAPTABILITY
To adapt the changes after deployment efficiently
![Page 28: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/28.jpg)
MAINTAINABILITY:
To deal with new technology or to fix the defects
![Page 29: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/29.jpg)
INTERNATIONALIZATION:
Ability to deal with deal with international conventions
![Page 30: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/30.jpg)
PORTABILITY
Can easily be transferred from one environment to another
![Page 31: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/31.jpg)
TAILORABILITY:
Changing aspects of an application’s functionality
![Page 32: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/32.jpg)
REPLACEABILITY:
Replacing another system that performs the same functionality
![Page 33: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/33.jpg)
![Page 34: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/34.jpg)
Implementation requirements
Physical requirements
Interface requirements
Packaging requirements
Operation requirements.
Legal requirements.
Furps +:
![Page 35: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/35.jpg)
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.
![Page 36: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/36.jpg)
2.Interface Requirements:•Buttons•Images•Colors•Labels•Panels•Icons•Short cut keys.
![Page 37: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/37.jpg)
3. Physical requirements:A physical requirement specifies a physical constraint imposed on the hardwaresuse for a software.
Example:
• Material
• Shape
• Size
• Weight
![Page 38: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/38.jpg)
4. Packaging requirements:These tools cover every aspect of building, installing and maintainingsoftware 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.
![Page 39: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/39.jpg)
Operation Requirements.
![Page 40: Non Functional Requirement](https://reader034.vdocument.in/reader034/viewer/2022052316/559cd6391a28ab9f5f8b45e8/html5/thumbnails/40.jpg)
6. Legal requirements.
• Piracy Control
• Copyright laws
• Privacy Laws
• Safety Instructions