金钱- 3014
海拔- 6258 米
- 积分
- 4173
- 精华
- 7
- 帖子
- 1201
- UID
- 3369
  
|
这个帖子是给初学CM,或者对CM有兴趣,想了解SCMP的人看的。
* R. w7 {( d% l, [6 g, F( H5 y- Q我只写过唯一的一份配置管理计划,没有太多的经验,因此,例子中肯定会有错误,仅供参考。7 Z1 N, y, i8 r1 U5 {
免责申明:如有人擅自使用该文档进行商业用途,一切责任与本人无关。# r3 n7 D0 i3 R2 `& [! e" d @
项目简介: \! [, p! v2 J+ J
该项目PROJECT大小约为20人年。重用XXX项目的部分库,主要实现OAM,REALTIME功能。应该算是一个比较全面的典型项目了。实际情况一般比这个要简单很多。( ~* o* |' R9 Z- ~4 d/ n
下面是目录:
' O! G5 r, x4 x5 hREFERENCED DOCUMENTS 61 O( u' }% U- w0 q; E' ^2 B( Y
• RELATED DOCUMENTS 6; a% m4 w: ?& b' C& P0 y2 d P1 Q4 S
PREFACE 7
+ U) `5 `) |: p$ X# }1 INTRODUCTION 8
) a% h: h. d$ u) q1.1 Objectives 88 f: }. K" G/ p# S7 }8 q
1.2 Scope 8* c8 i9 |/ F/ c. l) [
1.3 Definitions and abbreviation 87 O7 n3 Q% O. ~1 ?( e$ O% E
2 SOFTWARE CONFIGURATION MANAGEMENT 10, _" z% C. X% _# k/ B% E$ V3 }/ `
2.1 SCM organization 10$ d$ o5 B5 V5 i1 y5 e8 Q+ ^
2.1.1 Project SCM group missions 10
* o6 D& r- C# X; V" x7 G( u Z2.1.2 Project coach and site administrators missions: 10# i+ \% p! S6 V8 ?. d
2.1.3 SCMR missions 10
- f# h0 i' T8 A0 w( D# [2.1.4 Software Package correspondent missions 11
& v1 x# Q& C# r# X+ `2.2 SCM responsibilities 11; f" C8 T: i( g: B
2.3 Interfaces to other organizations on the project 11
" ]- k% i* W6 U, @ j+ A) G1 W2.3.1 TOMAS Team 12; F# z; D3 c5 }# d# M
2.3.2 DH FWK team: 128 w0 o6 \/ ]& `; `
3 SOFTWARE CONFIGURATION MANAGEMENT ARCHITECTURE 13
, o3 |' d& w& c; Z! v$ |4 t3.1 SOFTWARE CONFIGURATION MANAGEMENT ENTITIES 13; Q+ J& J5 I* [1 h
3.1.1 Software Function (SF) 134 I/ o, d$ Z: R) |) @
3.1.2 Software Package (SP) 13( p1 z( b' s; W
3.1.3 Domain (DOM) 13+ O- ^8 O4 O2 Y) P! K/ S2 u: {0 f/ f
3.1.4 Component (CNP) 13+ j- Q, u' ]' @% v. d
3.2 Static architecture 148 F* P% q d2 [! \3 D7 i
3.2.1 REAL TIME product tree 14 k9 J- m u- Q7 N1 ^
3.2.2 OAM product tree 15 g! L3 T3 a+ I% ^! M, e, d$ b" a6 [
3.3 Configuration item identification 16
' T! O. f F) z) F3.4 VOB description 166 B; O2 C9 Q& d
3.4.1 VOB naming rules 16' ^) H, D0 s& ?4 ]$ W) J/ c
3.4.2 VOB list and architecture. 17" x+ t) X( D* c+ \5 y
3.5 Multisite configuration 17
4 B5 G# K( ]7 D8 H$ j. `' e9 M0 V4 SOFTWARE CONFIGURATION MANAGEMENT IDENTIFICATION 19* D0 G( }) ? C9 O2 D% @
4.1 Documentation identification 19
6 k* m' {6 E/ ^4 a* a) J4.2 Naming rules generalities 19
; R; D9 l; l7 H+ W4.3 Version identification 197 Z9 y$ T, V: O) C$ J/ [8 g
4.4 Project baseline and labeling rules 19
2 c4 l) y: C1 o( ^4.4.1 Project baseline 19
* Q- N( x* p, o& ~, D' L0 ^. w( Z4.4.2 General labeling rules 20
4 P+ o+ m$ C/ h3 t& N4.5 Branch naming rules 21
: b+ \+ W/ m$ \5 m4.6 Views description 21; P! n4 N; Q% ^5 W9 w
4.6.1 View naming rules 21/ q% |) o* H! v
4.6.2 Views life cycle 221 y/ [1 O- q' J9 T+ ]. l) A$ t, v
5 SOFTWARE CONFIGURATION MANAGEMENT PROCESS 23% E1 ~7 t4 T* C
5.1 Introduction 23+ E/ ~8 J9 @9 m* |6 s% x- V" Y$ j
5.2 Software Package Development process overview 237 X `4 a- p; G7 r b& W' K! L
5.2.1 Branching management policy 23* i8 [. ?; B& ?# L7 D" H8 E4 m$ N
5.2.2 Activities description 24; c1 M1 r- d5 B9 Z# }. F5 j" d
5.3 Software Function common files development process overview 334 ~, t( x. {, \7 F9 m/ K
5.4 External and Third part components management 34
/ f0 Q: {- O1 g; k9 M5.4.1 TOMAS delivery management 34* l8 L& ^* b6 h% w' ^1 M( q* r
5.4.2 OAM generic deliveries management 34. B- U+ E+ }7 d# N0 s* |0 ^
6 SOFTWARE CONFIGURATION MANAGEMENT PROCEDURES 34
" x- {0 V3 v# w& D/ i' w6.1 View creation and synchronization procedure 34
! F( i N$ N0 }+ v* x& z% C6.2 View removing procedure 34. I& v3 P- {0 Y' k. O
6.3 View config spec management 34# p/ S8 J' X, }3 s
6.3.1 view files management 34# M U2 u2 M- Q, r* x. ^3 u
6.3.2 Config spec model management 35
- o, v8 K' w4 D0 o+ Z( A" U6.4 Gliding label management 352 u+ x; Z% O( P6 R' `8 ?8 q3 s5 [
6.5 Building procedures 35, W' p/ i8 \6 {) S& d
6.6 File marking and tracability 35
+ L. h4 K5 d* B! S& G4 ?6.7 Delivery procedure 35
+ r; O0 w2 a) O& V6.8 Patch delivery procedure 364 ]' y b% A2 [* J! t8 J
6.9 Change Control 36
) y0 M# j* ~/ _; p" r6.9.1 Change control process 36
: ?) N Q8 D/ B. u/ H u2 W$ ]& y6.9.2 Automated tools used to perform change control 36
5 n2 O$ L/ n5 S- \2 `6.10 Configuration Status Accounting 367 q2 ` d% o- ~5 L& J
6.11 Configuration Auditing 368 B, i" [8 d9 u' k1 E8 O3 m
6.11.1 product delivery check 36. {/ F9 [& L- X
6.11.2 SCM audit 36' M& h1 _, P' U, h3 T* j# h
7 CM MILESTONES 37
. ~. f0 w) V- t3 _! H4 ^1 W8 TRAINING 376 ?0 T. J/ h8 w
9 SUBCONTRACTOR/VENDOR SUPPORT 37
7 {0 E5 `* s# r9 d6 GA. ANNEXE: SCM RESPONSIBILITIES 38 |
|