在談CMMI-ACQ時有些用詞需要特別注意，因為這些用詞如果沒有深入了解其意義，就很容易陷入acquisition == procurement的迷思中，而使得在組織在判斷是否適合採用CMMI-ACQ時發生問題。

以下的用詞被CMMI-ACQ所使用(未特別指明出處者，即錄自CMMI-ACQ之詞彙)，但是這些詞在CMMI-ACQ中的定義，則來自於各項工業(IEEE)及國際標準(ISO)。在此要特別別點出來的是，筆者在之前所提acquisition包含procurement，但不全等於procurement，讀者可以從CMMI-ACQ中提到獲取者應決定獲取策略(acquisition strategy)(其他標準談及獲取過程，亦有同樣的要求，例如ISO/IEC 12207)中，即可看出其不同。獲取策略要求思考的範圍包括了獲取方法、契約或協議的型式等，吾人即可知道，採購並非獲取的唯一方式，亦即，採購不等同於獲取；再者，供應者，並非一定在組織的外部，也可能就在組織本身，因此，不一定有所謂的買賣行為；而契約，所指的是具有法律約束效力的相互認可(的文件)，但並不一定是與外界的廠商所簽訂者，有可能是內部的其他組織，而在獲取過程中，約束雙方(甲乙雙方)的契約中，協議也是選項之一。

Acquirer: The stakeholder that acquires or procures a product or service from a supplier. (See also “stakeholder.”)
獲取者：自供應者獲取或採購產品或服務的利害相關者。
此與IEEE STD 1062 Recommended Practice for Software Acquisition及ISO/IEC 12207 Software Life Cycle Processes相同。

Acquisition: The process of obtaining products or services through supplier agreements. (See also “supplier agreement.”)
獲取：透過供應者協議獲得產品或服務的過程。
acquisition: The process of obtaining a system or software product.
獲取：獲得系統或軟體產品的過程。(IEEE STD 1062 Recommended Practice for Software Acquisition)
acquisition: process of obtaining a system, software product or software service.
獲取：獲得系統、軟體產品或軟體服務的過程。(ISO/IEC 12207 Software Life Cycle Processes)

Acquisition strategy: The specific approach to acquiring products and services that is based on considerations of supply sources, acquisition methods, requirements specification types, contract or agreement types, and related acquisition risks.
獲取策略：在供應源、獲取方法、需求規格型式、合約或協議型式、以及相關獲取風險等考量下，獲取產品與服務的特定作法。

Agreement: mutual acknowledgement of terms and conditions under which a working relationship is conducted.
協議：條款與條件的相互確認，據此，工作關係進行。(ISO/IEC 12207 Software Life Cycle Processes)

contract: binding agreement between two paties, especially enforceable by law, or a similar internal agreement wholly within an organization
契約：在雙方間用以束縛的協議，特別是以法律所強制者，或者是在整個組織中的類似的內部協議。(ISO/IEC 12207 Software Life Cycle Processes)

contract: a binding agreement between two paties, especially enforceable by law or similar internal agreement wholly within an organization, for supply of service or for the supply, development, production, operation, or maintenance of a software product.
契約：就服務的供應，或軟體產品之供應、發展、生產、運作、或維護之目的，在雙方間用以束縛的協議，特別是以法律或在整個組織內類似內部協議所強制要求。(IEEE STD 1062 Recommended Practice for Software Acquisition)

software acquisition process: The period of time that begins with the decision to acquire a software prodcut and ends when the product is no longer available for use. The software acquisition process typically includes nine steps associated with planning the organizational strategy, implementing an organization's process, determining the software requirements, identifying potential suppliers, preparing contract requirements, evaluating proposals and selecting the supplier, managing suppiler performance, accepting the software, and using the software.
軟體獲取過程：以獲取軟體產品之決策為開始，並於該產品不再可用時為止的一段時間。軟體獲取過程一般涵蓋與規劃組織策略、實作組織過程、決定軟體需求、識別可能的供應者、準備契約需求、評估建議書與選擇供應者、管理供應者績效、接收軟體、及使用軟體等九個步驟。(IEEE STD 1062 Recommended Practice for Software Acquisition)

supplier: (1) An entity delivering products or performing services being acquired. (2) An individual, partnership, company, corporation, association, or other service having an agreement with an acquirer for the design, development, manufacture, maintenance, modification, or supply of items under the terms of an agreement. (See also “acquirer.”)
供應者：(1) 交付被獲取之產品或履行被獲取之服務的個體 (2)在協議條款下，就各種品項設計、發展、製造、維護、修改、或供應，與獲取者簽訂協議的個人、夥伴、公司、企業、公協會或其他服務單位。

Supplier: organization or individual that enters into an agreement with the acquirer for the supply of a product or service
NOTE1: The "supplier" could be a contractor, producer, seller, or vendor.
NOTE2: Sometimes the acquirer and the supplier are part of the same organization.
供應者：進入與獲取者的協議中以供應產品或服務的組織或個人。
備考1："供應者"可為合約者、生產者、銷售者、或零售者。
備考2： 有時候，獲取者與供應者同時隸屬於同一個組織中。
(ISO/IEC 12207 Software Life Cycle Processes)

----------------
引文: