Configuration management

1. Configuration Management
การจัดการโครงแบบ
1
นาเสนอ รศ. ดร.ญาใจ ลิ่มปิยะกรณ์
2110730 Software Quality and Process Management

2. Why Configuration Management?
2

3. Topic
3
● Configuration Management Plan
● Software Configuration Items
● Change Management
● Status Report
● Configuration Management Audit
● Software Configuration Management Tools
● Demo

4. Software Configuration Management Planning
● Purpose
● Configuration Items
● Naming
● Policy
● SCM Directory
4

5. Software Configuration Management Planning
Purpose
● Identification
● Control
● Status accounting
● Audits and reviews
5

6. Software Configuration Management Planning
Configuration Items
● Project Plan
● Software requirements specifications
● System design descriptions
● Source code
● Software test documents
6

7. Software Configuration Management Planning
[4 digit Projectname]_[Document name]_[Year]_[Version]
Example
CALC_SRS_2016_1.0
CALC_SDD_2016_1.0
7

8. Software Configuration Management Planning
Software
8
Software TortoiseSVN,SnailSVN
URL http://103.208.25.164/svn/project_calc/

9. Software Configuration Management Planning
Policy
● Do not allow developer submit without testing
9

10. SCM Directory
10

11. ชิ้นส่วนโครงแบบซอฟต์แวร ์(software configuration
Item-CIs)
An approved and accepted deliverable, changes have to be
made through formal procedure
Example :-
● Software Project Plans
● Software requirements specifications
● Software design descriptions
● Source code
● Software test documents
11

12. Configuration Item tree
12

13. Change Management
CM is the handling of change request to
baseline including CI in baseline
Change request leads to the creation of new
version, revision and release
13

14. Change Request Process
• Change is requested that can be done by anyone including
users and developers
• Change request is assessed against with project goals
• Following the assessment, the change is accepted or rejected
• If it accepted, the change is assigned to a developer and
implemented
• The implemented change is audited
14

15. CR Process of Calculator
15

16. Section 1: Submitter
16

17. Section 2: PM
Section 3: CCB
17

18. รายงาน
สถานะ
(Status
Report)
1818

19. รายงานสถานะ (Status Report)
The Status Report is separated into the following section.
Project Status Summary:
The short overall view status of the report
1919

20. รายงานสถานะ (Status Report)
What were planned and actually
achieved within the duration
between report
-Which Baseline
-The detail of the work if
related to prototype and
baseline
-By who
-Effect who
2020

21. รายงานสถานะ (Status Report)
Open Issues:
Risk that had happened and
still effect the project will be
listed here.
Open Risk:
Risk that had chance to
happen in the future will be
listed here
2121

22. รายงานสถานะ (Status Report)
Milestones:
The overview trend
of the project
milestones
Open Change Requests
The approved CR
that were not yet
completed will be
listed here
22

23. การตรวจสอบการจัดการโครงแบบซอฟต์แวร์ (SCM Audit)
● Are software configuration management activities planned for the project?
● Has the project identified, controlled, and made available the software work
products through the use of configuration management?
SCMP define configuration management activities, roles,
items, and baselines for the Project Calculator completely
23
Software work products were implemened according to SCMP

24. การตรวจสอบการจัดการโครงแบบซอฟต์แวร์ (SCM Audit)
● Does the project follow a documented procedure to control changes to
configuration items/units?
All changes have been controlled by procedure defined in SCMP
24

25. การตรวจสอบการจัดการโครงแบบซอฟต์แวร์ (SCM Audit)
● Are standard reports on software baselines (e.g., software configuration control
board minutes and change request summary and status reports) distributed to
affected groups and individuals?
All affected groups and individuals have been
informed every standard reports on software baselines
which related to their responsibilities
25

26. การตรวจสอบการจัดการโครงแบบซอฟต์แวร์ (SCM Audit)
● Does the project follow a written organizational policy for implementing
software configuration management activities?
● Are project personnel trained to perform the software configuration
management activities for which they are responsible?
The Project Calculator follows by the organizational policy
26
All project personnel were trained for which they are
responsible before the beginning of the project

27. Software Configuration Management tools(SCM tools)
Tortoise SVN (for Windows), Snail SVN (for Mac)
27

28. Software Configuration Management tools(SCM tools)
การปิดกั้นอย่างเข้มงวด หรืออนุญาตให้นาออกได้ตามอาเภอใจ (Strict locking versus
permissive checkouts)
28
รูปแบบที่มีกรรมสิทธิ์ หรือรูปแบบเปิด (Proprietary or
open format)

29. Software Configuration Management tools(SCM tools)
การรวมเข้าอย่างอัตโนมัติ หรือจัดการเรื่องกิ่งก้านอย่างไร(Automatic
merging? What about of branches?)
29
ความสามารถในการรายงานผล
(Reporting capabilities)

30. Software Configuration Management tools(SCM tools)
ความสามารถในการขยาย และการบูรณาการกับเครื่องมืออื่น(Extensibility
and integration with other tools)
30
การสนับสนุนของแฟลตฟอร์ม
(Platform support)

31. Demo
31

32. Team members
32
Chakrit Phain 5970917221 CS
Soraya Chalard 5970974021 CS
Thongham Chongmesuk 5970176521 CM
Wiphop Pomak 5970959621 CS
Korrakod Vadhanavira 5970902821 CS
Chanon Yaklai 5970145021 CM
Ratthida Wongsakthaworn 5970997421 CS