🌁Software Engineering: Failure (Definitions)

"[...] a fault is a potential failure, which can cause an incorrect result (failure) in the future, or may have already caused one. The failure may not have observable consequences, however, and so may not be reported as a problem." (Richard D Stutzke, "Estimating Software-Intensive Systems: Projects, Products, and Processes", 2005)

"1. Deviation of the component or system from its expected delivery, service, or result. (For a test result, the observed result and the expected [specified or predicted] result do not match.) 2. Result of a fault that, during test execution, shows an externally observable wrong result. 3. Behavior of a test object that does not conform to a specified functionality that should be suitable for its use." (Tilo Linz et al, "Software Testing Foundations, 4th Ed", 2014)

"The condition of not achieving the desired end results." (Ken Sylvester, "Negotiating in the Leadership Zone", 2015)

"A system failure is an event that occurs when the delivered service deviates from correct service (implementing system function). A system may fail either because it does not comply with the specification or because the specification did not adequately describe its function." (O Sami Saydjari, "Engineering Trustworthy Systems: Get Cybersecurity Design Right the First Time", 2018)

"Deviation of the component or system from its expected delivery, service or result." (Software Quality Assurance)

"Loss of ability to operate to specification, or to deliver required output" (ITIL)

"The inability of a system or component to perform its required functions within specified performance requirements. The fault tolerance discipline distinguishes between a human action (a mistake), its manifestation (a hardware or software fault), the result of the fault (a failure), and the amount by which the results are incorrect (the error)." (IEEE Std 610.12-1990) 

🌁Software Engineering: User Story (Definitions)

"Informal description of a functional requirement or product property in XP. A user story serves as the basis for acceptance tests that formally check whether the product complies with the described function or property." (Johannes Link & Peter Fröhlich, "Unit Testing in Java", 2003)

"A requirement formulated into a small number of sentences in the user’s natural language. User stories are common in Extreme Programming (XP)." (Bruce P Douglass, "Real-Time Agility", 2009)

"A short narrative that explains who wants something to happen in a piece of software, what they want, and why they want it." (Jon Radoff, "Game On: Energize Your Business with Social Media Games", 2011)

"A narrative description of a software requirement, function, feature, or quality attribute presented as a narrative of desired user interactions with a software system." (Project Management Institute, "Software Extension to the PMBOK® Guide" 5th Ed., 2013)

"A short story explaining how the system will let the user do something." (Rod Stephens, "Beginning Software Engineering", 2015)

"A tool used in Agile software development to capture a description of a software feature from an end-user perspective. The user story describes the type of user, what he or she wants, and why. A user story helps to create a simplified description of a requirement." (Pierre Pureur & Murat Erder, "Continuous Architecture", 2015)

"Description of the functionality that a product should have, written from the perspective of the user. A very simplified and focused requirement description." (Pamela Schure & Brian Lawley, "Product Management For Dummies", 2017)

"User stories are short, text-based descriptions of functionality required by a stakeholder group." (Cate McCoy & James L Haner, "CAPM Certified Associate in Project Management Practice Exams", 2018)

"A high-level user or business requirement commonly used in agile software development, typically consisting of one or more sentences in the everyday or business language capturing what functionality a user needs, any non-functional criteria, and also includes acceptance criteria. " (ISTQB)

Software Engineering: XML Namespace (Definitions)

"A collection of element and attribute names designed to reduce confusion and ambiguity when dealing with XML documents. Generally available for consultation from a commonly available Internet address." (Robert D. Schneider and Darril Gibson, "Microsoft SQL Server 2008 All-In-One Desk Reference For Dummies", 2008)

"The set of unique names used to identify objects within a well-defined domain, particularly relevant for XML applications. An XML Namespace is a W3C recommendation for providing uniquely named elements and attributes in an XML instance. A namespace is declared using the reserved XML attribute xmlns, the value of which must be a URI (Uniform Resource Identifier) reference." (J P Getty Trust, "Introduction to Metadata" 2nd Ed., 2008)

"A defined domain within which a name is guaranteed to be unique and findable. A reusable reference glossary of XML attributes found at a URL address. Entity and attribute names used in XML documents can be easily qualified by associating them with namespaces identified by URL references." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

"A namespace is the metadata realm in which a metadata tag applies. The purpose of a namespace is to distinguish metadata tags that have the same name, but a different meaning." (Jules H Berman, "Principles of Big Data: Preparing, Sharing, and Analyzing Complex Information", 2013)

"In XML and XQuery, a uniform resource identifier (URI) that provides a unique name to associate with the element, attribute, and type definitions in an XML schema or with the names of elements, attributes, types, functions, and errors in XQuery expressions." (Sybase, "Open Server Server-Library/C Reference Manual", 2019)

"A unique identifier that indicates the names of particular data elements or attributes used within an XML file." (Microfocus)

"A collection of names that is used to identify elements, types, and attributes in XML documents identified in a URI reference" (RFC 3986)

🌁Software Engineering: Nonfunctional Requirement (Definitions)

"Non-functional requirements have no direct impact on functionality. As regards software, non-functional requirements include complexity, level of nesting, testability, and maintainability. Non-functional requirements may, for example, result from the operational environment, e.g., requirements regarding a temperature range in which a system needs to work correctly (e.g., –58 to 176 degrees Fahrenheit)." (Lars Dittmann et al, "Automotive SPICE in Practice", 2008)

"Technical requirements for an IT system, including performance, reliability, security, monitoring, and operational environments." (Tilak Mitra et al, "SOA Governance", 2008)

"Defines the quality aspects a system should possess to meet its functional requirements. Other terms for nonfunctional requirements are constraints, quality attributes, and nonbehavioral requirements." (Mark S Merkow & Lakshmikanth Raghavan, "Secure and Resilient Software Development", 2010)

"A description of expected operation of a system separate independent of any specific tasks or functions, and may not be measureable in the same terms as other requirements. Includes reliability, efficiency, portability, etc." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

"A requirement that does not directly relate to functionality but to how well or with which quality the system fulfills its function. Its implementation has a great influence on how satisfied the customer or user is with the system. The attributes from [ISO 9126] are reliability, efficiency, usability, maintainability, and portability. The attributes from [ISO 25010] are performance efficiency, compatibility, usability, reliability, security, maintainability, and portability." (Tilo Linz et al, "Software Testing Foundations" 4th Ed., 2014)

"Statements about the quality of an application’s behavior or constraints on how it produces a wanted result such as the application’s performance, reliability, and security characteristics." (Rod Stephens, "Beginning Software Engineering", 2015)

"Nonfunctional Requirements 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." (Dean Leffingwell, "SAFe 4.5 Reference Guide: Scaled Agile Framework for Lean Enterprises" 2nd Ed, 2018)

 "A requirement that does not relate to functionality, but to attributes of such as reliability, efficiency, usability, maintainability and portability." (Software Quality Assurance)

🌁Software Engineering: Test Plan (Definitions)

"Test case scenarios written to test the different functionalities of the system and make sure it meets requirements." (Timothy J  Kloppenborg et al, "Project Leadership", 2003)

"A document describing the scope, approach, characteristics and features to be tested, necessary tasks, resources, task schedule, responsibilities, and risks." (Richard D Stutzke, "Estimating Software-Intensive Systems: Projects, Products, and Processes", 2005)

[engagement test plan:] "A plan designed to gather sufficient appropriate evidence to support an evaluation of how well the key controls function. This may be developed as part of an engagement work program or may replace the engagement work program." (Sally-Anne Pitt, "Internal Audit Quality", 2014)

[level test plan:] "A plan for a specified level of testing. It identifies the items being tested, the features to be tested, the testing tasks to be performed, the personnel responsible for each task, and the associated risk(s). In the title of the plan, the word level is replaced by the organization’s name for the particular level being documented by the plan (e.g., Component Test Plan, Component Integration Test Plan, System Test Plan, and Acceptance Test Plan)." (Tilo Linz et al, "Software Testing Foundations" 4th Ed, 2014)

"It identifies, among other test items, the features to be tested, the testing tasks, who will do each task, the degree of tester independence, the test environment, the test design techniques, and the techniques for measuring results with a rationale for their choice. Additionally, risks requiring contingency planning are described. Thus, a test plan is a record of the test planning process. The document can be divided into a master test plan or a level test plan." (Tilo Linz et al, "Software Testing Foundations, 4th Ed", 2014)

"A document that specifies how a program is to be tested" (Nell Dale & John Lewis, "Computer Science Illuminated" 6th Ed., 2015)

"A document describing the scope, approach, resources and schedule of intended test activities. It identifies amongst others test items, the features to be tested, the testing tasks, who will do each task, degree of tester independence, the test environment, the test design techniques and entry and exit criteria to be used, and the rationale for their choice, and any risks requiring contingency planning. It is a record of the test planning process." (IEEE 829)

"A document that outlines the specific steps that will be performed for a particular test, including the required logistical items and expected outcome or response for each step." (NIST SP 800-84)

[level test plan:] "A test plan that typically addresses one test level." (ISTQB)

🌁Software Engineering: Deployment (Definitions)

"The process whereby software is installed into an operational environment." (Kim Haase et al, "The J2EE™ Tutorial", 2002)

"The process of 'putting the product into service'. Delivering a new or updated product to users. This can be as simple as shipping magnetic media or posting files for downloading. It can involve installing the product at each user site, training the users at the sites, and activating a unique or very complex system, usually because the user lacks the skills and knowledge to do these activities. " (Richard D Stutzke, "Estimating Software-Intensive Systems: Projects, Products, and Processes", 2005)

"The process whereby the results of the data analysis or data mining are provided to the user of the information." (Glenn J Myatt, "Making Sense of Data: A Practical Guide to Exploratory Data Analysis and Data Mining", 2006)

[service deployment:] "A governed process that manages the registration and configuration of services and release into production. Service changes and versioning are also managed by this process." (Tilak Mitra et al, "SOA Governance", 2008)

"The act of putting information technology into productive use. Installation puts the system into the production environment. Deployment includes installation, but also includes efforts to train and encourage effective use." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

[staged deployment:] "Deployment that begins with building the application in a fully functional staging environment, so you can practice deployment until you’ve worked out all the kinks." (Rod Stephens, "Beginning Software Engineering", 2015)

"The process of delivering a finished application to the users. Also called implementation or installation." (Rod Stephens, "Beginning Software Engineering", 2015)

"Continuous Deployment is the process that takes validated Features from Continuous Integration and deploys them into the production environment, where they are tested and readied for release. It is the third element in the four-part Continuous Delivery Pipeline of Continuous Exploration (CE), Continuous Integration (CI), Continuous Deployment, and Release on Demand." (Dean Leffingwell, "SAFe 4.5 Reference Guide: Scaled Agile Framework for Lean Enterprises 2nd Ed", 2018)

 "activity responsible for movement of new or changed software, documentation, processes or any other deliverable to the live environment" (ITIL)

"The process whereby software is installed into an operational environment." (Microfocus)

[continuous deployment:] "The technical capabilities to continuously deploy infrastructure, software, and process changes in support of digital business applications or services to customers." (Forrester)

🌁Software engineering: Open Source (Definitions)

"A style of licensing software based on the principle that anyone should be able to copy, use, and improve upon a program's source code, although other restrictions may apply." (Bill Pribyl & Steven Feuerstein, "Learning Oracle PL/SQL", 2001)

"A movement in the software industry that makes programs available along with the source code used to create them so others can inspect and modify how programs work." (Judith Hurwitz et al, "Service Oriented Architecture For Dummies" 2nd Ed., 2009)

"Software provided with all the source code available, enabling developers to contribute changes. Most open software is available for free; although, many companies also license commercial software on an open basis." (Jon Radoff, "Game On: Energize Your Business with Social Media Games", 2011)

"software created by the worldwide user community. Open source software is generally free, can be modified by anyone, and usually doesn't have any single “owner.” Outsourcing: the process of a company arranging with one or more third parties to provide services that the first company could provide but chose not to." (Bill Holtsnider & Brian D Jaffe, "IT Manager's Handbook" 3rd Ed, 2012)

"A movement in the software industry that makes programs available along with the source code used to create them so that others can inspect and modify how programs work. Changes to source code are shared with the community at large." (Marcia Kaufman et al, "Big Data For Dummies", 2013)

"Software is open source if the source code is available to anyone who has access to the software." (Jules H Berman, "Principles of Big Data: Preparing, Sharing, and Analyzing Complex Information", 2013)

"A copyright or licensing system that, compared with conventional commercial licensing schemes, allows wide use and modification of the material." (Mike Harwood, "Internet Security: How to Defend Against Attackers on the Web" 2nd Ed., 2015)

"A program in which the source code is available to the general public for use or modification from its original design free of charge. Common Open Source licenses include the GNU General Public License, GNU Library General Public License, Artistic License, BSD license, Mozilla Public License, and other similar licenses listed at http://www.opensource.org/licenses. Open Source code is typically created as a collaborative effort in which programmers improve on the code and share the changes within the community." (James R Kalyvas & Michael R Overly, "Big Data: A Businessand Legal Guide", 2015)

[Open source platform:] "refers to any program whose source code is made available for use or modification by other users or developers. An open source platform is usually developed as a public collaboration and made freely available." (Accenture)

"Software for which the source code is available under an open licence. Not only can the software be used for free, but users with the necessary technical skills can inspect the source code, modify it and run their own versions of the code, helping to fix bugs, develop new features, etc. Some large open source software projects have thousands of volunteer contributors. The Open Definition was heavily based on the earlier Open Source Definition, which sets out the conditions under which software can be considered open source." (Open Data Handbook)

🌁Software Engineering: Accessibility (Definitions)

"The art of ensuring that, to as large an extent as possible, facilities (such as, for example, Web access) are available  to people whether or not they have impairments of one sort or another." (Tim Berners-Lee, "Weaving the Web", 1999)

"Accessibility is a subfield of human-computer interaction and deals with users with deficiencies. These deficiencies mostly lie in the perception capabilities. For example, users who cannot see or hear as well as other require special consideration during the implementation of user interfaces." (Thomas Mandl, "Automatic Quality Assessment for Internet Pages", 2008)

"The degree to which a system is usable by as many people as possible without modification and is characterized in terms of the ability of users to have physical access to the system, the nature of users’ interface with the system, and the ability to physically retrieve potentially relevant information." (Deepak Khazanchi, "Information Availability", 2009)

"Making system resources available to a wider user community regardless of their geographical locations or the physical capabilities of their access devices." (Heba Kurdi & H S Al-Raweshidy, "Taxonomy of Grid Systems", 2010)

"The quality of a system incorporating hardware or software to engage a flexible, customizable user interface, alternative input and output methods, and greater exposure of screen elements to make the computer usable by people with cognitive, hearing, physical, or visual disabilities." (Microsoft, "SQL Server 2012 Glossary", 2012)

"The design of information systems such that they can be used by everyone, regardless of their ability or disability." (Julius T Nganji, "A Disability-Aware Mentality to Information Systems Design and Development", 2018)

"Any product, service, technology or environment is accessible and available to everyone, including individuals/learners with special needs." (Sunagul Sani-Bozkurt, "Universal Design Principles and Technology-Supported Learning in the Digital Era", 2019)

"In the learning object sense, ensuring that all information is versioned in multi-perceptual ways for the broadest available human use (for example, image information is made available in text format, which is machine/screen reader- and human-readable)." (Shalin Hai-Jew, "Methods for Analyzing and Leveraging Online Learning Data", 2019)

"Requirement that characterizes projects, objects, device, services, settings, easily usable by every kind of user. In particular, it refers to the possibility for an individual with motorial, perceptive, and/or psychical disability to approach public services and cultural initiatives in conditions of safety and independence, in order to remove the so-called 'barriers', both architectural and perceptive, that represent the obstacles for an equal public dimension, that respects disabilities." (Cecilia Cecchini & Miriam Mariani, "Exhibit Design for Architecture: A Non-Digital Method for the Inclusive Communication of an Architecture", 2019)

"The concept used to describe the degree to which practices and environments are able to be understood and utilized by people of differing abilities." (Kathryn R Green & Steven Tolman, "Equitable Means Accessible: Using Universal Design for Learning and Student Development Theory to Inform Online Pedagogy", 2019)

"Extend to which a person can access and use an object, reach a place, or obtain a service." (Sandra Sanchez-Gordon, "Striving for Inclusion in E-Learning and E-Health", 2021)

🌁Software Engineering: Middleware (Definitions)

"An intermediate layer that may consist of either hardware or software that facilitates interaction across dissimilar hardware and network environments." (Microsoft Corporation, "Microsoft SQL Server 7.0 Data Warehouse Training Kit", 2000)

"A general term for any software that allows two separate and usually already existing programs to exchange data without the need for custom coding." (Richard D Stutzke, "Estimating Software-Intensive Systems: Projects, Products, and Processes", 2005)

"Multipurpose software that lives at a layer between the operating system and application in distributed computing environments." (Judith Hurwitz et al, "Service Oriented Architecture For Dummies" 2nd Ed., 2009)

"Computer software or hardware that connects other software components or systems. This technology evolved to provide for interoperability in support of the move to coherent distributed architectures, which are used most often to support complex distributed applications. It includes Web servers, application servers, and similar tools that support application development and delivery. Middleware is especially integral in managing and optimizing a system-of-systems at the enterprise level. Middleware sits “in the middle” between applications that may be working on different operating systems. It is similar to the middle layer of a three-tier single-system architecture, except that it is stretched across multiple systems or applications. " (David Lyle & John G Schmidt, "Lean Integration", 2010)

"Software that connects software components or applications, functioning as a conversion or translation layer or a consolidator and integrator. Middleware enables one application to communicate with another that runs on a different platform or comes from a different vendor, and it allows multiple processes running on one or more machines to interact across a network." (Janice M Roehl-Anderson, "IT Best Practices for Financial Managers", 2010)

"The term refers to software services that are placed between applications and database servers to make the data interchange transparent and efficient." (Paulraj Ponniah, "Data Warehousing Fundamentals for IT Professionals", 2010)

"Software that allows applications to interact across hardware and network environments." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

"software that connects other software." (Bill Holtsnider & Brian D Jaffe, "IT Manager's Handbook" 3rd Ed., 2012)

"Software that connects two otherwise separate applications." (Craig S Mullins, "Database Administration", 2012)

"Software that sits between two or more types of software and translates information between them. Middleware can cover a broad spectrum of software and generally sits between an application and an operating system, a network operating system, or a database management system." (Microsoft, "SQL Server 2012 Glossary", 2012)

🌁Software Engineering: Granularity (Definitions)

"An important software design concept, especially in relation to components. The amount of detail or functionality - from fine to coarse - provided within a service component. One software component can do something quite simple, such as calculate a square root. Or, it can have a great deal of detail and functionality to represent a complex business rule or workflow. The first is fine grained, and the second coarse grained. Developers often aggregate fine-grained services into coarse-grained services to create a business service." (Judith Hurwitz et al, "Service Oriented Architecture For Dummies" 2nd Ed., 2009)

"Loosely defined as the amount of computation done before synchronization is needed. The longer the time between synchronizations, the coarser the granularity will be. Fine-grained parallelism runs the danger of not having enough work assigned to threads to overcome the overhead costs of using threads. Adding more threads, when the amount of computation doesn’t change, only exacerbates the problem. Coarse-grained parallelism has lower overhead costs and tends to be more readily scalable to an increase in the number of threads." (Clay Breshears, "The Art of Concurrency", 2009)

"A description, from "coarse" to "fine", of a computer activity or feature (such as screen resolution, searching and sorting, or time slice allocation) in terms of the size of the units it handles (pixels, sets of data, or time slices). The larger the pieces, the coarser the granularity." (Microsoft, "SQL Server 2012 Glossary", 2012)

"The amount of decomposition applied to the parallelization of an algorithm, and the grain size of that decomposition. If the granularity is too coarse, there are not enough parallel tasks to effectively make use of all parallel hardware units and hide latency. If the granularity is too fine, there are too many parallel tasks and overhead may dominate the computation." (Michael McCool et al, "Structured Parallel Programming", 2012)

🌁Software Engineering: Interface (Definitions)

"(1) A shared boundary across which information is passed. (2) A hardware or software component that connects two or more other components for the purpose of passing information from one to the other. (3) To connect two or more components for the purpose of passing information from one to the other. (4) To serve as a connecting or connected component as in (2)."  (IEEE, "IEEE Standard Glossary of Software Engineering Terminology", 1990)

"(1) A shared boundary between two or more hardware or software components that conveys power and/or information from one to the other (2) To connect two or more components for the purpose of passing power and/or information from one to the other." (Richard D Stutzke, "Estimating Software-Intensive Systems: Projects, Products, and Processes", 2005)

"An interface exists between different systems or between systems and networks when considered within the context of computer technology. An interface can also refer to the way in which people interact with a computer or other type of device (a user interface or graphical user interface). An interface can also have an organizational connotation where one organization works closely with (interfaces with) another. There are other definitions based on the industry context. However, these may be most common to product managers." (Steven Haines, "The Product Manager's Desk Reference", 2008)

"The connection between two components of a system. Analysis is concerned with the data content of an interface, and design is concerned with the behavior and appearance of the interface." (James Robertson et al, "Complete Systems Analysis: The Workbook, the Textbook, the Answers", 2013)

"Interconnection and interrelation between, for example, people, systems, devices, applications, and so on." (Gilbert Raymond & Philippe Desfray, "Modeling Enterprise Architecture with TOGAF", 2014)

🌁Software Engineering: Specification (Definitions)

"A document used in procurement or development that describes the technical requirements for products, components, or services, usually including the procedures to be used to determine that the requirements have been met. Large systems may have multiple levels of specifications. Some specifications are common to multiple systems or products (e.g., interface definitions)." (Richard D Stutzke, "Estimating Software-Intensive Systems: Projects, Products, and Processes", 2005)

"A specific quantifiable set point that typically has a nominal or target value and a tolerance of acceptable values associated with it. This is what results when a team tries to use tools and best practices to fulfill a requirement. Requirements are hopefully completely fulfilled by a final design specification - but many times they are not." (Lynne Hambleton, "Treasure Chest of Six Sigma Growth Methods, Tools, and Best Practices", 2007)

"A detailed coherent statement of particulars. A requirements specification details requirements whereas a design specification details the design of a system or element." (Bruce P Douglass, "Real-Time Agility: The Harmony/ESW Method for Real-Time and Embedded Systems Development", 2009)

"A document that specifies, ideally in a complete, precise, concrete and verifiable form, the requirements or other characteristics of a component or system. It serves the developers as a basis for programming, and it serves the testers as a basis for developing test cases with black box test design methods. (Often, a specification includes procedures for determining whether these requirements have been satisfied.) special software Software developed for one or a group of customers." (Tilo Linz et al, "Software Testing Foundations" 4th Ed, 2014)

"A precise statement of the needs to be satisfied and the essential characteristics that are required." (Project Management Institute, "A Guide to the Project Management Body of Knowledge (PMBOK® Guide )", 2017)

"A statement of the intended functionality of a given system." (O Sami Saydjari, "Engineering Trustworthy Systems: Get Cybersecurity Design Right the First Time", 2018)

"A document that specifies, ideally in a complete, precise and verifiable manner, the requirements, design, behavior, or other characteristics of a system or component, and, often, the procedures for determining whether these provisions have been satisfied" (IEEE 610)

🌁Software Engineering: Baseline (Definitions)

"A set of specifications or work products that has been formally reviewed and agreed on, which thereafter serves as the basis for further development, and which can be changed only through change control procedures capability evaluation An appraisal by a trained team of professionals used as a discriminator to select suppliers, for contract monitoring, or for incentives. Evaluations are used to help decision makers make better acquisition decisions, improve subcontractor performance, and provide insight to a purchasing organization." (Sandy Shrum et al, "CMMI®: Guidelines for Process Integration and Product Improvement", 2003)

"In configuration management, the initial approved technical data package (including, for software, the source code listing) defining a configuration item during the production, operation, maintenance, and logistic support of its life cycle." (Sandy Shrum et al, "CMMI®: Guidelines for Process Integration and Product Improvement", 2003)

"A set of configuration items (software documents and software components) that has been formally reviewed and agreed upon, that thereafter serves as the basis for future development, and that can be changed only through formal change control procedures." (Richard D Stutzke, "Estimating Software-Intensive Systems: Projects, Products, and Processes", 2005)

"(1) A specification, document, software element, hardware item, or product that has been formally reviewed and approved by designated stakeholders at a specific time during the configuration item’s life cycle. Thereafter, it serves as the basis for further development and can be changed only through formal change control procedures. (2) The action of placing any product under formal configuration control." (Richard D Stutzke, "Estimating Software-Intensive Systems: Projects, Products, and Processes", 2005)

"The approved documentation describing all the functional and physical characteristics of a product, and those functional and physical characteristics selected for its acceptance testing." (Richard D Stutzke, "Estimating Software-Intensive Systems: Projects, Products, and Processes", 2005)

"A set of data or information about an aspect of a business (or product) that provides a point of perspective from which future options can be evaluated. A baseline analysis during the product strategy formulation process allows a product manager to assess the past and current business and market environment for a product, so that future strategic options can be considered." (Steven Haines, "The Product Manager's Desk Reference", 2008)

"A configuration describing a particular development level (e.g., a requirements baseline, design baseline, or baseline related to the production of releases). Associated and related configuration items are 'preserved' when forming a baseline, i.e., they are protected against changes." (Lars Dittmann et al, "Automotive SPICE in Practice", 2008)

"Benchmark used as a reference point" (ITIL)

[configuration baseline] "Baseline of a configuration that has been formally agreed and is managed through the Change Management process." (ITIL)

🌁Software Engineering: Scalability (Definitions)

"A characteristic of a system that provides increased performance with the addition of resources. SQL Server is scalable. For example, it can use memory or additional processors to accommodate more user connections." (Microsoft Corporation, "SQL Server 7.0 System Administration Training Kit", 1999)

"The ability to accommodate future growth requirements." (Ralph Kimball & Margy Ross, "The Data Warehouse Toolkit" 2nd Ed., 2002)

"The capacity of a thing to expand to accommodate future requirements." (Sharon Allen & Evan Terry, "Beginning Relational Data Modeling" 2nd Ed., 2005)

"Used to indicate that an application can handle an increased workload to accommodate a growing number of users. Scalability is accomplished by either scaling up (by increasing the hardware capacity of the current server) or scaling out, (by increasing the number of servers)." (Sara Morganand & Tobias Thernstrom , "MCITP Self-Paced Training Kit : Designing and Optimizing Data Access by Using Microsoft SQL Server 2005 - Exam 70-442", 2007)

"The capability of a product, service, or platform to be readily enlarged or expanded to handle greater capacity than offered by a single instantiation, whether through replication, customization, or additional supporting elements." (Steven Haines, "The Product Manager's Desk Reference", 2008)

"The ability of an application to maintain acceptable response time and throughput when the number of simultaneous users increases." (John Goodson & Robert A Steward, "The Data Access Handbook", 2009)

"The ability to support increasing numbers of users in cost-effective increments without adversely affecting business operations." (Paulraj Ponniah, "Data Warehousing Fundamentals for IT Professionals", 2010)

"The ability to scale to support larger or smaller volumes of data and more or less users. The ability to increase or decrease size or capability in cost-effective increments with minimal impact on the unit cost of business and the procurement of additional services." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

"The capability of the software product to be upgraded to accommodate increased loads." (Requirements Engineering Qualifications Board, "Standard glossary of terms used in Requirements Engineering", 2011)

"Being able to add additional capacity incrementally, quickly and as needed." (Linda Volonino & Efraim Turban, "Information Technology for Management 8th Ed", 2011)

"The ability to increase or decrease size or capability in cost-effective increments with minimal impact on the unit cost of business and the procurement of additional services." (Craig S Mullins, "Database Administration", 2012)

"In regard to hardware, the capability to go from small to large amounts of processing power with the same architecture. It also applies to software products such as databases, in which case it refers to the consistency of performance per unit of power as hardware resources increase." (Marcia Kaufman et al, "Big Data For Dummies", 2013)

"The ability of a software application to function well and with minimal loss of performance, despite changing computing environments; the volume of computations, users, or data. Scalable software is able to take full advantage of increases in computing capability such as those that are provided by the use of SMP hardware and threaded processing." (Jim Davis & Aiman Zeid, "Business Transformation: A Roadmap for Maximizing Organizational Insights", 2014)

"It is the capacity of the system to handle increasing amount work without affecting existing system." (Dharmendra T Patel, "Distributed Computing for Internet of Things (IoT)", 2019)

"Ability to perform in agreed function/parameters when the workload or scope changes" (ITIL)

🌁Software Engineering: Failure Modes & Effects Analysis [FMEA] (Definitions)

"A risk-analysis technique that identifies and ranks the potential failure modes of a design or process and then prioritizes improvement actions." (Clyde M Creveling, "Six Sigma for Technical Processes: An Overview for R Executives, Technical Leaders, and Engineering Managers", 2006)

"An approach to analyzing the effect of faults on system reliability." (Bruce P Douglass, "Real-Time Agility: The Harmony/ESW Method for Real-Time and Embedded Systems Development", 2009)

"An analytical procedure in which each potential failure mode in every component of a product is analyzed to determine its effect on the reliability of that component and, by itself or in combination with other possible failure modes, on the reliability of the product or system and on the required function of the component; or the examination of a product (at the system and/or lower levels) for all ways that a failure may occur. For each potential failure, an estimate is made of its effect on the total system and of its impact. In addition, a review is undertaken of the action planned to minimize the probability of failure and to minimize its effects." (For Dummies, "PMP Certification All-in-One For Dummies, 2nd Ed.", 2013)

"Approach that dissects a component into its basic functions to identify flaws and those flaw’s effects." (Adam Gordon, "Official (ISC)2 Guide to the CISSP CBK" 4th Ed., 2015)

"(1) A process for analysis of potential failure modes within a system for classification by severity or determination of the effect of failures on the system. (2) A structured method for analyzing risk by ranking and documenting potential failure mode in a system, design or process. The analysis includes: identification of potential failures and their effects; ranking of factors (e.g., severity, frequency of occurrence, detectability of the potential failures); and identification and results of actions taken to reduce or eliminate risk." (International Aerospace Quality Group)

"A systematic approach to risk identification and analysis of identifying possible modes of failure and attempting to prevent their occurrence." (SQA)

"FMEA (failure modes effects analysis) is a technique used in product life cycle management activities to predict how a product or process might fail and what the effects of that failure might be." (Gartner)