ISO/IEC/IEEE 24765:2017 Systems and software engineering - Vocabulary

ISO/IEC/IEEE 24765:2017 Systems and software engineering - Vocabulary
https://www.iso.org/standard/71952.html

無償です。ぜひダウンロードしてください。

Systems and software engineering — Vocabulary 単語帳. 
https://qiita.com/kaizen_nagoya/items/6140f01ea158ef9263c8

ISO/IEC JTC1 SC7 Software and System Engineering 
https://qiita.com/kaizen_nagoya/items/48b43f0f6976a078d907

ISO/IEC/IEEE 24765:2017 Systems and software engineering - Vocabulary
https://qiita.com/kaizen_nagoya/items/955e606bd16e4160a49e

# 見る前に書け
あやしげな教材、あやしげな教育では、Wikiを引用したり参照したりして記述していることがあります。Wikiはみるものじゃなくて書くものという技術者の原則（私的主張）を外れています。

Wikipediaに追記する よい記法７つ 仮説(211)
https://qiita.com/kaizen_nagoya/items/7b081d53c214307af75f

Wikipediaが悪いわけではありません。
Wikipediaの内容を評価せずに、おかしいところがあると思えば、追記せずに引用したり、参照するのが駄目ってことです。

じゃ、国際規格が正かというとそうではありません。複数の意見のうちの一部しか採用していなかったり、発行後どんどん古くなっていたり、特定の分野の人たちの内輪だけで通用するような内容のこともあります。
国際規格を引用したり参照したりするときも、正誤表をつけたり、問題点を指摘することが大事です。

たとえば、C言語/C++規格をよく引用、参照します。
RationaleにあるCの原則、Cの精神も引用、参照するようにしています。
サンプルはコンパイルできるようにするべきだと主張し、コンパイル結果もQiitaに掲載しています。まだ、全部の断片をコンパイルエラーがないようにはできていません。ごめんなさい。

ISO/IEC/IEEE 24765:2017 Systems and software engineering - Vocabularyの誤植などは最後に掲載予定です。

ここではShort Nameだけ引用しながら確認します。

### 3.15 ABC
activity-based costing

### 3.28 AC
actual cost [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]

### 3.47 ACIA
asynchronous communication interface adapter
### 3.48 ACID
Atomicity Consistency Isolation Durability [ISO/IEC 10746-1:1998 Information technology - Open Distributed
Processing - Reference model: Overview]
### 3.49 ACQ
acquirer [ISO/IEC TR 29110-5-6-2:2014 Systems and software engineering - Lifecycle profiles for Very Small Entities (VSEs) - Part 5-6-2: Systems engineering - Management and engineering guide: Generic profile group: Basic profile, 4.2]

### 3.78 activity-based costing (ABC)
cost accounting method that allocates overhead costs based on specific production activities rather than
allocating from a single overhead pool

### 3.81 actual cost (AC)
actual cost of work performed (ACWP)
the realized cost incurred for the work performed on an activity during a specific time period [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]
cf. earned value management, earned value technique

### 3.86 ACWP
actual cost of work performed

### 3.106 ADM
architecture-driven modernization [ISO/IEC 19506:2012 Information technology - Object Management Group Architecture-Driven Modernization (ADM) - Knowledge Discovery Meta-Model (KDM), 4]

### 3.108 ADT
Abstract Data Type [ISO/IEC 19500-2:2012 Information technology - Object Management Group - Common
Object Request Broker Architecture (CORBA) - Part 2: Interoperability, ### 3.3]

### 3.111 AE(I)
Application Entity (Invocation) [ISO/IEC 10746-1:1998 Information technology - Open Distributed Processing ?
Reference model: Overview]

### 3.122 AHP
analytic hierarchy process

### 3.134 ALS
Application Layer Structure [ISO/IEC 10746-1:1998 Information technology - Open Distributed Processing ?
Reference model: Overview]

### 3.144 analytic hierarchy process (AHP)
use of matrixes to manage pair-wise relationships in decision-making
cf. additive weighting, nondimensional scaling, compensatory decision technique
### 3.154 annual equivalent AE(i)
representation of a cash flow as a series of equal annual payments (at a stated interest rate) over the planning horizon.
cf. future worth, present worth

### 3.155 annual percentage rate (APR)
nominal annual interest rate

### 3.158 ANSI
American National Standards Institute.

### 3.161 AOA
analysis of alternatives [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense Programs, ### 3.2]

### 3.162 AON
Activity-on-Node

### 3.163 AP(I)
Application Process (Invocation) [ISO/IEC 10746-1:1998 Information technology - Open Distributed Processing - Reference model: Overview]

### 3.165 API
Application Program Interface [ISO/IEC 10746-1:1998 Information technology - Open Distributed Processing - Reference model: Overview]

### 3.193 application specific integrated circuit (ASIC)
integrated circuit customized for a particular use

### 3.217 architecture description (AD)
architectural description
work product used to express an architecture [ISO/IEC/IEEE 42010:2011 Systems and software engineering - Architecture description, ### 3.3]

### 3.221 architecture-driven modernization (ADM)
process of understanding and evolving existing software assets of a system of interest [ISO/IEC 19506:2012 Information technology - Object Management Group Architecture-Driven Modernization (ADM) - Knowledge Discovery Meta-Model (KDM), 4]
Note 1 to entry: ADM does not preclude source-to-source migrations (where appropriate), but encourages user organizations to consider modernization from an analysis and design perspective.

### 3.234 artificial intelligence (AI)
branch of computer science devoted to developing data processing systems that perform functions normally associated with human intelligence, such as reasoning, learning, and self-improvement [ISO/IEC 2382:2015, Information technology - Vocabulary]

### 3.235 ASIC
application specific integrated circuit

### 3.237 ASO
1. Application Service Object [ISO/IEC 10746-1:1998 Information technology - Open Distributed Processing ?
Reference model: Overview]

### 3.239 ASR
alternative systems review [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense Programs, ### 3.2]

### 3.283 asynchronous communication interface adapter (ACIA)
functional unit to connect interfaces for asynchronous communications

### 3.315 BAC
budget at completion [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]

### 3.329 ball grid array (BGA)
surface-mounted integrated circuit package with multiple connections in a grid pattern on the bottom surface
Note 1 to entry: provides more connections than on packages with connectors on the edges only

### 3.333 base functional component (BFC)
functional service
an elementary unit of functional user requirements defined by and used by an FSM method for measurement purposes [ISO/IEC 14143-1:2007 Information technology - Software measurement - Functional size measurement;
Part 1: Definition of concepts, ### 3.1; ISO/IEC 19761:2011 Software engineering - COSMIC: a functional size measurement method, 2.1; ISO/IEC 20926:2009 Software and systems engineering - Software measurement - IFPUG functional size measurement method 2009, ### 3.8]
EXAMPLE: A functional user requirement "Maintain Customers" consists of the following BFCs: "Add a new customer", "Report Customer Purchases", and "Change Customer Details". A collection of logically related business data is maintained by the software as "Customer Details".

### base practice (BP)
activity that, when consistently performed, contributes to achieving a specific process purpose [ISO/IEC 33001:2015 Information technology - Process assessment - Concepts and terminology, ### 3.### 3.2]

###  basic engineering object BEO
engineering object that requires the support of a distributed infrastructure [ISO/IEC 10746-3:2009 Information technology - Open Distributed Processing - Reference Model: Architecture, 8.1.1]

### 3.356 BCWP
budgeted cost of work performed BCWS
budgeted cost of work scheduled

### 3.370 BEO
Basic Engineering Object [ISO/IEC 10746-1:1998 Information technology - Open Distributed Processing - Reference model: Overview; ISO/IEC 19793:2015 Information technology - Open Distributed Processing - Use of UML for ODP system specifications, 4]

### 3.372 BFC
base functional component [ISO/IEC 14143-1:2007 Information technology - Software measurement - Functional size measurement; Part 1: Definition of concepts, 4; ISO/IEC 19761:2011 Software engineering - COSMIC: a functional size measurement method, 2.1]

### 3.374 BGA
ball grid array

### 3.378 bill of materials (BOM)
documented formal hierarchical tabulation of the physical assemblies, subassemblies, and components needed to fabricate a product

### 3.379 binary digit (bit)
unit of information that can be represented by either a zero or a one. 2 element of computer storage that can hold a unit of information as in (1) ### 3. numeral used to represent one of the two digits in the binary numeration system; zero (0) or one (1)

### 3.395 BMT
Bench Mark Test [ISO/IEC 14102:2008 Information Technology - Guideline for the evaluation and selection of CASE tools, 8.2]

### 3.398 BOM
bill of materials

### 3.418 BP
base practice [ISO/IEC TR 29110-3-1:2015 Systems and software engineering - Lifecycle profiles for Very Small Entities (VSEs) - Part 3-1: Assessment Guide, 4.2]

### 3.426 BRS 
business requirements specification [ISO/IEC/IEEE 29148:2011 Systems and software engineering - Life cycle processes - Requirements engineering, 4.2]

### 2.429 budget at completion (BAC)
the sum of all the budgets established for the work to be performed [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]

### 3.434 built-in random access memory (RAM)
RAM embedded in a microcontroller unit (MCU) chip

### 3.450 byte
group of adjacent binary digits operated upon as a unit and usually shorter than a computer word (frequently connotes a group of eight bits) 2. element of computer storage that can hold a group of bits as in (1) ### 3. string that consists of a number of bits, treated as a unit, and usually representing a character or a part of a character [ISO/IEC
2382:2015, Information technology - Vocabulary]

### C4I
command, control, communications, computer, and intelligence [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense Programs, ### 3.2]

### 3.453 CAD
Computer Aided Design [ISO/IEC 10746-1:1998 Information technology - Open Distributed Processing - Reference model: Overview]

### 3.455 CAI
critical application item [IEEE 15288.1:2014 IEEE Standard for Application of Systems Engineering on Defense Programs, ### 3.2]

### 3.469 CAN
controller area network

### 3.479 CARD
cost analysis requirements description [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense Programs, ### 3.2]

### 3.485 CASE tool
software tool used for computer-aided software engineering (CASE) [IEEE 1175.1-2002 (R2007) IEEE Guide for CASE Tool Interconnections-Classification and Description, ### 3.3] 2. software product that can assist software engineers by providing automated support for software life-cycle activities [ISO/IEC 14102:2008 Information Technology - Guideline for the evaluation and selection of CASE tools, ### 3.2] ### 3. software product that can assist software and system engineers by providing automated support for software and system engineering life-cycle activities [ISO/IEC 15940:2013 Systems and software engineering - Software Engineering Environment Services, 2.3]
Note 1 to entry: A CASE tool can provide support in only selected functional areas or in a wide variety of functional areas.

### 3.497 CBa
conduct benchmarking activity [ISO/IEC 29155-2:2013: Systems and software engineering - Information technology project performance benchmarking framework - Part 2: Requirements for benchmarking, 4]
### 3.498 CCB
configuration control board [IEEE 828-2012 IEEE Standard for Configuration Management in Systems and Software Engineering, 2.2; ISO/IEC/IEEE 16326:2009 Systems and software engineering - Life cycle processes - Project management, 3] 2. change control board [IEEE 828-2012 IEEE Standard for Configuration Management in Systems and Software Engineering, 2.2; ISO/IEC/IEEE 16326:2009 Systems and software engineering - Life cycle processes - Project management, 3]
### 3.499 CCCS
Client Conversion Code Sets [ISO/IEC 19500-2:2012 Information technology - Object Management Group - Common Object Request Broker Architecture (CORBA) - Part 2: Interoperability, ### 3.3]
### 3.500 CCM
CORBA Component Model [ISO/IEC 19500-3:2012 Information technology - Object Management Group - Common Architecture Request Broker Architecture (CORBA) - Part 3: Components, 4.3]
### 3.501 CCS
Conversion Code Sets [ISO/IEC 19500-2:2012 Information technology - Object Management Group - Common Object Request Broker Architecture (CORBA) - Part 2: Interoperability, ### 3.3]
### 3.502 CD
Compact Disk
### 3.503 CD-ROM
compact disc, read-only memory [IEEE 828-2012 IEEE Standard for Configuration Management in Systems and Software Engineering, 2.2]
### 3.504 CDD
capability development document [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense Programs, ### 3.2]
### 3.505 CDIF
CASE Data Interchange Format (originally) [ISO/IEC 15474-1:2002 Information technology - CDIF framework - Part 1: Overview, 5.2]

### 3.519 CDR
critical design review [IEEE 15288.1:2014 IEEE Standard for Application of Systems Engineering on Defense Programs, ### 3.2] 2. common data representation [ISO/IEC 19500-2:2012 Information technology - Object Management Group - Common Object Request Broker Architecture (CORBA) - Part 2: Interoperability, ### 3.3]
### 3.520 CDRL
contract data requirements list [ISO/IEC/IEEE 16326:2009 Systems and software engineering - Life cycle processes - Project management, 3]

### 3.521 central processing unit (CPU)
functional unit that consists of one or more processors and their internal storage [ISO/IEC 2382:2015, Information technology - Vocabulary]

### 3.531 CFD
cumulative flow diagram [Software Extension to the PMBOK? Guide Fifth Edition]
### 3.532 CFP
COSMIC function point [ISO/IEC 19761:2011 Software engineering - COSMIC: a functional size measurement method, 3]

### 3.538 change control board (CCB)
a formally chartered group responsible for reviewing, evaluating, approving, delaying, or rejecting changes to a project, and for recording and communicating such decisions [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]
cf. configuration control board

### 3.570 CI
configuration item
### 3.571 CIDL
Component Implementation Definition Language [ISO/IEC 19500-3:2012 Information technology - Object Management Group - Common Architecture Request Broker Architecture (CORBA) - Part 3: Components, 4.3]
### 3.572 CIF
Component Implementation Framework [ISO/IEC 19500-3:2012 Information technology - Object Management Group - Common Architecture Request Broker Architecture (CORBA) - Part 3: Components, 4.3]

### 3.573 CIM
Computer Integrated Manufacturing [ISO/IEC 10746-1:1998 Information technology - Open Distributed Processing - Reference model: Overview]

### 3.589 clock pulse generator (CPG)
electronic unit to produce uniform timed signals
EXAMPLE: embedded in an MCU

### 3.602 CM
configuration management

### 3.605CMDB
configuration management database [IEEE 828-2012 IEEE Standard for Configuration Management in Systems and Software Engineering, 2.2]
### 3.606 CMIP
Common Management Information Protocol [ISO/IEC 10746-1:1998 Information technology - Open Distributed Processing - Reference model: Overview]
### 3.607 CMIR
client makes it right [ISO/IEC 19500-2:2012 Information technology - Object Management Group - Common Object Request Broker Architecture (CORBA) - Part 2: Interoperability, ### 3.3]
### 3.608 CMIS
Common Management Information Service [ISO/IEC 10746-1:1998 Information technology - Open Distributed Processing - Reference model: Overview]

### 3.609 CMP
configuration management plan [IEEE 828-2012 IEEE Standard for Configuration Management in Systems and Software Engineering, 2.2]
### 3.610 CMS
configuration management system [IEEE 828-2012 IEEE Standard for Configuration Management in Systems and Software Engineering, 2.2]
### 3.611 CMT
container-managed transaction [ISO/IEC 19500-3:2012 Information technology - Object Management Group - Common Architecture Request Broker Architecture (CORBA) - Part 3: Components, 4.3]
### 3.612 CNCS
Client Native Code Set [ISO/IEC 19500-2:2012 Information technology - Object Management Group - Common Object Request Broker Architecture (CORBA) - Part 2: Interoperability, ### 3.3]

### 3.642 commercial-off-the-shelf (COTS)
[software] product available for purchase and use without the need to conduct development activities [ISO/IEC 90003:2014 Software engineering - Guidelines for the application of ISO 9001:2008 to computer software, ### 3.4; ISO/IEC/IEEE 15289:2015 Systems and software engineering - Content of life-cycle information products (documentation), 5.4]
cf. software product
Note 1 to entry: COTS software product includes the product description (including all cover information, data sheet, web siteinformation, etc.), the user documentation (necessary to install and use the software), the software contained on a computer sensible media (disk, CD-ROM, internet downloadable, etc.). Software is mainly composed of programs and data. This definition applies also to product descriptions, user documentation and software which are produced and supported as separate manufactured goods, but for which typical commercial fees and licensing considerations do not apply.

### 3.663 communication technology (CT)
specific tools, systems, computer programs, etc., used to transfer information among project stakeholders [A Guide to the Project Management Body of Knowledge (PMBOK Guide) - Fifth Edition]

### 3.693 complex programmable logic device (CPLD)
hardware component with a fully programmable AND/OR gate array

### 3.732 computer software component (CSC)
functionally or logically distinct part of a computer software configuration item, typically an aggregate of two or more software units
cf. computer software configuration item, software configuration item, software item
### 3.733computer software configuration item (CSCI)
software configuration item (SWCI) 
aggregation of software that is designated for configuration management and treated as a single entity in the configuration management process
cf. computer software component, hardware configuration item, configuration item, software configuration item, software item

### 3.735 computer-aided (CA)
pertaining to a technique or process in which a computer does part of the work [ISO/IEC 2382:2015, Information technology - Vocabulary]
### 3.736 computer-aided design (CAD)
use of a computer to design a device or a system, display it on a computer monitor or printer, simulate its operation, and provide statistics on its performance
Note 1 to entry: The computer is provided with data concerning the item to be designed, how it is to function, and the rules for the way in which the different components can be joined.
### 3.737 computer-aided software engineering (CASE)
use of computers to aid in the software engineering process [ISO/IEC 15940:2013 Systems and software engineering - Software Engineering Environment Services, 2.2]
cf. integrated development environment
EXAMPLE: the application of software tools to software design, requirements tracing, code production, testing, document generation, and other software engineering activities
### 3.738 computer-based software system (CBSS)
software system running on a computer [ISO/IEC 14756:1999 Information technology - Measurement and rating of performance of computer-based software systems, 4.5]
Note 1 to entry: A CBSS can be a data processing system as seen by human users at their terminals or at equivalent machineuser-interfaces. It includes hardware and all software (system software and application software) which is necessary for realizing data processing functions required by its users

### 3.745 COMSEC
communications security [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense Programs, ### 3.2]

### 3.748 concept of operations (ConOps) document
user-oriented document that describes a system's operational characteristics from the end user's viewpoint
cf. operational concept description (OCD)

### 3.774 configuration control board (CCB)
group of people responsible for evaluating and approving or disapproving proposed changes to configuration items, and for ensuring implementation of approved changes [IEEE 828-2012 IEEE Standard for Configuration Management in Systems and Software Engineering, 2.1] 2. qualified personnel who evaluate, for approval or disapproval, all proposed changes to the current developmental baseline [IEEE 828-2012 IEEE Standard for
Configuration Management in Systems and Software Engineering, 2.1]

### 3.777 configuration item (CI)
item or aggregation of hardware, software, or both that is designated for configuration management and treated as a single entity in the configuration management process [ISO/IEC TS 24748-1:2016 Systems and software engineering - Life cycle management - Part 1: Guide for life cycle management, 2.14; ISO/IEC/IEEE 15288:2015 Systems and software engineering - System life cycle processes, 4.1.13] 2. component of an infrastructure or an item which is or will be under control of configuration management [ISO/IEC 19770-5:2015 Information technology - IT asset management - Part 5: Overview and vocabulary, ### 3.7] ### 3. aggregation of work products that is designated for configuration management and treated as a single entity in the configuration management process [IEEE 828-2012 IEEE Standard for Configuration Management in Systems and Software Engineering, 2.1] 4. entity within a configuration that satisfies an end use function and that can be uniquely identified at a given reference point [ISO/IEC 12207:2008 Systems and software engineering - Software life cycle processes, 4.7] 5. item or aggregation
of software that is designed to be managed as a single entity and its underlying components, such as documentation, data structures, scripts [ISO/IEC 16350-2015 Information technology - Systems and software engineering - Application management, 4.12] 6. any system element or aggregation of system elements that satisfies an end use function and is designated by the acquirer for separate configuration control [IEEE 15288.1:2014 IEEE Standard for Application of Systems Engineering on Defense Programs, 3.1]
cf. hardware configuration item, computer software configuration item, configuration identification, critical item ote 1 to entry: Configuration items can vary widely in complexity, size and type, ranging from

### 3.779 configuration management (CM)
discipline applying technical and administrative direction and surveillance to: identify and document the functional and physical characteristics of a configuration item, control changes to those characteristics, record and report change processing and implementation status, and verify compliance with specified requirements [IEEE 828-2012 IEEE Standard for Configuration Management in Systems and Software Engineering, 2.1] 2. technical and organizational activities, comprising configuration identification, control, status accounting and auditing [IEEE 828-2012 IEEE Standard for Configuration Management in Systems and Software Engineering, 2.1] 3. coordinated activities to direct and control the configuration [ISO/IEC TR 18018:2010 Information technology - Systems and software engineering - Guide for configuration management tool capabilities,  3.7]
cf. baseline, change management, configuration identification, configuration control, configuration status accounting, configuration audit

### 3. configuration management database (CMDB)
specific type of repository for CM information, usually a data store, used to record attributes of configuration items, and the relationships between configuration items, throughout their lifecycle [IEEE 828-2012 IEEE Standard for Configuration Management in Systems and Software Engineering, 2.1] 2. database containing all the relevant details of each configuration item and details of the important relationships between them [ISO/IEC 19770-5:2015 Information technology - IT asset management - Part 5: Overview and vocabulary, 3.8]
cf. configuration management system

### 3.783
configuration status accounting (CSA)
1. element of configuration management that consists of the recording and reporting of information needed to
manage a configuration effectively [ISO/IEC TR 18018:2010 Information technology - Systems and software
engineering - Guide for configuration management tool capabilities, ### 3.10]
cf. configuration control, configuration identification, configuration index, configuration item, development record.
Note 1 to entry: This information includes a listing of the approved configuration identification, the status of proposed changes
to the configuration, and the implementation status of approved changes.

### 3.794
ConOps
1. concept of operations [ISO/IEC/IEEE 29148:2011 Systems and software engineering - Life cycle processes ?
Requirements engineering, 4.2]

### 3.833
continuing professional development (CPD)
1. set of activities undertaken by an individual professional to maintain professional competence [ISO/IEC TR
29154:2013, Software engineering - Guide for the application of ISO/IEC 24773:2008 (Certification of software
engineering professionals - Comparison framework), ### 3.4]

### 3.842
contract work breakdown structure (CWBS)
1. portion of the overall work breakdown structure applicable to a contract, developed and maintained by the
supplier

### 3.872
controller area network (CAN)
1. high-integrity bus system for networking intelligent devices within a system
Note 1 to entry: commonly used in embedded networks for vehicles or medical equipment

### 3.882
COQ
1. cost of quality [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]
### 3.883
CORBA
1. Common Object Request Broker Architecture [ISO/IEC 14769:2001 Information technology - Open Distributed
Processing - Type Repository Function, 4; ISO/IEC 19500-2:2012 Information technology - Object Management
Group - Common Object Request Broker Architecture (CORBA) - Part 2: Interoperability, 5]


### 3.893
COS
1. common object services [ISO/IEC 19500-3:2012 Information technology - Object Management Group - Common
Architecture Request Broker Architecture (CORBA) - Part 3: Components, 4.3]
### 3.894
COSMIC
1. Common Software Measurement International Consortium [ISO/IEC 19761:2011 Software engineering ?
COSMIC: a functional size measurement method]

### 3.902
cost of quality (COQ)
1. a method of determining the costs incurred to ensure quality. Prevention and appraisal costs (cost of
conformance) include costs for quality planning, quality control (QC), and quality assurance to ensure compliance
to requirements (i.e., training, QC systems, etc.). Failure costs (cost of non-conformance) include costs to rework
products, components, or processes that are non-compliant, costs of warranty work and waste, and loss of
reputation [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]

### 3.904
cost performance index (CPI)
1. a measure of the cost efficiency of budgeted resources expressed as the ratio of earned value to actual cost [A
Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]


### 3.906
cost plus award fee contracts (CPAF)
1. a category of contract that involves payments to the seller for all legitimate actual costs incurred for completed
work, plus an award fee representing seller profit [A Guide to the Project Management Body of Knowledge (PMBOK?
Guide) - Fifth Edition]
### 3.907
cost plus fixed fee contract (CPFF)
1. a type of cost-reimbursable contract where the buyer reimburses the seller for the seller's allowable costs
(allowable costs are defined by the contract) plus a fixed amount of profit (fee) [A Guide to the Project Management
Body of Knowledge (PMBOK? Guide) - Fifth Edition]
### 3.908
cost plus incentive fee contract (CPIF)
1. a type of cost-reimbursable contract where the buyer reimburses the seller for the seller's allowable costs
(allowable costs are defined by the contract), and the seller earns its profit if it meets defined performance criteria
[A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]
### 3.909
cost variance (CV)
1. the amount of budget deficit or surplus at a given point in time, expressed as the difference between the earned
value and the actual cost [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]

### 3.911
cost-plus-fee (CPF)
1. contract in which the acquirer reimburses the supplier's allowable costs for performing the contract work and
also pays a fee
### 3.912
cost-plus-fixed-fee (CPFF) contract
1. a type of cost-reimbursable contract where the buyer reimburses the seller for the seller's allowable costs
(allowable costs are defined by the contract) plus a fixed amount of profit (fee) [A Guide to the Project Management
Body of Knowledge (PMBOK? Guide) - Fifth Edition]
### 3.913
cost-plus-incentive-fee (CPIF) contract
1. a type of cost-reimbursable contract where the buyer reimburses the seller for the seller's allowable costs
(allowable costs are defined by the contract), and the seller earns its profit if it meets defined performance criteria
[A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]

### 3.915
COTS
Commercial-Off-The-Shelf [ISO/IEC 90003:2014 Software engineering - Guidelines for the application of ISO
9001:2008 to computer software, ### 3.4]

### 3.920 CPAF
cost plus award fee [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]
### 3.921 CPC
computer program component
cf. computer software component
### 3.922 CPCI
computer program configuration item
cf. computer software configuration
### 3.923 CPD
continuing professional development [ISO/IEC TR 29154:2013, Software engineering - Guide for the application of ISO/IEC 24773:2008 (Certification of software engineering professionals - Comparison framework),  3.4] 
2. capability production document [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense Programs, 3.2]
### 3.924 CPF 
cost-plus-fee
### 3.925 CPFF
cost plus fixed fee [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]
### 3.926 CPG
clock pulse generator
### 3.927 CPI
cost performance index [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]
critical program information [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense Programs, 3.2]

### 3.928 CPIF
cost plus incentive fee [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]
### 3.929 CPLD
complex programmable logic device
### 3.930 CPM
critical path method 2. Counting Practices International Standard [ISO/IEC 24570:2005 Software engineering - NESMA functional size measurement method version 2.1 - Definitions and counting guidelines for the application ofFunction Point Analysis]
### 3.931 CPPC
cost plus percentage of cost
### 3.932 CPU
central processing unit [IEEE 1012-2012 IEEE Standard for System and Software Verification and Validation,  3.1]

### 3.941 critical design review (CDR)
review conducted to verify that the detailed design of one or more configuration items satisfy specified requirements; to establish the compatibility among the configuration items and other items of equipment, facilities, software, and personnel; to assess risk areas for each configuration item; and, as applicable, to assess the results of producibility analyses, review preliminary hardware product specifications, evaluate preliminary test planning, and evaluate the adequacy of preliminary operation and support documents 2. review as in (1) of any hardware or
software component

### 3.946 critical path method (CPM)
a method used to estimate the minimum project duration and determine the amount of scheduling flexibility on the logical network paths within the schedule model [A Guide to the Project Management Body of Knowledge
(PMBOK? Guide) - Fifth Edition]

### 3.958
CRUD
1. create, read, update, delete [ISO/IEC 19500-3:2012 Information technology - Object Management Group ?
Common Architecture Request Broker Architecture (CORBA) - Part 3: Components, 4.3]
### 3.959
CSA
1. configuration status accounting [ISO/IEC TR 18018:2010 Information technology - Systems and software
engineering - Guide for configuration management tool capabilities, ### 3.10]
### 3.960
CSC
1. computer software component

### 3.961
CSCI
SWCI
1. computer software configuration item
### 3.962
CSF
1. critical success factor [ISO/IEC TR 14471:2007 Information technology - Software engineering - Guidelines for
the adoption of CASE tools, 2.2]
### 3.963
CSIv2
1. common secure interoperability, version 2 [ISO/IEC 19500-2:2012 Information technology - Object Management
Group - Common Object Request Broker Architecture (CORBA) - Part 2: Interoperability, 5]
### 3.964
CSS
1. cascading style sheets [ISO/IEC 15909-2:2011 Software and system engineering - High-level Petri nets - Part 2:
Transfer format, 4.2.1; ISO/IEC/IEEE 23026:2015 Systems and software engineering - Engineering and management
of websites for systems, software, and services information, 5]
### 3.965
CSS2
1. cascading stylesheets level 2 [ISO/IEC 15909-2:2011 Software and system engineering - High-level Petri nets ?
Part 2: Transfer format, 4.2.2]
### 3.966
CT
1. communication technology
### 3.967
cumulative flow diagram (CFD)
1. a chart indicating features completed over time, plus features in development, and those features in the backlog
[Software Extension to the PMBOK? Guide Fifth Edition]
Note 1 to entry: may indicate features at some intermediate milestones, such as features designed but not yet constructed

### 3.976
CV
1. cost variance [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]
### 3.977
CVE
1. Common Vulnerabilities and Exposures [ISO/IEC/IEEE 23026:2015 Systems and software engineering ?
Engineering and management of websites for systems, software, and services information, 5]
### 3.978
CVSS
1. Common Vulnerability Scoring System [ISO/IEC/IEEE 23026:2015 Systems and software engineering ?
Engineering and management of websites for systems, software, and services information, 5]
### 3.979
CWBS
1. contract work breakdown structure [IEEE 15288.1:2014 IEEE Standard for Application of Systems Engineering on
Defense Programs, ### 3.2]

### 3.991
data buffer register (DBR)
1. region of a physical memory storage used to temporarily store data while it is being moved, e.g., from input to
processing

### 3.1003
data element type (DET)
1. unique, user-recognizable, non-repeated attribute [ISO/IEC 20926:2009 Software and systems engineering ?
Software measurement - IFPUG functional size measurement method 2009, ### 3.15] 2. the most elementary form of
data as seen by the user that serves for controlling, recording, or transferring information [ISO/IEC 24570:2005
Software engineering - NESMA functional size measurement method version 2.1 - Definitions and counti
ng
guidelines for the application of Function Point Analysis] ### 3. a unique, user-recognizable, non-recursive item of
information [ISO/IEC 20968:2002 Software engineering - Mk II Function Point Analysis - Counting Practices
Manual, 10]

### 3.1007
data flow diagram (DFD)
data flowchart
data flow graph
1. diagram that depicts data sources, data sinks, data storage, and processes performed on data as nodes, and
logical flow of data as links between the nodes
cf. control flow diagram, data structure diagram

### 3.1022
data processing (DP)
automatic data processing (ADP)
1. systematic performance of operations upon data [ISO/IEC 2382:2015, Information technology - Vocabulary]
EXAMPLE: arithmetic or logic operations upon data, merging or sorting of data, assembling or compiling of
programs, or operations on text, such as editing, sorting, merging, storing, retrieving, displaying, or printing
Note 1 to entry: The term data processing is not a synonym for information processing

### 3.1036
data transfer controller (DTC)
1. functional unit to control data communication without going through the central processing unit (CPU)

### 3.1053
DBMS
1. Database Management System [ISO/IEC 25024:2015 Systems and software engineering - Systems and software
Quality Requirements and Evaluation (SQuaRE) - Measurement of data, 5]
### 3.1054
DBR
1. data buffer register
### 3.1055
DCE
1. Distributed Computing Environment. [ISO/IEC 19500-2:2012 Information technology - Object Management
Group - Common Object Request Broker Architecture (CORBA) - Part 2: Interoperability, ### 3.3]
### 3.1056
DDR
1. detailed design review2. double data rate
### 3.1057
DDR2
1. double data rate x 2 (twice as fast as DDR)

### 3.1058
DDR2 SDRAM
1. double data rate synchronous dynamic random access memory unit with higher performance than DDR SDRAM,
because the device transfers data four times (four consecutive words) in one internal clock cycle.
### 3.1059
DDR3
1. double data rate 3, which transfers data 2 to the third power (8 times) faster than DDR
### 3.1060
DDR3 SDRAM
1. double data rate synchronous dynamic random access memory unit with higher performance because it transfers
data 2 to the third power (8) times (8 consecutive words) in one internal clock cycle.
### 3.1061
DDR4
1. double data rate 4; data transfer is 2 to the 4th power = 16 times that of a SDRAM
### 3.1062
DDR4 SDRAM
1. double data rate synchronous dynamic random access memory unit with higher performance, because it transfers
data at the rate of 2 to the 4th power (16) times (16 consecutive words) in one internal clock cycle

### 3.1091
definitive software library (DSL)
1. secure storage environment, formed of physical media or of one or more electronic software repositories, capable
of control and protection of definitive authorized versions of all software configuration items and masters of all
software controlled by SAM [ISO/IEC 19770-5:2015 Information technology - IT asset management - Part 5:
Overview and vocabulary, ### 3.11]
### 3.1092
degree of influence (DI)
1. a numerical indicator of the impact of each of the 19 (or more) technical complexity adjustment factors, ranging
from 0 (no influence) to 5 (strong influence, throughout) [ISO/IEC 20968:2002 Software engineering - Mk II
Function Point Analysis - Counting Practices Manual, 10]
Note 1 to entry: These indicators are used to compute the value adjustment factor

### 3.1105
DEMIL
1. demilitarization [IEEE 15288.1:2014 IEEE Standard for Application of Systems Engineering on Defense Programs,
### 3.2]

### 3.1162
DET
1. data element type [ISO/IEC 20926:2009 Software and systems engineering - Software measurement - IFPUG
functional size measurement method 2009, 4]

### 3.1180
development project function point count (DFP)
1. a count that measures a project that provides end-users with the first installation of the software [ISO/IEC
24570:2005 Software engineering - NESMA functional size measurement method version 2.1 - Definitions and
counting guidelines for the application of Function Point Analysis] 2. a count that measures the functionality provided
to the end users with the first installation of the software, developed when the project is complete [ISO/IEC
20968:2002 Software engineering - Mk II Function Point Analysis - Counting Practices Manual, 10] ### 3. activity of
applying ISO/IEC 20926:2009 to measure the functional size of a development project [ISO/IEC 20926:2009
Software and systems engineering - Software measurement - IFPUG functional size measurement method 2009,
### 3.20]

### 3.1189
DFD
1. data flow diagram

### 3.1203
DIB
1. Directory Information Base [ISO/IEC 13235-3:1998 Information technology - Open Distributed Processing ?
Trading Function - Part 3: Provision of Trading Function using OSI Directory service, 4]

### 3.1208
digital signal processing (DSP)
1. modification of an information signal represented by a sequence of digits or symbols to affect the representation
of discrete time, discrete frequency, or other attributes
### 3.1209
digital signal processor (DSP)
1. microprocessor designed to perform digital signal processing
### 3.1210
DII
1. dynamic invocation interface [ISO/IEC 19500-3:2012 Information technology - Object Management Group ?
Common Architecture Request Broker Architecture (CORBA) - Part 3: Components, 4.3]

### 3.1212
DIP
1. dual inline 

### 3.1218
direct memory access (DMA)
1. technique in which a peripheral takes direct control of a central processing unit's memory bus to transfer data to
or from memory
### 3.1219
direct memory access controller (DMAC)
1. functional unit that performs direct memory access

### 3.1245
DIT
1. Directory Information Tree [ISO/IEC 13235-3:1998 Information technology - Open Distributed Processing ?
Trading Function - Part 3: Provision of Trading Function using OSI Directory service, 4]
### 3.1248
DL
1. Definition Language [ISO/IEC 10746-1:1998 Information technology - Open Distributed Processing - Reference
model: Overview]
### 3.1249
DLC
1. Data-Life-Cycle [ISO/IEC 25024:2015 Systems and software engineering - Systems and software Quality
Requirements and Evaluation (SQuaRE) - Measurement of data, 5]

### 3.1263
DoDAF
1. Department of Defense architecture framework [IEEE 15288.1:2014 IEEE Standard for Application of Systems
Engineering on Defense Programs, ### 3.2]


### 3.1282
double data rate (DDR) SDRAM
1. synchronous dynamic random access memory unit with higher access speed and bandwidth, because it transfers
two consecutive words in one internal clock cycle

ーー訂正　### 3.1288, 2.1289の間にあって番号がついていない。
DP
1. data processing [ISO/IEC 2382:2015, Information technology - Vocabulary] 2. deployment package [ISO/IEC TR
29110-1:2016 Software engineering - Lifecycle profiles for Very Small Entities (VSEs) - Part 1: Overview, 4.2]
### 3.1289
DR
1. decision review [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense Programs, ### 3.2]
### 3.1290
DRAM
1. dynamic random access memory

### 3.1292
DSA
1. Directory System Agent [ISO/IEC 13235-3:1998 Information technology - Open Distributed Processing - Trading
Function - Part 3: Provision of Trading Function using OSI Directory service, 4]
### 3.1293
DSL
1. definitive software library [ISO/IEC 19770-5:2015 Information technology - IT asset management - Part 5:
Overview and vocabulary, ### 3.11]
### 3.1294
DSP
1. digital signal processing 2. digital signal processor [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and
Audits on Defense Programs, ### 3.2]
### 3.1295
DT
1. development test [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense Programs, ### 3.2]
### 3.1296
DT&E
1. developmental test and evaluation [IEEE 15288.1:2014 IEEE Standard for Application of Systems Engineering on
Defense Programs, ### 3.2]
### 3.1297
DTC
1. data transfer controller
### 3.1298
DTD
1. document type definition [ISO/IEC 19500-3:2012 Information technology - Object Management Group ?
Common Architecture Request Broker Architecture (CORBA) - Part 3: Components, 4.3]
Note 1 to entry: for XML or SGML specifications
### 3.1299
DUA
1. Directory User Agent [ISO/IEC 13235-3:1998 Information technology - Open Distributed Processing - Trading
Function - Part 3: Provision of Trading Function using OSI Directory service, 4]

### 3.1301
dual inline package (DIP)
1. microcircuit unit with connectors (pins) arranged in two rows

### 3.1304
duration (DU or DUR)
1. the total number of work periods (not including holidays or other nonworking periods) required to complete a
schedule activity or work breakdown structure component. Usually expressed as workdays or workweeks.
Sometimes incorrectly equated with elapsed time [A Guide to the Project Management Body of Knowledge (PMBOK?
Guide) - Fifth Edition]
cf. effort
### 3.1305
DVD
1. digital versatile disc [IEEE 828-2012 IEEE Standard for Configuration Management in Systems and Software
Engineering, 2.2] 2. digital video disc

### 3.1326
E-R diagram
1. entity-relationship diagram
### 3.1327
EAC
1. estimate at completion [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]
### 3.1328
early finish date (EF)
1. in the critical path method, the earliest possible point in time on which the uncompleted portions of a schedule activity can
finish, based on the schedule network logic, the data date, and any schedule constraints [A Guide to the Project Management
Body of Knowledge (PMBOK? Guide) - Fifth Edition]
### 3.1329
early start date (ES)
1. in the critical path method, the earliest possible point in time on which the uncompleted portions of a schedule activity can
start, based on the schedule network logic, the data date, and any schedule constraints [A Guide to the Project Management
Body of Knowledge (PMBOK? Guide) - Fifth Edition]

### 3.1331
earned value (EV)
budgeted cost of work performed (BCWP)
1. the measure of work performed expressed in terms of the budget authorized for that work [A Guide to the Project
Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]
### 3.1332
earned value management (EVM)
1. a methodology that combines scope, schedule, and resource measurements to assess project performance and progress [A
Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]

### 3.1335
ECP
1. engineering change proposal [IEEE 15288.1:2014 IEEE Standard for Application of Systems Engineering on Defense
Programs, ### 3.2]
### 3.1336
ECR
1. engineering change request [IEEE 15288.1:2014 IEEE Standard for Application of Systems Engineering on Defense
Programs, ### 3.2]
### 3.1337
EDA
1. electronic design automation
### 3.1338
EDI
1. electronic data interchange

### 3.1340
EDRAP
1. engineering data requirements agreement plan [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and
Audits on Defense Programs, ### 3.2]
### 3.1341
EEPROM
1. electric erasable programmable read only memory
### 3.1342
EF
1. early finish date [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]

### 3.1352
EI
1. external input [ISO/IEC 20926:2009 Software and systems engineering - Software measurement - IFPUG
functional size measurement method 2009, 4; ISO/IEC 24570:2005 Software engineering - NESMA functional size
measurement method version 2.1 - Definitions and counting guidelines for the application of Function Point Analysis]
### 3.1353
EIF
1. external interface file [ISO/IEC 20926:2009 Software and systems engineering - Software measurement - IFPUG
functional size measurement method 2009, 4; ISO/IEC 24570:2005 Software engineering - NESMA functional size
measurement method version 2.1 - Definitions and counting guidelines for the application of Function Point Analysis]
### 3.1354
EJB
1. Enterprise Java Beans [ISO/IEC 19500-3:2012 Information technology - Object Management Group - Common
Architecture Request Broker Architecture (CORBA) - Part 3: Components, 4.3]
### 3.1355
electric erasable programmable read only memory (EEPROM)
1. type of programmable ROM in which the memory can be erased using electrical current and rewritten
cf. flash memory
### 3.1356
electronic data interchange (EDI)
1. structured way of transmitting data held electronically from database to database, usually using
telecommunications networks
### 3.1357
electronic design automation (EDA)
1. software-driven design and development of electronic components such as microcomputer units and circuit
boards
### 3.1358
electronic mail (Email)
1. correspondence in the form of messages transmitted over a computer network [ISO/IEC 2382:2015, Information
technology - Vocabulary]

### 3.1369
EMC
1. electromagnetic compatibility [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense
Programs, ### 3.2]
### 3.1370
EMD
1. engineering and manufacturing development [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits
on Defense Programs, ### 3.2]

### 3.1372
EMI
1. electromagnetic interference [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense
Programs, ### 3.2]

### 3.1378
EMV
1. expected monetary value [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth
Edition]

### 3.1386
ENCODING.1
1. primary encoding defined within the CDIF family of standards [ISO/IEC 15474-1:2002 Information technology ?
CDIF framework - Part 1: Overview, 4.2]
Note 1 to entry: The CDIF family of standards supports multiple transfer formats, each composed of a syntax and an encoding.

### 3.1395
engineering change proposal (ECP)
1. in configuration management, a proposed engineering change and the documentation by which the change is
described and suggested
cf. configuration control

### 3.1402
enhancement project function point count (EFP)
1. count that measures a project that realizes modifications to an existing application [ISO/IEC 24570:2005 Software
engineering - NESMA functional size measurement method version 2.1 - Definitions and counting guidelines for the
application of Function Point Analysis] 2. activity of applying ISO/IEC 20926:2009 to measure the functional size of
an enhancement project [ISO/IEC 20926:2009 Software and systems engineering - Software measurement - IFPUG
functional size measurement method 2009, ### 3.24]

### 3.1404
Ent
1. [software] entitlement schema [ISO/IEC 19770-3:2016, Information technology - IT asset management - Part 3:
Entitlement schema, ### 3.2]


### 3.1424
EO
1. external output [ISO/IEC 20926:2009 Software and systems engineering - Software measurement - IFPUG
functional size measurement method 2009, 4; ISO/IEC 24570:2005 Software engineering - NESMA functional size
measurement method version 2.1 - Definitions and counting guidelines for the application of Function Point Analysis]

### 3.1428
EPROM
1. erasable programmable read only memory
### 3.1429
EQ
1. external inquiry [ISO/IEC 20926:2009 Software and systems engineering - Software measurement - IFPUG
functional size measurement method 2009, 4; ISO/IEC 24570:2005 Software engineering - NESMA functional size
measurement method version 2.1 - Definitions and counting guidelines for the application of Function Point Analysis]

### 3.1435
equivalent IDL
1. client mappings; that is, mappings of the externally-visible component features for component declarations, or
home features for home declarations [ISO/IEC 19500-3:2012 Information technology - Object Management Group
? Common Architecture Request Broker Architecture (CORBA) - Part 3: Components, 4.1]
Note 1 to entry: Implicitly defined by a component definition in IDL (interface definition language)

### 3.1437
ERA
1. Entity-Relationship-Attribute modeling [ISO/IEC 15474-1:2002 Information technology - CDIF framework ?
Part 1: Overview, 5.2]
### 3.1438
erasable programming read only memory (EPROM)
1. type of programmable ROM which can be rewritten after erasing the existing data using ultraviolet (UV) rays
Note 1 to entry: The device can be rewritten many times.

### 3.1449
ES
1. early start date [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]

### 3.1452
ESIOP
1. environment specific inter-ORB protocol [ISO/IEC 19500-2:2012 Information technology - Object Management
Group - Common Object Request Broker Architecture (CORBA) - Part 2: Interoperability, 5]
### 3.1453
ESOH
1. environment, safety, and occupational health [IEEE 15288.1:2014 IEEE Standard for Application of Systems
Engineering on Defense Programs, ### 3.2]

### 3.1460
estimate at completion (EAC)
1. the expected total cost of completing all work expressed as the sum of the actual cost to date and the estimate to
complete [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]
cf. earned value technique, estimate to complete

### 3.1462
estimate to complete (ETC)
1. the expected cost to finish all the remaining project work [A Guide to the Project Management Body of Knowledge
(PMBOK? Guide) - Fifth Edition]
cf. estimate at completion

### 3.1464
ETC
1. estimate to complete [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]
### 3.1465
EV
1. earned value [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]

### 3.1474
evaluation module (EVM)
1. microcomputer module used in application development, e.g., to benchmark software, prototype applications,
and debug algorithms for computer systems

### 3.1495
EVM
1. earned value management [IEEE 15288.1:2014 IEEE Standard for Application of Systems Engineering on Defense
Programs, ### 3.2] 2. evaluation module

### 3.1516
expected monetary value (EMV) Analysis
1. a statistical technique that calculates the average outcome when the future includes scenarios that may or may
not happen. A common use of this technique is within decision tree analysis. [A Guide to the Project Management
Body of Knowledge (PMBOK? Guide) - Fifth Edition]

### 3.1521
expert system (ES)
1. computer system that provides for expertly solving problems in a given field or application area by drawing
inferences from a knowledge base developed from human expertise [ISO/IEC 2382:2015, Information technology ?
Vocabulary]
Note 1 to entry: Some expert systems are able to improve their knowledge base and develop new inference rules based on their
experience with previous problems.


extensible markup language (XML)
1. license-free and platform-independent markup language that carries rules for generating text formats that
contain structured data [ISO/IEC 19770-5:2015 Information technology - IT asset management - Part 5: Overview
and vocabulary, ### 3.15]

### 3.1540
external input (EI)
1. a unique function recognized by the user in which data and/or control information from outside the application
is entered into the application [ISO/IEC 24570:2005 Software engineering - NESMA functional size measurement
method version 2.1 - Definitions and counting guidelines for the application of Function Point Analysis] 2.
elementary process that processes data or control information sent from outside the boundary [ISO/IEC
20926:2009 Software and systems engineering - Software measurement - IFPUG functional size measurement
method 2009, ### 3.27]
cf. external inquiry, external output
Note 1 to entry: The primary intent of an EI is to maintain one or more ILFs and/or to alter the behavior of the system. An external
input is a type of base functional component.
### 3.1541
external inquiry (EQ)
1. a unique input/output combination recognized by the user in which the application distributes an output fully
determined in size without further data processing, as a result of the input [ISO/IEC 24570:2005 Software
engineering - NESMA functional size measurement method version 2.1 - Definitions and counting guidelines for the
application of Function Point Analysis] 2. elementary process that sends data or control information outside the
boundary [ISO/IEC 20926:2009 Software and systems engineering - Software measurement - IFPUG functional size
measurement method 2009, ### 3.28]
cf. external input, external output
Note 1 to entry: The primary intent of an external inquiry is to present information to a user through the retrieval of data or
control information from an ILF or EIF. The processing logic contains no mathematical formulas or calculations, and creates no
derived data. No ILF is maintained during the processing, nor is the behavior of the system altered. An external inquiry is a type
of base functional component.
### 3.1542
external interface file (EIF)
1. a logical group of permanent data seen from the perspective of the user that an application uses but that a
different application maintains [ISO/IEC 24570:2005 Software engineering - NESMA functional size measurement
method version 2.1 - Definitions and counting guidelines for the application of Function Point Analysis] 2. userrecognizable
group of logically related data or control information, which is referenced by the application being
measured, but which is maintained within the boundary of another application [ISO/IEC 20926:2009 Software and
systems engineering - Software measurement - IFPUG functional size measurement method 2009, ### 3.29]
cf. internal logical file
Note 1 to entry: The primary intent of an EIF is to hold data referenced through one or more elementary processes within the
boundary of the application counted. This means an EIF counted for an application must be in an ILF in another application. An
external interface file is a type of base functional component.

### 3.1547
external output (EO)
1. a unique output recognized by the user which crosses the application boundary [ISO/IEC 24570:2005 Software
engineering - NESMA functional size measurement method version 2.1 - Definitions and counting guidelines for the
application of Function Point Analysis] 2. elementary process that sends data or control information outside the
application's boundary and includes additional processing logic beyond that of an external inquiry [ISO/IEC
20926:2009 Software and systems engineering - Software measurement - IFPUG functional size measurement
method 2009, ### 3.30]
cf. external input, external inquiry
Note 1 to entry: The primary intent of an external output is to present information to a user through processing logic other than,
or in addition to, the retrieval of data or control information. The processing logic must contain at least one mathematical formula
or calculation, or create derived data. An external output can also maintain one or more ILFs and/or alter the behavior of the
system. An external output is a type of base functional component.

### 3.1551
F-profile
1. Format and presentation profile [ISO/IEC 10746-1:1998 Information technology - Open Distributed Processing ?
Reference model: Overview]

### 3.1576
FCA
1. functional configuration audit

### 3.1577
FD
1. full deployment [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense Programs, ### 3.2]
### 3.1578
FDC
1. functional domain categorization [ISO/IEC TR 14143-5:2004 Information technology - Software measurement ?
Functional size measurement - Part 5: Determination of functional domains for use with functional size measurement,
4]
### 3.1579
FDT
1. formal description techniques [ISO/IEC 10746-1:1998 Information technology - Open Distributed Processing ?
Reference model: Overview]

### 3.1589
FF
1. finish-to-finish [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]
### 3.1590
FFP
1. firm fixed price (contract) [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth
Edition]

### 3.1592
field programmable gate array (FPGA)
1. logic device designed to be programmed after it is acquired
Note 1 to entry: often based on look-up table architecture

### 3.1594
fifth-generation language (5GL)
1. computer language that incorporates the concepts of knowledge-based systems, expert systems, inference
engines, and natural language processing
cf. assembly language, fourth-generation language, high-order language, machine language

### 3.1597
file type referenced (FTR)
1. data function read or maintained by a transactional function [ISO/IEC 20926:2009 Software and systems
engineering - Software measurement - IFPUG functional size measurement method 2009, ### 3.31] 2. an internal logical
file (ILF) or an external interface file (EIF) maintained or read by a transaction [ISO/IEC 24570:2005 Software　engineering - NESMA functional size measurement method version 2.1 - Definitions and counting guidelines for the
application of Function Point Analysis]

### 3.1602
finish-to-finish (FF)
1. a logical relationship in which a successor activity cannot finish until a predecessor activity has finished [A
Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]
cf. logical relationship
### 3.1603
finish-to-start (FS)
1. a logical relationship in which a successor activity cannot start until a predecessor activity has finished [A Guide
to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]
cf. logical relationship

### 3.1605
firm-fixed-price contract (FFP)
1. a type of fixed price contract where the buyer pays the seller a set amount (as defined by the contract), regardless
of the seller's costs [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]
### 3.1606

### 3.1608
FiSMA
1. Finnish Software Measurement Association [ISO/IEC 29881:2010 Information technology - Software and systems
engineering - FiSMA 1.1 functional size measurement method, A.10]
Note 1 to entry: a network of Finnish companies, which share interest in developing software measurement and/or software
processes.

### 3.1611
fixed price with economic price adjustment contract (FP-EPA)
1. A fixed-price contract, but with a special provision allowing for pre-defined final adjustments to the contract price
due to changed conditions, such as inflation changes, or cost increases (or decreases) for specific commodities [A
Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]

### 3.1615
fixed-price-incentive-fee (FPIF) contract
1. a type of contract where the buyer pays the seller a set amount (as defined by the contract), and the seller can
earn an additional amount if the seller meets defined performance criteria [A Guide to the Project Management Body
of Knowledge (PMBOK? Guide) - Fifth Edition]

### 3.1617
flash memory
NVRAM
non-volatile random access memory
1. larger and faster programmable ROM which allows data to be electrically erased from memory and rewritten
many times
cf. EEPROM

FMEA
1. failure mode and effect analysis [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth
Edition]
### 3.1624
FMECA
1. failure mode, effects, and criticality analysis [IEEE 15288.1:2014 IEEE Standard for Application of Systems
Engineering on Defense Programs, ### 3.2]
### 3.1625
FOC
1. full operational capability [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense
Programs, ### 3.2]

### 3.1628
For Exposition Only (FEO) page
1. model page that contains pictorial and graphical information (in contrast to text) about a specific diagram [IEEE
1320.1-1998 (R2004) IEEE Standard for Functional Modeling Language - Syntax and Semantics for IDEF0, 2.1.51]
Note 1 to entry: Unlike a diagram, the contents of a For Exposition Only page (FEO page) need not comply with IDEF0 rules.

### 3.1640
formal qualification review (FQR)
1. test, inspection, or analytical process by which a group of configuration items comprising a system is verified to
have met specific contractual performance requirements
cf. code review, design review, requirements review, test readiness review

### 3.1649
FOSS
1. free and open source software

### 3.1652
fourth-generation language (4GL)
1. computer language designed to improve the productivity achieved by high-order (third-generation) languages
and, often, to make computing power available to non-programmers
cf. machine language, assembly language, high order language, fifth-generation language
Note 1 to entry: Features typically include an integrated database management system, query language, report generator, screen
definition facility, graphics generator, decision support function, financial modeling, spreadsheet capability, and statistical
analysis functions.
### 3.1653
FP-EPA
1. fixed price with economic price adjustment [A Guide to the Project Management Body of Knowledge (PMBOK?
Guide) - Fifth Edition]
### 3.1654
FPA
1. function point analysis [ISO/IEC 20926:2009 Software and systems engineering - Software measurement - IFPUG
functional size measurement method 2009, 4; ISO/IEC 24570:2005 Software engineering - NESMA functional size
measurement method version 2.1 - Definitions and counting guidelines for the application of Function Point Analysis]

### 3.1656
FPA tables EIF
1. the external interface file that is counted for the set of all FPA tables identified in an application that are only used
by the application to be counted, but that are maintained by a different application [ISO/IEC 24570:2005 Software
engineering - NESMA functional size measurement method version 2.1 - Definitions and counting guidelines for the
application of Function Point Analysis]
### 3.1657
FPA tables ILF
1. the internal logical file that is counted for the set of all identifiable and maintainable FPA tables in an application
[ISO/IEC 24570:2005 Software engineering - NESMA functional size measurement method version 2.1 - Definitions
and counting guidelines for the application of Function Point Analysis]
### 3.1658
FPGA
1. field programmable gate array [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense
Programs, ### 3.2]
### 3.1659
FPIF
1. fixed price incentive fee [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]
### 3.1660
FQR
1. formal qualification review
### 3.1661
FRACAS
1. failure reporting and corrective action system [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits
on Defense Programs, ### 3.2]

### 3.1668
FRP
1. full-rate production. [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense Programs,
### 3.2]
### 3.1669
FRR
1. flight readiness review. [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense Programs,
### 3.2]
### 3.1670
FS
1. finish-to-start. [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]
### 3.1671
FSM
1. functional size measurement. [ISO/IEC 14143-1:2007 Information technology - Software measurement ?
Functional size measurement; Part 1: Definition of concepts, 4; ISO/IEC 19761:2011 Software engineering - COSMIC:
a functional size measurement method, 2.11]
### 3.1672
FSM method
1. a specific implementation of FSM defined by a set of rules. [ISO/IEC 14143-1:2007 Information technology ?
Software measurement - Functional size measurement; Part 1: Definition of concepts, ### 3.4]
### 3.1673
FSMM
1. functional size measurement method. [ISO/IEC 14143-6:2012 Information technology - Software measurement
? Functional size measurement - Part 6: Guide for use of ISO/IEC 14143 series and related International Standards,
2]
### 3.1674
FTP
1. File Transfer Protocol. [ISO/IEC/IEEE 23026:2015 Systems and software engineering - Engineering and
management of websites for systems, software, and services information, 5]
### 3.1675
FTR
1. file type referenced. [ISO/IEC 20926:2009 Software and systems engineering - Software measurement - IFPUG
functional size measurement method 2009, 4; ISO/IEC 24570:2005 Software engineering - NESMA functional size
measurement method version 2.1 - Definitions and counting guidelines for the application of Function Point Analysis]

### 3.1679
function point (FP)
1. a unit which expresses the size of an application or of a project [ISO/IEC 24570:2005 Software engineering ?
NESMA functional size measurement method version 2.1 - Definitions and counting guidelines for the application of
Function Point Analysis] 2. unit of measure for functional size as defined within ISO/IEC 20926:2009 [ISO/IEC
20926:2009 Software and systems engineering - Software measurement - IFPUG functional size measurement
method 2009, ### 3.35] ### 3. a measure of the delivered software functionality [IEEE 1045-1992, (R2002) IEEE Standard
for Software Productivity Metrics, ### 3.2]
### 3.1680
function point analysis (FPA)
1. a method used to acquire a measurement of the amount of functionality an application provides a user [ISO/IEC
24570:2005 Software engineering - NESMA functional size measurement method version 2.1 - Definitions and
counting guidelines for the application of Function Point Analysis] 2. a form of functional size measurement (FSM)
that measures the functional size of software development, enhancement and maintenance activities associated
with business applications, from the customer's point of view [ISO/IEC 20968:2002 Software engineering - Mk II
Function Point Analysis - Counting Practices Manual, 10] ### 3. method for measuring functional size as defined in
ISO/IEC 29026:2009 [ISO/IEC 20926:2009 Software and systems engineering - Software measurement - IFPUG
functional size measurement method 2009, ### 3.36]

### 3.1692
functional configuration audit (FCA)
1. audit conducted to verify that the development of a configuration item has been completed satisfactorily, that the
item has achieved the performance and functional characteristics specified in the functional or allocated
configuration identification, and that its operational and support documents are complete and satisfactory [IEEE
828-2012 IEEE Standard for Configuration Management in Systems and Software Engineering, 2.1]
cf. configuration management, physical configuration audit

### 3.1698
functional domain categorization (FDC)
1. a process for identifying functional domains that conforms to the requirements of ISO/IEC TR 14143-5:2004, 5.2.
[ISO/IEC TR 14143-5:2004 Information technology - Software measurement - Functional size measurement - Part
5: Determination of functional domains for use with functional size measurement, ### 3.2]

### 3.1706
functional size
FS
1. size of the software derived by quantifying the functional user requirements [ISO/IEC 14143-1:2007 Information
technology - Software measurement - Functional size measurement; Part 1: Definition of concepts, ### 3.6; ISO/IEC
20926:2009 Software and systems engineering - Software measurement - IFPUG functional size measurement
method 2009, ### 3.33]
### 3.1707
functional size measurement (FSM)
1. the process of measuring functional size [ISO/IEC 14143-1:2007 Information technology - Software measurement
? Functional size measurement; Part 1: Definition of concepts, ### 3.7; ISO/IEC 19761:2011 Software engineering ?
COSMIC: a functional size measurement method, 2.11]
### 3.1708
functional size measurement method (FSMM)
FSM method
1. specific implementation of FSM defined by a set of rules [ISO/IEC 19761:2011 Software engineering - COSMIC: a
functional size measurement method, 2.12]

### 3.1715
functional user requirements (FUR)
1. subset of the user requirements specifying what the software shall do in terms of tasks and services [ISO/IEC
20926:2009 Software and systems engineering - Software measurement - IFPUG functional size measurement
method 2009, ### 3.34] 2. a subset of the user requirements describing what the software does in terms of tasks and
services [ISO/IEC 14143-1:2007 Information technology - Software measurement - Functional size measurement;
Part 1: Definition of concepts, ### 3.8; ISO/IEC 19761:2011 Software engineering - COSMIC: a functional size
measurement method, 2.14]
Note 1 to entry: Functional User Requirements include but are not limited to: data transfer (for example Input customer data,
Send control signal); data transformation (for example Calculate bank interest, Derive average temperature); data storage (for
example Store customer order, Record ambient temperature over time); data retrieval (for example List current employees,
Retrieve aircraft position). User Requirements that are not Functional User Requirements include but are not limited to: quality
constraints (for example usability, reliability, efficiency and portability); organizational constraints (for example locations for
operation, target hardware and compliance to standards); environmental constraints (for example interoperability, security,
privacy and safety); implementation constraints (for example development language, delivery schedule).

### 3.1718
FUR
1. functional user requirement(s) [ISO/IEC 14143-1:2007 Information technology - Software measurement ?
Functional size measurement; Part 1: Definition of concepts, 4; ISO/IEC 19761:2011 Software engineering - COSMIC:
a functional size measurement method, 2.14]
### 3.1719
fuse ROM
1. programmable ROM with written data based on a fuse connection state
EXAMPLE: If the normal state of the fuse means logic "1", the breaking state is "0."

### 3.1723
GATES
1. Stage-Gate methodology [ISO/IEC/IEEE 16326:2009 Systems and software engineering - Life cycle processes ?
Project management, 3]
### 3.1724
general purpose input/output port (GPIO)
1. generic pin (port) on a microcomputer whose function (whether it is an input or output pin) is not predefined
and is user-controlled

### 3.1726
general system characteristics (GSCs)
1. terminology for technical complexity adjustment factors [ISO/IEC 20968:2002 Software engineering - Mk II
Function Point Analysis - Counting Practices Manual, 10]

### 3.1740
GFE
1. government-furnished equipment [IEEE 15288.1:2014 IEEE Standard for Application of Systems Engineering on
Defense Programs, ### 3.2]
### 3.1741
GFI
1. government-furnished information [IEEE 1517-2010 IEEE Standard for Information Technology - System and
software life cycle processes - Reuse processes, ### 3.2]
### 3.1742
GIF
1. General Interworking Framework [ISO/IEC 14752:2000 Information technology - Open Distributed Processing ?
Protocol support for computational interactions, 4] 2. Graphics Interchange Format [ISO/IEC/IEEE 23026:2015
Systems and software engineering - Engineering and management of websites for systems, software, and services
information, 5]
### 3.1743
GIOP
1. General Inter-ORB Protocol [ISO/IEC 19500-2:2012 Information technology - Object Management Group ?
Common Object Request Broker Architecture (CORBA) - Part 2: Interoperability, ### 3.3]

### 3.1751
globally unique identifier (GUID)
1. 16-byte string of characters that is generated in a manner that gives a high probability that the string is unique in
any context [ISO/IEC 19770-5:2015 Information technology - IT asset management - Part 5: Overview and
vocabulary, ### 3.16]
Note 1 to entry: GUID as an all capitalized term refers specifically to the 16-byte version. If the term is in lowercase (guid), it
refers to a general algorithm that can use either a URI or a 16-byte-based identifier.

### 3.1756
GOTS
1. government-off-the-shelf.

Government-off-the-Shelf
GOTS
1. software supplied by the government for reuse in another project
cf. COTS
### 3.1759
GPIO
1. general-purpose input/output port

### 3.1771
GUI
1. Graphical User Interface [ISO/IEC 10746-1:1998 Information technology - Open Distributed Processing ?
Reference model: Overview]
### 3.1772
GUID
1. globally unique identifier [ISO/IEC 19770-5:2015 Information technology - IT asset management - Part 5:
Overview and vocabulary, ### 3.16]

### 3.1782
hardware configuration item (HCI)
1. aggregation of hardware that is designated for configuration management and treated as a single entity in the
configuration management process
cf. software configuration item
Note 1 to entry: An HCI exists where functional allocations have been made that clearly distinguish equipment functions from
software functions and where the hardware has been established as a configuration item.
### 3.1783
hardware description language (HDL)
hardware design language
1. software programming language used to design and model hardware, especially digital logic circuits
EXAMPLE: VHDL (IEEE 1076), Verilog (IEEE 1364)

### 3.1789
HCI
HWCI
1. human computer interface [ISO/IEC 10746-1:1998 Information technology - Open Distributed Processing ?
Reference model: Overview] 2. hardware configuration item
### 3.1790
HDD
1. hardware design description [IEEE 1012-2012 IEEE Standard for System and Software Verification and Validation,
### 3.2]
### 3.1791
HDL
1. hardware description language 2. hardware design language
cf. design language
### 3.1792
HDTV
1. High Definition TV [ISO/IEC 10746-1:1998 Information technology - Open Distributed Processing - Reference
model: Overview]

### 3.1809
high-order language (HOL)
high-level language
higher order language
third-generation language
1. programming language that requires little knowledge of the computer on which a program will run, can be
translated into several different machine languages, allows symbolic naming of operations and addresses, provides
features designed to facilitate expression of data structures and program logic, and usually results in several
machine instructions for each program statement
cf. assembly language, fifth-generation language, fourth-generation language, machine language
EXAMPLE: Ada, COBOL, FORTRAN, ALGOL, PASCAL

### 3.1813
HLL
1. high-level language
cf. high-order language
### 3.1814
HLPN
1. High-level Petri Net [ISO/IEC 15909-1:2004 Software and system engineering - High-level Petri nets - Part 1:
Concepts, definitions and graphical notation, 2.2.1]
### 3.1815
HLPNG
1. High-level Petri Net Graph [ISO/IEC 15909-1:2004 Software and system engineering - High-level Petri nets - Part
1: Concepts, definitions and graphical notation, 2.2.2]

### 3.1816
HLPNS
1. High-level Petri Net Schema [ISO/IEC 15909-1:2004 Software and system engineering - High-level Petri nets ?
Part 1: Concepts, definitions and graphical notation, 2.2.3]
### 3.1817
HMI
1. human-machine interface
cf. user interface
### 3.1818
HOL
1. high-order language

### 3.1825
HREF
1. HTML reference designator [ISO/IEC/IEEE 23026:2015 Systems and software engineering - Engineering and
management of websites for systems, software, and services information, 5]
### 3.1826
HRS
1. hardware requirements specification [IEEE 1012-2012 IEEE Standard for System and Software Verification and
Validation, ### 3.1]
### 3.1827
HSI
1. human systems integration [ISO/IEC/IEEE 29148:2011 Systems and software engineering - Life cycle processes
? Requirements engineering, 4.2]
### 3.1828
HTML
1. HyperText Markup Language [ISO/IEC/IEEE 23026:2015 Systems and software engineering - Engineering and
management of websites for systems, software, and services information, 5]
### 3.1829
HTTP
1. HyperText Transfer Protocol [ISO/IEC/IEEE 23026:2015 Systems and software engineering - Engineering and
management of websites for systems, software, and services information, 5]

### 3.1833
human systems integration (HSI)
1. interdisciplinary technical and process for integrating human considerations with and across all
system elements, an essential enabler to systems engineering practice [ISO/IEC/IEEE 29148:2011 Systems and
software engineering - Life cycle processes - Requirements engineering, 4.1.11]

### 3.1836
HW
1. hardware [IEEE 1012-2012 IEEE Standard for System and Software Verification and Validation, ### 3.2]
### 3.1837
HWCI
1. hardware configuration item [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense
Programs, ### 3.2]

### 3.1840
I/O
1. input/output
### 3.1841
I/O task-structuring criteria
1. category of the task-structuring criteria addressing how device interface objects are mapped to I/O tasks and
when an I/O task is activated
### 3.1842
I2C
IIC
1. inter-integrated circuit bus
### 3.1843
IAP
1. in-application programming
### 3.1844
IBa
1. issue benchmarks activity [ISO/IEC 29155-2:2013: Systems and software engineering - Information technology
project performance benchmarking framework - Part 2: Requirements for benchmarking, 4]
### 3.1845
IBD
1. information-based domain [ISO/IEC 24744:2014 Software Engineering - Metamodel for development
methodologies, 4.2]

### 3.1846
ICD
1. initial capabilities document [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense
Programs, ### 3.2]
### 3.1847
ICE
1. in-circuit emulator
### 3.1848
ICOM
1. input, control, output, and mechanism [IEEE 1320.1-1998 (R2004) IEEE Standard for Functional Modeling
Language - Syntax and Semantics for IDEF0, 2.2]

### 3.1852
ICS
1. Implementation Conformance Statement [ISO/IEC 10746-1:1998 Information technology - Open Distributed
Processing - Reference model: Overview]
### 3.1853
ICT
1. information and communication technology [ISO/IEC/IEEE 23026:2015 Systems and software engineering ?
Engineering and management of websites for systems, software, and services information, 5]
### 3.1854
ICWG
1. Interface Control Working Group [ISO/IEC/IEEE 16326:2009 Systems and software engineering - Life cycle
processes - Project management, 5]
Note 1 to entry: Depending on the size and complexity of a project, can be a group of people, a single person or a function
### 3.1855
IDD
interface design document
IEEE 1012-2012 IEEE Standard for System and Software Verification and Validation,
### 3.2]

### 3.1856
IDE
1. integrated development environment

### 3.1859
IDEF0 model
1. abstractly, a hierarchical set of IDEF0 diagrams that depict, for a specific purpose and from a specific viewpoint,
the functions of a system or subject area, along with supporting glossary, text, and For Exposition Only (FEO)
information [IEEE 1320.1-1998 (R2004) IEEE Standard for Functional Modeling Language - Syntax and Semantics for
IDEF0, 2.1.60]
Note 1 to entry: Concretely, a set of model pages that include at least an A-0 context diagram and an A0 decomposition diagram,
a glossary or specific glossary pages, one or more text pages to accompany each diagram, and FEO pages and model pages of
other types as needed.
### 3.1860
IDEF1X model
1. et of one or more IDEF1X views, often represented as view diagrams that depict the underlying semantics of the
views, along with definitions of the concepts used in the views [IEEE 1320.2-1998 (R2004) IEEE Standard for
Conceptual Modeling Language Syntax and Semantics for IDEF1X97 (IDEFobject), ### 3.1.75]

### 3.1867
IDL
1. Interface Definition Language [ISO/IEC 10746-1:1998 Information technology - Open Distributed Processing ?
Reference model: Overview]

### 3.1870
IEC
1. International Electrotechnical Commission [ISO/IEC/IEEE 16326:2009 Systems and software engineering - Life
cycle processes - Project management, 5]
### 3.1871
IEEE
1. Institute of Electrical and Electronics Engineers [ISO/IEC/IEEE 16326:2009 Systems and software engineering ?
Life cycle processes - Project management, 3]
### 3.1872
IETF
1. Internet Engineering Task Force

### 3.1874
IFB
1. invitation for bid [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]
### 3.1875
iff
1. if and only if [ISO/IEC 15909-1:2004 Software and system engineering - High-level Petri nets - Part 1: Concepts,
definitions and graphical notation, 2.2.4]
### 3.1876
IFPUG
1. International Function Point Users Group [ISO/IEC 20926:2009 Software and systems engineering - Software
measurement - IFPUG functional size measurement method 2009]
Note 1 to entry: membership governed, non-profit organization committed to promoting and supporting function point analysis
and other software measurement techniques. The IFPUG maintains the definition of the direct descendent of the Albrecht 1984
FPA method
### 3.1877
IIOP
1. Internet Inter-ORB Protocol [ISO/IEC 19500-2:2012 Information technology - Object Management Group ?
Common Object Request Broker Architecture (CORBA) - Part 2: Interoperability, ### 3.3]
### 3.1878
IIOP-IOR
1. Internet Inter-ORB Protocol - Interoperable Object Reference [ISO/IEC 14753:1999 Information technology ?
Open Distributed Processing - Interface references and binding, 4]
### 3.1879
ILF
1. internal logical file [ISO/IEC 20926:2009 Software and systems engineering - Software measurement - IFPUG
functional size measurement method 2009, 4; ISO/IEC 24570:2005 Software engineering - NESMA functional size
measurement method version 2.1 - Definitions and counting guidelines for the application of Function Point Analysis]

### 3.1887
IMP
1. integrated master plan [IEEE 15288.1:2014 IEEE Standard for Application of Systems Engineering on Defense
Programs, ### 3.2]

### 3.1902
IMS
1. integrated master schedule [IEEE 15288.1:2014 IEEE Standard for Application of Systems Engineering on Defense
Programs, ### 3.2]
### 3.1903
in-application programming (IAP)
1. capability of a microcontroller unit to fetch new program code and reprogram itself while the system is operating
cf. in-system programming
### 3.1904
in-circuit emulator (ICE)
1. hardware device used to debug the software of an embedded system
### 3.1905
in-system programming (ISP)
1. capability of a microcontroller unit to allow the user to download new code (reprogram the unit), activated by
restarting the unit
cf. in-application programming

### 3.1927
independent verification and validation (IV&V)
1. verification and validation performed by an organization that is technically, managerially, and financially
independent of the development organization [IEEE 1012-2012 IEEE Standard for System and Software Verification
and Validation, ### 3.1]

### 3.1962
information retrieval (IR)
1. actions, methods, and procedures for obtaining information on a given subject from stored data [ISO/IEC 2382:2015,
Information technology - Vocabulary]

### 3.1966
information technology
IT
1. resources required to acquire, process, store and disseminate information
Note 1 to entry: includes Communication Technology (CT) and the composite term Information and Communication Technology
(ICT)

### 3.1969
Information-based domain (IBD)
1. realm of activity for which information is the most valuable asset [ISO/IEC 24744:2014 Software Engineering ?
Metamodel for development methodologies, ### 3.1]
Note 1 to entry: Information creation, manipulation, and dissemination are the most important activities within informationbased
domains. Typical information-based domains are software and systems engineering, business process reengineering, and
knowledge management

### 3.1999
input-process-output (IPO) chart
1. diagram of a software system or module, consisting of a rectangle on the left listing inputs, a rectangle in the
center listing processing steps, a rectangle on the right listing outputs, and arrows connecting inputs to processing
steps and processing steps to outputs
cf. block diagram, box diagram, bubble chart, flowchart, graph, structure chart

### 3.2028
integrated circuit (IC)
microchip
chip
1. small piece of semiconductive material that contains interconnected electronic elements [ISO/IEC 2382:2015,
Information technology - Vocabulary]
### 3.2029
integrated development environment (IDE)
1. set of software tools or applications to provide comprehensive facilities for software development

### 3.2045
inter-integrated circuit bus (I2C)
1. bi-directional two-wire serial bus that provides a communication link between integrated circuits

### 3.2060
interface design document (IDD)
1. documentation that describes the architecture and design interfaces between system and components [IEEE
1012-2012 IEEE Standard for System and Software Verification and Validation, ### 3.1.16] 2. description of the
architecture and design of interfaces between system and components
cf. interface requirements specification (IRS)
Note 1 to entry: These descriptions include control algorithms, protocols, data contents and formats, and performance.

### 3.2062
interface requirements specification (IRS)
1. documentation that specifies requirements for interfaces between or among systems and components [IEEE
1012-2012 IEEE Standard for System and Software Verification and Validation, ### 3.1.17]
Note 1 to entry: These requirements include constraints on formats and timing.

### 3.2080
internal logical file (ILF)
1. user-recognizable group of logically related data or control information maintained within the boundary of the
application being measured [ISO/IEC 20926:2009 Software and systems engineering - Software measurement ?
IFPUG functional size measurement method 2009, ### 3.39] 2. a logical group of permanent data seen from the
perspective of the user that an application uses and maintains [ISO/IEC 24570:2005 Software engineering - NESMA
functional size measurement method version 2.1 - Definitions and counting guidelines for the application of Function
Point Analysis]
cf. external interface file
Note 1 to entry: The primary intent of an ILF is to hold data maintained through one or more elementary processes of the
application being counted. An internal logical file is a type of base functional component


### 3.2086
international standard (IS)
1. standard that is adopted by an international standardizing/standards organization and made available to the
public [ISO/IEC TR 29110-1:2016 Software engineering - Lifecycle profiles for Very Small Entities (VSEs) - Part 1:
Overview, 2.11]
Note 1 to entry: [ISO/IEC Directives, Part 2]


### 3.2103
interrupt service routine
ISR
1. routine that responds to interrupt requests by storing the contents of critical registers, performing the processing
required by the interrupt request, restoring the register contents, and restarting the interrupted process

### 3.2114
invitation for bid (IFB)
1. generally, this term is equivalent to request for proposal. However, in some application areas, it may have a
narrower or more specific meaning [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth
Edition]

### 3.2118
IOC
1. initial operational capability [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense
Programs, ### 3.2]
### 3.2119
IOR
1. Interoperable Object Reference [ISO/IEC 19500-2:2012 Information technology - Object Management Group ?
Common Object Request Broker Architecture (CORBA) - Part 2: Interoperability, ### 3.3]
### 3.2120
IOT&E
1. initial operational test and evaluation [IEEE 15288.1:2014 IEEE Standard for Application of Systems Engineering
on Defense Programs, ### 3.2]
### 3.2121
IP
1. Internet Protocol [ISO/IEC/IEEE 23026:2015 Systems and software engineering - Engineering and management
of websites for systems, software, and services information, 5]
### 3.2122
IPO chart
1. input-process-output chart
### 3.2123
IPR
1. intellectual property rights [ISO/IEC/IEEE 23026:2015 Systems and software engineering - Engineering and
management of websites for systems, software, and services information, 5]
### 3.2124
IPSE
1. integrated programming support environment
cf. programming support environment
### 3.2125
IPT
1. integrated product team [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense Programs,
### 3.2]

IRR
1. integration readiness review [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense
Programs, ### 3.2]

### 3.2128
IRS
1. interface requirements specification.
### 3.2129
IS
1. International Standard
### 3.2130
ISO
1. International Organization for Standardization [ISO/IEC/IEEE 16326:2009 Systems and software engineering ?
Life cycle processes - Project management, 5]
### 3.2131
ISO file
1. file image of an entire CD or DVD that is encoded according to ISO 9660 [IEEE 828-2012 IEEE Standard for
Configuration Management in Systems and Software Engineering, 2.1]

### 3.2133
ISP
1. in-system programming
### 3.2134
ISR
2. interrupt service routine -->誤植1が正しい。


### 3.2137
IT
1. Information Technology [ISO/IEC 10746-1:1998 Information technology - Open Distributed Processing ?
Reference model: Overview]

### 3.2143
IV&V
1. independent verification and validation
### 3.2144
IVV
1. integration, verification, validation [ISO/IEC TR 29110-5-6-2:2014 Systems and software engineering - Lifecycle
profiles for Very Small Entities (VSEs) - Part 5-6-2: Systems engineering - Management and engineering guide:
Generic profile group: Basic profile, 4.2]
### 3.2145
IXIT
1. Implementation Extra Information for Testing [ISO/IEC 10746-1:1998 Information technology - Open Distributed
Processing - Reference model: Overview]
### 3.2146
JCIDS
1. joint capabilities integration and development system [IEEE 15288.1:2014 IEEE Standard for Application of
Systems Engineering on Defense Programs, ### 3.2]

### 3.2147
JCL
1. job control language
### 3.2148
JDK
1. Java development kit [ISO/IEC 19500-3:2012 Information technology - Object Management Group - Common
Architecture Request Broker Architecture (CORBA) - Part 3: Components, 4.3]
### 3.2149
JFC
1. Java Foundation Class [ISO/IEC/IEEE 23026:2015 Systems and software engineering - Engineering and
management of websites for systems, software, and services information, 5]
### 3.2150
JNDI
1. Java naming and directory interface [ISO/IEC 19500-3:2012 Information technology - Object Management Group
? Common Architecture Request Broker Architecture (CORBA) - Part 3: Components, 4.3]

### 3.2152
job control language (JCL)
1. language used to identify a sequence of jobs, describe their requirements to an operating system, and control
their execution

### 3.2158
JPEG
1. Joint Photographic Experts Group [ISO/IEC/IEEE 23026:2015 Systems and software engineering - Engineering
and management of websites for systems, software, and services information, 5]
Note 1 to entry: image format
### 3.2159
JPG
1. Joint Photographic Group [ISO/IEC/IEEE 23026:2015 Systems and software engineering - Engineering and
management of websites for systems, software, and services information, 5]
Note 1 to entry: image format
### 3.2160
JTA
1. Java Transaction API [ISO/IEC 19500-3:2012 Information technology - Object Management Group - Common
Architecture Request Broker Architecture (CORBA) - Part 3: Components, 4.3]

### 3.2163
KDM
1. knowledge discovery meta-model [ISO/IEC 19506:2012 Information technology - Object Management Group
Architecture-Driven Modernization (ADM) - Knowledge Discovery Meta-Model (KDM), 4]

### 3.2173
knowledge base (K-base)
1. database that contains inference rules and information about human experience and expertise in a domain
[ISO/IEC 2382:2015, Information technology - Vocabulary]
Note 1 to entry: In self-improving systems, the knowledge base additionally contains information resulting from the solution of
previously encountered problems

KOPS
1. kilo-operations per second; that is, thousands of operations per second
cf. MFLOPS, MIPS
Note 1 to entry: a measure of computer processing speed

### 3.2176
KPP
1. key performance parameter [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense
Programs, ### 3.2]
### 3.2177
KSA
1. key system attribute [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense Programs,
### 3.2]

### 3.2185
late finish date (LF)
1. in the Critical Path Method, the latest possible point in time when the uncompleted portions of a schedule activity
can finish based on the schedule network logic, the project completion date, and any schedule constraints [A Guide
to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]

### 3.2186
late start date (LS)
1. in the Critical Path Method, the latest possible point in time when the uncompleted portions of a schedule activity
can start based on the schedule network logic, the project completion date, and any schedule constraints [A Guide
to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]

### 3.2193
LCC
1. life-cycle cost [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense Programs, ### 3.2]
### 3.2194
LCCE
1. life-cycle cost estimate [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense Programs,
### 3.2]
### 3.2195
LCSP
1. life cycle sustainment plan [IEEE 15288.1:2014 IEEE Standard for Application of Systems Engineering on Defense
Programs, ### 3.2]

### 3.2207
level of effort (LOE)
1. an activity that does not produce definitive end products and is measured by the passage of time [A Guide to the
Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]
EXAMPLE: customer liaison, project cost accounting, project management
Note 1 to entry: One of three EVM types of activities used to measure work performance

### 3.2210
LF
1. late finish date [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]
### 3.2211
LFT&E
1. live fire test and evaluation [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense
Programs, ### 3.2]

### 3.2236
LITSR
1. level interim test status report.

### 3.2244
local area network (LAN)
1. computer network located on a user's premises within a limited geographical area [ISO/IEC 2382:2015,
Information technology - Vocabulary]
Note 1 to entry: Communication within a local area network is not subject to external regulations; however, communication
across the LAN boundary can be subject to some form of regulation.

### 3.2259
LOE
1. level of effort [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]

### 3.2270
logical source statement (LSS)
1. software instruction, independent of the physical format (lines of code) in which it appears
cf. physical source statement

### 3.2283
low-profile quad flat package (LQFP)
1. semiconductor device based on a leadframe with gull wing-shaped leads on all four sides
Note 1 to entry: The LQFP package can be encapsulated in plastic.

### 3.2285
LQFP
1. low-profile quad flat package
### 3.2286
LRIP
1. low-rate initial production [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense
Programs, ### 3.2]
### 3.2287
LS
1. late start date [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]
### 3.2288
LTC
1. level test case.
### 3.2289
LTD
1. level test design.
### 3.2290
LTL
1. level test log.
### 3.2291
LTP
1. level test plan.
cf. LTPr
### 3.2292
LTPr
1. level test procedure.]
cf. LTP
### 3.2293
LTR
1. level test report.
### 3.2294
M&S
1. modeling and simulation [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense
Programs, ### 3.2]
### 3.2295
MAC
1. Media Access Control [ISO/IEC/IEEE 23026:2015 Systems and software engineering - Engineering and
management of websites for systems, software, and services information, 5]

maintenance manual (MM)
1. software engineering project-deliverable document that enables a system's maintenance personnel (rather than
users) to maintain the system
cf. operator manual, user manual

### 3.2362
MARR
1. minimum attractive rate of return

### 3.2364
mask ROM
1. read-only memory unit whose  are programmed during the manufacturing process

### 3.2376
MBLa
1. manage benchmarking business level activity [ISO/IEC 29155-2:2013: Systems and software engineering ?
Information technology project performance benchmarking framework - Part 2: Requirements for benchmarking, 4]
### 3.2377
MCU
1. microcontroller unit
### 3.2378
MD5
1. message digest 5 [ISO/IEC 19770-5:2015 Information technology - IT asset management - Part 5: Overview and
vocabulary, ### 3.22]
### 3.2379
MDA
1. Model Driven Architecture - [ISO/IEC 19500-3:2012 Information technology - Object Management Group ?
Common Architecture Request Broker Architecture (CORBA) - Part 3: Components, A.8]

### 3.2383
mean time between failures (MTBF)
1. the expected or observed time between consecutive failures in a system or component
cf. up time
### 3.2384
mean time to repair (MTTR)
1. expected or observed duration required to return a malfunctioning system or component to normal operations
2. the mean time the maintenance team requires to implement a change and restore the system to working order
cf. down time

### 3.2390
measure of effectiveness (MOE)
1. operational measure of success that is closely related to the achievement of the operational objective being
evaluated in the intended operational environment under a specified set of conditions [ISO/IEC/IEEE 24748-4:2016,
Systems and software engineering-Life cycle management-Part 4: Systems engineering planning, 4.7]
### 3.2391
measure of performance (MOP)
1. engineering parameter that provides critical performance requirements to satisfy a measure of effectiveness
(MOE) [ISO/IEC/IEEE 24748-4:2016, Systems and software engineering-Life cycle management-Part 4: Systems
engineering planning, 4.8]
Note 1 to entry: An MOP typically characterizes physical or functional attributes relating to the system operation.

meta-object facility
MOF
1. specification of the object management group for repositories of type information for arbitrary type systems
[ISO/IEC 14769:2001 Information technology - Open Distributed Processing - Type Repository Function, ### 3.### 3.1]

### 3.2445
MFLOPS
1. millions of floating point operations per second 2. megaflops, a unit of measure of processing performance equal
to one million floating-point operations per second [ISO/IEC 2382:2015, Information technology - Vocabulary]
cf. KOPS, MIPS
Note 1 to entry: a measure of computer processing speed

### 3.2450
microcontroller (unit) (MCU)
single chip microcomputer
1. unit with application control function on a single chip
Note 1 to entry: It contains a processor, RAM, ROM, clock, register, and I/O control unit.

### 3.2467
MIM
1. Management Information Model [ISO/IEC 10746-1:1998 Information technology - Open Distributed Processing
? Reference model: Overview]

### 3.2470
minimum attractive rate of return (MARR)
1. lowest rate of return at which an organization will consider investing; the interest rate used in business decision
analysis
cf. opportunity cost
Note 1 to entry: reflects a rate of return that the organization is confident it can achieve through typical activities

### 3.2473
MIPS
1. million instructions per second
cf. KOPS, MFLOPS
Note 1 to entry: a measure of computer processing speed

### 3.2475
MIS
1. management information system

### 3.2479
MMC(S)
1. Multimedia Conferencing (System) [ISO/IEC 10746-1:1998 Information technology - Open Distributed Processing
? Reference model: Overview]

### 3.2480 ->改定要求 Human Machine interface
MMI
1. man-machine interface
cf. user interface

### 3.2500
modification request (MR)
1. proposed changes to a product that is being maintained [IEEE 14764-2006 Software Engineering - Software Life
Cycle Processes - Maintenance, ### 3.6] 2. forms associated with the various trouble/problem-reporting documents and
the configuration change control documents
cf. change request, request for change
Note 1 to entry: The MR can be classified as a correction or enhancement and identified as corrective, preventive, adaptive, or
perfective maintenance. Trouble/problem-reporting documents include incident and problem reports; configuration change
control documents include software change requests (SCRs).

### 3.2502
modified-off-the-shelf (MOTS)
1. software product that is already developed and available, usable either 'as is' or with modification, and provided
by the supplier, acquirer, or a third party [IEEE 1062-2015 IEEE Recommended Practice for Software Acquisition, ### 3.1]
### 3.2503
MODL
1. Meta-Object Definition Language [ISO/IEC 14769:2001 Information technology - Open Distributed Processing ?
Type Repository Function, 4]

### 3.2510
MOE
1. measure of effectiveness [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense Programs,
### 3.2]

### 3.2511
MOF
1. meta-object facility [ISO/IEC 14769:2001 Information technology - Open Distributed Processing - Type
Repository Function, 4; ISO/IEC 19793:2015 Information technology - Open Distributed Processing - Use of UML for
ODP system specifications, 4]

### 3.2520
MOP
1. measure of performance [ISO/IEC/IEEE 29148:2011 Systems and software engineering - Life cycle processes ?
Requirements engineering, 4.2]

### 3.2521
MOPS
1. million operations per second

### 3.2523
MOTS
1. modified-off-the-shelf [IEEE 1062-2015 IEEE Recommended Practice for Software Acquisition, ### 3.1]
### 3.2524
MOU
1. memorandum of understanding

### 3.2526
MPa
1. measure IT project activity [ISO/IEC 29155-2:2013: Systems and software engineering - Information technology
project performance benchmarking framework - Part 2: Requirements for benchmarking, 4]
### 3.2527
MPLa
1. manage benchmarking program level activity [ISO/IEC 29155-2:2013: Systems and software engineering ?
Information technology project performance benchmarking framework - Part 2: Requirements for benchmarking, 4]
### 3.2528
MRa
1. maintain repository activity [ISO/IEC 29155-2:2013: Systems and software engineering - Information technology
project performance benchmarking framework - Part 2: Requirements for benchmarking, 4]
### 3.2529
MTBF
1. mean time between failures
### 3.2530
MTP
1. master test plan.
### 3.2531
MTR
1. master test report.
### 3.2532
MTTR
1. mean time to repair

### 3.2546
multiple-criteria decision making (MCDM)
multi-attribute decision making
1. making preference decisions (e.g., evaluation, prioritization, and selection) of available alternatives characterized
by multiple criteria [ISO/IEC 33003:2015 Information technology - Process assessment - Requirements for process
measurement frameworks, ### 3.9]
Note 1 to entry: An MCDM with one alternative is the same as the development of a composite measure.

### 3.2559
N 2 diagram
1. system engineering or software engineering tool for tabulating, defining, analyzing, and describing functional
interfaces and interactions among system components
Note 1 to entry: The N 2 diagram is a matrix structure that graphically displays the bidirectional interrelationships between
functions and components in a given system or structure.
### 3.2560
n-address instruction
1. computer instruction that contains n address fields, where n is any non-negative integer
cf. one-address instruction, two-address instruction, n-plus-one address instruction
### 3.2561
N-ary relationship
1. relationship with arity (degree) n > 2 [ISO/IEC 15474-1:2002 Information technology - CDIF framework - Part
1: Overview, 4.2]
Note 1 to entry: A relationship that has more than two participating entities. (Note that a single entity can participate several
times in a single relationship.)
### 3.2562
n-level address
1. indirect address that specifies the first of a chain of n storage locations, the first n-1 of which contains the
address of the next location in the chain and the last of which contains the desired operand
cf. direct address, immediate data
EXAMPLE: a two-level address
### 3.2563
n-plus-one address instruction
1. computer instruction that contains n+1 address fields, the last containing the address of the instruction to be
executed next
cf. one-plus-one address instruction, two-plus-one address instruction, n-address instruction

### 3.2564
N/A
1. not applicable [IEEE 1012-2012 IEEE Standard for System and Software Verification and Validation, ### 3.2] 2. not
available

### 3.2580
NDI
1. non-developmental item.

### 3.2628 -> not orじゃないのはなぜ？
NOR
1. in configuration management, a notice of revision

### 3.2635
notice of revision (NOR)
1. form used in configuration management to propose revisions to a drawing or list, and, after approval, to notify
users that the drawing or list has been, or will be, revised accordingly
cf. configuration control, engineering change, specification change notice

### 3.2638
O&S
1. operations and support [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense Programs,
### 3.2]

### 3.2641
object identifier
OID
1. some concrete representation for the identity of an object (instance) [IEEE 1320.2-1998 (R2004) IEEE Standard
for Conceptual Modeling Language Syntax and Semantics for IDEF1X97 (IDEFobject), ### 3.1.128]
Note 1 to entry: The object identifier (OID) is used to show examples of instances with identity, to formalize the notion of identity,
and to support the notion in programming languages or database systems.

### 3.2643
Object Management Group (OMG)
1. international standards organization that owns and maintains CORBA and UML standards

### 3.2658
OBS
1. organizational breakdown structure. [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) ?
Fifth Edition]

### 3.2663
OCD
1. operational concept document. [IEEE 1012-2012 IEEE Standard for System and Software Verification and
Validation, ### 3.2]
cf. concept of operations (ConOps) document
### 3.2664
OCL
1. Object Constraint Language. [ISO/IEC 14769:2001 Information technology - Open Distributed Processing - Type
Repository Function, 4; ISO/IEC 19793:2015 Information technology - Open Distributed Processing - Use of UML for
ODP system specifications, 4]

### 3.2666
ODP
1. Open Distributed Processing [ISO/IEC 19793:2015 Information technology - Open Distributed Processing - Use
of UML for ODP system specifications, 4]

### 3.2671
ODP-RM
RM-ODP
1. Open Distributed Processing: Reference Model. [ISO/IEC 14769:2001 Information technology - Open Distributed
Processing - Type Repository Function, 4]
### 3.2672
OEM
1. original equipment manufacturer. [ISO/IEC 19770-3:2016, Information technology - IT asset management - Part
3: Entitlement schema, ### 3.2]

### 3.2674
office automation (OA)
1. integration of office activities by means of an information processing system [ISO/IEC 2382:2015, Information
technology - Vocabulary]
Note 1 to entry: This term includes in particular the processing and communication of text, images, and voice.

### 3.2677
OGC
1. Office of Government Commerce (UK) [ISO/IEC/IEEE 16326:2009 Systems and software engineering - Life cycle
processes - Project management, 3]
### 3.2678
OID
1. object identifier [ISO/IEC 13235-3:1998 Information technology - Open Distributed Processing - Trading
Function - Part 3: Provision of Trading Function using OSI Directory service, 4]
### 3.2679
OMG
1. Object Management Group [ISO/IEC 10746-1:1998 Information technology - Open Distributed Processing ?
Reference model: Overview; ISO/IEC 19793:2015 Information technology - Open Distributed Processing - Use
of UML for ODP system specifications, 4]
### 3.2680
OMT
1. Object Modeling Technique [ISO/IEC 10746-1:1998 Information technology - Open Distributed Processing ?
Reference model: Overview]

### 3.2687
one-time programming (OTP)
1. method of recording data in ROM which can only be written once

### 3.2692
OOD
1. object-oriented design
### 3.2693
OPA
1. organizational process asset

### 3.2711
operational concept (OpsCon)
1. verbal and graphic statement of an organization's assumptions or intent in regard to an operation or series of
operations of a system or a related set of systems [ISO/IEC TS 24748-1:2016 Systems and software engineering ?
Life cycle management - Part 1: Guide for life cycle management, 2.26; ISO/IEC/IEEE 15288:2015 Systems and
software engineering - System life cycle processes, 4.1.25; ISO/IEC/IEEE 29148:2011 Systems and software
engineering - Life cycle processes - Requirements engineering, 4.1.14]
cf. concept of operations
Note 1 to entry: The operational concept is designed to give an overall picture of the operations using one or more specific
systems, or set of related systems, in the organization's operational environment from the users' and operators' perspective.

### 3.2721
OpsCon
1. operational concept [ISO/IEC/IEEE 29148:2011 Systems and software engineering - Life cycle processes ?
Requirements engineering, 4.2]
### 3.2722
optical disc (OD)
1. disk which stores binary data in the form of pits which interrupt the reflection of light from a laser

### 3.2732
ORB
1. Object Request Broker [ISO/IEC 19500-2:2012 Information technology - Object Management Group - Common
Object Request Broker Architecture (CORBA) - Part 2: Interoperability, ### 3.3]

### 3.2740
organizational breakdown structure (OBS)
1. A hierarchical representation of the project organization that illustrates the relationship between project
activities and the organizational units that will perform those activities [A Guide to the Project Management Body of
Knowledge (PMBOK? Guide) - Fifth Edition]

### 3.2757
OSE
1. Open System Environment [ISO/IEC 10746-1:1998 Information technology - Open Distributed Processing ?
Reference model: Overview]
### 3.2758
OSF
1. Open Software Foundation [ISO/IEC 10746-1:1998 Information technology - Open Distributed Processing ?
Reference model: Overview]
### 3.2759
OSI
1. Open Systems Interconnection [ISO/IEC 10746-1:1998 Information technology - Open Distributed Processing ?
Reference model: Overview]
### 3.2760
OT
1. operational test [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense Programs, ### 3.2]

### 3.2761
OTE
1. operational test and evaluation [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense
Programs, ### 3.2]
### 3.2762
OTP
1. one-time programming 2. one-time password [ISO/IEC/IEEE 23026:2015 Systems and software engineering ?
Engineering and management of websites for systems, software, and services information, 5]
### 3.2763
OTRR
1. operational test readiness review [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense
Programs, ### 3.2]

### 3.2785
P&D
1. production and deployment [IEEE 15288.1:2014 IEEE Standard for Application of Systems Engineering on Defense
Programs, ### 3.2]
### 3.2786
P-V pair
1. combination of a test item parameter with a value assigned to that parameter, used as a test condition and
coverage item in combinatorial test design techniques [ISO/IEC/IEEE 29119-4:2015 Software and systems
engineering - Software testing - Part 4: Test techniques, 4.22]
### 3.2787
P/T net
1. Place/Transition net [ISO/IEC 15909-2:2011 Software and system engineering - High-level Petri nets - Part 2:
Transfer format, 4.2.4]
### 3.2788
PA
1. process attribute [ISO/IEC TR 29110-3-1:2015 Systems and software engineering - Lifecycle profiles for Very Small
Entities (VSEs) - Part 3-1: Assessment Guide, 4.2]

### 3.2803
PAM
1. process assessment model [ISO/IEC TR 29110-3-1:2015 Systems and software engineering - Lifecycle profiles for
Very Small Entities (VSEs) - Part 3-1: Assessment Guide, 4.2]

### 3.2844
PBO
1. project-based organization [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth
Edition]
### 3.2845
PCA
1. physical configuration audit 2. programmable counter array
### 3.2846
PCB
1. printed circuit board
### 3.2847
PCBA
1. printed circuit board assembly
### 3.2848
PCO
1. Point of Control and Observation [ISO/IEC 10746-1:1998 Information technology - Open Distributed Processing
? Reference model: Overview]
### 3.2849
PDCA
1. Plan-Do-Check-Act

### 3.2850
PDL
1. program design language
### 3.2851
PDM
1. precedence diagramming method [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) ?
Fifth Edition]
### 3.2852
PDPC
1. process decision program chart [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth
Edition]
### 3.2853
PDR
1. preliminary design review [IEEE 15288.1:2014 IEEE Standard for Application of Systems Engineering on Defense
Programs, ### 3.2]

### 3.2856
PEO
1. program executive office [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense
Programs, ### 3.2]

### 3.2869
performance measurement baseline
PMB
1. an approved integrated scope-schedule-cost plan for the project work against which project execution is
compared to measure and manage performance. The PMB includes contingency reserve, but excludes management
reserve [A Guide to the Project Management Body of Knowledge (PMBOK? Guide) - Fifth Edition]

### 3.2888
personal computer (PC)
1. microcomputer primarily intended for stand-alone use by an individual [ISO/IEC 2382:2015, Information
technology - Vocabulary]

### 3.2891
PERT
1. program evaluation review technique [ISO/IEC/IEEE 16326:2009 Systems and software engineering - Life cycle
processes - Project management, 3]

### 3.2893
PESTEL
1. political, economic, social, technological, environmental, and legal

### 3.2895
PG
1. profile group [ISO/IEC TR 29110-1:2016 Software engineering - Lifecycle profiles for Very Small Entities (VSEs) ?
Part 1: Overview, 4.2]

### 3.2897
physical configuration audit (PCA)
1. audit conducted to verify that a configuration item, as built, conforms to the technical documentation that defines
it [IEEE 828-2012 IEEE Standard for Configuration Management in Systems and Software Engineering, 2.1]
cf. functional configuration audit
Note 1 to entry: For software, the purpose of the software physical configuration audit (PCA) is to ensure that the design and
reference documentation is consistent with the as-built software product.
### 3.2898
physical requirement
1. requirement that specifies a physical characteristic that a system or system component must possess
cf. design requirement, functional requirement, implementation requirement, interface requirement, performance
requirement
EXAMPLE: material, shape, size, weight
### 3.2899
physical source statement (PSS)
1. source statement considered as a line of code
cf. logical source statement
### 3.2900
PIa
1. provide instruments activity [ISO/IEC 29155-2:2013: Systems and software engineering - Information technology
project performance benchmarking framework - Part 2: Requirements for benchmarking, 4]
### 3.2901
PICS
1. Protocol Implementation Conformance Statement [ISO/IEC 10746-2:2009 Information technology - Open
Distributed Processing - Reference Model: Foundations, 4]

### 3.2903
PII
1. personally identifiable information [ISO/IEC/IEEE 23026:2015 Systems and software engineering - Engineering
and management of websites for systems, software, and services information, 5]

### 3.2905
PIM
1. platform independent model [ISO/IEC 19500-3:2012 Information technology - Object Management Group ?
Common Architecture Request Broker Architecture (CORBA) - Part 3: Components, 4.3]
### 3.2906
PIN
1. personal identification number [ISO/IEC/IEEE 23026:2015 Systems and software engineering - Engineering and
management of websites for systems, software, and services information, 5]

### 3.2909
PIXIT
1. Protocol Implementation Extra Information for Testing [ISO/IEC 10746-2:2009 Information technology - Open
Distributed Processing - Reference Model: Foundations, 4]

### 3.2926
planned value (PV)
budgeted cost of work scheduled (BCWS)
1. the authorized budget assigned to scheduled work [A Guide to the Project Management Body of Knowledge
(PMBOK® Guide) — Fifth Edition]

### 3.2930
plastic leaded chip carrier (PLCC)
1. rectangular chip unit, made of plastic for use in low-heat devices, usually with surface-mount or J-shaped (J-lead)
connectors

### 3.2933
PLCC
1. plastic leaded chip carrier

### 3.2936
PM
1. Project Manager [ISO/IEC/IEEE 16326:2009 Systems and software engineering — Life cycle processes — Project
management, 5] 2. program manager

### 3.2937
PM&P
1. parts, materials, and processes [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense
Programs, ### 3.2]
### 3.2938
PMB
1. performance measurement baseline [A Guide to the Project Management Body of Knowledge (PMBOK® Guide) —
Fifth Edition]
### 3.2939
PMBOK®
1. Project Management Body of Knowledge [A Guide to the Project Management Body of Knowledge (PMBOK® Guide)
— Fifth Edition]
### 3.2940
PMI
1. Project Management Institute [ISO/IEC/IEEE 16326:2009 Systems and software engineering — Life cycle processes
— Project management]
### 3.2941
PMIS
1. project management information system [A Guide to the Project Management Body of Knowledge (PMBOK® Guide)
— Fifth Edition]
### 3.2942
PMO
1. project management office2. program management office [IEEE 15288.2:2014 IEEE Standard for Technical
Reviews and Audits on Defense Programs, ### 3.2] 

### 3.2943
PMP
1. Project Management Plan [ISO/IEC/IEEE 16326:2009 Systems and software engineering — Life cycle processes —
Project management, 3] 2. Program Management Plan
### 3.2944
PMP®
1. Project Management Professional [A Guide to the Project Management Body of Knowledge (PMBOK® Guide) —
Fifth Edition]
### 3.2945
PN
1. Petri Net [ISO/IEC 15909-1:2004 Software and system engineering — High-level Petri nets — Part 1: Concepts,
definitions and graphical notation, 2.2.5]
### 3.2946
PNG
1. Portable Network Graphics [ISO/IEC/IEEE 23026:2015 Systems and software engineering — Engineering and
management of websites for systems, software, and services information, 5]
### 3.2947
PNML
1. Petri Net Markup Language [ISO/IEC 15909-2:2011 Software and system engineering — High-level Petri nets —
Part 2: Transfer format, 4.2.5]

### 3.2953
PO
1. purchase order [ISO/IEC TR 29110-5-6-2:2014 Systems and software engineering — Lifecycle profiles for Very Small
Entities (VSEs) — Part 5-6-2: Systems engineering — Management and engineering guide: Generic profile group: Basic
profile, 4.2]
### 3.2954
POA
1. portable object adapter [ISO/IEC 19500-3:2012 Information technology — Object Management Group — Common
Architecture Request Broker Architecture (CORBA) — Part 3: Components, 4.3]

### 3.2979
PPL
1. Product Parts List [ISO/IEC/IEEE 16326:2009 Systems and software engineering — Life cycle processes — Project
management, 3]
### 3.2980
PPP
1. program protection plan [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense Programs,
### 3.2]
### 3.2981
PPSL
1. program parts selection list [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense
Programs, ### 3.2]
### 3.2982
PR&RPI
1. Problem Reporting and Resolution Planned Information. 

### 3.2984
precedence diagramming method (PDM)
activity-on-node (AON)
1. a technique used for constructing a schedule model in which activities are represented by nodes and are
graphically linked by one or more logical relationships to show the sequence in which the activities are to be
performed [A Guide to the Project Management Body of Knowledge (PMBOK® Guide) — Fifth Edition]

### 3.2996
preliminary design review (PDR)
1. review conducted to evaluate the progress, technical adequacy, and risk resolution of the selected design
approach for one or more configuration items; to determine each design's compatibility with the requirements for
the configuration item; to evaluate the degree of definition and assess the technical risk associated with the selected
manufacturing methods and processes; to establish the existence and compatibility of the physical and functional
interfaces among the configuration items and other items of equipment, facilities, software and personnel; and, as
applicable, to evaluate the preliminary operational and support documents 2. review as in (1) of any hardware or
software component
cf. critical design review, system design review

### 3.3014
printed circuit board (PCB)
1. configuration of connections between electronic components, typically using metallic paths etched on a nonconducting substrate (board)
### 3.3015
printed circuit board assembly (PCBA)
1. printed circuit board with embedded components and devices

### 3.3024
PRM
1. process reference model [ISO/IEC TR 29110-3-1:2015 Systems and software engineering — Lifecycle profiles for
Very Small Entities (VSEs) — Part 3-1: Assessment Guide, 4.2] 

### 3.3029
problem report (PR)
1. document used to identify and describe problems detected in a product [IEEE 14764-2006 Software Engineering
- Software Life Cycle Processes - Maintenance, ### 3.9]
Note 1 to entry: PRs are either submitted directly to denote faults or established after impact analysis is performed on
Modification Requests and faults are found.

### 3.3045
process assessment model (PAM)
1. model suitable for the purpose of assessing a specified process quality characteristic, based on one or more
process reference models [ISO/IEC 33001:2015 Information technology — Process assessment — Concepts and terminology, ### 3.### 3.9; ISO/IEC TR 29110-1:2016 Software engineering — Lifecycle profiles for Very Small Entities (VSEs)
— Part 1: Overview, ### 3.38]
cf. process reference model (PRM)
Note 1 to entry: Process assessment models addressing a specific process quality characteristic can include the identification of
the characteristic in the title; for example, a process assessment model addressing process capability can be termed a "process
capability assessment model."

### 3.3047
process attribute (PA)
process quality attribute
1. measurable property of a process quality characteristic [ISO/IEC 33001:2015 Information technology — Process
assessment — Concepts and terminology, ### 3.4.3]

### 3.3079
process reference model (PRM)
1. model comprising definitions of processes in a domain of application described in terms of process purpose and
outcomes, together with an architecture describing the relationships between the processes [ISO/IEC 33001:2015
Information technology — Process assessment — Concepts and terminology, ### 3.### 3.16] 2. model comprising definitions
of processes in a lifecycle described in terms of process purpose and outcomes, together with an architecture
describing the relationships between the processes [ISO/IEC TR 29110-1:2016 Software engineering — Lifecycle
profiles for Very Small Entities (VSEs) — Part 1: Overview, ### 3.44]
cf. process assessment model (PAM)

### 3.3122
profile group
PG
1. collection of profiles which are related by composition of processes (i.e., activities, tasks) or by capability level,
or both [ISO/IEC TR 29110-1:2016 Software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 1:
Overview, 2.24] 2. collection of profiles which are related by composition of processes (i.e., activities, tasks), or by
requirements sharing or composition [ISO/IEC 29110-2-1:2015 — Software engineering — Lifecycle profiles for Very
Small Entities (VSEs) — Part 2-1: Framework and taxonomy, 4.45] 

### 3.3125
program design language (PDL)
1. specification language with special constructs and, sometimes, verification protocols, used to develop, analyze,
and document a program design
cf. hardware design language, pseudo code
### 3.3126
Program Evaluation and Review Technique (PERT)
1. a technique for estimating that applies a weighted average of optimistic, pessimistic, and most likely estimates
when there is uncertainty with the individual activity estimates [A Guide to the Project Management Body of
Knowledge (PMBOK® Guide) — Fifth Edition]

### 3.3135
program status word (PSW)
1. computer word that contains information specifying the current status of a computer program 2. special-purpose
register that contains a program status word as in (1)
Note 1 to entry: The information can include error indicators, the address of the next instruction to be executed, or currently
enabled interrupts.

### 3.3141
programmable read-only memory (PROM)
1. read-only memory unit without a rewrite or an erase data function, which the user can program only once
### 3.3142
programmable reload timer (PRT)
1. reconfigurable device to restart a function, using decrementing, status control, and reload registers

### 3.3167
project management (PM)
1. the application of knowledge, skills, tools, and techniques to project activities to meet the project requirements
[A Guide to the Project Management Body of Knowledge (PMBOK® Guide) — Fifth Edition] 2. activities concerned
with project planning and project control [ISO/IEC 2382:2015, Information technology — Vocabulary]
### 3.3168
Project Management Body of Knowledge (PMBOK®)
1. An inclusive term that describes the sum of knowledge within the profession of project management. As with
other professions, such as law, medicine, and accounting, the body of knowledge rests with the practitioners and
academics that apply and advance it. The complete project management body of knowledge includes proven
traditional practices that are widely applied and innovative practices that are emerging in the profession. The body
of knowledge includes both published and unpublished materials. This body of knowledge is constantly evolving [A
Guide to the Project Management Body of Knowledge (PMBOK® Guide) — Fifth Edition]
### 3.3169
project management information system (PMIS)
1. an information system consisting of the tools and techniques used to gather, integrate, and disseminate the
outputs of project management processes. It is used to support all aspects of the project from initiating through
closing, and can include both manual and automated systems [A Guide to the Project Management Body of Knowledge
(PMBOK® Guide) — Fifth Edition]

### 3.3171
project management office (PMO)
1. an organizational structure that standardizes the project-related governance processes and facilitates the sharing
of resources, methodologies, tools and techniques [A Guide to the Project Management Body of Knowledge (PMBOK®
Guide) — Fifth Edition] 

### 3.3178
project manager (PM)
PJM
1. the person assigned by the performing organization to lead the team that is responsible for achieving the project
objectives [A Guide to the Project Management Body of Knowledge (PMBOK® Guide) — Fifth Edition] 2. person with
overall responsibility for the management and running of a project [ISO/IEC 26514:2008 Systems and software
engineering — requirements for designers and developers of user documentation, 4.39] 

### 3.3204
PROM
1. programmable read-only memory

### 3.3223
PRR
1. production readiness review [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense
Programs, ### 3.2]
### 3.3224
PRT
1. programmable reload timer
### 3.3225
PSCI
1. Protocol Support for Computational Interactions [ISO/IEC 14752:2000 Information technology — Open Distributed
Processing — Protocol support for computational interactions, 4]
### 3.3226
PSDL
1. persistent state definition language [ISO/IEC 19500-3:2012 Information technology — Object Management Group
— Common Architecture Request Broker Architecture (CORBA) — Part 3: Components, 4.3]

### 3.3229
pseudostatic random access memory (PSRAM)
1. dynamic random access memory unit with an automatic refresh circuit on the unit
### 3.3230
PSM
1. platform-specific model [ISO/IEC 19500-3:2012 Information technology — Object Management Group — Common
Architecture Request Broker Architecture (CORBA) — Part 3: Components, 4.3]
### 3.3231
PSP
1. product support plan [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense Programs,
### 3.2]
### 3.3232
PSRAM
1. pseudostatic random access memory
### 3.3233
PSW
1. program status word

### 3.3234
PTNG
1. Place/Transition Net Graph [ISO/IEC 15909-1:2004 Software and system engineering — High-level Petri nets —
Part 1: Concepts, definitions and graphical notation, 2.2.6] 

### 3.3237
pulse width modulation (PWM)
1. control of electrical signals with various cycle and duty ratios

### 3.3240
PV
1. planned value [A Guide to the Project Management Body of Knowledge (PMBOK® Guide) — Fifth Edition]
### 3.3241
PWM
1. pulse width modulation
### 3.3242
QA
1. quality assurance
### 3.3243
QC
1. quality control
### 3.3244
QCD
1. quality, cost, delivery [ISO/IEC TR 29110-2-2:2011 Systems and software engineering — Lifecycle profiles for Very
Small Entities (VSEs) — Part 2-2: Guide for the development of domain-specific profiles, 4]
### 3.3245
QE
1. quality engineering [IEEE 730-2014 IEEE Standard for Software Quality Assurance Processes, ### 3.3]

### 3.3246
QFD
1. quality function deployment [A Guide to the Project Management Body of Knowledge (PMBOK® Guide) — Fifth
Edition]
### 3.3247
QFP
1. quad flat pack
### 3.3248
QM
1. quality management 2. quality measure [ISO/IEC 25021:2012 Software engineering — Software product Quality
Requirements and Evaluation (SQuaRE) — Quality measure elements, 5 b)]
### 3.3249
QME
1. quality measure element [ISO/IEC 25021:2012 Software engineering — Software product Quality Requirements
and Evaluation (SQuaRE) — Quality measure elements, 5]
### 3.3250
QMS
1. quality management system
Note 1 to entry: [ISO 9000:2005]
### 3.3251
QOS
1. Quality of Service [ISO/IEC 19793:2015 Information technology — Open Distributed Processing — Use of UML for
ODP system specifications, 4]
### 3.3252
QR
1. quality requirements [ISO/IEC TR 14143-4:2002 Information technology — Software measurement — Functional
size measurement — Part 4: Reference model, 4]

### 3.3253
quad flat pack (QFP)
1. surface mount rectangular circuit package with gull-wing shaped leads extending from each of the four sides
Note 1 to entry: A low profile QFP (LQFP) is thinner than a QFP

### 3.3260
quality assurance (QA)
1. part of quality management focused on providing confidence that quality requirements will be fulfilled [ISO/IEC
TS 24748-1:2016 Systems and software engineering — Life cycle management — Part 1: Guide for life cycle
management, 2.37; ISO/IEC/IEEE 15288:2015 Systems and software engineering — System life cycle processes, 4.1.34]
2. all the planned and systematic activities implemented within the quality system, and demonstrated as needed, to
provide adequate confidence that an entity will fulfill requirements for quality [ISO/IEC 12207:2008 Systems and
software engineering — Software life cycle processes, 4.34]
Note 1 to entry: [ISO 9000:2005] There are both internal and external purposes for quality assurance: within an organization,
quality assurance provides confidence to management; in contractual situations, quality assurance provides confidence to the
customer or others. Some quality control and quality assurance actions are interrelated. Unless requirements for quality fully
reflect the needs of the user, quality assurance does not necessarily provide adequate confidence.

### 3.3265
quality control (QC)
1. set of activities designed to evaluate the quality of developed or manufactured products2. monitoring service
performance or product quality, recording results, and recommending necessary changes
cf. quality assurance
Note 1 to entry: This term has no standardized meaning in software engineering at this time.

### 3.3271
quality function deployment (QFD)
1. a facilitated workshop technique that helps determine critical characteristics for new product development [A
Guide to the Project Management Body of Knowledge (PMBOK® Guide) — Fifth Edition]

### 3.3278
quality measure
QM
1. measure that is defined as a measurement function of two or more values of quality measure elements [ISO/IEC
25010:2011 Systems and software engineering — Systems and software Quality Requirements and Evaluation
(SQuaRE) — System and software quality models, 4.### 3.10] 2. derived measure that is defined as a measurement
function of two or more values of quality measure elements [ISO/IEC 25021:2012 Software engineering — Software
product Quality Requirements and Evaluation (SQuaRE) — Quality measure elements, 4.13]
cf. software quality measure
### 3.3279
quality measure element (QME)
1. measure defined in terms of a property and the measurement method for quantifying it, including optionally the
transformation by a mathematical function [ISO/IEC 25000:2014 Systems and software Engineering — Systems and
software product Quality Requirements and Evaluation (SQuaRE) — Guide to SQuaRE, 4.26; ISO/IEC 25021:2012
Software engineering — Software product Quality Requirements and Evaluation (SQuaRE) — Quality measure
elements, 4.14] 2. measure defined in terms of an attribute and the measurement method for quantifying it, including
optionally the transformation by a mathematical function [ISO/IEC 25010:2011 Systems and software engineering —
Systems and software Quality Requirements and Evaluation (SQuaRE) — System and software quality models, 4.### 3.11]
Note 1 to entry: The software quality characteristics or subcharacteristics of the entity are derived afterwards by calculating a
software quality measure.

### 3.3295
R&D
1. research and development [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense
Programs, ### 3.2]
### 3.3296
R&M
1. reliability and maintainability [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense
Programs, ### 3.2]
### 3.3297
RACI
1. responsible, accountable, consult, and inform 2. a common type of responsibility assignment matrix that uses
responsible, accountable, consult, and inform statuses to define the involvement of stakeholders in project activities
[A Guide to the Project Management Body of Knowledge (PMBOK® Guide) — Fifth Edition]
### 3.3298
RAM
1. responsibility assignment matrix [A Guide to the Project Management Body of Knowledge (PMBOK® Guide) — Fifth
Edition] 2. random-access memory
### 3.3299
RAM-C
1. reliability, availability, maintainability, and cost [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and
Audits on Defense Programs, ### 3.2]

### 3.3301
random-access memory (RAM)
1. volatile semiconductor storage device which allows data to be written or accessed in approximately the same
amount of time, regardless of the data's physical location
Note 1 to entry: often used for caches or main memory in a computer and embedded in an MCU chip. Compare to a CD where
data is stored and accessed sequentially.

### 3.3308
RBS
1. risk breakdown structure [A Guide to the Project Management Body of Knowledge (PMBOK® Guide) — Fifth
Edition] 2. resource breakdown structure
### 3.3309
RDA
1. Remote Database Access [ISO/IEC 10746-1:1998 Information technology — Open Distributed Processing —
Reference model: Overview]
### 3.3310
RDBMS
1. Relational Database Management System [ISO/IEC 25024:2015 Systems and software engineering - Systems and
software Quality Requirements and Evaluation (SQuaRE) - Measurement of data, 5]
### 3.3311
RDF
1. Resource Description Framework [ISO/IEC/IEEE 23026:2015 Systems and software engineering — Engineering
and management of websites for systems, software, and services information, 5] 

### 3.3312
RDN
1. Relative Distinguished Name [ISO/IEC 13235-3:1998 Information technology — Open Distributed Processing —
Trading Function — Part 3: Provision of Trading Function using OSI Directory service, 4] 

### 3.3319
read-only memory (ROM)
1. non-volatile semiconductor storage device, from which data cannot be removed once it is written

### 3.3323
ready to use software product (RUSP)
1. software product available to any user, at cost or not, to use without the need to conduct development activities
[ISO/IEC 25051:2014 Software engineering — Software product Quality Requirements and Evaluation (SQuaRE) —
Requirements for quality of Ready to Use Software Product (RUSP) and instructions for testing, 4.1.6]
cf. commercial off the shelf (COTS)
Note 1 to entry: includes the product description (including cover information, data sheet, and website information; the user
documentation necessary to install and use the software, including any configuration of the operating system or target computer
required to operate the product; the software contained on a computer sensible media (e.g., disk or CD-ROM) or internet
downloadable. Includes software produced and supported without typical commercial fees and licensing considerations.

### 3.3329
real-time clock (RTC)
1. integrated circuit that tracks the current time in human units
### 3.3330
real-time operating system (RTOS)
1. operating system intended to handle transaction requests immediately upon receipt

### 3.3338
record element type (RET)
1. user-recognizable sub-group of data element types within a data function [ISO/IEC 20926:2009 Software and
systems engineering — Software measurement — IFPUG functional size measurement method 2009, ### 3.46]

### 3.3358
reference user requirements (RUR)
1. a standard set of user requirements which conforms to the requirements [ISO/IEC TR 14143-4:2002 Information
technology — Software measurement — Functional size measurement — Part 4: Reference model, ### 3.4]

### 3.3365
regid
1. registration identifier [ISO/IEC 19770-5:2015 Information technology — IT asset management — Part 5: Overview
and vocabulary, ### 3.27]

### 3.3368
registration identifier
regid
1. unique identifier for an entity [ISO/IEC 19770-5:2015 Information technology — IT asset management — Part 5:
Overview and vocabulary, ### 3.27] 

### 3.3381
RELAX NG
1. regular language description for XML/New Generation [ISO/IEC 15909-2:2011 Software and system engineering
— High-level Petri nets — Part 2: Transfer format, 4.2.6]

### 3.3399
remote job entry (RJE)
remote batch entry
1. submission of jobs through a remote input device connected to a computer through a data link
### 3.3400
remote terminal emulator (RTE)
1. data processing system realizing a set of emulated users [ISO/IEC 14756:1999 Information technology —
Measurement and rating of performance of computer-based software systems, 4.15]

### 3.3424
request for information (RFI)
1. a type of procurement document whereby the buyer requests a potential seller to provide various pieces of
information related to a product or service or seller capability [A Guide to the Project Management Body of
Knowledge (PMBOK® Guide) — Fifth Edition]
### 3.3425
request for proposal (RFP)
request for tender
solicitation package
1. collection of formal documents that includes a description of the desired form of response from a potential
supplier, the relevant statement of work for the supplier, and required provisions in the supplier agreement 2. a
type of procurement document used to request proposals from prospective sellers of products or services. In some
application areas, it may have a narrower or more specific meaning. [A Guide to the Project Management Body of
Knowledge (PMBOK® Guide) — Fifth Edition]
### 3.3426
request for quotation (RFQ)
1. a type of procurement document used to request price quotations from prospective sellers of common or
standard products or services. Sometimes used in place of request for proposal and in some application areas, it
may have a narrower or more specific meaning. [A Guide to the Project Management Body of Knowledge (PMBOK®
Guide) — Fifth Edition] 

### 3.3450
requirements traceability matrix (RTM)
1. table that links requirements to their origin and traces them throughout the project life cycle2. a grid that links
product requirements from their origin to the deliverables that satisfy them [A Guide to the Project Management
Body of Knowledge (PMBOK® Guide) — Fifth Edition]

### 3.3463
resource breakdown structure (RBS)
1. a hierarchical representation of resources by category and type [A Guide to the Project Management Body of
Knowledge (PMBOK® Guide) — Fifth Edition]

### 3.3478
responsibility assignment matrix (RAM)
1. a grid that shows the project resources assigned to each work package [A Guide to the Project Management Body
of Knowledge (PMBOK® Guide) — Fifth Edition]
### 3.3479
responsive web design (RWD)
1. method for web page construction to detect the user's screen size and orientation and dynamically change the
layout accordingly [ISO/IEC/IEEE 23026:2015 Systems and software engineering — Engineering and management of
websites for systems, software, and services information, 4.22] 

### 3.3483
RET
1. record element type [ISO/IEC 20926:2009 Software and systems engineering — Software measurement — IFPUG
functional size measurement method 2009, 4; ISO/IEC 20968:2002 Software engineering — Mk II Function Point
Analysis — Counting Practices Manual, 4]

### 3.3492
return on investment (ROI)
1. ratio of revenue from output (product or service) to development and production costs, which determines
whether an organization benefits from performing an action to produce something

### 3.3507
RFC
1. request for change [IEEE 828-2012 IEEE Standard for Configuration Management in Systems and Software
Engineering, 2.2]
### 3.3508
RFI
1. request for information [A Guide to the Project Management Body of Knowledge (PMBOK® Guide) — Fifth Edition]
### 3.3509
RFP
1. request for proposal [A Guide to the Project Management Body of Knowledge (PMBOK® Guide) — Fifth Edition]
### 3.3510
RFQ
1. request for quotation [A Guide to the Project Management Body of Knowledge (PMBOK® Guide) — Fifth Edition]

### 3.3518
risk breakdown structure (RBS)
1. a hierarchical representation of risks according to their risk categories [A Guide to the Project Management Body
of Knowledge (PMBOK® Guide) — Fifth Edition] 

### 3.3527
risk leverage factor (rlf)
1. rlf _ (reb _ rea)/rmc, where reb is risk exposure before risk mitigation, rea is risk exposure after risk mitigation,
and rmc is the risk mitigation activity's cost
Note 1 to entry: Larger rlfs indicate better mitigation strategies.

### 3.3551
RJE
1. remote job entry
### 3.3552
RM-ODP
1. Reference Model of Open Distributed Processing [ISO/IEC 10746-1:1998 Information technology — Open
Distributed Processing — Reference model: Overview; ISO/IEC 19793:2015 Information technology — Open
Distributed Processing — Use of UML for ODP system specifications, 4] 2. Open Distributed Processing: Reference
Model [ISO/IEC 14752:2000 Information technology — Open Distributed Processing — Protocol support for
computational interactions, 4]
### 3.3553
RMI
1. remote method invocation [ISO/IEC 19500-3:2012 Information technology — Object Management Group —
Common Architecture Request Broker Architecture (CORBA) — Part 3: Components, 4.3]

### 3.3556
ROI
1. return on investment

### 3.3562
ROM
1. read-only memory

### 3.3569
RPC
1. Remote Procedure Call [ISO/IEC 10746-1:1998 Information technology — Open Distributed Processing —
Reference model: Overview]
### 3.3570
RTC
1. real-time clock
### 3.3571
RTM
1. requirements traceability matrix
### 3.3572
RTOS
1. real-time operating system

### 3.3574
Rule and Constraint Language (RCL)
1. declarative specification language that is used to express the realization of responsibilities and to state queries
[IEEE 1320.2-1998 (R2004) IEEE Standard for Conceptual Modeling Language Syntax and Semantics for IDEF1X97
(IDEFobject), ### 3.1.168]
cf. specification language

### 3.3574
Rule and Constraint Language (RCL)
1. declarative specification language that is used to express the realization of responsibilities and to state queries
[IEEE 1320.2-1998 (R2004) IEEE Standard for Conceptual Modeling Language Syntax and Semantics for IDEF1X97
(IDEFobject), ### 3.1.168]
cf. specification language

### 3.3590
SAIV
1. schedule as independent variable [Software Extension to the PMBOK® Guide Fifth Edition]
### 3.3591
SAM
1. software asset management [ISO/IEC 19770-3:2016, Information technology — IT asset management — Part 3:
Entitlement schema, ### 3.2]

### 3.3598
SAR
1. software requirements and architecture review [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and
Audits on Defense Programs, ### 3.2]
cf. SRR
### 3.3599
SAS
1. security attribute service [ISO/IEC 19500-2:2012 Information technology — Object Management Group — Common
Object Request Broker Architecture (CORBA) — Part 2: Interoperability, 5]

### 3.3602
SBI
1. serial bus interface
### 3.3603
SBS
1. system breakdown structure [ISO/IEC TR 29110-5-6-2:2014 Systems and software engineering — Lifecycle profiles
for Very Small Entities (VSEs) — Part 5-6-2: Systems engineering — Management and engineering guide: Generic
profile group: Basic profile, 4.2]

### 3.3610
SCCS
1. Server Conversion Code Sets [ISO/IEC 19500-2:2012 Information technology — Object Management Group —
Common Object Request Broker Architecture (CORBA) — Part 2: Interoperability, ### 3.3] 

### 3.3613
schedule as independent variable (SAIV)
1. a date-certain scheduling method for a project with a specific end date, after which the value of the project
declines precipitously or a penalty for non-completion is applied [Software Extension to the PMBOK® Guide Fifth
Edition] 

### 3.3623
schedule performance index (SPI)
1. a measure of schedule efficiency expressed as the ratio of earned value to planned value [A Guide to the Project
Management Body of Knowledge (PMBOK® Guide) — Fifth Edition]
### 3.3624
schedule variance (SV)
1. a measure of schedule performance expressed as the difference between the earned value and the planned value
[A Guide to the Project Management Body of Knowledge (PMBOK® Guide) — Fifth Edition] 

### 3.3626
SCI
1. Software Configuration Item [ISO/IEC TR 15846:1998 Information technology — Software life cycle processes —
Configuration Management, 5.1] 2. serial communication interface
### 3.3627
SCM
1. Software Configuration Management [ISO/IEC TR 15846:1998 Information technology — Software life cycle
processes — Configuration Management, 5.1]
### 3.3628
SCMP
1. software configuration management plan
### 3.3629
SCMPI
1. Software Configuration Management Planned Information.
### 3.3630
SCN
1. specification change notice

### 3.3636
SCRM
1. supply chain risk management [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense
Programs, ### 3.2] 

### 3.3642
SDa
1. submit data activity [ISO/IEC 29155-2:2013: Systems and software engineering — Information technology project
performance benchmarking framework — Part 2: Requirements for benchmarking, 4]
### 3.3643
SDD
1. software design description [IEEE 1012-2012 IEEE Standard for System and Software Verification and Validation]
2. software design document ### 3. system design document [ISO/IEC TR 29110-5-6-2:2014 Systems and software
engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 5-6-2: Systems engineering — Management and
engineering guide: Generic profile group: Basic profile, 4.2]
### 3.3644
SDP
1. software development plan [ISO/IEC/IEEE 16326:2009 Systems and software engineering — Life cycle processes
— Project management, 3] 

### 3.3645
SDR
1. system design review
### 3.3646
SDRAM
1. synchronous dynamic random access memory
### 3.3647
SE
1. Software Engineering [ISO/IEC/IEEE 16326:2009 Systems and software engineering — Life cycle processes —
Project management, 3]
### 3.3648
SECIOP
1. Secure Inter-ORB Protocol [ISO/IEC 19500-3:2012 Information technology — Object Management Group —
Common Architecture Request Broker Architecture (CORBA) — Part 3: Components, Secure Inter-ORB Protocol] 

### 3.3662
SEE
1. Software Engineering Environment [ISO/IEC/IEEE 16326:2009 Systems and software engineering — Life cycle
processes — Project management, 5]

### 3.3668
SEI
1. serial expansion interface 2. Software Engineering Institute

### 3.3680
Semantic Transfer Language (STL)
1. language for the purpose of representing software application behavior descriptions [IEEE 1175.3-2004 IEEE
Standard for CASE Tool Interconnections - Reference Model for Specifying Software Behavior]
Note 1 to entry: The Semantic Transfer Language has a formal syntax that is computer-parsable, while remaining easy for users
to read and write.

### 3.3686
SEMDM
1. software engineering metamodel for development methodologies [ISO/IEC 24744:2014 Software Engineering —
Metamodel for development methodologies, 4.2]

### 3.3688
SEMP
1. Systems Engineering Management Plan [ISO/IEC/IEEE 16326:2009 Systems and software engineering — Life cycle
processes — Project management, 3] 

### 3.3691
SEP
1. Systems Engineering Plan [ISO/IEC TR 29110-5-6-2:2014 Systems and software engineering — Lifecycle profiles for
Very Small Entities (VSEs) — Part 5-6-2: Systems engineering — Management and engineering guide: Generic profile
group: Basic profile, ### 3.5]

### 3.3700
serial bus interface (SBI)
1. connection for bidirectional serial data communication
EXAMPLE: RS232, RS485
Note 1 to entry: based on the IEEE 1394 standards
### 3.3701
serial communication interface (SCI)
1. unit that enables the serial exchange of data between a microprocessor and peripherals

### 3.3703
serial expansion interface (SEI)
1. connection to serve multiple serial channels

### 3.3704
serial peripheral interface (SPI)
1. synchronous (full duplex) serial communication interface used for two devices in embedded systems

### 3.3716
service level agreement (SLA)
1. documented agreement between the service provider and customer that identifies services and service targets
Note 1 to entry: A service level agreement can also be established between the service provider and a supplier, an internal group,
or a customer acting as a supplier. A service level agreement can be included in a contract or another type of documented
agreement. An Application Management organization can be the service provider, but it can also be a customer itself, of another
supplier.

### 3.3718
service management system (SMS)
1. management system to direct and control the provision of one or more services
Note 1 to entry: The SMS includes all service management policies, objectives, plans, processes, documentation and
resources required for the design, transition, delivery and improvement of services and to fulfill the requirements.

### 3.3726
SETA
1. systems engineering and technical assistance [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits
on Defense Programs, ### 3.2]
### 3.3727
SETR
1. systems engineering technical review [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on
Defense Programs, ### 3.2]

### 3.3729
SF
1. start-to-finish [A Guide to the Project Management Body of Knowledge (PMBOK® Guide) — Fifth Edition]
### 3.3730
SFR
1. system functional review [IEEE 15288.1:2014 IEEE Standard for Application of Systems Engineering on Defense
Programs, ### 3.2] 2. special function register
### 3.3731
SGML
1. Standard Generalized Markup Language [ISO/IEC/IEEE 23026:2015 Systems and software engineering —
Engineering and management of websites for systems, software, and services information, 5]
### 3.3732
SGRAM
1. synchronous graphics random access memory

### 3.3733
SHA
1. secure hash algorithm [ISO/IEC 19770-2:2015 Information technology — Software asset management — Part 2:
Software identification tag, ### 3.2]

### 3.3737
shrink small outline package (SSOP)
1. thinner rectangular surface mount integrated circuit unit with gull-wing leads on the two long sidesv

### 3.3743
SIL
1. system integration laboratory [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense
Programs, ### 3.2]
### 3.3744
SIM
1. [mobile telecommunications] subscriber identity module 2. [embedded software] system integration module

### 3.3758
SIP
1. system integration plan [IEEE 15288.1:2014 IEEE Standard for Application of Systems Engineering on Defense
Programs, ### 3.2]

### 3.3763
SLA
1. service level agreement
### 3.3764
SLC
1. software life cycle [IEEE 730-2014 IEEE Standard for Software Quality Assurance Processes, ### 3.3]
### 3.3765
SLCP
1. Software Life Cycle Processes
### 3.3766
SLOC
1. Source Lines of Code, the number of lines of programming language code in a program before compilation
[ISO/IEC 20968:2002 Software engineering — Mk II Function Point Analysis — Counting Practices Manual, 10] 

### 3.3768
Small and Medium Enterprise (SME)
1. enterprises which employ fewer than 250 persons and which have an annual turnover not exceeding 50 million
euro, and/or an annual balance sheet total not exceeding 43 million euro) [ISO/IEC TR 29110-5-6-2:2014 Systems
and software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 5-6-2: Systems engineering —
Management and engineering guide: Generic profile group: Basic profile, ### 3.6] 2. enterprise which employs fewer than
250 persons [ISO/IEC 29110-2-1:2015 — Software engineering — Lifecycle profiles for Very Small Entities (VSEs) —
Part 2-1: Framework and taxonomy, 4.52]
### 3.3769
small outline integrated circuit (SOIC)
1. surface-mounted integrated circuit (chip) package with gull-wing pins extending outward
### 3.3770
small outline package (SOP)
1. rectangular surface mount integrated circuit unit with gull-wing leads on the two long sides
### 3.3771
SMART
1. specific, measurable, achievable, relevant and traceable [ISO/IEC TR 29110-5-6-2:2014 Systems and software
engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 5-6-2: Systems engineering — Management and
engineering guide: Generic profile group: Basic profile, 4.2]
### 3.3772
SME
1. subject-matter expert [ISO/IEC 26514:2008 Systems and software engineering — requirements for designers and
developers of user documentation] 2. small and medium enterprise [ISO/IEC TR 29110-5-6-2:2014 Systems and
software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 5-6-2: Systems engineering —
Management and engineering guide: Generic profile group: Basic profile, ### 3.6] 

### 3.3773
SMIR
1. Server Makes It Right [ISO/IEC 19500-2:2012 Information technology — Object Management Group — Common
Object Request Broker Architecture (CORBA) — Part 2: Interoperability, ### 3.3]
### 3.3774
SMS
1. service management system
### 3.3775
SMT
1. self-managed transaction [ISO/IEC 19500-3:2012 Information technology — Object Management Group —
Common Architecture Request Broker Architecture (CORBA) — Part 3: Components, Secure Inter-ORB Protocol]
### 3.3776
SN
1. symmetric net [ISO/IEC 15909-2:2011 Software and system engineering — High-level Petri nets — Part 2: Transfer
format, 4.2.7]

### 3.3778
SNCS
1. Server Native Code Set [ISO/IEC 19500-2:2012 Information technology — Object Management Group — Common
Object Request Broker Architecture (CORBA) — Part 2: Interoperability, ### 3.3] 

### 3.3780
SoC
1. system on a chip

### 3.3783
software
SW
1. 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] 2. all or 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-1:2012 Information technology — Software asset management — Part 1: Processes
and tiered assessment of conformance, ### 3.14] ### 3. 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]
cf. application software
EXAMPLE: command files, job control language, both executable and non-executable software, such as fonts,
graphics, audio and video recordings, templates, dictionaries, and documents
Note 1 to entry: include both executable and non-executable software, such as fonts, graphics, audio and video recordings,
templates, dictionaries, documents, and information structures such as database records

### 3.3787
software asset management (SAM)
1. control and protection of software and related assets within an organization, and control and protection of
information about related assets which are needed in order to control and protect software assets. [ISO/IEC 19770-
5:2015 Information technology — IT asset management — Part 5: Overview and vocabulary, ### 3.35]
Note 1 to entry: infrastructure and processes necessary for the effective management, control and protection of the software
assets within an organization, throughout all stages of their lifecycle

### 3.3791
software component (SC)
1. entity with discrete structure, such as an assembly or software module, within a system considered at a particular
level of analysis [ISO/IEC 19770-5:2015 Information technology — IT asset management — Part 5: Overview and
vocabulary, ### 3.36] 2. functionally or logically distinct part of a software configuration item, distinguished for the
purpose of convenience in designing and specifying a complex SCI as an assembly of subordinate elements ### 3. software system or element [ISO/IEC TR 29110-1:2016 Software engineering — Lifecycle profiles for Very Small
Entities (VSEs) — Part 1: Overview, 2.32]
EXAMPLE: data, document, module, unit
Note 1 to entry: Software component refers to a part of a whole, such as a component of a software product or a component of a
software identification tag.
### 3.3792
software configuration item (SCI)
1. software entity that has been established as a configuration item
cf. computer software component, computer software configuration item, hardware configuration item, software
item
Note 1 to entry: The SCI exists where functional allocations have been made that clearly distinguish equipment functions from
software functions and where the software has been established as a configurable item.
### 3.3793
software configuration management (SCM)
1. process of applying configuration management throughout the software life cycle to ensure the completeness and
correctness of SCIs [ISO/IEC TR 15846:1998 Information technology — Software life cycle processes — Configuration
Management, 4.4] 

### 3.3799
software design description (SDD)
1. representation of software created to facilitate analysis, planning, implementation, and decision-making [IEEE
1012-2012 IEEE Standard for System and Software Verification and Validation, ### 3.1.28]
Note 1 to entry: The software design description is used as a medium for communicating software design information and can
be thought of as a blueprint or model of the system.

### 3.3804
software development file (SDF)
software development folder
software development notebook
unit development folder
1. collection of material pertinent to the development of a given software unit or set of related units
Note 1 to entry: Contents typically include the requirements, design, technical reports, code listings, test plans, test results,
problem reports, schedules, and notes for the units.

### 3.3806
software development plan (SDP)
1. project plan for a software development project

### 3.3811
software engineering environment (SEE)
1. environment that provides automated system context services and software-specific services for the engineering
of software systems and related domains, such as project management and process management [ISO/IEC
15940:2013 Systems and software engineering — Software Engineering Environment Services, 2.7] 2. hardware,
software, and firmware used to perform a software engineering effort [IEEE 730-2014 IEEE Standard for Software
Quality Assurance Processes, ### 3.2]
cf. infrastructure
Note 1 to entry: It includes the platform, system software, utilities, and CASE tools installed.

### 3.3817
software identification tag
SWID tag
SWID
1. information structure containing identification information about a software configuration item, which can be
authoritative if provided by a software creator [ISO/IEC 19770-5:2015 Information technology — IT asset
management — Part 5: Overview and vocabulary, ### 3.40] ### 3. set of structured data elements containing authoritative
identification information about a software configuration item [ISO/IEC 19770-3:2016, Information technology — IT
asset management — Part 3: Entitlement schema, ### 3.1.31]

### 3.3823
software life cycle (SLC)
1. project-specific sequence of activities that is created by mapping the activities of a standard onto a selected
software life cycle model (SLCM) [IEEE 730-2014 IEEE Standard for Software Quality Assurance Processes, ### 3.2] 2.
software system or software product cycle initiated by a user need or a perceived customer need and terminated
by discontinued use of the product or when the software is no longer available for use

### 3.3832
software project life cycle (SPLC)
1. portion of the entire software life cycle applicable to a specific project.
Note 1 to entry: It is the sequence of activities created by mapping the activities of IEEE Std 1074 onto a selected software project
life cycle model (SPLCM).
### 3.3833
software project life cycle model (SPLCM)
1. framework selected by each using organization on which to map the activities of IEEE Std 1074 to produce the
software project life cycle (SPLC).
### 3.3834
software project life cycle process (SPLCP)
1. project-specific description of the process developed by adding the organizational process assets (OPAs) to the
software project life cycle (SPLC) and the OPAs.

### 3.3836
software quality assurance (SQA)
1. a set of activities that assess adherence to, and the adequacy of the software processes used to develop and modify
software products. SQA also determines the degree to which the desired results from software quality control are
being obtained [Software Extension to the PMBOK® Guide Fifth Edition] 2. set of activities that define and assess the
adequacy of software processes to provide evidence that establishes confidence that the software processes are
appropriate for and produce software products of suitable quality for their intended purposes [IEEE 730-2014 IEEE
Standard for Software Quality Assurance Processes, ### 3.2]
Note 1 to entry: A key attribute of SQA is the objectivity of the SQA function with respect to the project. The SQA function can
also be organizationally independent of the project; that is, free from technical, managerial, and financial pressures from the
project.

### 3.3838
software quality control (SQC)
1. a set of activities that measure, evaluate and report on the quality of software project artifacts throughout the
project life cycle [Software Extension to the PMBOK® Guide Fifth Edition]

### 3.3852
software requirements review (SRR)
1. review of the requirements specified for one or more software configuration items to evaluate their
responsiveness to and interpretation of the system requirements and to determine whether they form a satisfactory
basis for proceeding into preliminary design of the configuration items 2. review as in (1) for any software
component
cf. system requirements review
Note 1 to entry: This review is called software specification review by the US Department of Defense.
### 3.3853
software requirements specification (SRS)
1. documentation of the essential requirements (functions, performance, design constraints, and attributes) of the
software and its external interfaces [IEEE 1012-2012 IEEE Standard for System and Software Verification and
Validation, ### 3.1.29] 2. structured collection of the requirements (functions, performance, design constraints, and
attributes) of the software and its external interfaces [ISO/IEC/IEEE 29148:2011 Systems and software engineering
— Life cycle processes — Requirements engineering, 4.1.24] 

### 3.3858
software test environment (STE)
1. facilities, hardware, software, firmware, procedures, and documentation needed to perform qualification or other
testing of software [ISO/IEC 25051:2014 Software engineering — Software product Quality Requirements and
Evaluation (SQuaRE) — Requirements for quality of Ready to Use Software Product (RUSP) and instructions for testing,
4.1.15]
Note 1 to entry: Elements include simulators, code analyzers, test case generators, path analyzers, and elements used in the
software engineering environment

### 3.3871
SOI
1. system-of-interest [ISO/IEC/IEEE 15288:2015 Systems and software engineering — System life cycle processes, 4.2]
### 3.3872
SOIC
1. small outline integrated circuit

### 3.3874
SOO
1. statement of objectives [IEEE 15288.1:2014 IEEE Standard for Application of Systems Engineering on Defense
Programs, ### 3.2]
### 3.3875
SOP
1. standard operating procedure 2. small outline package
### 3.3876
SoPC
1. system on a programmable chip

### 3.3879
SoS
1. system of systems [ISO/IEC/IEEE 15288:2015 Systems and software engineering — System life cycle processes, 4.2

### 3.3888
source statements (SS)
1. encoded logic of the software product
Note 1 to entry: Source statements can be classified by function as executable, data declaration, compiler directive, or comment.
They can also be classified as deliverable or nondeliverable.
### 3.3889
SOW
1. statement of work [A Guide to the Project Management Body of Knowledge (PMBOK® Guide) — Fifth Edition;
ISO/IEC TR 29110-5-6-2:2014 Systems and software engineering — Lifecycle profiles for Very Small Entities (VSEs) —
Part 5-6-2: Systems engineering — Management and engineering guide: Generic profile group: Basic profile, 4.2] 

### 3.3892
special function register (SFR)
1. register used to control or monitor functions in a microprocessor

### 3.3896
specification change notice (SCN)
1. a document used in configuration management to propose, transmit, and record changes to a specification
cf. configuration control, engineering change, notice of revision

### 3.3901
SPI
1. schedule performance index [A Guide to the Project Management Body of Knowledge (PMBOK® Guide) — Fifth
Edition] 2. serial peripheral interface ### 3. system/software process improvement [ISO/IEC TR 29110-3-4:2015
Systems and software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 3-4: Autonomy-based
improvement method, 4.2]

### 3.3903
SPLC
1. software project life cycle.
### 3.3904
SPLCM
1. software project life cycle model.
### 3.3905
SPLCP
1. software project life cycle process. 

### 3.3907
SPMPI
1. Software Project Management Planned Information. 

### 3.3912
SPQM-RM
1. software product quality measurement reference model [ISO/IEC 25020:2007 Software engineering — Software
product Quality Requirements and Evaluation (SQuaRE) — Measurement reference model and guide, 5]

### 3.3915
SPS
1. system performance specification [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense
Programs, ### 3.1]
### 3.3916
SQA
1. Software Quality Assurance [IEEE 730-2014 IEEE Standard for Software Quality Assurance Processes, ### 3.3]

### 3.3917
SQAP
1. software quality assurance plan [IEEE 730-2014 IEEE Standard for Software Quality Assurance Processes, ### 3.3]
### 3.3918
SQC
1. software quality control [ISO/IEC 25051:2014 Software engineering — Software product Quality Requirements and
Evaluation (SQuaRE) — Requirements for quality of Ready to Use Software Product (RUSP) and instructions for testing,
4.2]
### 3.3919
SQL
1. Structured Query Language

### 3.3921
sr
1. system definition and realization [ISO/IEC TR 29110-5-6-2:2014 Systems and software engineering — Lifecycle
profiles for Very Small Entities (VSEs) — Part 5-6-2: Systems engineering — Management and engineering guide:
Generic profile group: Basic profile, 4.2]
### 3.3922
SRAM
1. static random access memory
### 3.3923
SRD
1. system requirements document [IEEE 1012-2012 IEEE Standard for System and Software Verification and
Validation, ### 3.2]
### 3.3924
SRMPI
1. Software Release Management Planned Information.
### 3.3925
SRR
1. software requirements review 2. system requirements review [IEEE 15288.2:2014 IEEE Standard for Technical
Reviews and Audits on Defense Programs, ### 3.2]
cf. SAR
### 3.3926
SRS
1. software requirements specification [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on
Defense Programs, ### 3.2] 2. system requirements specification.
cf. SyRS
### 3.3927
SS
1. start-to-start [A Guide to the Project Management Body of Knowledge (PMBOK® Guide) — Fifth Edition]
### 3.3928
SSE
1. system security engineering [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense Programs, ### 3.2]

### 3.3929
SSL
1. secure sockets layer [ISO/IEC 19500-3:2012 Information technology — Object Management Group — Common
Architecture Request Broker Architecture (CORBA) — Part 3: Components, 4.3]
### 3.3930
SSOP
1. shrink small outline package
cf. SOIC
### 3.3931
SSR
1. software specification review [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense
Programs, ### 3.2]
cf. software requirements review
### 3.3932
SSS
1. system/subsystem specification [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense
Programs, ### 3.1] 

### 3.3955
start-to-finish (SF)
1. a logical relationship in which a successor activity cannot finish until a predecessor activity has started [A Guide
to the Project Management Body of Knowledge (PMBOK® Guide) — Fifth Edition]
cf. logical relationship
### 3.3956
start-to-start (SS)
1. a logical relationship in which a successor activity cannot start until a predecessor activity has started [A Guide
to the Project Management Body of Knowledge (PMBOK® Guide) — Fifth Edition]
cf. logical relationship

### 3.3966
statement of work (SOW)
1. document used by the acquirer to describe and specify the tasks to be performed under the contract [ISO/IEC
12207:2008 Systems and software engineering — Software life cycle processes, 4.46] 2. a narrative description of
products, services, or results to be delivered by the project [A Guide to the Project Management Body of Knowledge
(PMBOK® Guide) — Fifth Edition] ### 3. document used by the acquirer that includes the needs and expectations, the
scope, objectives and deliverables [ISO/IEC TR 29110-5-6-2:2014 Systems and software engineering — Lifecycle
profiles for Very Small Entities (VSEs) — Part 5-6-2: Systems engineering — Management and engineering guide:
Generic profile group: Basic profile, ### 3.11] 4. means to describe and specify the tasks to be performed under the
contract [ISO/IEC TR 29110-1:2016 Software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part
1: Overview, ### 3.65] 

### 3.3977
static random access memory (SRAM)
1. random access memory without refresh process, which keeps data as long as it is powered on
Note 1 to entry: based on a circuit architecture with double stable states

### 3.3984
STE
1. software test environment [IEEE 730-2014 IEEE Standard for Software Quality Assurance Processes, ### 3.3] 

### 3.3988
STK
1. stakeholder [ISO/IEC TR 29110-5-6-2:2014 Systems and software engineering — Lifecycle profiles for Very Small
Entities (VSEs) — Part 5-6-2: Systems engineering — Management and engineering guide: Generic profile group: Basic
profile, 4.2]
### 3.3989
STL
1. semantic transfer language [IEEE 1175.3-2004 IEEE Standard for CASE Tool Interconnections - Reference Model for
Specifying Software Behavior]
### 3.3990
stock keeping unit (sku)
1. identification, usually alphanumeric, of a particular product that allows it to be tracked for inventory and software
entitlement purposes [ISO/IEC 19770-5:2015 Information technology — IT asset management — Part 5: Overview
and vocabulary, ### 3.48]
Note 1 to entry: typically associated with unique products for sales purposes, such as software entitlements. It can correspond
uniquely to specific software products, or represent packages of software, with specific terms and conditions, such as whether
it relates to a full product, upgrade product, or maintenance on an existing product.

### 3.3998
STP
1. software test plan [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense Programs, ### 3.2] 

### 3.4008
StRS
1. stakeholder requirements specification [ISO/IEC/IEEE 29148:2011 Systems and software engineering — Life cycle
processes — Requirements engineering, 4.2] 

### 3.4063
SV
1. schedule variance [A Guide to the Project Management Body of Knowledge (PMBOK® Guide) — Fifth Edition]
### 3.4064
SVD
1. software version description [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense
Programs, ### 3.2]
### 3.4065
SVR
1. system verification review [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense
Programs, ### 3.2]
### 3.4066
SW
1. software [IEEE 1012-2012 IEEE Standard for System and Software Verification and Validation, ### 3.2]

### 3.4068
SWEBOK
1. Software Engineering Body of Knowledge [ISO/IEC/IEEE 16326:2009 Systems and software engineering — Life
cycle processes — Project management, 3]
### 3.4069
SWID
1. software identification [ISO/IEC 19770-5:2015 Information technology — IT asset management — Part 5: Overview
and vocabulary, ### 3.40]
### 3.4070
SWOT
1. strengths, weaknesses, opportunities, and threats [A Guide to the Project Management Body of Knowledge
(PMBOK® Guide) — Fifth Edition] 

### 3.4080
synchronous graphics random access memory (SGRAM)
1. SDRAM designed for the graphics card of a computer

### 3.4088
SYNTAX.1
1. primary syntax defined within the CDIF family of standards [ISO/IEC 15474-1:2002 Information technology —
CDIF framework — Part 1: Overview, 4.2]
Note 1 to entry: The CDIF family of standards supports multiple transfer formats, each composed of a syntax and an encoding.
### 3.4089
SyRS
1. System Requirement Specification [ISO/IEC/IEEE 29148:2011 Systems and software engineering — Life cycle
processes — Requirements engineering, 4.2]
cf. SRS

### 3.4092
system breakdown structure (SBS)
1. system hierarchy, with identified enabling systems, and personnel that is typically used to assign development
teams, support technical reviews, and to partition the assigned work and associated resource allocations to each of
the tasks necessary to accomplish the technical objectives of the project [ISO/IEC/IEEE 24748-4:2016, Systems and
software engineering-Life cycle management-Part 4: Systems engineering planning, 4.12]
Note 1 to entry: It also provides the basis for cost tracking and control.

### 3.4095
system design review (SDR)
1. review conducted to evaluate the manner in which the requirements for a system have been allocated to
configuration items, the system engineering process that produced the allocation, the engineering planning for the
next phase of the effort, manufacturing considerations, and the planning for production engineering
cf. critical design review, preliminary design review

### 3.4105
system integration module (SIM)
1. module in a microcontroller unit (MCU) that controls a system functional unit

### 3.4111
system of systems (SoS)
1. system-of-interest (SOI) whose elements are themselves systems [ISO/IEC/IEEE 15288:2015 Systems and
software engineering — System life cycle processes, G.1] 2. large system that delivers unique capabilities, formed by
integrating independently useful systems

### 3.4113
system requirements review (SRR)
1. review conducted to evaluate the completeness and adequacy of the requirements defined for a system; to
evaluate the system engineering process that produced those requirements; to assess the results of system
engineering studies; and to evaluate system engineering plans
cf. software requirements review
### 3.4114
system requirements specification (SyRS)
1. structured collection of information that embodies the requirements of the system 2. structured collection of the
requirements (functions, performance, design constraints, and attributes) of the system and its operational
environments and external interfaces [ISO/IEC/IEEE 29148:2011 Systems and software engineering — Life cycle
processes — Requirements engineering, 4.1.29]
cf. software requirements specification, SRS

### 3.4123
system under test (SUT)
1. parts of the CBSS to be tested [ISO/IEC 14756:1999 Information technology — Measurement and rating of
performance of computer-based software systems, 4.18]
Note 1 to entry: The SUT consists of hardware, system software, data communication features, or application software, or a
combination of them.
### 3.4124
system-of-interest (SOI)
1. system whose life cycle is under consideration [ISO/IEC 15026-3:2015 Systems and software engineering —
Systems and software assurance — Part 3: System integrity levels, ### 3.23; ISO/IEC/IEEE 15288:2015 Systems and
software engineering — System life cycle processes, 4.1.48] 2. system whose life cycle is under consideration in the
application of verification and validation (V&V)[IEEE 1012-2012 IEEE Standard for System and Software Verification
and Validation] 

### 3.4127
systems engineering (SE)
1. interdisciplinary approach governing the total technical and managerial effort required to transform a set of
stakeholder needs, expectations, and constraints into a solution, and to support that solution throughout its life
[ISO/IEC 15940:2013 Systems and software engineering — Software Engineering Environment Services, 2.6; ISO/IEC
TS 24748-1:2016 Systems and software engineering — Life cycle management — Part 1: Guide for life cycle
management, 2.56; ISO/IEC/IEEE 15288:2015 Systems and software engineering — System life cycle processes, 4.1.49]
Note 1 to entry: System engineering is used when there is a single system-of-interest; systems engineering is for the discipline
in general. It includes the definition of technical performance measures; the integration of engineering specialties toward the
establishment of an architecture; and the definition of supporting lifecycle processes that balance cost, performance, and
schedule objectives.
### 3.4128
Systems Engineering Plan (SEP)
Systems Engineering Management Plan (SEMP)
1. top level technical plan for managing the systems engineering effort which defines how the technical aspects of
the project will be organized, structured, and conducted and how the systems engineering processes will be
controlled to provide a product that satisfies stakeholder requirements [ISO/IEC/IEEE 24748-4:2016, Systems and
software engineering-Life cycle management-Part 4: Systems engineering planning, 4,14] 2. top-level plan for
managing the SE effort which, as such, defines how the project will be organized, structured, and conducted and
how the total engineering process will be controlled to provide a product that satisfies stakeholder requirements
[ISO/IEC TR 29110-5-6-2:2014 Systems and software engineering — Lifecycle profiles for Very Small Entities (VSEs)
— Part 5-6-2: Systems engineering — Management and engineering guide: Generic profile group: Basic profile, ### 3.5] ### 3.
top-level technical planning document for a project which addresses technical management processes established
by three principal sources: the project's contract or agreement, applicable organizational processes, and the
systems engineering project team, as necessary to successfully accomplish the systems engineering-related tasks of
the project [ISO/IEC 29110-2-1:2015 — Software engineering — Lifecycle profiles for Very Small Entities (VSEs) —
Part 2-1: Framework and taxonomy, 4.60] 

S_Packet
1. logically coherent grouping of STL sentences that describes a set of software concepts [IEEE 1175.3-2004 IEEE
Standard for CASE Tool Interconnections - Reference Model for Specifying Software Behavior]
### 3.4131
T&E
1. test and evaluation [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense Programs, ### 3.2]
### 3.4132
T&M
1. time and material [A Guide to the Project Management Body of Knowledge (PMBOK® Guide) — Fifth Edition]
### 3.4133
T-DUA
1. Trader Directory User Agent [ISO/IEC 13235-3:1998 Information technology — Open Distributed Processing —
Trading Function — Part 3: Provision of Trading Function using OSI Directory service, 4]
### 3.4134
T-profile
1. Transfer profile [ISO/IEC 10746-1:1998 Information technology — Open Distributed Processing — Reference
model: Overview] 

### 3.4168
TBD
1. to be determined [ISO/IEC/IEEE 29148:2011 Systems and software engineering — Life cycle processes —
Requirements engineering, 4.2]
### 3.4169
TBR
1. to be resolved [ISO/IEC/IEEE 29148:2011 Systems and software engineering — Life cycle processes —
Requirements engineering, 4.2] 2. to be revised [ISO/IEC/IEEE 29148:2011 Systems and software engineering — Life
cycle processes — Requirements engineering, 4.2]
### 3.4170
TBS
1. to be supplied [ISO/IEC/IEEE 29148:2011 Systems and software engineering — Life cycle processes —
Requirements engineering, 4.1] 2. to be specified [ISO/IEC/IEEE 29148:2011 Systems and software engineering —
Life cycle processes — Requirements engineering, 4.2]
### 3.4171
TCP
1. Transmission Control Protocol [ISO/IEC 14752:2000 Information technology — Open Distributed Processing —
Protocol support for computational interactions, 4]
### 3.4172
TCPI
1. to complete performance index

### 3.4173
TCS
1. Transmission Code Set [ISO/IEC 19500-2:2012 Information technology — Object Management Group — Common
Object Request Broker Architecture (CORBA) — Part 2: Interoperability, ### 3.3]
### 3.4174
TCS-C
1. Char Transmission Code Set [ISO/IEC 19500-2:2012 Information technology — Object Management Group —
Common Object Request Broker Architecture (CORBA) — Part 2: Interoperability, ### 3.3]
### 3.4175
TCS-W
1. Wchar Transmission Code Set [ISO/IEC 19500-2:2012 Information technology — Object Management Group —
Common Object Request Broker Architecture (CORBA) — Part 2: Interoperability, ### 3.3]
### 3.4176
TDP
1. technical data package [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense Programs,
### 3.2] 

### 3.4180
technical contact
subject-matter expert
SME
1. person responsible for providing a documentation developer with technical information about a software product
or for checking the technical accuracy of drafts of documentation [ISO/IEC 26514:2008 Systems and software
engineering — requirements for designers and developers of user documentation, 4.49]

### 3.4184
technical performance measure (TPM)
1. measure used to assess design progress, compliance to performance requirements, and technical risks for critical
performance parameters [ISO/IEC/IEEE 29148:2011 Systems and software engineering — Life cycle processes —
Requirements engineering, 6.### 3.### 3.1]

### 3.4186
Technical Report (TR)
1. document published by ISO or IEC containing collected data of a different kind from that normally published as
an International Standard or Technical Specification [ISO/IEC TR 29110-1:2016 Software engineering — Lifecycle
profiles for Very Small Entities (VSEs) — Part 1: Overview, 2.35]
EXAMPLE: data obtained from a survey carried out among the national bodies, data on work in other international
organizations or data on the "state of the art" in relation to standards of national bodies on a particular subject
Note 1 to entry: [ISO/IEC Directives, Part 2]

### 3.4192
TEMP
1. test and evaluation master plan [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense
Programs, ### 3.2]

### 3.4256
test readiness review (TRR)
1. review conducted to evaluate preliminary test results for one or more configuration items; to verify that the test
procedures for each configuration item are complete, comply with test plans and descriptions, and satisfy test
requirements; and to verify that a project is prepared to proceed to formal testing of the configuration items 2.
review as in (1) for any hardware or software component
cf. code review, formal qualification review, design review, requirements review

### 3.4300
TIM
1. technical interchange meeting [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense
Programs, ### 3.2]

### 3.4302
time and material (T&M) contract
1. a type of contract that is a hybrid contractual arrangement containing aspects of both cost-reimbursable and
fixed-price contracts. Time and material contracts resemble cost-reimbursable type arrangements in that they have
no definitive end, because the full value of the arrangement is not defined at the time of the award. Thus, time and
material contracts can grow in contract value as if they were cost-reimbursable-type arrangements. Conversely,
time and material arrangements can also resemble fixed-price arrangements. For example, the unit rates are preset
by the buyer and seller, when both parties agree on the rates for the category of senior engineers [A Guide to the
Project Management Body of Knowledge (PMBOK® Guide) — Fifth Edition]

### 3.4315
timer pulse unit (TPU)
1. microcontroller unit to generate timed pulses

### 3.4321
TINA
1. Telecommunication Information Networking Architecture [ISO/IEC 10746-1:1998 Information technology —
Open Distributed Processing — Reference model: Overview]

### 3.4323
TLS
1. Transport Layer Security [ISO/IEC/IEEE 23026:2015 Systems and software engineering — Engineering and
management of websites for systems, software, and services information, 5]
### 3.4324
TMRR
1. technology maturation and risk reduction [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on
Defense Programs, ### 3.2]
### 3.4325
to-complete performance index (TCPI)
1. a measure of the cost performance that must be achieved with the remaining resources in order to meet a
specified management goal, expressed as the ratio of the cost to finish the outstanding work to the remaining budget
[A Guide to the Project Management Body of Knowledge (PMBOK® Guide) — Fifth Edition]
### 3.4326
TOC
1. total ownership cost [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense Programs,
### 3.2] 

### 3.4341
total float (TF)
1. the amount of time that a schedule activity can be delayed or extended from its early start date without delaying
the project finish date or violating a schedule constraint [A Guide to the Project Management Body of Knowledge
(PMBOK® Guide) — Fifth Edition]
### 3.4342
total quality management (TQM)
1. holistic approach to quality improvement in all life-cycle phases
### 3.4343
TP
1. Transaction Processing [ISO/IEC 10746-2:2009 Information technology — Open Distributed Processing —
Reference Model: Foundations, 4]
### 3.4344
TPM
1. technical performance measure [ISO/IEC/IEEE 29148:2011 Systems and software engineering — Life cycle
processes — Requirements engineering, 4.2] 2. technical performance management [ISO/IEC TR 29110-5-6-2:2014
Systems and software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 5-6-2: Systems
engineering — Management and engineering guide: Generic profile group: Basic profile, 4.2]
### 3.4345
TPU
1. timer pulse unit
### 3.4346
TQM
1. Total Quality Management
### 3.4347
TR
1. technical requirements [ISO/IEC TR 14143-4:2002 Information technology — Software measurement — Functional
size measurement — Part 4: Reference model, 4] 2. ODP Type Repository [ISO/IEC 14769:2001 Information
technology — Open Distributed Processing — Type Repository Function, 4]

### 3.4348
TRA
1. threat and risk assessment [IEEE 1012-2012 IEEE Standard for System and Software Verification and Validation,
### 3.2] 

### 3.4388
TRR
1. test readiness review [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on Defense Programs,
### 3.2] 

### 3.4405
UART
1. universal asynchronous receiver/transmitter
### 3.4406
UDF
1. unit development folder
cf. software development file
### 3.4407
ULA
1. Upper Layers Architecture [ISO/IEC 10746-1:1998 Information technology — Open Distributed Processing —
Reference model: Overview]
### 3.4408
UML
1. Unified Modeling Language [ISO/IEC 14769:2001 Information technology — Open Distributed Processing — Type
Repository Function, 4; ISO/IEC 19793:2015 Information technology — Open Distributed Processing — Use of UML for
ODP system specifications, 4] 

### 3.4420
Unified Modeling Language (UML)
1. graphical language for visualizing, specifying, constructing, and documenting an object-oriented softwareintensive system's artifacts
### 3.4421
uniform resource identifier (URI)
1. compact sequence of characters that identifies an abstract or physical resource available on the Internet [ISO/IEC
19770-5:2015 Information technology — IT asset management — Part 5: Overview and vocabulary, ### 3.51]
Note 1 to entry: The syntax used for URIs is defined in IETF RFC 3986.
### 3.4422
Uniform Resource Locator (URL)
1. mechanism for identifying resources on the Internet (such as web pages) by specifying the address of the resource
and the access protocol used [ISO/IEC/IEEE 23026:2015 Systems and software engineering — Engineering and
management of websites for systems, software, and services information, 4.25]
Note 1 to entry: The term as specified by the IETF is uniform resource identifier (URI) of which URL is a subset

### 3.4431
universal asynchronous receiver/transmitter (UART)
1. electronic unit used for serial communications that translates data between parallel and serial forms
Note 1 to entry: The data format and transmission speeds are configurable. Commonly part of a microcontroller.
### 3.4432
universal serial bus (USB)
1. serial communication interface with two data lines and two power lines between a computer and peripherals

### 3.4435
UNSP-SC
1. United Nations standard products and services code [ISO/IEC 19770-3:2016, Information technology — IT asset
management — Part 3: Entitlement schema, ### 3.2]

### 3.4438
UNTIL
post-tested iteration
1. single-entry, single-exit loop, in which the loop control is executed after the loop body.
cf. closed loop, WHILE, trailing decision

### 3.4440
UOD
1. Universe of Discourse [ISO/IEC 19793:2015 Information technology — Open Distributed Processing — Use of UML
for ODP system specifications, 4] 

### 3.4447
UR
1. user requirements [ISO/IEC TR 14143-4:2002 Information technology — Software measurement — Functional size
measurement — Part 4: Reference model, 4]
### 3.4448
URa
1. utilize benchmarking results activity [ISO/IEC 29155-2:2013: Systems and software engineering — Information
technology project performance benchmarking framework — Part 2: Requirements for benchmarking, 4]
### 3.4449
URI
1. uniform resource identifier [ISO/IEC 19770-5:2015 Information technology — IT asset management — Part 5:
Overview and vocabulary, ### 3.51]

### 3.4450
URL
1. uniform resource locator [ISO/IEC/IEEE 23026:2015 Systems and software engineering — Engineering and
management of websites for systems, software, and services information]

### 3.4461
USB
1. universal serial bus

### 3.4482
user requirements (UR)
usage requirements
1. requirements for use that provide the basis for design and evaluation of interactive systems to meet identified
user needs [ISO/IEC TR 25060:2010 Systems and software engineering — Systems and software product Quality
Requirements and Evaluation (SQuaRE) — Common Industry Format (CIF) for usability: General framework for
usability-related information, 2.21] 2. description of the set of user needs for the software [ISO/IEC 14143-1:2007
Information technology — Software measurement — Functional size measurement; Part 1: Definition of concepts,
### 3.12] ### 3. expression of perceived need from individual or group that benefits from a system during its utilization
[ISO/IEC TR 24766:2009 Information technology — Systems and software engineering — Guide for requirements
engineering tool capabilities, ### 3.10]
Note 1 to entry: User requirements specify the extent to which user needs and capabilities are to be met when using the system.
They are not requirements on the users. User requirements are derived from user needs and capabilities in order to make use
of the system in an effective, efficient, safe and satisfying manner. User requirements comprise two subsets: functional user
requirements and non-functional user requirements. [ISO 25063:2014] In software-engineering terms, user requirements
comprise both "functional" and "non-functional" requirements based on user needs and capabilities.

### 3.4490
UTC
1. Coordinated Universal Time [ISO/IEC/IEEE 23026:2015 Systems and software engineering — Engineering and
management of websites for systems, software, and services information, 5]

### 3.4494
V&V
1. verification and validation.
### 3.4495
VAC
1. variance at completion [A Guide to the Project Management Body of Knowledge (PMBOK® Guide) — Fifth Edition]

### 3.4505
value engineering (VE)
1. an approach used to optimize project life cycle costs, save time, increase profits, improve quality, expand market
share, solve problems, and/or use resources more effectively [A Guide to the Project Management Body of Knowledge
(PMBOK® Guide) — Fifth Edition]

### 3.4508
value-added reseller (VAR)
1. company licensed to repackage and support existing products, such as combined software packages [ISO/IEC
19770-2:2015 Information technology — Software asset management — Part 2: Software identification tag, 4.1.45]
### 3.4509
VAR
1. value-added reseller

### 3.4528
variance at completion (VAC)
1. a projection of the amount of budget deficit or surplus, expressed as the difference between the budget at
completion and the estimate at completion [A Guide to the Project Management Body of Knowledge (PMBOK® Guide)
— Fifth Edition] 

### 3.4532
VCRM
1. verification cross-reference matrix [IEEE 15288.2:2014 IEEE Standard for Technical Reviews and Audits on
Defense Programs, ### 3.2]
cf. RTM
### 3.4533
VDD
1. version description document

### 3.4539
verification and validation (V&V)
1. process of determining whether the requirements for a system or component are complete and correct, the
products of each development phase fulfill the requirements or conditions imposed by the previous phase, and the
final system or component complies with specified requirements
cf. independent verification and validation
### 3.4540
verification and validation (V&V) effort
1. work associated with performing the V&V processes, activities, and tasks [IEEE 1012-2012 IEEE Standard for
System and Software Verification and Validation, ### 3.1.37]

### 3.4544
Verilog hardware description language (VHDL)
1. hardware description language used to design and verify digital circuits
Note 1 to entry: standardized in IEEE 1394

### 3.4547
version description document (VDD)
1. document that accompanies and identifies a given version of a system or component
Note 1 to entry: Typical contents include an inventory of system or component parts, identification of changes incorporated into
this version, and installation and operating information unique to the version described.

### 3.4551
very small entity (VSE)
1. entity (enterprise, organization, department or project) having up to 25 people [ISO/IEC TR 29110-1:2016
Software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 1: Overview, 2.41]
### 3.4552
VHSIC
1. very high speed integrated circuit
### 3.4553
video display terminal (VDT)
visual display terminal
visual display unit (VDU)
1. user terminal with a display screen and usually equipped with an input unit such as a keyboard [ISO/IEC
2382:2015, Information technology — Vocabulary]
### 3.4554
video random access memory (VRAM)
1. random access memory designed for the frame buffers of graphics cards

### 3.4564
virtual machine (VM)
1. virtual data processing system that appears to be at the disposal of a particular user, but whose functions are
accomplished by sharing the resources of a real data processing system [ISO/IEC 2382:2015, Information technology
— Vocabulary]

### 3.4573
VRAM
1. video random access memory
### 3.4574
VSCID
1. vendor service context codeset ID [ISO/IEC 19500-2:2012 Information technology — Object Management Group
— Common Object Request Broker Architecture (CORBA) — Part 2: Interoperability, ### 3.3]
### 3.4575
VSE
1. very small entity [ISO/IEC TR 29110-1:2016 Software engineering — Lifecycle profiles for Very Small Entities (VSEs)
— Part 1: Overview, ### 3.2; ISO/IEC TR 29110-5-6-2:2014 Systems and software engineering — Lifecycle profiles for Very
Small Entities (VSEs) — Part 5-6-2: Systems engineering — Management and engineering guide: Generic profile group:
Basic profile, 4.2]
Note 1 to entry: The plural is VSEs (very small entities)

### 3.4576
VVP
1. verification and validation plan [IEEE 1012-2012 IEEE Standard for System and Software Verification and
Validation, ### 3.2]
### 3.4577
W3C
1. World Wide Web Consortium [ISO/IEC 19770-3:2016, Information technology — IT asset management — Part 3:
Entitlement schema, ### 3.2] 

### 3.4580
WAP
1. Wireless Application Protocol [ISO/IEC/IEEE 23026:2015 Systems and software engineering — Engineering and
management of websites for systems, software, and services information, 5] 

### 3.4583
watchdog timer (WDT)
1. electronic unit that triggers a reset of an embedded system or other corrective action if the main program, due to
some fault condition, fails to periodically signal it

### 3.4585
WBS
1. work breakdown structure [ISO/IEC TR 29110-5-6-2:2014 Systems and software engineering — Lifecycle profiles
for Very Small Entities (VSEs) — Part 5-6-2: Systems engineering — Management and engineering guide: Generic
profile group: Basic profile, 4.2; ISO/IEC/IEEE 16326:2009 Systems and software engineering — Life cycle processes
— Project management, 5]
### 3.4586
WCAG
1. Web Content Accessibility Guidelines [ISO/IEC/IEEE 23026:2015 Systems and software engineering — Engineering
and management of websites for systems, software, and services information, 5]
### 3.4587
WDT
1. watchdog timer

### 3.4603
work breakdown structure (WBS)
1. a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the
project objectives and create the required deliverables [A Guide to the Project Management Body of Knowledge
(PMBOK® Guide) — Fifth Edition] 2. deliverable-oriented hierarchical decomposition of the work to be executed by
the project team to accomplish the project objectives and create the required deliverables [ISO/IEC TR 29110-5-6-
2:2014 Systems and software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 5-6-2: Systems
engineering — Management and engineering guide: Generic profile group: Basic profile, ### 3.12]

### 3.4625
XFN
1. X/Open Federated Naming [ISO/IEC 14771:1999 Information technology — Open Distributed Processing —
Naming framework, 4]
### 3.4626
XHTML
1. Extended HyperText Markup Language [ISO/IEC/IEEE 16326:2009 Systems and software engineering — Life cycle
processes — Project management, 5]
### 3.4627
XMI
1. XML Metadata Interchange [ISO/IEC 19500-3:2012 Information technology — Object Management Group —
Common Architecture Request Broker Architecture (CORBA) — Part 3: Components, 4.3; ISO/IEC 19793:2015
Information technology — Open Distributed Processing — Use of UML for ODP system specifications, 4]
### 3.4628
XML
1. extensible markup language [ISO/IEC 15909-2:2011 Software and system engineering — High-level Petri nets —
Part 2: Transfer format, 4.2.9]
### 3.4629
XML schema definition
1. XML-based language that specifies a set of rules and structure for the creation of XML documents 2. language that
describes the structure of XML information [ISO/IEC 19770-3:2016, Information technology — IT asset management
— Part 3: Entitlement schema, ### 3.1.42]
Note 1 to entry: XML documents follow all rules defined in an XSD definition in order to be considered a valid document.
### 3.4630
XML schema document (XSD)
1. document that describes the structure of XML information [ISO/IEC 19770-5:2015 Information technology — IT asset management — Part 5: Overview and vocabulary, ### 3.55] 
### 3.4631 XSD
1. XML schema definition 2. XML schema document [ISO/IEC 19770-5:2015 Information technology — IT asset management — Part 5: Overview and vocabulary, ### 3.55]