Projektplan für die Einführung von SPICE®

Nicht erschlagen lassen“

Ja

es ist viel Arbeit.
Sie können die „Automotive“ Norm auch einsetzen, wenn Sie Webseiten entwickeln.
Meine Studenten haben Teile der Norm sinnvoll in großen Unternehmen, sowie in kleine Unternehmen eingesetzt.

Nein

Es ist (hoffentlich) nichts ausgelassen worden.

Oh Schreck

Lassen Sie sich nicht erschrecken!
Ja der Projektplan ist lang, aber abgesehen von den Anforderungen der ISO 16326 [Norm für Projektpläne]
Lieber zu Anfang etwas umfangreicher geplant, als später „nachkarten“ zu müssen.

Einfach

wird es, wenn man sich durchliest, was zu tun ist.
Der Plan beinhaltet viele Details, welche oftmals ausgelassen werden und zum Misserfolg führen können, wenn Sie nicht umgesetzt werden.

ISO/IEC/IEEE 16326

bietet normative Inhaltsspezifikationen für Projektmanagementpläne für Softwareprojekte und softwareintensive Systemprojekte. Es bietet auch detaillierte Diskussionen und Ratschläge für die Anwendung einer Reihe von Projektprozessen, die sowohl für den Software- als auch für den Systemlebenszyklus gelten, wie sie von ISO/IEC 12207 (IEEE Std 12207) bzw. ISO/IEC 15288 (IEEE Std 15288) abgedeckt werden. Die Diskussion und die Ratschläge sollen bei der Vorbereitung des normativen Inhalts von Projektmanagementplänen helfen. ISO/IEC/IEEE 16326ist das Ergebnis der Harmonisierung von ISO/IEC TR 16326 und IEEE Std 1058.

Übersicht über den Projektplan zur Einführung von Automotive SPICE®

Im Folgenden sehen Sie die Inhaltsangabe der Schritte zur Einführung von Automotive SPICE ® in Ihrem Unternehmen:

Automotive SPICE®- [QM] Project Plan – ASPICE ®1
  
Table of contents2
000. Project Plan – ASPICE ® overview14
000. Project Plan – ASPICE ®15
Copyright Information15
Basic presentation of content15
Project plan overview | Summary15
Auto creation of tasks15
Documentation16
Adjust what is needed16
Change History16
Workflow16
Project preparation17
Introduction18
Reason for the norm18
Capability determination19
Process capability20
Rating scales for work products20
Rating scales for processes21
Process house22
Tailoring22
Not allowed is22
Omit processes22
Omit Work Products22
Omit Work Products Characteristics22
Goal22
Create an environment where Automotive SPICE can be executed22
Base installation of codeBeamer23
Backup system for codeBeamer23
People trained on codebeamer23
Sufficient licenses23
Train people on SPICE23
Increase efficiency23
Other goals23
Purpose23
Assumptions23
Schedule23
Policy23
Standard problem procedure23
Communication rules24
Policy XXX24
Information flow on changes24
Confusion24
Accept errors24
Technical Standards24
Change your Mindset24
Management handling25
Task Owner25
Stakeholders25
Administrator / Manager25
Users / user / users25
Architect (Most professional specific (SW, HW mechanics, etc.)25
Architecture Department25
Client / customer / sponsor25
Works Council25
Designer25
Developer25
External service provider25
Requirements department25
Overall project manager | product Manager25
Hotline26
Infrastructure planning26
IT Configuration & Build Manager26
Build Server26
Management26
Methods and procedures26
Project Manager26
Project steering committee26
Quality Mangement26
Quality assurance26
Rollout Manager (for complex products)26
Security officer26
Standard Supplier27
Strategist27
Test department27
Tester27
Enterprise architect27
Related projects27
Version Manager27
Service Team27
Other external stakeholders27
Bug or Change Request27
Project plan for introduction27
Assign Level27
Calculation of costs27
Timing estimation28
Introduce ALM28
Create & Assign Roles28
Process model28
Life cycle model management process28
Relationships28
Information Management28
Timing28
Reviews28
Milestones28
Deliverables28
Modification of the work products29
Process tailoring29
Calculation of benefits29
Ressource planning29
Infrastructure plan29
Hardware29
Operating system29
Network29
Software29
Policies29
Procedures29
Standards30
Facilities (Office or other space)30
Methods, tools and techniques30
Ressource Acquisition30
Acceptance plan30
Project organization30
External interfaces30
Internal interfaces30
Quality assurance30
Authorities and responsibilities30
Schedule, Ressource & Budget allocation30
Present your calculations30
Base Training31
Goal of the training31
Make your company familiar with codeBeamer31
Requirements Management31
Distribute31
Verify understanding31
Correct if neccessary32
Handbooks32
cB Handling32
Change Control32
Schedule control plan32
Budget control plan32
Project closeout plan32
Reporting32
What informations to store where32
Supporting process plans33
Project supervision and work environment33
Decision management33
Risk management33
Configuration management33
Information management33
Documentation34
Quality assurance34
Measurement34
Reviews and audits34
Verification and validation34
Additional plans34
Get this Plan approved by Management34
Concerned to read34
Document what you do35
Data Storage35
Regular Meetings35
Steering committee35
Create a Standard Agenda35
Other Instances35
Standard Agenda35
Work products template creation35
Templates defined36
  
Singe or multiple issue template36
  
01 Items36
01-00 Configuration item36
01-03 Software item36
01-50 Integrated software37
01-51 Application Parameter37
02 Contract / Commitment37
02-00 Contract37
02-01 Commitment/agreement37
03 Data38
03-00* Data38
03-03 Benchmarking data38
03-04 Customer satisfaction data38
03-06 Process performance data39
04 Design39
04-00 Design39
04-02 Domain architecture39
04-03 Domain model39
04-04 Software architectural design40
04-06 System architectural design40
05 Goals40
05-00 Goals40
06 Documentation41
06-00 User Documentation41
06-01 Customer Manual41
06-02 Handling and storage guide41
06-04 Training material42
07 Measurement42
07-00 Measure42
07-01 Customer satisfaction survey42
07-02 Field measure43
07-03 Personnel performance measure43
07-04 Process measure43
07-05 Project measure43
07-06 Quality Measure44
07-07 Risk measure44
07-08 Service level measure44
08 Plans45
08-00 Plan45
08-04 Configuration management plan45
08-12 Project plan45
08-13 Quality plan45
08-14 Recovery plan46
08-16 Release plan Feature Rollout Plan46
08-17 Reuse plan46
08-18 Review Plan46
08-19 Risk management plan47
08-20 Risk mitigation plan47
08-26 Documentation plan47
08-27 Problem management plan48
08-28 Change management plan48
08-29 Improvement plan48
08-50 Test specification48
08-51 Technology monitoring plan49
08-52 Test plan49
09 Policy49
09-00 Policy49
09-03 Reuse policy49
10 Process50
10-00 Process description50
11 Products & Solutions50
11-00 Product50
11-03 Product Release Information50
11-04 Product release package51
11-05 Software unit51
11-06 System51
11-07 Temporary solution51
12 Proposals52
12-01 Request for proposal52
12-03 Reuse proposal52
12-04 Supplier proposal response52
13 Records53
13-01 Acceptance record53
13-04 Communication record53
13-05 Contract review record53
13-06 Delivery record53
13-07 Problem record54
13-08 Baseline54
13-09 Meeting support record54
13-10 Configuration management record55
13-13 Product release approval record55
13-14 Progress status record55
13-15 Proposal review record55
13-16 Change request56
13-17 Customer request56
13-18 Quality record56
13-19 Review record56
13-20 Risk action request57
13-21 Change control record57
13-22 Traceability record57
13-24 Validation results58
13-25 Verification results58
13-50 Test result58
14 Registers58
14-00* Register58
14-01 Change history59
14-02 Corrective action register59
14-05 Preferred suppliers register59
14-06 Schedule59
14-08 Tracking system60
14-09 Work Breakdown Structure60
14-11 Work product list60
14-50 Stakeholder groups list61
15 Reports61
15-00* Report61
15-01 Analysis report61
15-03 Configuration status report61
15-05 Evaluation report62
15-06 Project status report62
15-07 Reuse evaluation report62
15-08 Risk analysis report62
15-09 Risk status report63
15-12 Problem status report63
15-13 Assessment/audit report63
15-16 Improvement opportunity64
15-18 Process performance report: Template64
15-21 Supplier evaluation report: Template64
16 Repository64
16-00* Repository64
16-03 Configuration management system65
16-06 Process repository65
17 Requirements & Criteria65
17-00 Requirement specification65
17-02 Build list66
17-03 Customer requirements / Stakeholder Requirements66
17-05* Documentation66
17-08 Interface requirement specification66
17-11 Software requirements specification67
17-12 System requirements specification67
17-50 Verification criteria67
18 Criteria67
18-00* Standard67
18-01 Acceptance criteria68
18-06 Product release criteria68
18-07 Quality criteria68
18-50 Supplier qualification criteria69
19 Strategies69
19-00 Strategy69
19-05 Reuse strategy69
19-10 Verification strategy69
19-11 Validation strategy70
20 Templates70
21 Work Products (Templates)70
30 Suggestion70
18-60 Payment criteria71
Test Cases for Work products71
Assign Test cases71
Test configurations71
Work product delivery71
Process Definition72
Delivery of products72
Process scope72
Assign the Process owner72
ACQ.372
ACQ.472
ACQ.1172
ACQ.1272
ACQ.1372
ACQ.1472
ACQ.1572
SYS.172
SYS.273
SYS.373
SYS.473
SYS.573
SWE.173
SWE.273
SWE.373
SWE.473
SWE.573
SWE.673
SPL.173
SPL.273
PIM.373
REU.273
Information Management Process73
MAN.373
MAN.574
MAN.674
SUP.174
SUP.274
Not Part of HIS74
SUP.474
SUP.774
SUP.874
SUP.974
SUP.1074
Incoming work products74
Not defined in the Norm75
Define75
Define Testcases75
Integration75
Distribute processes76
Map Test cases76
Deploy process landscape76
Operate76
Loop76
Process capability levels and process attributes76
Target of this Plan76
Excellent quality of work products76
Level 176
Level 276
Company managed on KPI’s76
Level 376
KPI’s for the project77
Work products defined77
Work Products delivered77
Processes defined77
Processes successfully executed77
Errors / line of code77
Task force time77
Development time77
Customer statisfaction77
Other77

Schreibe einen Kommentar