Page 1 / 8

Software Configuration &

Change Management
for
<Project name>
Version <X.X>

<Doc. No. : xxxx-xxx-xx>

 Page 2 / 8

Revision History
Date Rev. Description Prepared by Approved by
 Page 3 / 8

TABLE OF CONTENTS

1 Identification 4
1.1 Document overview 4
1.2 Abbreviations and Glossary 4
1.2.1 Abbreviations 4
1.2.2 Glossary 4
1.3 References 4
1.3.1 Project References 4
1.3.2 Standard and regulatory References 4
2 Organization 5
2.1 Configuration management in a development cycle 5
2.2 Tasks in development and maintenance 5
3 Configuration identification 7
3.1 Identification rules of configuration items 7
3.2 History of Software 7
3.3 Identification rules of SOUPs 7
3.4 History of documents 7
 Page 4 / 8

1 Identification

1.1 Document overview

說明此文件的目的，內容

1.2 Abbreviations and Glossary

1.2.1 Abbreviations
請加上文件中有使用到的縮寫

1.2.2 Glossary
請加上文件中所使用到詞彙

1.3 References

1.3.1 Project References

# Document Identifier Document Title

[R1] 文件 ID 加上參考文件標題

1.3.2 Standard and regulatory References

# Document Identifier Document Title

[STD1] 標準 ID 加上參考的標準

增加參考的標準，可能包括 ISO14971，ISO 13485，IEC 60601，IEC62304…等

2 Configuration Identification
2.1 Organization
 Page 5 / 8

說明負責建構式管理(CM)的組織架構，例如公司是否有專屬的部門負責，或是在此次專案中負
責人員、組織為何?
 The project manager
 The technical manager
 The configuration management manager

2.2 Configuration management in a development cycle

請描述在軟體發展週期中是否有使用任何 CM tool 來管理不同版的軟體，每位軟體開發人員在
進行 checkout-checkin 時需要執行什麼步驟，假如有要進行軟體整合時， 請描述有無任何確
認機制，以及開發週期最後時整合出最終版本

例如你可以使用圖示來說明此專案中 CM 如何進行

Figure 1 illustrates a check in / checkout model for source code control

(Ref : http://www.ni.com/white-paper/4114/en/)

假如公司無使用任何工具來進行建構式管理，請根據實際如何對於軟體進行控管進行說明

2.3 Tasks in development and maintenance

請描述在軟體發展週期中，當有事件產生時 SCM Manager 必須要採取什麼樣的措施

例如 :

Event Operation
Launching the development of a new product Creating the source folder structure in the
master branch
Deciding to create a major version Fork of a branch from the current state of the
master branch
Releasing a major version Tagging the current version in its branch.
Archiving the tagged version
Releasing a minor version or a patch Adding a new tag to the current version in the
branch
Archiving the tagged version
Closing an iteration cycle Adding a new tag to the current version in the
master branch
Other events…
請定義當軟體在開發過程中可能出現的狀態，定義其屬於哪種狀態
 Page 6 / 8

Type of modification Location of the modification

Creating a new functionality in the next major In the master branch
version
Creating a new functionality in the next In the branch of the major version.
minor version
Modifying an existing functionality in the new In the branch of the major version.
minor version
Fixing a bug in a released version In the branch of the major version

Fixing a bug in a version in verification phase In the branch of the major version in
(not yet released) verification phase

2.4 Identification rules of configuration items

請描述軟體版本如何編排，例如初始版本為 Vm.n.p (V1.0.0)
• "Vm " 為主要版本代號
• n 為次要版本代號
• 假如需要的話可使用 p 來增加次要代號
 Page 7 / 8

3 Configuration Management
3.1 History of Software

Software Name :
Data Version Number Contents of Modification
2014/01/01 0.1.0 Draft

2014/03/01 0.2.3 For Engineering Product

2014/06/01 1.0.4 For Pre Product

2014/09/01 2.0.3 Release (Mass Production)

3.2 History of SOUPs

假如有使用到 SOUP，請在此描述 SOUP 的資訊
 SOUP 名稱
 製造商名稱
 SOUP 的版本

假如 open-source SOUP 沒有製造商名稱的話，描述 SOUP 的名稱即可，假如 SOUP 沒有版本資

訊，請依照 3.1 的規則自行定義
SOUP Software Name :
Data Manufacturer Version Number
2013/01/01 xxx 2.1.0

3.3 History of documentation

Document Name :
Data Version Number Contents of Modification
2014/01/01 0.1.0 Draft

2014/03/01 0.2.3 Draft

2014/06/01 1.0.4 Release

2014/09/01 2.0.3 Release

 Page 8 / 8

4 Change Management

4.1 Design Change Process

請描述在每項 Phase 中如果有 Change 需求時，要照著怎樣的流程進行評斷是否要進行修改，可
以用流程圖描述。

4.2 Planning of Design Change Meeting

請描述在每項 phase 中的參與人員及最後 review 的人員，輸入及輸出的文件
Responsible Person in Input output
No. Name Purpose
person charge document document