The Software Life-Cycle Based Configuration Management ...

[Pages:2]The Software Life-Cycle Based Configuration Management Tasks for the KNICS Project

Se-Woo Cheon and Kee-Choon Kwon Korea Atomic Energy Research Institute, 150 Deokjin, Yuseong, Daejeon, 305-353 Korea, swcheon@kaeri.re.kr

1. Introduction

Software configuration management (SCM) is an activity, which configures the form of a software system (e.g., design documents and programs) and systematically manages and controls the modifications used to compile the plans, development, and operations resulting from software development and maintenance. The SCM tool, NuSCM, has been specifically developed for the software life-cycle configuration management of developing the KNICS plant protection system (PPS). This paper presents the application of NuSCM to the KNICS project.

2. The Activities of Software Configuration Management

Configuration activities refer to the entire life cycle of the software, which includes the change management of the software both before and after delivery. Software life cycle management is principally the baseline management.

BTP HICB-14 [1] provides the SCM review guidance. Reg. Guide 1.169 [2] endorses IEEE Std 828 [3] which describes the minimum required contents for the SCM plan. IEEE Std 1042 [4] that is a companion to IEEE Std 828 presents an expanded discussion or interpretation for the requirements in IEEE Std 828.

SW Change

SW Enhancement

Defect

Analyze impacts

PPeerfroformrm CChhaannggiinngg aaccttiivviittiieess

SCR closed

Verify a change result

Prepare a change request

SCR

Evaluate a change request (CCB review)

Yes

No

Approved?

SCA

AAlelertrtaacchhaannggeereressuultlt to tthoeddraraftfeterr

Completed

All Events

Configuration Status

Accounting

Log a change result

CCB: Configuration Control Board SCR: Software Change Request SCA: Software Change Authorization

Figure 1. The general software change control process.

SCM activities are traditionally grouped into four functions: i.e., i) configuration identification, ii) configuration control, iii) status accounting, and iv) audits and reviews. The configuration identification activities should identify, name, and describe the documented physical and functional characteristic of the configuration items (CIs) elements to be controlled for the project. Figure 1 shows the general software change control process.

3. Software Configuration Management in the KNICS Project

NuSCM is a configuration management system centered on projects, based on developing software for nuclear power plants. The main menu functions in NuSCM include "Project," "CIs," "Request Forms," "Organization," "Query," "Administrator," and "Audit." The relationships between the NuSCM functions can be represented as a UML (unified modeling language) class diagram, as shown in Figure 2.

Department

parts of

Approval

assign to

draft

RequestProposals

User participate with

Role

responsible for responsible for

BasicRequestProposals

DetailRequestProposals

audit

ConfigurationItems

output Activities

WithdrawalRequestProposals

NewRegistRequestProposals ChangeCompletionRequestProposals

ChangeRequestProposals

Projects

CategoryOfChangeRequest

Figure 2. The class diagram of the NuSCM functions.

As shown in Figure 3, we have classified the higherlevel activities according to the software life cycle phases (i.e., planning, requirement, design, implementation, integration, and installation).

Hierarchical Project/Activities Tree

SQL DB Table Definition for Project/Activities

Projects (Development, V&V)

Activities (Target System: Safety-Grade PLC, RPS, ESF-CCS)

Higher-level Activities (SW Life Cycle Phases)

Subactivities (Plan, SRS, SDD, Test)

Config. Items

design documents drawings source codes

5"4,@*% MJDFOTJOH@DPODFQU MJODFOTJOHSFRVJSFNFOU MJDFOTJOHDPODFQU MJDFOTJOHEFTJHO MJDFOTJOHJNQMFNFOU MJDFOTJOHDPODFQUDPNNPO MJDFOTJOHTX@JOUFHSBUJPO MJDFJOTJOHTZT@JOU MJDFOTJOHWBMJEBUJPO TX@QMBO@EFWFMPQ MJDFOTJOHTX@QMBO@WW MJDFOTJOHTX@QMBO@EFWFMPQ MJDFOTJOHTZTJOU EJHJUBM@TBGFUZ@TZTUFN@1-$ TBGFUZ@TZTUFN@1-$ TBGFUZ@TZTUFN@1-$@DPODFQU TBGFUZ@TZTUFN@314 TBGFUZ@TZTUFN@&4'$$4 TBGFUZ@TZTUFN@01314 MJDFOTJOH@1-$ MJDFOTJOH@314 MJDFOTJOH@&4'$$4 MJDFOTJOH@01314 TBGFUZ@TZTUFN@1-$@SFRVJSF TBGFUZ@TZTUFN@1-$@EFTJHO TBGFUZ@TZTUFN@1-$@JNQMFN TBGFUZ@TZTUFN@1-$@TX@JOU TBGFUZ@TZTUFN@1-$@TZT@JOU TBGFUZ@TZTUFN@1-$@PN TBGFUZ@TZTUFN@1-$@MJDFOT MJDFOTJOH@1-$@DPODFQU MJDFOTJOH@1-$@SFRVJSFNFOU MJDFOTJOH@1-$@EFTJHO MJDFOTJOH@1-$@JNQMFNFOU MJDFOTJOH@1-$@TX@JOU MJDFOTJOH@1-$@TZT@JOU MJDFOTJOH@1-$@PN MJDFOTJOH@1-$@MJDFOTJOH TBGFUZ@TZTUFN@314@DPODFQU TBGFUZ@TZTUFN@314@SFRVJSF TBGFUZ@TZTUFN@&4'@DPODFQU MJDFOTJOH@314@DPODFQU MJDFOTJOH@&4'$$4@DPODFQU 1-$@QMBO@EFWFMPQ TBGFUZ@1-$@QMBO@EFWFMPQ MJDFOTF@1-$@QMBO@EFWFMPQ

5"4,@/".& 48 48 48 48 1-$ 1-$ 314 &4'$$4 314 1-$ 314 &4'$$4 314

4&26& 7*&8@',@5"4,@*%

',@5"4,@/".&

/

/

/

/

/

/ MJDFOTJOHDPODFQU

/

/

/

/ MJDFOTJOHDPODFQU

/ MJDFOTJOHDPODFQU

/ MJDFOTJOHTX@QMBO@EFWFMPQ 48

/

/

:

: TBGFUZ@TZTUFN@1-$

1-$

:

:

:

:

:

:

:

: TBGFUZ@TZTUFN@1-$

1-$

: TBGFUZ@TZTUFN@1-$

1-$

: TBGFUZ@TZTUFN@1-$

1-$

: TBGFUZ@TZTUFN@1-$

1-$

: TBGFUZ@TZTUFN@1-$

1-$

: TBGFUZ@TZTUFN@1-$

1-$

: TBGFUZ@TZTUFN@1-$

1-$

: MJDFOTJOH@1-$

1-$

: MJDFOTJOH@1-$

1-$

: MJDFOTJOH@1-$

1-$

: MJDFOTJOH@1-$

1-$

: MJDFOTJOH@1-$

1-$

: MJDFOTJOH@1-$

1-$

: MJDFOTJOH@1-$

1-$

: MJDFOTJOH@1-$

1-$

: TBGFUZ@TZTUFN@314

314

: TBGFUZ@TZTUFN@314

314

: TBGFUZ@TZTUFN@&4'$$4 &4'$$4

: MJDFOTJOH@314

314

: MJDFOTJOH@&4'$$4

&4'$$4

/ TBGFUZ@TZTUFN@1-$@DPODFQU

: TBGFUZ@TZTUFN@1-$@DPODFQU

: MJDFOTJOH@1-$@DPODFQU

',@130+@*% EJHJUBM@MJDFOTJOH EJHJUBM@MJDFOTJOH EJHJUBM@MJDFOTJOH EJHJUBM@MJDFOTJOH EJHJUBM@MJDFOTJOH EJHJUBM@MJDFOTJOH EJHJUBM@MJDFOTJOH EJHJUBM@MJDFOTJOH EJHJUBM@MJDFOTJOH EJHJUBM@MJDFOTJOH EJHJUBM@MJDFOTJOH EJHJUBM@MJDFOTJOH EJHJUBM@MJDFOTJOH EJHJUBM@TBGFUZ@TZTUFN EJHJUBM@TBGFUZ@TZTUFN EJHJUBM@TBGFUZ@TZTUFN EJHJUBM@TBGFUZ@TZTUFN EJHJUBM@TBGFUZ@TZTUFN EJHJUBM@TBGFUZ@TZTUFN EJHJUBM@MJDFOTJOH EJHJUBM@MJDFOTJOH EJHJUBM@MJDFOTJOH EJHJUBM@MJDFOTJOH EJHJUBM@TBGFUZ@TZTUFN EJHJUBM@TBGFUZ@TZTUFN EJHJUBM@TBGFUZ@TZTUFN EJHJUBM@TBGFUZ@TZTUFN EJHJUBM@TBGFUZ@TZTUFN EJHJUBM@TBGFUZ@TZTUFN EJHJUBM@TBGFUZ@TZTUFN EJHJUBM@MJDFOTJOH EJHJUBM@MJDFOTJOH EJHJUBM@MJDFOTJOH EJHJUBM@MJDFOTJOH EJHJUBM@MJDFOTJOH EJHJUBM@MJDFOTJOH EJHJUBM@MJDFOTJOH EJHJUBM@MJDFOTJOH EJHJUBM@TBGFUZ@TZTUFN EJHJUBM@TBGFUZ@TZTUFN EJHJUBM@TBGFUZ@TZTUFN EJHJUBM@MJDFOTJOH EJHJUBM@MJDFOTJOH EJHJUBM@TBGFUZ@TZTUFN EJHJUBM@TBGFUZ@TZTUFN EJHJUBM@MJDFOTJOH

Figure 3. The Hierarchical Project/Activities classification.

The configuration items in NuSCM include design documents, drawings, and source codes/packages. Figure 4 shows the check-in process of the configuration item from a spreadsheet to a NuSCM input field form. Figure 5 shows the change flow of the configuration item in NuSCM.

The request forms are classified into the detailed request form and the basic request form (see Figure 2), depending on whether the information in the CI requires changes or additions. The detailed request form consists of a new registration request form and a change

completion request form, and the basic request form consists of a withdrawal request form and a change request form.

Figure 4.The check-in process of the configuration items.

Not Registered

Register a New Return Request Form

Check-out

Register a New Request Form

Register a Change Request Form

Register a Change Request Form

Approve

Check-out

Approve the final stage

The New Request Form Approved

Check-in

Return

Approve the final stage

Register a Withdrawal Request Form Approve

Approve the final stage

The Change Completion Request Form Approved

Check-in

Check-in

Register a Withdrawal Request Form Withdrawal the CI

Figure 5.The change flow of the configuration item in NuSCM.

The new registration form is the application form that allows the user to have an authority to check-in a new CI to the server repository.

Figure 6 shows the main displays (such as the user login, the new CI registration tree, and the project/activities tree menu) of NuSCM.

4. Conclusion

We have described the application of NuSCM to the KNICS project. Based on the software life-cycle based projects and activities classification, the system can systematically manage the configuration items in the KNICS project.

REFERENCES

[1] BTP HICB-14, NUREG-0800, Guidance on Software Reviews for Digital Computer-Based Instrumentation and Control Systems, USNRC, 1997. [2] Reg. Guide 1.169, Configuration Management Plans for Digital Computer Software Used in Safety Systems of Nuclear Power Plants, USNRC, 1997. [3] IEEE Std 828, IEEE Standard for Software Configuration Management Plans, 1998. [4] IEEE Std 1042, IEEE Guide to Software Configuration Management, 1987. [5] S. W. Cheon et al., Guidelines for Evaluating Software Configuration Management Plans for Digital Instrumentation and Control Systems, KAERI/TR-1869/2001, Korea Atomic Energy Research Institute, 2001.

Figure 6.The main displays of NuSCM.

 ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download