DODI 5000.75 Glossary
|ATP||authority to proceed|
|BCAC||Business Capability Acquisition Cycle|
|BEA||Business Enterprise Architecture|
|CAE||Component Acquisition Executive|
|CCA||Clinger Cohen Act|
|CIO||Chief Information Officer|
|CMO||Chief Management Officer|
|DAB||Defense Acquisition Board|
|DAE||Defense Acquisition Executive|
|DBC||Defense Business Council|
|DCMO||Deputy Chief Management Officer|
|DoD CIO||DoD Chief Information Officer|
|DOT&E||Director, Operational Test & Evaluation|
|FYDP||Future Years Defense Program|
|MDAP||Major Defense Acquisition Program|
|RFP||request for proposal|
|T&E||test and evaluation|
|USD(AT&L)||Under Secretary of Defense for Acquisition, Technology & Logistics|
Unless otherwise noted, these terms and their definitions are for the purpose of this issuance.
|business capability||A business capability is the core ability the organization needs to deliver requisite products and services and provide value.|
|business enterprise architecture||The business enterprise architecture is a blueprint to guide the development of integrated business processes within DoD. It includes architectural viewpoints that display: capabilities, activities, processes, data, information exchanges, business rules, system functions, services, system data exchanges, technical standards, terms, and linkages to laws, regulations and policies.|
|business system||Business systems are information systems that are operated by, for, or on behalf of the Department of Defense, including: financial systems, financial data feeder systems, contracting systems, logistics systems, planning and budgeting systems, installations management systems, human resources management systems, and training and readiness systems. A business system does not include a national security system or an information system used exclusively by and within the defense commissary system or the exchange system or other instrumentality of the DoD conducted for the morale, welfare, and recreation of members of the armed forces using non-appropriated funds.|
|change management||Change management is the process of proactively preparing the user community for changes that will occur to an organization (because of the implementation of a business system, for purposes of this issuance).
deployment. A deployment either introduces a new release into the production environment or expands the user base of existing functionality. Deployment includes training and business systems operations activities such as help desk support.
|end state||An end state is a goal to achieve within the context of the business mission area.
IT infrastructure. IT infrastructure is the supporting hardware, software, communication, and information security services that a business system requires to operate, but that can be shared by multiple business systems for scalability.
|lifecycle support requirements||Lifecycle support requirements are requirements for availability, scalability, maintainability, supportability, and other requirements as appropriate for the specific initiative.|
|release||A release is a manageable subset of functionality that provides utility in support of the engineered business processes.
technical requirements. Technical requirements are requirements for infrastructure, hosting, security and lifecycle support requirements.