1. Definition
A category of non-functional requirements groups the NFRs that deal with the same quality of a solution, such as availability, security or usability. Each framework names and groups these qualities in its own way, so the checklist in section 5 combines several of them into a single list.
Frameworks
The categories below are derived from the following frameworks:
- ISO/IEC 25010:2011 – Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — System and software quality models [1]
- Consortium for IT Software Quality – Code Quality Standards [2]
- IBM/HP – RUP/FURPS+ and architectural requirements [3]
- SNAP derived from the Function Point sizing process [4]
2. Goal
Many requirements frameworks give examples of the types of non-functional requirements (NFRs) that should be elicited. When the proposed list is too short, it becomes very easy to overlook less frequent operational scenarios and the cost to introduce these “forgotten” requirements later in a project often becomes prohibitive. It is much simpler to have a very detailed list and show that, as a business analyst, you gave them some thought, even if it means that no requirements were derived or found in a particular category.
3. Questions to Ask Stakeholders
- Which categories caused problems or late changes on past projects?
- Who owns each category: the business, IT operations, security, compliance or a vendor?
- Which regulations, standards or certifications apply to this solution?
- Where, and by whom, will the solution be operated?
- Which categories can be marked “not applicable”, and who approves that decision?
- Which NFRs must be met at launch, and which can wait for a later release?
4. Common Pitfalls
- A list that is too short. Requirements forgotten at the start are expensive to add later in the project.
- Discarding categories too early. Go through all of them before deciding that one does not apply.
- Downgrading NFRs to “nice to have”. Postponed NFRs often become the defects of the first release.
- Arguing about labels. Whether a need is functional or non-functional matters less than documenting it so it can be traced.
Point of View
“There is no absolute point of view from which real and ideal can be finally separated and labelled.”
— T.S. Eliot [5]
Depending on the type of enterprise you are working for and the type of business analyst you are, non-functional requirements can actually become functional in a different context. A simple example would be an administrative console to review system software logs. If this requirement were presented to stakeholders, it would definitely be considered a non-functional requirement as it is not a sought-after feature, something that the solution should perform or deliver as an output. However, the same requirement presented to a system administrator (sysadmin) becomes a functional requirement as it is a function that will help them perform their jobs.
Try to adopt the point of view of the bulk of your audience when categorizing your functional and non-functional requirements. It does not matter if they don’t end up in the right section, type or category: as long as they are documented, they become traceable. Many stakeholders might be tempted to downgrade non-functional requirements to “nice to have” or for “future releases”; be careful about sacrificing the intrinsic qualities and performances of what will be delivered. Remember the phrase, “Works as designed, performs as defined.” [6]
5. Related NFRs
Some of these categories might not seem relevant in your work environment or project, but play the game of going through all of them before discarding anything. You might realize at one point that the brand-new fleet of ATMs being deployed around the globe may have very different operational environments. Some will be installed as standalone in shopping malls, others facing the street directly through the wall of a branch; they might be in northern Canada or downtown Cairo. Right there, by analyzing one type of NFR, others appear, such as internationalization and security.
| Type | Short definition or example |
|---|---|
| Accessibility | Make buildings, products, software or environments accessible by design to people with special needs. |
| Adaptability | In software engineering and IT, adaptability is the ease with which software meets differing system constraints and user needs, and with which a system, or parts of it, can be adapted to changing requirements [7]. |
| Auditability and control | Making sure that an IT solution can generate or obtain artifacts showing that system assets are safe, data integrity is maintained and that it is operating effectively. For software, compliance with requirements, standards, service level agreements (SLAs), policies, laws, etc. could be audited. |
| Availability | The degree to which a system is operational and accessible when it is required for use [1]. It is usually expressed as a percentage of the agreed service time, such as 99.9% per month. In ISO/IEC 25010, availability is a sub-characteristic of reliability: it depends on how often the system fails and how quickly it is restored after each failure. |
| Backup |
A backup is a copy of server/computer data taken and stored elsewhere so it may be used to restore the original after a data loss or corruption event. Things to consider:
|
| Boot up time | How long a system, device or application takes to go from being started to being ready for use [8]. It matters for ATMs, kiosks and servers that restart after maintenance. |
| Capacity, current and forecast | Capacity management makes sure that enough capacity is available at all times to meet the agreed needs of the business, at a reasonable cost. It has three subprocesses: business, service and component capacity management [9]. As a business analyst you need to know how many users will use the solution being developed, how many transactions will be processed per second and what is the expected growth year over year for that solution. |
| Certification |
It is not unusual to see a solution that needs a certain level of certification for its hardware, software, architecture, process or operating personnel. Certification, also referred to as accreditation, can be an internal requirement or be required by an external third party.
|
| Compatibility | The ability of a system to work alongside other systems, versions or components without conflict, including its own previous versions. In ISO/IEC 25010, compatibility covers co-existence and interoperability [1]. |
| Compliance |
Compliance is both a state, being in accordance with established guidelines or specifications, and the process of reaching that state. Software can be developed in compliance with the specifications of a standards body, then deployed by user organizations in compliance with a vendor’s licensing agreement. Compliance also covers the efforts made to respect industry regulations and government legislation [10]. Some of the most well-known standards affecting IT:
IT governance and management frameworks:
Financial compliance in Canada:
|
| Configuration management | Configuration Management (CM) is an Information Technology Infrastructure Library (ITIL) and an IT Service Management (ITSM) process that tracks all of the individual Configuration Items (CI) in an IT system which may be as simple as a single server, or as complex as the entire IT department. Many modern tools use the configuration management database (CMDB) as a single source of truth. Without a well-maintained CMDB, such things as automation, AI, monitoring and incident/problem management and capacity management will become more difficult or simply impossible. |
| Conformance | How closely a system follows a specified standard, protocol or specification, such as a file format, an API specification or an accessibility standard [11], [12]. |
| Cost, initial and life-cycle cost | Helps track the total cost of ownership (TCO) of an asset over its life cycle. If a chargeback model is in place, it will also enable IT to charge the proper department or customer for its usage. Beyond the purchase price, TCO includes the training of support staff and users, planned and unplanned outages, performance incidents, security breaches, disaster preparedness and recovery, floor space, electricity, development, testing and quality assurance, growth, decommissioning and e-waste handling. In a financial benefit analysis (e.g., ROI, IRR or EVA), TCO provides the cost basis for judging the economic value of the investment [13] |
| Data integrity |
Data integrity is the overall accuracy, completeness and consistency of data. It also covers the safety of data from a security and regulatory standpoint (for example, GDPR compliance) and is maintained by processes, rules and standards put in place during design. When data integrity is secured, stored information remains complete, accurate and reliable, however long it is kept and however often it is accessed [14]. It includes:
|
| Data retention |
Data retention defines the data and records management for meeting legal and business data archival requirements. On top of your organization’s data retention policies, most countries have their own laws and framework regarding data retention.
|
| Decommission & disposition of IT assets |
Ensuring the proper disposition of decommissioned assets while making sure that potential data security breaches are addressed, and that environmental hazards are mitigated. Activities and processes involved are:
|
| Dependency on other parties | Not usually documented as NFRs, but often a source of them. The same logic applies to other dependencies, constraints & assumptions. |
| Deployment |
This category usually covers the following subjects [15]:
|
| Development environment |
This category is rarely defined as part of NFR unless there are specific parameters or constraints to be addressed. (e.g., offshoring, inshoring or nearshoring of coding, military software development or imposed corporate framework) This is the working environment of individual developers, programming pairs, or individual feature teams. The purpose of this environment is for the developer/pair/team to work in seclusion from the rest of their project team, enabling them to make and validate changes without having to worry about adversely affecting the rest of their project team. These environments are likely to have their own databases to enable regression testing and, more importantly, agile testing strategies. |
| Disaster recovery | A disaster recovery (DR) plan describes how data will be restored and accessed after an event that destroys part or all of an organization’s resources. Its purpose is to make sure that, whatever happens, vital data can be recovered and mission-critical applications brought back online as quickly as possible [16]. |
| Documentation |
The following are typical IT project and operational documentation types. The following are typical software documentation types
The following are typical hardware and service documentation types
Service catalogue and service portfolio (ITIL):
|
| Durability |
Durability can cover several physical properties of designed products, including [17]:
|
| Efficiency | “Efficiency is operational in nature and asks questions such as ‘How will it be created?’ and ‘How will it be delivered?’’ [18] |
| Effectiveness |
Effectiveness can be documented as business objectives, benefits, losses and the desired results of a project. “Effectiveness is strategic in nature and asks questions such as “What is the business objective?” and “What is the best possible outcome?” [18] |
| Elasticity | The ability of a system to add or remove resources automatically so that its capacity follows the workload [19], [20]. Scalability asks whether the system can grow; elasticity asks whether it grows and shrinks on its own. |
| Emotional factors |
|
| Environmental protection | The degree to which a solution limits its impact on the environment: the energy it consumes, the carbon emissions linked to that energy and to its hardware, and the electronic waste it produces. The ISO/IEC 21031 standard (Software Carbon Intensity) describes a method for calculating the rate of carbon emissions of a software system, so that targets can be set during design and progress can be tracked [21]. |
| Escrow |
Many companies depend on custom software and want its operation and maintenance to continue even if the licensor can no longer provide them, for example after a bankruptcy. The simplest safeguard would be a copy of the current source code, but licensors are usually reluctant, since source code is often one of their most closely guarded trade secrets. Source code escrow resolves this conflict of interest: the licensee gets access to the source code only when maintenance can no longer be assured otherwise, under conditions agreed in the contract [22]. |
| Ethics | How well a system respects fairness, non-discrimination, transparency, privacy and the rights of its users, especially when it makes automated decisions such as credit scoring [23]. |
| Exploitability | In security, exploitability is the ease with which a weakness in a system could be used by an attacker to cause harm; a well-protected system has low exploitability. The Common Vulnerability Scoring System (CVSS), maintained by FIRST, rates it with metrics such as attack vector, attack complexity, privileges required and user interaction [24]. In design, the term is also used for solutions made exploitable “as commodities in an aggregated revenue stream” [25]. |
| Extensibility | Extensibility is the ability of a system to be extended with new functionality with little or no effect on its internal structure and data flow [26]. It is closely coupled with the modifiability, maintainability and scalability categories. |
| Failure management | Process-oriented category covering not only incident and problem management but communication, change failures, sponsorship, knowledge of technology, support training, vendor management. |
| Fault tolerance |
Encompasses both fault avoidance and fault tolerance [27]:
|
| Flexibility | How easily a system can be changed to handle future requirements, including ones nobody can predict today [28]. It is closely related to modifiability and extensibility. |
| Footprint reduction | Keeping a system small: the size of its installer or executable, of the pages and scripts it downloads, of its memory use and of the storage it needs [29]. |
| Geographical distribution (users, systems, etc.) |
Special considerations are often needed when users or distributed systems are geographically far apart.
|
| Integrability (system integration) |
System integration (SI) is the IT or engineering process of joining different subsystems or components into one larger system, while making sure each integrated subsystem still functions as required [30]. SI methods are as follows:
|
| Internationalization and localization |
“localization revolves around combining language and technology to produce a product that can cross cultural and language barriers.” [31]
|
| Interoperability |
Interoperability is the ability of a product or system whose interfaces are fully understood to work with other products or systems, present or future, without restriction in either implementation or access [32]. Degree of operability
|
| Legal and licensing issues or patent-infringement-avoidability |
Things to consider:
|
| Maintainability (code) |
Specific to software code and supported by an international standard (ISO/IEC 25010:2011) [1]. Maintainability is a set of attributes that bear on the effort needed to make specified modifications. It is often encompassed in the “modifiability” category of NFRs (IEEE framework for example) The maintainability sub-characteristics defined in ISO/IEC 25010 are:
|
| Management | How easily a system can be administered, configured, monitored and controlled by the people who run it [33]. |
| Memory optimization | The efficient use of memory (RAM): using no more than needed and releasing it when it is no longer used. Memory leaks often appear only after hours or days of operation and are found with soak tests [34], [35]. |
| Modifiability |
Modifiability encompasses two aspects [36]:
|
| Network topology | Most of the time this will be decided at the solution design stage. However, if users are working from a cruise ship or even living for a few months in the International Space Station where it is almost impossible to deploy new equipment in a timely fashion it might be of importance to your solution architect or supplier. |
| Open source |
Companies, stakeholders or projects might have reasons/biases/beliefs/preferences for or against using open-source software and code. Reasons that qualify or disqualify open source are often based on these criteria:
|
| Operability |
Operability requirements aim to support reliable operations with sufficient performance. The more operational needs the software itself addresses, the less repetitive work remains for staff, who can then focus on improving automated operations and optimizing the system [37]. It can be encompassed in multiple categories such as deployment, monitoring and manageability but always with a set goal of making the solution easier to operate and maintain through automation and reducing repetitive tasks. |
| Operational environment | Your operating environment is the set of external forces within which every organization operates and that influence your business from the outside. Some trends and issues move slowly and do not need constant watching, but keeping an eye on them can make the difference between success and failure. An issue that seems irrelevant to you may be someone else’s reality [38]. |
| Performance and response time | This can mean different things to different people, but in the end the goal is to provide a good quality of experience (QoE) to the end-user. Response time measures the performance of a single transaction or query: the time between the moment a user sends a request and the moment the application indicates that the request is complete [39]. |
| Physical | Constraints on the physical characteristics of a system or its hardware: size, weight, power consumption, heat, noise, and resistance to temperature, humidity, dust, shocks or vibration [40], [41]. |
| Platform compatibility | Compatible with a given platform: a specific type of computer hardware, as in “platform-independent”, or a specific combination of hardware, operating system and/or compiler, as when a program is said to have been ported to several platforms [42]. |
| Privacy |
Privacy concerns cover a wide range of information that can be collected, aggregated and acted upon.
They are often covered by industry codes, self-regulation, co-regulation, legislation and laws. |
| Portability | A software unit is portable across a class of environments to the degree that transporting and adapting it to a new environment in that class costs less than redeveloping it [43]. |
| Quality | In this view, quality means satisfying applicable specifications: producing products or delivering services whose measurable characteristics meet a fixed, usually numerical, set of specifications [44]. |
| Readability |
Software is built on requirements that are likely to change, because it interacts with a real world that keeps changing. When they change, a developer, often not the original author, must read the existing code, understand its abstractions, find what needs to change and then make the change. Readable code makes this work easier, supports the evolution of the codebase and saves future developers time and effort. Readability matters most in large projects with many developers, where code will be modified by people other than its author [45]. |
| Reliability | Reliability engineering is a sub-discipline of systems engineering focused on dependability throughout the life cycle of a product. Reliability describes the ability of a system or component to function under stated conditions for a specified period of time. It is closely related to availability, the ability of a component or system to function at a specific moment or interval of time [46] (e.g., monitoring, mean time between/to failures – MTBF/MTTF). |
| Reporting |
Unless required, paper reports coming out of printers the size of a washing machine are a thing of the past. Reporting is often an afterthought in a project even with the new delivery methods available to IT. Analysts should define these requirements early in the project stage as they might have direct impacts on the solution architecture and data storage.
|
| Resilience |
Resilience is the ability of a network or system to provide and maintain an acceptable level of service despite faults and other challenges to normal operation [47]. For the applications it serves, this means:
|
| Resource constraints | Constraints related to physical hardware resources such as memory, processor speed, display resolution, network bandwidth. Often the case in embedded systems such as mobile phones, ATMs, IoT devices etc. |
| Reusability | Reuse can take different forms. Compositional reuse builds new software products by assembling existing reusable assets, while generative reuse uses application generators to build new applications from high-level descriptions [48]. |
| Robustness | “The degree to which a system or component can function correctly in the presence of invalid inputs or stressful environmental conditions” [36] |
| Safety | The ability of a system to avoid causing harm to people, property or the environment, including when things go wrong [49]. |
| Scalability (horizontal, vertical) |
Scalability is the ability of a network, system or process to accommodate a growing number of elements or objects, to handle increasing volumes of work gracefully, and/or to be enlarged [50]. Four types of scalability are commonly distinguished:
|
| Schedule | Time constraints on developing and delivering a solution: deadlines, milestones, release windows and dates imposed by laws, contracts or market events [51], [52]. |
| Security |
Main domains where security is of concern for a solution:
|
| Software, tools and standards | The obligation to use, or to be compatible with, specific software products, tools, frameworks, languages or technical standards, often those on the organization’s approved technology list [53]. |
| Stability |
Stability is not related to the concept of a software being “stable” from a user standpoint but is a model tightly intertwined with the reusability and maintainability categories. The Software Stability Model is built using three main concepts [54]:
|
| Supportability | Also known as serviceability, supportability is the ability of technical support staff to install, configure and monitor a solution, to detect faults and trace them to their root cause, and to maintain the hardware or software to restore service. Including serviceability features in the requirements usually makes maintenance more efficient, lowers operating costs and helps preserve business continuity. Supportability is one of the main requirement categories of the RUP/FURPS+ model [3]. |
| Testability | In short, these requirements are documented to make sure that everything can be tested. Testability is the degree to which a system or component makes it possible to set test criteria and to run tests that show whether those criteria are met [36]. The more testable an artifact is (a software system, a module, or a requirements or design document), the easier it is to find its faults through testing. |
| Throughput | The amount of work that a system or component can perform in a given period of time [36], for example transactions, requests or messages per second. Throughput is different from response time: a system can answer each request quickly and still slow down when many requests arrive at once, so both must be specified. |
| Training | The learning effort and the materials needed so that users, operators and support staff can use the solution effectively [55], [56]. |
| Transparency | In human-computer interaction, a change to a system is transparent when its users do not notice it: the system keeps its external interface as unchanged as possible while its internal behavior changes [57]. More broadly, transparency also describes how far a system makes its behavior, its decisions and its use of data visible and understandable to users and stakeholders. |
| Usability |
Usability is a quality attribute that assesses how easy user interfaces are to use. The term also refers to methods for improving ease of use during design. Usability has five quality components [58]:
|
| Volume | Refers to the expected volume of users, requests and data a solution will have to deal with. Further down the road of development these requirements will make it to load/volume testing. |
6. FAQ
A functional requirement describes what the system does; a non-functional requirement describes how well it must do it, such as how fast, how secure or how available. The same need can be either, depending on who reads it.
No. Every category should be reviewed, but many will be marked “not applicable”. What matters is that the decision is recorded and can be traced.
None is complete on its own. ISO/IEC 25010 is the international reference for quality models; FURPS+, CISQ and SNAP add other angles. This checklist combines them.
7. Acronyms, Initialisms & Terms
Acronyms are abbreviations pronounced as words (like NASA); initialisms are spelled out letter by letter (like FBI). The classification below follows common pronunciation.
Acronyms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| COBIT | Control Objectives for Information and Related Technologies | Framework from ISACA for the governance and management of enterprise IT. | [59] |
| EULA | End-user license agreement | Contract between the publisher of a software product and the person or organization using it. | [60] |
| FINTRAC | Financial Transactions and Reports Analysis Centre of Canada | Canada’s financial intelligence unit, responsible for anti-money-laundering compliance. | [61] |
| FIRST | Forum of Incident Response and Security Teams | International association of security teams; it maintains the CVSS. | [24] |
| FURPS+ | Functionality, Usability, Reliability, Performance, Supportability (+ constraints) | Model used to classify software requirements, popularized with the Rational Unified Process. | [3] |
| HIPAA | Health Insurance Portability and Accountability Act | U.S. law that protects the privacy and security of health information. | [62] |
| ISO | International Organization for Standardization | Independent international body that publishes standards, such as ISO/IEC 25010. | [63] |
| ITIL | Information Technology Infrastructure Library | Set of best practices for IT service management. | [64] |
| NIST | National Institute of Standards and Technology | U.S. agency that publishes standards and guidance, including on cybersecurity. | [65] |
| OSFI | Office of the Superintendent of Financial Institutions | Federal regulator of banks, insurers and pension plans in Canada. | [66] |
| PIPEDA | Personal Information Protection and Electronic Documents Act | Canadian federal privacy law for the private sector. | [67] |
| RAM | Random-access memory | Working memory of a computer, where running programs keep their data. | [68] |
| RUP | Rational Unified Process | Iterative software development process created by Rational Software, later part of IBM. | [69] |
| SNAP | Software Non-functional Assessment Process | IFPUG method that measures the size of the non-functional part of software, as a complement to function points. | [70] |
| SOX | Sarbanes-Oxley Act | U.S. law of 2002 on financial reporting and internal controls of public companies. | [71] |
| SQuaRE | Systems and software Quality Requirements and Evaluation | Family of ISO/IEC 25000 standards that includes the ISO/IEC 25010 quality model. | [1] |
| VoIP | Voice over Internet Protocol | Technology that carries telephone calls over an IP network. | [72] |
Initialisms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| AI | Artificial intelligence | Computer systems that perform tasks normally requiring human intelligence. | [73] |
| API | Application programming interface | Defined way for one piece of software to call another and exchange data. | [74] |
| ATM | Automated teller machine | Self-service machine that lets bank customers withdraw cash and perform transactions. | [75] |
| BO | Business object | In the Software Stability Model, an object that is stable inside but adapts its behavior to the application. | [54] |
| CI | Configuration item | Any component that must be managed to deliver an IT service, such as a server or an application. | [76] |
| CISM | Certified Information Security Manager | ISACA certification for information security managers. | [77] |
| CM | Configuration management | Process that keeps a system’s components and their relationships accurately recorded over time. | [78] |
| CMDB | Configuration management database | Database that stores configuration items and their relationships. | [79] |
| CVSS | Common Vulnerability Scoring System | Open standard for rating the severity of security vulnerabilities from 0 to 10. | [24] |
| DR | Disaster recovery | Policies and procedures for restoring IT systems after a disaster. | [80] |
| EBT | Enduring business theme | In the Software Stability Model, a core concept of the business that does not change over time. | [54] |
| EU | European Union | Political and economic union of European countries; source of the GDPR. | [81] |
| EVA | Economic value added | Measure of the profit a business makes above the cost of the capital it uses. | [82] |
| FAQ | Frequently asked questions | List of common questions with their answers. | [83] |
| GDPR | General Data Protection Regulation | European Union regulation on data protection and privacy. | [84] |
| GLBA | Gramm-Leach-Bliley Act | U.S. law that requires financial institutions to protect customers’ personal information. | [85] |
| IBM | International Business Machines | U.S. technology company; it acquired Rational Software and the RUP. | [86] |
| IEC | International Electrotechnical Commission | International body that publishes standards for electrical and electronic technologies, often jointly with ISO. | [87] |
| IEEE | Institute of Electrical and Electronics Engineers | Professional association that publishes engineering standards and glossaries. | [88] |
| IO | Industrial object | In the Software Stability Model, a concrete, replaceable object tied to a specific technology or implementation. | [54] |
| IoT | Internet of things | Physical devices with sensors and software that connect and exchange data over networks. | [89] |
| IRR | Internal rate of return | Discount rate at which the net present value of an investment equals zero. | [90] |
| IT | Information technology | Use of computers and networks to store, process and exchange information. | [91] |
| ITSM | IT service management | Activities that design, deliver and manage IT services for customers. | [92] |
| MTBF | Mean time between failures | Average time a repairable system runs between two failures. | [93] |
| MTTF | Mean time to failure | Average time a non-repairable component runs before it fails. | [93] |
| NFR | Non-functional requirement | Requirement that describes how well a system must work (its qualities, such as speed or security) rather than what it does. | [94] |
| PCI DSS | Payment Card Industry Data Security Standard | Security standard for organizations that handle payment card data. | [95] |
| QoE | Quality of experience | Overall satisfaction of the user with a service, as the user perceives it. | [96] |
| RFI | Request for information | Document used to collect information from potential suppliers. | [97] |
| RFP | Request for proposal | Document that invites suppliers to submit a proposal for a product or service. | [98] |
| ROI | Return on investment | Ratio of the gain from an investment to its cost. | [99] |
| SI | System integration | Process of joining subsystems or components into one working system. | [100] |
| SLA | Service-level agreement | Agreement between a service provider and its customer on measurable service levels. | [101] |
| SOW | Statement of work | Document that defines the work, deliverables and schedule of a contract. | [102] |
| SSAE | Statement on Standards for Attestation Engagements | AICPA attestation standards; SSAE 18 replaced SSAE 16 in May 2017. | [103] |
| TCO | Total cost of ownership | All direct and indirect costs of an asset over its life cycle. | [104] |
| VM | Virtual machine | Software emulation of a computer that runs its own operating system. | [105] |
Terms
Plain-language definitions of technical and project-management terms used in this article.
| Term | Plain-language definition | Ref. |
|---|---|---|
| Business analyst | Person who identifies business needs and translates them into requirements for a solution. | [106] |
| Elicitation | Gathering requirements from stakeholders through interviews, workshops, observation and document review. | [107] |
| Function point | Unit that measures the amount of business functionality a system provides to its users. | [108] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [109] |
| Traceability | Ability to follow a requirement from its origin to its design, code and tests. | [110] |
8. Sources and Further Reading
- [1] ISO/IEC JTC 1/SC 7 Software and systems engineering, “ISO/IEC 25010:2011 – Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — System and software quality models,” International Organization for Standardization, 03 2011. [Online]. Available: https://www.iso.org/standard/35733.html. [Accessed 01 02 2019].
- [2] Consortium for IT Software Quality, “Code Quality Standards – CISQ,” CISQ, 2018. [Online]. Available: https://it-cisq.org/standards/code-quality-standards/. [Accessed 01 02 2019].
- [3] P. Eeles, “Capturing Architectural Requirements,” IBM – United States, 15 November 2005. [Online]. Available: https://www.ibm.com/developerworks/rational/library/4706.html#N100A7. [Accessed 20 09 2019].
- [4] J. Mylopoulos, L. Chung and E. Yu, “From Object-Oriented to Goal-Oriented Requirements Analysis,” University of Toronto, Toronto, 1999.
- [5] G. Martin, Eliot in perspective: a symposium, Volume 1970,Partie 1, vol. 1970, G. Martin, Ed., Detroit, Michigan: Macmillan, 1970, p. 216.
- [6] F. Gracioppo, Interviewee, « Works as designed, performs as defined. ». [Interview]. January 2017.
- [7] A. Katja and N. Gronau, “An Approach to Increase Adaptability in ERP Systems,” in 2005 Information Recources Management Association International Conference, San Diego, 2005.
- [8] “Booting.” Wikipedia. https://en.wikipedia.org/wiki/Booting (accessed Nov. 19, 2026).
- [9] BMC, “ITIL Capacity Management,” BMC, 2019. [Online]. Available: https://www.bmc.com/blogs/itil-capacity-management/. [Accessed 26 08 2019].
- [10] M. Rouse and J. Biscobing, “What is compliance? – Definition from WhatIs.com,” TechTarget, 04 2015. [Online]. Available: https://searchdatamanagement.techtarget.com/definition/compliance. [Accessed 26 08 2019].
- [11] “Conformance testing.” Wikipedia. https://en.wikipedia.org/wiki/Conformance_testing (accessed Nov. 19, 2026).
- [12] “Conformity assessment.” Wikipedia. https://en.wikipedia.org/wiki/Conformity_assessment (accessed Nov. 19, 2026).
- [13] Wikipedia, “Whole-life cost – Wikipedia,” 16 08 2019. [Online]. Available: https://en.wikipedia.org/wiki/Whole-life_cost#IT_industry_usage. [Accessed 26 08 2019].
- [14] S. Pearlman, “What is Data Integrity and Why Is It Important? – Talend,” talend, 08 08 2019. [Online]. Available: https://www.talend.com/resources/what-is-data-integrity/. [Accessed 26 08 2019].
- [15] OMG, “DCbk,” Adopted Specification of the Object Management Group, Inc., 06 2003. [Online]. Available: https://staff.info.unamur.be/ven/CIS/OMG/Deployment%20and%20Configuration%20of%20Component-based%20Distributed%20Applications.pdf. [Accessed 04 09 2019].
- [16] Editor, “The Importance of Disaster Recovery,” Pronto Marketing, 27 01 2016. [Online]. Available: http://www.techadvisory.org/2016/01/the-importance-of-disaster-recovery/. [Accessed 05 09 2019].
- [17] J. Lienig and H. Bruemmer, “New Design Strategy – Product Durability,” in Fundamentals of Electronic Systems Design, 1 ed., vol. 1, Dresden, Hannover, Springer International Publishing, 2017, pp. 201-203.
- [18] E. Bloom, “Efficiency vs. effectiveness within IT | CIO,” IDG, 31 05 2016. [Online]. Available: https://www.cio.com/article/3076102/efficiency-vs-effectiveness-within-it.html. [Accessed 05 09 2019].
- [19] “Elasticity (computing).” Wikipedia. https://en.wikipedia.org/wiki/Elasticity_(computing) (accessed Nov. 19, 2026).
- [20] “Autoscaling.” Wikipedia. https://en.wikipedia.org/wiki/Autoscaling (accessed Nov. 19, 2026).
- [21] International Organization for Standardization and International Electrotechnical Commission, Information technology — Software Carbon Intensity (SCI) specification, ISO/IEC 21031:2024, Mar. 2024. [Online]. Available: https://www.iso.org/standard/86612.html
- [22] Macha, “Source code escrow – Wikipedia,” Wikimedia Foundation, Inc., 27 06 2019. [Online]. Available: https://en.wikipedia.org/wiki/Source_code_escrow#cite_note-Heusler_178-2. [Accessed 09 09 2019].
- [23] “Algorithmic bias.” Wikipedia. https://en.wikipedia.org/wiki/Algorithmic_bias (accessed Nov. 19, 2026).
- [24] Forum of Incident Response and Security Teams (FIRST), “Common Vulnerability Scoring System Version 4.0: Specification Document,” Nov. 2023. [Online]. Available: https://www.first.org/cvss/v4.0/specification-document
- [25] J. Pitt, “From Usability to Exploitability Digital Technology and Non-Parcipatory Design – IEEE Technology and Society,” IEEE, 21 09 2018. [Online]. Available: https://technologyandsociety.org/from-usability-to-exploitability/. [Accessed 10 09 2019].
- [26] N. Johansson, A. Löfgren and C. M. Olsson, “Designing for extensibility: An action research study of maximising extensibility by means of design principles.,” Göteborgs universitetsbibliotek, Gothenburg, 2009.
- [27] J.-C. Laprie, “Dependable computing and fault tolerance: concepts and terminology,” in Proceedings of 15th International Symposium on Fault-Tolerant Computing, Toulouse, 1985.
- [28] “Flexibility (engineering).” Wikipedia. https://en.wikipedia.org/wiki/Flexibility_(engineering) (accessed Nov. 19, 2026).
- [29] “Software bloat.” Wikipedia. https://en.wikipedia.org/wiki/Software_bloat (accessed Nov. 19, 2026).
- [30] Techopedia, “What is System Integration (SI)? – Definition from Techopedia,” Janalta Interactive Inc., [Online]. Available: https://www.techopedia.com/definition/9614/system-integration-si. [Accessed 11 09 2019].
- [31] B. Esselink, “The Evolution of Localization,” 2003. [Online]. Available: http://isg.urv.es/library/papers/Esselink_Evolution.pdf (deprecated). [Accessed 11 09 2019].
- [32] J. McCreesh, “Definition: Interoperability,” Interoperability Working Group, [Online]. Available: http://interoperability-definition.info/en/. [Accessed 11 09 2019].
- [33] “Systems management.” Wikipedia. https://en.wikipedia.org/wiki/Systems_management (accessed Nov. 19, 2026).
- [34] “Memory leak.” Wikipedia. https://en.wikipedia.org/wiki/Memory_leak (accessed Nov. 19, 2026).
- [35] “Soak testing.” Wikipedia. https://en.wikipedia.org/wiki/Soak_testing (accessed Nov. 19, 2026).
- [36] The Institute of Electrical and Electronics Engineers, “IEEE Standard Glossary of Software Engineering Terminology,” The Institute of Electrical and Electronics Engineers, New York, 1990.
- [37] eBook Shop for iT-Professionals, “Template Software Operability Requirements – Overview,” eBook Shop for iT-Professionals, [Online]. Available: http://www.it-checklists.com/Operability-Requirements-Checklist-Template.html. [Accessed 12 09 2019].
- [38] E. Olsen, “SWOT Analysis: Finding Opportunities in Your Operating Environment,” John Wiley & Sons inc., 11 2011. [Online]. Available: https://www.dummies.com/business/business-strategy/swot-analysis-finding-opportunities-in-your-operating-environment/. [Accessed 12 09 2019].
- [39] loadfocus, “What is Response Time in Performance Testing?,” loadfocus, 07 03 2013. [Online]. Available: https://loadfocus.com/blog/2013/07/what-is-response-time-in-performance-testing/. [Accessed 27 09 2019].
- [40] “Rack unit.” Wikipedia. https://en.wikipedia.org/wiki/Rack_unit (accessed Nov. 19, 2026).
- [41] “IP code.” Wikipedia. https://en.wikipedia.org/wiki/IP_code (accessed Nov. 19, 2026).
- [42] D. Howe, “platform from FOLDOC,” 07 12 1994. [Online]. Available: http://foldoc.org/platform. [Accessed 26 09 2019].
- [43] D. J. Mooney, “Bringing Portability to the Software Process,” West Virginia University – Dept. of Statistics and Computer Science, 2000. [Online]. Available: https://pdfs.semanticscholar.org/ef08/695a3e437ea58f48e247f72b4bac61140c5c.pdf. [Accessed 26 09 2019].
- [44] B. P. Crosby, E. W. Deming and M. J. Juran, “Introduction to Quality,” in Quality Management System Handbook for Product Development Companies, vol. 1, Boca Raton, Florida: CRC Press, 2005, p. 2.
- [45] S. V. Fernandez, “Code readability matters | Info | The Guardian,” The Guardian, 01 29 2019. [Online]. Available: https://www.theguardian.com/info/2019/jan/29/code-readability-matters. [Accessed 28 09 2019].
- [46] Wyatts, “Reliability engineering – Wikipedia,” Wikipedia, 05 08 2019. [Online]. Available: https://en.wikipedia.org/wiki/Reliability_engineering. [Accessed 29 09 2019].
- [47] J. P. G. Sterbenz, D. Hutchison, E. K. Çetinkaya, A. Jabbar, J. P. Rohrer, M. Schöller and P. Smith, “Resilience and survivability in communication networks: Strategies, principles, and survey of disciplines,” Computer Networks, vol. 54, no. 8, pp. 1245–1265, Jun. 2010, doi: 10.1016/j.comnet.2010.03.005.
- [48] The Lombard Hill Group, “What is Software Reuse?,” The Lombard Hill Group, 2018. [Online]. Available: http://softwarereuse.x10host.com/Article/. [Accessed 29 09 2019].
- [49] “Functional safety.” Wikipedia. https://en.wikipedia.org/wiki/Functional_safety (accessed Nov. 19, 2026).
- [50] A. B. Bondi, “Characteristics of Scalability and Their Impact on Performance,” in WOSP ’00 Proceedings of the 2nd international workshop on Software and performance, Toronto, 2000.
- [51] “Schedule (project management).” Wikipedia. https://en.wikipedia.org/wiki/Schedule_(project_management) (accessed Nov. 19, 2026).
- [52] “Milestone (project management).” Wikipedia. https://en.wikipedia.org/wiki/Milestone_(project_management) (accessed Nov. 19, 2026).
- [53] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 19, 2026).
- [54] M. E. Fayad and A. Altman, “Thinking objectively: An introduction to software stability,” Communications of the ACM, vol. 44, no. 9, p. 95, Sep. 2001. [Online]. Available: https://cacm.acm.org/opinion/thinking-objectively/
- [55] “Training.” Wikipedia. https://en.wikipedia.org/wiki/Training (accessed Nov. 19, 2026).
- [56] “Learnability.” Wikipedia. https://en.wikipedia.org/wiki/Learnability (accessed Nov. 19, 2026).
- [57] Wikipedia, “Transparency (human–computer interaction),” Wikimedia Foundation. [Online]. Available: https://en.wikipedia.org/wiki/Transparency_(human–computer_interaction). [Accessed: Nov. 19, 2026].
- [58] J. Nielsen, “Usability 101: Introduction to Usability,” Nielsen Norman Group, 03 01 2012. [Online]. Available: https://www.nngroup.com/articles/usability-101-introduction-to-usability/. [Accessed 02 10 2019].
- [59] “COBIT.” Wikipedia. https://en.wikipedia.org/wiki/COBIT (accessed Nov. 19, 2026).
- [60] “End-user license agreement.” Wikipedia. https://en.wikipedia.org/wiki/End-user_license_agreement (accessed Nov. 19, 2026).
- [61] “Financial Transactions and Reports Analysis Centre of Canada.” Wikipedia. https://en.wikipedia.org/wiki/Financial_Transactions_and_Reports_Analysis_Centre_of_Canada (accessed Nov. 19, 2026).
- [62] “Health Insurance Portability and Accountability Act.” Wikipedia. https://en.wikipedia.org/wiki/Health_Insurance_Portability_and_Accountability_Act (accessed Nov. 19, 2026).
- [63] “International Organization for Standardization.” Wikipedia. https://en.wikipedia.org/wiki/International_Organization_for_Standardization (accessed Nov. 19, 2026).
- [64] “ITIL.” Wikipedia. https://en.wikipedia.org/wiki/ITIL (accessed Nov. 19, 2026).
- [65] “National Institute of Standards and Technology.” Wikipedia. https://en.wikipedia.org/wiki/National_Institute_of_Standards_and_Technology (accessed Nov. 19, 2026).
- [66] “Office of the Superintendent of Financial Institutions.” Wikipedia. https://en.wikipedia.org/wiki/Office_of_the_Superintendent_of_Financial_Institutions (accessed Nov. 19, 2026).
- [67] “Personal Information Protection and Electronic Documents Act.” Wikipedia. https://en.wikipedia.org/wiki/Personal_Information_Protection_and_Electronic_Documents_Act (accessed Nov. 19, 2026).
- [68] “Random-access memory.” Wikipedia. https://en.wikipedia.org/wiki/Random-access_memory (accessed Nov. 19, 2026).
- [69] “Rational Unified Process.” Wikipedia. https://en.wikipedia.org/wiki/Rational_Unified_Process (accessed Nov. 19, 2026).
- [70] “SNAP Points.” Wikipedia. https://en.wikipedia.org/wiki/SNAP_Points (accessed Nov. 19, 2026).
- [71] “Sarbanes–Oxley Act.” Wikipedia. https://en.wikipedia.org/wiki/Sarbanes–Oxley_Act (accessed Nov. 19, 2026).
- [72] “Voice over IP.” Wikipedia. https://en.wikipedia.org/wiki/Voice_over_IP (accessed Nov. 19, 2026).
- [73] “Artificial intelligence.” Wikipedia. https://en.wikipedia.org/wiki/Artificial_intelligence (accessed Nov. 19, 2026).
- [74] “API.” Wikipedia. https://en.wikipedia.org/wiki/API (accessed Nov. 19, 2026).
- [75] “Automated teller machine.” Wikipedia. https://en.wikipedia.org/wiki/Automated_teller_machine (accessed Nov. 19, 2026).
- [76] “Configuration item.” Wikipedia. https://en.wikipedia.org/wiki/Configuration_item (accessed Nov. 19, 2026).
- [77] “Certified Information Security Manager.” Wikipedia. https://en.wikipedia.org/wiki/Certified_Information_Security_Manager (accessed Nov. 19, 2026).
- [78] “Configuration management.” Wikipedia. https://en.wikipedia.org/wiki/Configuration_management (accessed Nov. 19, 2026).
- [79] “Configuration management database.” Wikipedia. https://en.wikipedia.org/wiki/Configuration_management_database (accessed Nov. 19, 2026).
- [80] “Disaster recovery.” Wikipedia. https://en.wikipedia.org/wiki/Disaster_recovery (accessed Nov. 19, 2026).
- [81] “European Union.” Wikipedia. https://en.wikipedia.org/wiki/European_Union (accessed Nov. 19, 2026).
- [82] “Economic value added.” Wikipedia. https://en.wikipedia.org/wiki/Economic_value_added (accessed Nov. 19, 2026).
- [83] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [84] “General Data Protection Regulation.” Wikipedia. https://en.wikipedia.org/wiki/General_Data_Protection_Regulation (accessed Nov. 19, 2026).
- [85] “Gramm–Leach–Bliley Act.” Wikipedia. https://en.wikipedia.org/wiki/Gramm–Leach–Bliley_Act (accessed Nov. 19, 2026).
- [86] “IBM.” Wikipedia. https://en.wikipedia.org/wiki/IBM (accessed Nov. 19, 2026).
- [87] “International Electrotechnical Commission.” Wikipedia. https://en.wikipedia.org/wiki/International_Electrotechnical_Commission (accessed Nov. 19, 2026).
- [88] “Institute of Electrical and Electronics Engineers.” Wikipedia. https://en.wikipedia.org/wiki/Institute_of_Electrical_and_Electronics_Engineers (accessed Nov. 19, 2026).
- [89] “Internet of things.” Wikipedia. https://en.wikipedia.org/wiki/Internet_of_things (accessed Nov. 19, 2026).
- [90] “Internal rate of return.” Wikipedia. https://en.wikipedia.org/wiki/Internal_rate_of_return (accessed Nov. 19, 2026).
- [91] “Information technology.” Wikipedia. https://en.wikipedia.org/wiki/Information_technology (accessed Nov. 19, 2026).
- [92] “IT service management.” Wikipedia. https://en.wikipedia.org/wiki/IT_service_management (accessed Nov. 19, 2026).
- [93] “Mean time between failures.” Wikipedia. https://en.wikipedia.org/wiki/Mean_time_between_failures (accessed Nov. 19, 2026).
- [94] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 19, 2026).
- [95] “Payment Card Industry Data Security Standard.” Wikipedia. https://en.wikipedia.org/wiki/Payment_Card_Industry_Data_Security_Standard (accessed Nov. 19, 2026).
- [96] “Quality of experience.” Wikipedia. https://en.wikipedia.org/wiki/Quality_of_experience (accessed Nov. 19, 2026).
- [97] “Request for information.” Wikipedia. https://en.wikipedia.org/wiki/Request_for_information (accessed Nov. 19, 2026).
- [98] “Request for proposal.” Wikipedia. https://en.wikipedia.org/wiki/Request_for_proposal (accessed Nov. 19, 2026).
- [99] “Return on investment.” Wikipedia. https://en.wikipedia.org/wiki/Return_on_investment (accessed Nov. 19, 2026).
- [100] “System integration.” Wikipedia. https://en.wikipedia.org/wiki/System_integration (accessed Nov. 19, 2026).
- [101] “Service-level agreement.” Wikipedia. https://en.wikipedia.org/wiki/Service-level_agreement (accessed Nov. 19, 2026).
- [102] “Statement of work.” Wikipedia. https://en.wikipedia.org/wiki/Statement_of_work (accessed Nov. 19, 2026).
- [103] “SSAE No. 18.” Wikipedia. https://en.wikipedia.org/wiki/SSAE_No._18 (accessed Nov. 19, 2026).
- [104] “Total cost of ownership.” Wikipedia. https://en.wikipedia.org/wiki/Total_cost_of_ownership (accessed Nov. 19, 2026).
- [105] “Virtual machine.” Wikipedia. https://en.wikipedia.org/wiki/Virtual_machine (accessed Nov. 19, 2026).
- [106] “Business analyst.” Wikipedia. https://en.wikipedia.org/wiki/Business_analyst (accessed Nov. 19, 2026).
- [107] “Requirements elicitation.” Wikipedia. https://en.wikipedia.org/wiki/Requirements_elicitation (accessed Nov. 19, 2026).
- [108] “Function point.” Wikipedia. https://en.wikipedia.org/wiki/Function_point (accessed Nov. 19, 2026).
- [109] “Project stakeholder.” Wikipedia. https://en.wikipedia.org/wiki/Project_stakeholder (accessed Nov. 19, 2026).
- [110] “Requirements traceability.” Wikipedia. https://en.wikipedia.org/wiki/Requirements_traceability (accessed Nov. 19, 2026).
Written by Philippe Huard · LinkedIn · Last updated: November 19, 2026 · Header photo by @jakubzerdzicki; inline photo by @ttepavac, both on Unsplash.




