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 contents | 2 |
000. Project Plan – ASPICE ® overview | 14 |
000. Project Plan – ASPICE ® | 15 |
Copyright Information | 15 |
Basic presentation of content | 15 |
Project plan overview | Summary | 15 |
Auto creation of tasks | 15 |
Documentation | 16 |
Adjust what is needed | 16 |
Change History | 16 |
Workflow | 16 |
Project preparation | 17 |
Introduction | 18 |
Reason for the norm | 18 |
Capability determination | 19 |
Process capability | 20 |
Rating scales for work products | 20 |
Rating scales for processes | 21 |
Process house | 22 |
Tailoring | 22 |
Not allowed is | 22 |
Omit processes | 22 |
Omit Work Products | 22 |
Omit Work Products Characteristics | 22 |
Goal | 22 |
Create an environment where Automotive SPICE can be executed | 22 |
Base installation of codeBeamer | 23 |
Backup system for codeBeamer | 23 |
People trained on codebeamer | 23 |
Sufficient licenses | 23 |
Train people on SPICE | 23 |
Increase efficiency | 23 |
Other goals | 23 |
Purpose | 23 |
Assumptions | 23 |
Schedule | 23 |
Policy | 23 |
Standard problem procedure | 23 |
Communication rules | 24 |
Policy XXX | 24 |
Information flow on changes | 24 |
Confusion | 24 |
Accept errors | 24 |
Technical Standards | 24 |
Change your Mindset | 24 |
Management handling | 25 |
Task Owner | 25 |
Stakeholders | 25 |
Administrator / Manager | 25 |
Users / user / users | 25 |
Architect (Most professional specific (SW, HW mechanics, etc.) | 25 |
Architecture Department | 25 |
Client / customer / sponsor | 25 |
Works Council | 25 |
Designer | 25 |
Developer | 25 |
External service provider | 25 |
Requirements department | 25 |
Overall project manager | product Manager | 25 |
Hotline | 26 |
Infrastructure planning | 26 |
IT Configuration & Build Manager | 26 |
Build Server | 26 |
Management | 26 |
Methods and procedures | 26 |
Project Manager | 26 |
Project steering committee | 26 |
Quality Mangement | 26 |
Quality assurance | 26 |
Rollout Manager (for complex products) | 26 |
Security officer | 26 |
Standard Supplier | 27 |
Strategist | 27 |
Test department | 27 |
Tester | 27 |
Enterprise architect | 27 |
Related projects | 27 |
Version Manager | 27 |
Service Team | 27 |
Other external stakeholders | 27 |
Bug or Change Request | 27 |
Project plan for introduction | 27 |
Assign Level | 27 |
Calculation of costs | 27 |
Timing estimation | 28 |
Introduce ALM | 28 |
Create & Assign Roles | 28 |
Process model | 28 |
Life cycle model management process | 28 |
Relationships | 28 |
Information Management | 28 |
Timing | 28 |
Reviews | 28 |
Milestones | 28 |
Deliverables | 28 |
Modification of the work products | 29 |
Process tailoring | 29 |
Calculation of benefits | 29 |
Ressource planning | 29 |
Infrastructure plan | 29 |
Hardware | 29 |
Operating system | 29 |
Network | 29 |
Software | 29 |
Policies | 29 |
Procedures | 29 |
Standards | 30 |
Facilities (Office or other space) | 30 |
Methods, tools and techniques | 30 |
Ressource Acquisition | 30 |
Acceptance plan | 30 |
Project organization | 30 |
External interfaces | 30 |
Internal interfaces | 30 |
Quality assurance | 30 |
Authorities and responsibilities | 30 |
Schedule, Ressource & Budget allocation | 30 |
Present your calculations | 30 |
Base Training | 31 |
Goal of the training | 31 |
Make your company familiar with codeBeamer | 31 |
Requirements Management | 31 |
Distribute | 31 |
Verify understanding | 31 |
Correct if neccessary | 32 |
Handbooks | 32 |
cB Handling | 32 |
Change Control | 32 |
Schedule control plan | 32 |
Budget control plan | 32 |
Project closeout plan | 32 |
Reporting | 32 |
What informations to store where | 32 |
Supporting process plans | 33 |
Project supervision and work environment | 33 |
Decision management | 33 |
Risk management | 33 |
Configuration management | 33 |
Information management | 33 |
Documentation | 34 |
Quality assurance | 34 |
Measurement | 34 |
Reviews and audits | 34 |
Verification and validation | 34 |
Additional plans | 34 |
Get this Plan approved by Management | 34 |
Concerned to read | 34 |
Document what you do | 35 |
Data Storage | 35 |
Regular Meetings | 35 |
Steering committee | 35 |
Create a Standard Agenda | 35 |
Other Instances | 35 |
Standard Agenda | 35 |
Work products template creation | 35 |
Templates defined | 36 |
Singe or multiple issue template | 36 |
01 Items | 36 |
01-00 Configuration item | 36 |
01-03 Software item | 36 |
01-50 Integrated software | 37 |
01-51 Application Parameter | 37 |
02 Contract / Commitment | 37 |
02-00 Contract | 37 |
02-01 Commitment/agreement | 37 |
03 Data | 38 |
03-00* Data | 38 |
03-03 Benchmarking data | 38 |
03-04 Customer satisfaction data | 38 |
03-06 Process performance data | 39 |
04 Design | 39 |
04-00 Design | 39 |
04-02 Domain architecture | 39 |
04-03 Domain model | 39 |
04-04 Software architectural design | 40 |
04-06 System architectural design | 40 |
05 Goals | 40 |
05-00 Goals | 40 |
06 Documentation | 41 |
06-00 User Documentation | 41 |
06-01 Customer Manual | 41 |
06-02 Handling and storage guide | 41 |
06-04 Training material | 42 |
07 Measurement | 42 |
07-00 Measure | 42 |
07-01 Customer satisfaction survey | 42 |
07-02 Field measure | 43 |
07-03 Personnel performance measure | 43 |
07-04 Process measure | 43 |
07-05 Project measure | 43 |
07-06 Quality Measure | 44 |
07-07 Risk measure | 44 |
07-08 Service level measure | 44 |
08 Plans | 45 |
08-00 Plan | 45 |
08-04 Configuration management plan | 45 |
08-12 Project plan | 45 |
08-13 Quality plan | 45 |
08-14 Recovery plan | 46 |
08-16 Release plan Feature Rollout Plan | 46 |
08-17 Reuse plan | 46 |
08-18 Review Plan | 46 |
08-19 Risk management plan | 47 |
08-20 Risk mitigation plan | 47 |
08-26 Documentation plan | 47 |
08-27 Problem management plan | 48 |
08-28 Change management plan | 48 |
08-29 Improvement plan | 48 |
08-50 Test specification | 48 |
08-51 Technology monitoring plan | 49 |
08-52 Test plan | 49 |
09 Policy | 49 |
09-00 Policy | 49 |
09-03 Reuse policy | 49 |
10 Process | 50 |
10-00 Process description | 50 |
11 Products & Solutions | 50 |
11-00 Product | 50 |
11-03 Product Release Information | 50 |
11-04 Product release package | 51 |
11-05 Software unit | 51 |
11-06 System | 51 |
11-07 Temporary solution | 51 |
12 Proposals | 52 |
12-01 Request for proposal | 52 |
12-03 Reuse proposal | 52 |
12-04 Supplier proposal response | 52 |
13 Records | 53 |
13-01 Acceptance record | 53 |
13-04 Communication record | 53 |
13-05 Contract review record | 53 |
13-06 Delivery record | 53 |
13-07 Problem record | 54 |
13-08 Baseline | 54 |
13-09 Meeting support record | 54 |
13-10 Configuration management record | 55 |
13-13 Product release approval record | 55 |
13-14 Progress status record | 55 |
13-15 Proposal review record | 55 |
13-16 Change request | 56 |
13-17 Customer request | 56 |
13-18 Quality record | 56 |
13-19 Review record | 56 |
13-20 Risk action request | 57 |
13-21 Change control record | 57 |
13-22 Traceability record | 57 |
13-24 Validation results | 58 |
13-25 Verification results | 58 |
13-50 Test result | 58 |
14 Registers | 58 |
14-00* Register | 58 |
14-01 Change history | 59 |
14-02 Corrective action register | 59 |
14-05 Preferred suppliers register | 59 |
14-06 Schedule | 59 |
14-08 Tracking system | 60 |
14-09 Work Breakdown Structure | 60 |
14-11 Work product list | 60 |
14-50 Stakeholder groups list | 61 |
15 Reports | 61 |
15-00* Report | 61 |
15-01 Analysis report | 61 |
15-03 Configuration status report | 61 |
15-05 Evaluation report | 62 |
15-06 Project status report | 62 |
15-07 Reuse evaluation report | 62 |
15-08 Risk analysis report | 62 |
15-09 Risk status report | 63 |
15-12 Problem status report | 63 |
15-13 Assessment/audit report | 63 |
15-16 Improvement opportunity | 64 |
15-18 Process performance report: Template | 64 |
15-21 Supplier evaluation report: Template | 64 |
16 Repository | 64 |
16-00* Repository | 64 |
16-03 Configuration management system | 65 |
16-06 Process repository | 65 |
17 Requirements & Criteria | 65 |
17-00 Requirement specification | 65 |
17-02 Build list | 66 |
17-03 Customer requirements / Stakeholder Requirements | 66 |
17-05* Documentation | 66 |
17-08 Interface requirement specification | 66 |
17-11 Software requirements specification | 67 |
17-12 System requirements specification | 67 |
17-50 Verification criteria | 67 |
18 Criteria | 67 |
18-00* Standard | 67 |
18-01 Acceptance criteria | 68 |
18-06 Product release criteria | 68 |
18-07 Quality criteria | 68 |
18-50 Supplier qualification criteria | 69 |
19 Strategies | 69 |
19-00 Strategy | 69 |
19-05 Reuse strategy | 69 |
19-10 Verification strategy | 69 |
19-11 Validation strategy | 70 |
20 Templates | 70 |
21 Work Products (Templates) | 70 |
30 Suggestion | 70 |
18-60 Payment criteria | 71 |
Test Cases for Work products | 71 |
Assign Test cases | 71 |
Test configurations | 71 |
Work product delivery | 71 |
Process Definition | 72 |
Delivery of products | 72 |
Process scope | 72 |
Assign the Process owner | 72 |
ACQ.3 | 72 |
ACQ.4 | 72 |
ACQ.11 | 72 |
ACQ.12 | 72 |
ACQ.13 | 72 |
ACQ.14 | 72 |
ACQ.15 | 72 |
SYS.1 | 72 |
SYS.2 | 73 |
SYS.3 | 73 |
SYS.4 | 73 |
SYS.5 | 73 |
SWE.1 | 73 |
SWE.2 | 73 |
SWE.3 | 73 |
SWE.4 | 73 |
SWE.5 | 73 |
SWE.6 | 73 |
SPL.1 | 73 |
SPL.2 | 73 |
PIM.3 | 73 |
REU.2 | 73 |
Information Management Process | 73 |
MAN.3 | 73 |
MAN.5 | 74 |
MAN.6 | 74 |
SUP.1 | 74 |
SUP.2 | 74 |
Not Part of HIS | 74 |
SUP.4 | 74 |
SUP.7 | 74 |
SUP.8 | 74 |
SUP.9 | 74 |
SUP.10 | 74 |
Incoming work products | 74 |
Not defined in the Norm | 75 |
Define | 75 |
Define Testcases | 75 |
Integration | 75 |
Distribute processes | 76 |
Map Test cases | 76 |
Deploy process landscape | 76 |
Operate | 76 |
Loop | 76 |
Process capability levels and process attributes | 76 |
Target of this Plan | 76 |
Excellent quality of work products | 76 |
Level 1 | 76 |
Level 2 | 76 |
Company managed on KPI’s | 76 |
Level 3 | 76 |
KPI’s for the project | 77 |
Work products defined | 77 |
Work Products delivered | 77 |
Processes defined | 77 |
Processes successfully executed | 77 |
Errors / line of code | 77 |
Task force time | 77 |
Development time | 77 |
Customer statisfaction | 77 |
Other | 77 |