Laten we beginnen. Het is Gratis
of registreren met je e-mailadres
SQA Components Door Mind Map: SQA Components

1. Infrastructure components for error prevention and improvement

1.1. The goal of SQA infrastructure are the prevention of software faults or, at least, the lowering of software fault rates, together with the improvement of productivity

1.2. This class of SQA components includes

1.2.1. Procedures and work instruction

1.2.1.1. procedures usually provide detailed definitions for the performance .

1.2.1.2. Work instructions, provide detailed directions for the use of methods .

1.2.2. Templates and checklists

1.2.2.1. Contributing to the completeness of the documents and reviews.

1.2.3. Staff training, retraining and certification

1.2.3.1. keeping an organization’s human resources knowledgeable and updated .

1.2.4. Preventive and corrective actions

1.2.4.1. Systematic study of previous failures and success stories to implement.

1.2.5. Configuration management

1.2.5.1. Configuration management deals with these hazards by introducing procedures to control the change process.

1.2.6. Documentation control

2. Management SQA components

2.1. Project progress control in terms of schedule and cost

2.1.1. Project control activities focus on

2.1.1.1. Schedules

2.1.1.2. Resource usage

2.1.1.3. Risk management activities

2.1.1.4. The budget.

2.2. Software quality costs

2.3. Software quality metrics to measure quality

2.3.1. we can list metrics for

2.3.1.1. Quality of software development and maintenance activities

2.3.1.2. Development teams’ productivity

2.3.1.3. Help desk and maintenance teams’ productivity

2.3.1.4. Software faults density

2.3.1.5. Schedule deviations.

3. SQA standerds

3.1. Project process standards

3.2. Quality management standards

4. Organizing for SQA - the human components

5. Pre-project component

5.1. * Contract Reviews :- Reviewing the contract prior to final agreement

5.1.1. Contract review activities include

5.1.1.1. ■ Clarification of the customer’s requirements

5.1.1.2. ■ Review of the project’s schedule and resource requirement estimates

5.1.1.3. ■ Evaluation of the customer’s capacity to fulfill his obligations

5.1.1.4. ■ Evaluation of development risks.

5.2. * Development and quality plan :- Preparation of plans before the actual work is performed

5.2.1. Development plan

5.2.1.1. The main issues treated in the project development plan are

5.2.1.1.1. ■ Schedules .

5.2.1.1.2. ■ Required manpower and hardware resources

5.2.1.1.3. ■ Risk evaluations

5.2.1.1.4. ■ Organizational issues:.

5.2.1.1.5. ■ Project methodology, development tools, etc.

5.2.1.1.6. ■ Software reuse plans.

5.2.2. Quality plan

5.2.2.1. Usually a software quality plan includes

5.2.2.1.1. ■ Quality goals.

5.2.2.1.2. ■ Criteria for starting and ending each project stage

5.2.2.1.3. ■ Lists of reviews, tests, and other scheduled verification and validation activities.

6. Software project life cycle component

6.1. Reviews

6.2. Expert opinions

6.2.1. Insufficient in-house professional capabilities in a given area.

6.3. Software testing

6.3.1. The tests are based on a prepared list of test cases

6.4. Assurance of the quality of external participants’ work