Партнеры

Имя	Роль	Проектные задачи
N/A

Персонал

Имя	Роль	%еженедельной занятости в проекте	Project Tasks
Голубев И.	Руководитель проекта
Петров С.А.	Старший Java-разработчик/Тестер/Специалист по базам данных	50%

3.6. План предотвращения дефектов

3.6.1 Команда предотвращения дефектов проекта

Команда предотвращения дефектов проекта состоит из:

• Руководителя проекта

• Тестера

3.6.2 Деятельность по предотвращению дефектов

[] Сопровождение процесса

[] Использование контрольных перечней документов

Document checklists contain the list of the most frequent and common errors made during preparation of appropriate project document. Use these checklists before sending document for review. Documents checklists are available on K:/process/checklists

[] Использование контрольных перечней кода

Стартовое совещаниеCode checklists contain the list of the most frequent and common errors made during coding phase . Use these checklists during when coding. Checklists are available on K:/process/checklistsСтаставfd

The project leader should conduct the meeting and ensure that it is cooperative and nonthreatening. The intent is for everyone to understand what is to be done, to be aware of relevant defect prevention action, and to be committed to the common quality effort.

Effective kick-off meetings are held one hour and half at most.

Kick-off meeting minutes shall be distributed among project team, project manager and quality leader.

[x] Начальный анализ требований

[] Начальная функциональная спецификация разработки

[x] Начальная разработка дизайна

[] Начальное системное тестирование

[] Введение в этап кода

Тренинги

[] Тренинг по планированию

Helps to eliminate defects of illegal estimation.

[] Тренинг по дизайну

Helps to eliminate defects of work breakdown structure, interface and algorithm errors.

[] Тренинг по языкам программирования и интсрументальным программным средствам

Helps to eliminate defects caused by incomplete knowledge of these languages/tools

[] Тренинг по ходу развития разработки

Helps to eliminate defects of standards and process violation.

[x] Тренинг по английскому языку

Helps to eliminate English grammar errors.

[] Рецензирование

Helps to find planning, design, and specification errors at the early stages of the project. For the description of review procedure, refer to Chapter 5 of Software Engineering Handbook: Review Process.

[x] Просмотр кода

The most critical parts of code are inspected

[] Инспекции

The most critical documents or their parts are inspected, most critical parts of code are inspected also. For the description of inspection procedure, refer to Chapter 5 of Software Engineering Handbook.

[] Повторное использование обзоров критериев приемки

When source code is to be reused, a special review shall be organized where the possible issues are considered. Review Notes shall be distributed to SQA to put them into project notebook.

Собрание для причинного анализа

Causal Analysis (CA) is the process of examining defects by tracing them to their source and developing methods to prevent a particular type of defect from being reintroduced. To be most effective, Causal Analysis should be done at the earliest possible time with respect to when the defect was found. Cause Analysis meeting shall be planned in the project’s SPMP. CA needs to be performed as early as possible in the development activities with relation to when the errors or defects were introduced into the work. All CA meetings results shall be documented as corresponding meeting minutes or as Review Notes and shall be distributed to SQA to put them into project notebook.

[] После того, как SPMP был выполнен и утвержден

Errors found during review shall be investigated.

[x] Анализ пост-релизных ошибок и дефектов

Project teem shall analyze all post-release defects (submitted in defects tracking system) related to the scope of project (experience of previous project in the similar area).

[] После того, как функциональные спецификации были выполнены и утверждены

Review and inspection faults are to be considered, as well as all defects on earlier stages found to date.

[] В процессе анализа по завершении проекта

For all coding defects found during testing phase and coding errors discovered during coding phase. This meeting is mandatory for all SPSD projects.

[] QPM триггеры

CA meeting shall be organized to address the problems encountered during quantitative analysis of measurement data, e.g. exceeding the process capability baselines. This meeting is mandatory for all outbreaks of process capability baselines

Анализ по завершении проекта

The purpose of a postmortem is to critically analyze the past activities of the project till the end of a phase, or till the end of the project. Based on the activities, during postmortem, the participants systematically identify the strengths and weaknesses of the process and collectively evolve strategies and action plans to fortify the strengths and eliminate the weaknesses.

[] Заключение по достижению требований и планированию

To be performed after project plans approval

[] Заключение по анализу требований

To be perfoemed after FS approval

[] Заключение по дизайну

To be performed after Detailed Design approval

[] Заключение по кодированию

To be performed before formal system test cycle

[x] Заключение по релизу

To performed during Release review

[] Участие в новостной группе разрабатываемого ПО