COMPUTER SCIENCE AND ENGINEERING
SOFTWARE ENGINEERING
|
Question
[CLICK ON ANY CHOICE TO KNOW THE RIGHT ANSWER]
|
|
|
Product-oriented Approach-Focus on system (or software) quality
|
|
|
Process-oriented Approach-Focus on how NFRs can be used in the design process.
|
|
|
Quantitative Approach-Find measurable scales for the functionality attributes
|
|
|
Qualitative Approach-Study various relationships between quality goals
|
Detailed explanation-1: -Examples of Non-functional Requirements Scalability: The system must be able to scale up or down as needed. Availability: The system must be available when needed. Maintenance: The system must be easy to maintain and update. Portability: The system must be able to run on different platforms with minimal changes.
Detailed explanation-2: -Question: Which of the following is not a non-functional requirement? performance of the software. the functionality of the software.
Detailed explanation-3: -Nonfunctional Requirements (NFRs) define system attributes such as security, reliability, performance, maintainability, scalability, and usability. They serve as constraints or restrictions on the design of the system across the different backlogs.
Detailed explanation-4: -What are the key types of non-functional requirements? The most common ones are performance, scalability, portability, compatibility, reliability, availability, maintainability, security, localization, and usability.