1什麼是Defect:
Defect 監控和記錄與問題相關的資訊。Defect問題相關，但并不一定與CMVC中的檔案相關。defect可以記錄個人的問題，硬體問題，流程的問題以及産品相關的問題。
什麼是Feature?
Featyre 監控和記錄proposed設計變更相關的資訊。可以說流程方面，硬體設計以及軟體産品設計方面的。
Defect和Feature共同的屬性：
Name:名稱
Component:opened against a single component for evaluation, management, and resolution or implementation.
State:Valid states are open, design, size, review, working, verify, closed, returned, and canceled.
Originator:誰開的
Owner:誰負責實作或解決
Remarks:Information describing the defect or feature.
Prefix:A code for specifying different types of defects or features.
Age:自open以來的時間
Reference:
Abstract:
For Defects and Features:
- Priority – An indication of the relative importance of the defect or feature.
- Target – An indication of when the defect is to be resolved or the feature is to be implemented.
For Defects Only:
- Phase Found – The development phase in progress when the problem was discovered.
- Phase Injected – The development phase in progress when the defect was reported (injected).
什麼是track?
Track: 用來監控defect和feature的resolution(解決）情況。當track最初建立的時候其狀态可能是approve也可能是fix狀态。 如果track的release有approval的子過程，則track的初始狀态為initial狀态，否則為為fix狀态。
track在defect/feature進入working stage狀态的時候建立，由于一個defect/feature可能會影響多個release，是以必須針對defect和release建立track.。每個defect/feature和release對唯一決定了一個track.
Track的屬性：
* Name ：
* Release ：
* Prefix – d/f
* State – Valid states are approve, fix, integrate, commit, test, and complete.
* Owner –
* Abstract –
* Level – The level in which the track is committed. This value is updated by CMVC, and are blank if the track is committed without a level.
* Target – Each track can optionally have a target for the resolution of the defect or implementation of the feature.
* Reference – The track reference is that of the respective defect or feature.
一個track狀态的變遷：
Track的狀态解釋：
Approve:在設定有approval subprocess的情況下，track建立後其初始狀态為approve狀态。當進入approve state狀态的時候，approve record被記錄。隻有當所有的approval record變為accept 或者abstain狀态的時候此狀态才會改變.
Build: 位于integrate和commit狀态的中間狀态，當對應的level進入build狀态的時候，track變為build 狀态。
Certify: Build狀态之後，commit狀态之前的狀态。
Commit狀态： 當track對應的level變為committed後，track自動變為commit狀态。此時，所有相關的檔案變更都被committed.
complete:track的最終狀态，當track關聯的level completed，track自動變為completed狀态。當track變為此狀态時，其對應的feature/defect自動變為verify或者complete 狀态。
Fix狀态：While the track is in the fix state, file changes for the resolution of the feature or defect are made and checked in to the CMVC server.
Integrate狀态：If the fix and level subprocesses are configured, the track moves automatically to the integrate state when all fix records are complete.
Ready狀态： build狀态之後，commit狀态之前的狀态。
Review：between the fix and integrate states. 當track在integrate狀态的時候，必須先變為fix狀态才能回到review狀态。
Test:ready for formal testing in the specified environments.
What is level?
level的出現是因為： 在每個release裡面有許多問題需要解決，而将一系列的問題以及和其對應的檔案組合在一起變構成了level所要解決的問題。個人了解是分解，将一個很大的target設定為很多milestone，每個level可以了解為milestone，在每個level裡面解決了那個defect或者加了哪些feature。
A level is a CMVC object used to monitor and implement the integration of file changes within a release. The level provides a method for systematically integrating changes into a release under development. Levels can only be created for tracked releases using the level subprocess.
Level狀态的轉換：
Level的幾種狀态的解釋：
Level的working狀态：level建立的初始狀态，在此階段，level不包含任何track，是以也不包含任何的file change,在建立level的時候僅僅隻包含名字和level的owner
Level的Integrate狀态： 當有任何track加入的時候，自動由working狀态變為integrate狀态。在integrate狀态階段，任何加入到level中的track都被叫做level member.當level在此狀态時，隻能做delta file tree (隻包含在本level中被更改的file)extracted.
Commit狀态：可以做delta file tree 也可作full file tree extracted. level中的所有track都被置為commit狀态，并且所有的file變更都将是永久的。
Completed狀态：ready for formal environment testing
什麼是release?
與産品特定版本相關聯的檔案的邏輯組織，不改變檔案的實體位置。
與release相關的屬性： Name，Owner，Component,process,Desription。
每一個release都有一個component與之相關聯。
什麼是Component？
Components are the building blocks of the CMVC environment. They organize data for information retrieval, access control, notification control, problem reporting, and data organization. Each file under CMVC control is managed by a component.
Release和Component的關系：
A release has a one-to-one relationship with a component for management purposes and a one-to-many relationship with files for product-related activities
Component 管理 Feature 和defect，release以及File
Level是跟release相關聯的
當一個release和另一個release相關聯的時候，那麼會在這兩個release之間建立共同的檔案。在一個release改變的檔案會影響到另一個release
Component 管理File而release 則Group File
Feature和Defect定義了Track，而Track決定了level member，level 又屬于level