17 Questions
Which of the following is an example of scalability in a software system?
Any increase in the number of customers shall not degrade system availability
What is the main characteristic of scalability in a software system?
The ability to expand its processing capabilities to support business growth
What is the primary goal of scalability in software development?
To enable the system to support business growth
Which of the following is an example of expandability?
The Automated Money Machine (AMM) System shall be designed to allow for future addition of 4 user buttons and 4 additional banking services
What is the primary goal of the safety aspect of a software system?
To eliminate hazardous conditions due to errors in process control software
What is the primary focus of manageability in software development?
Providing administrator tools for software modification
What is the main goal of the correctness aspect of a software system?
To conform to the stated requirements
Which of the following is an example of reusability?
The payment subsystem design is based on the payment module from the ALPHA product line
What is the primary focus of reusability in software development?
Converting a portion of the software system for use in another context
What is the primary concern of the 'availability' non-functional requirement?
The ability of the system to be up and running during normal operating times
What is the main focus of the 'efficiency' non-functional requirement?
The ability of the system to handle capacity and throughput
Which of the following is an example of an 'integrity' non-functional requirement?
The system must check for data inconsistencies twice per second
What is the primary concern of the 'reliability' non-functional requirement?
The ability of the system to consistently perform its specified functions
Which of the following is an example of a 'survivability' non-functional requirement?
The system must have default values specified for report parameters
What is the primary concern of the 'usability' non-functional requirement?
The ease of use and learning of the system
Which of the following is an example of a 'reliability' non-functional requirement?
No more than 10 claim assignments out of 5000 can be unassigned due to system failure
What is the purpose of the 'password expiration duration' policy?
To ensure that users change their passwords regularly
Study Notes
Non-Functional Requirements (NFRs)
Flexibility
- It should be possible to add new delivery options by developing and "plugging in" the required functionality.
Maintainability
- A regression test procedure should allow complete re-testing within 2 business days.
Scalability
- The system should be able to expand processing capabilities to support business growth without affecting availability.
Verifiability
- The maximum number of test cases for any particular source code module should be 20.
Interoperability
- The system must be able to interface with any HTML browser.
Portability
- The system should be able to run in different environments, such as business offices or manufacturing assembly plants.
Reusability
- The payment subsystem design is based on the payment module from the ALPHA product line.
Correctness
- Deals with the extent to which the software design and implementation conform to the stated requirements, such as time limits and effort constraints.
Safety
- The system should not operate under hazardous conditions, such as temperatures below 4°C.
Expandability
- The system should be designed to allow for future additions, such as new user buttons and banking services.
Manageability
- Administrator tools should be available to support software modification during development and maintenance periods.
Availability
- The system should be available at least 99.5% of the time during "normal operating times" and at least 99.95% available during peak hours.
Efficiency
- The system should handle capacity, throughput, and response time efficiently, such as downloading new rate parameters within 10 minutes.
Integrity
- The system should ensure data accuracy, authenticity, and prevent corruption, with regular checks for inconsistencies.
Reliability
- The system should consistently perform specified functions without failure, with a maximum of 10 claim assignments out of 5000 being "unassigned" due to system failures.
Survivability
- The system should continue to function and recover in the presence of system failures, with default values specified for policy statement parameters.
Usability
- The system should be easy to learn, operate, and prepare inputs, with intuitive interaction and interpretation of outputs.
Test your understanding of order entry efficiency and software flexibility in adapting to different environments. Learn about the importance of modifying software to support new delivery options.
Make Your Own Quizzes and Flashcards
Convert your notes into interactive study material.
Get started for free
