Page History
| Include Page | ||||
|---|---|---|---|---|
|
| Show If | |||||||
|---|---|---|---|---|---|---|---|
| |||||||
|
...
| 11 | W, X, Y, Z |
|---|---|
| 0 | A, B |
| 1 | C, D |
| 2 | E, F |
| 3 | G,H |
| 4 | I, J |
| 5 | K, L |
| 6 | M, N |
| 7 | O, P |
| 8 | Q, R |
| 9 | S, T |
| 10 | U, V |
...
| id | tabs-1 |
|---|
...
Term
...
Definition
...
- stakeholder that acquires or procures a product or service from a supplier (ISO/IEC 12207, ISO/IEC 15288)
- individual or organization that specifies requirements for and accepts delivery of a new or modified software product and its documentation (IEEE 1058-1998)
- individual or organization that acquires or procures a system, software product or software service from a supplier (ISO/IEC 25040) Note: The acquirer may be internal or external to the supplier organization. Acquisition of a software product may involve, but does not necessarily require, a legal contract or a financial transaction between the acquirer and supplier. From the IEEE resource listed in the blue box at the top of this terms list.
...
- systematic, independent and documented process for obtaining audit evidence and evaluating it objectively to determine the extent to which audit criteria are fulfilled
- independent examination of a work product or set of work products to assess compliance with specifications, standards, contractual agreements, or other criteria
- independent examination of a software product, software process, or set of software processes to assess compliance with specifications, standards, contractual agreements, or other criteria
- systematic, independent, documented process for obtaining records, statements of fact, or other relevant information and assessing them objectively, to determine the extent to which specified requirements are fulfilled.
...
| id | tabs-2 |
|---|
...
Term
...
Definition
...
- measurable qualitative or quantitative attribute that is stipulated for a requirement and that indicates a circumstance or event under which a requirement applies
- description of a contingency to be considered in the representation of a problem, or a reference to other procedures to be considered as part of the condition
- true or false logical predicate
- logical predicate involving one or more behavior model elements
- Boolean expression containing no Boolean operators.
...
| id | tabs-3 |
|---|
...
Term
...
Definition
...
- occurrence of a particular set of circumstances
- external or internal stimulus used for synchronization purposes
- change detectable by the subject software
- fact that an action has taken place
- singular moment in time at which some perceptible phenomenological change (energy, matter, or information) occurs at the port of a unit.
...
| id | tabs-4 |
|---|
...
Term
...
Definition
...
| id | tabs-5 |
|---|
...
Term
...
Definition
...
| id | tabs-6 |
|---|
...
Term
...
Definition
...
| id | tabs-7 |
|---|
...
Term
...
Definition
...
| id | tabs-8 |
|---|
...
Term
...
Definition
...
| id | tabs-9 |
|---|
...
Term
...
Definition
...
| id | tabs-10 |
|---|
...
Term
...
Definition
...
- Causes or contributes to a system hazardous condition/event,
- Provides control or mitigation for a system hazardous condition/event,
- Controls safety-critical functions,
- Mitigates damage if a hazardous condition/event occurs,
- Detects, reports, and takes corrective action if the system reaches a potentially hazardous state.
...
In this directive, “software” is defined as
- computer programs, procedures and possibly associated documentation and data pertaining to the operation of a computer system (IEEE 828-2012 IEEE Standard for Configuration Management in Systems and Software Engineering, 2.1)
- all or a part of the programs, procedures, rules, and associated documentation of an information processing system (IEEE 828-2012 IEEE Standard for Configuration Management in Systems and Software Engineering, 2.1) (ISO/IEC 19770-5:2015 Information technology--IT asset management--Overview and vocabulary, 3.34)
- program or set of programs used to run a computer (ISO/IEC 26514:2008 Systems and software engineering--requirements for designers and developers of user documentation, 4.46)
- all or part of the programs which process or support the processing of digital information (ISO/IEC 19770-1:2017 Information technology -- IT asset management -- Part 1: IT asset management systems--Requirements, 3.49)
- part of a product that is the computer program or the set of computer programs (ISO/IEC/IEEE 26513:2017 Systems and software engineering--Requirements for testers and reviewers of information for users, 3.34). This definition applies to software developed by NASA, software developed for NASA, software maintained by or for NASA, COTS, GOTS, MOTS, OSS, reused software components, auto-generated code, embedded software, the software executed on processors embedded in programmable logic devices (see NASA-HDBK-4008), legacy, heritage, applications, freeware, shareware, trial or demonstration software, and open-source software components.
...
- Totality of activities required to provide cost-effective support to a software system.
- Entitlement of additional rights (such as additional functionality, upgrade, or support) for a previously granted software entitlement.
- A set of services a Publisher can sell to a Customer for the ongoing development and delivery of software bug fixes and product upgrades.
...
- Separately compilable piece of code.
- The lowest element in one or more software components.
...
| id | tabs-11 |
|---|
...
Term
...
Definition
...
- The estimated amount or percentage by which an observed or calculated value may differ from the true value.
- A broad and general term used to describe an imperfect state of knowledge or a variability resulting from a variety of factors including, but not limited to, lack of knowledge, the applicability of information, physical variation, randomness or stochastic behavior, indeterminacy, judgment, and approximation. (Source: NPR 8000.4).
...
- Testing of individual routines and modules by the developer or an independent tester (ISO/IEC/IEEE 24765).
- A test of individual programs or modules in order to ensure that there are no analysis or programming errors (ISO/IEC 2382-20).
- Test of individual hardware or software units or groups of related units. (ISO/IEC/IEEE 24765).
...
- Confirmation, through the provision of objective evidence, that the requirements for a specific intended use or application have been fulfilled (ISO/IEC 25000:2014 Systems and software Engineering--Systems and software product Quality Requirements and Evaluation (SQuaRE) -- Guide to SQuaRE, 4.41) (ISO/IEC/IEEE 12207:2017 Systems and software engineering--Software life cycle processes, 3.1.71) (ISO/IEC/IEEE 15288:2015 Systems and software engineering--System life cycle processes, 4.1.53) (ISO/IEC TS 24748-1:2016 Systems and software engineering--Life cycle management--Part 1: Guide for life cycle management, 2.61).
- process of providing evidence that the system, software, or hardware and its associated products satisfy requirements allocated to it at the end of each life-cycle activity, solve the right problem (e.g., correctly model physical laws, implement business rules, and use the proper system assumptions), and satisfy intended use and user needs (IEEE 1012-2017 IEEE Standard for System, Software, and Hardware Verification and Validation, 3.1.35).
- the assurance that a product, service, or system meets the needs of the customer and other identified stakeholders. It often involves acceptance and suitability with external customers. (A Guide to the Project Management Body of Knowledge (PMBOK(R) Guide) -- Fifth Edition) (4) process of evaluating a system or component during or at the end of the development process to determine whether it satisfies specified requirements (IEEE 1012-2017 IEEE Standard for System, Software, and Hardware Verification and Validation, 3.1) Note: Validation in a system life-cycle context is the set of activities ensuring and gaining confidence that a system is able to accomplish its intended use, goals, and objectives. The right system has been built. Validation demonstrates that the system can be used by the users for their specific tasks. "Validated" is used to designate the corresponding status. [ISO 9000:2005] Multiple validations can be carried out if there are different intended uses.
...
| id | tabs-12 |
|---|
...
Term
...
Definition
...
