Every software development, enhancement, or maintenance project includes some quality assurance activities. Even a simple, one-person development job has QA activities embedded in it, even if the programmer denies that "quality assurance" plays a part in what is to be done. Each programmer has some idea of how code should be written, and this idea functions as a coding standard for that programmer.
Similarly, each of us has some idea of how documentation should be written¾this is a personal documentation standard. We proofread and revise our documents, and programmers review their products to make sure they meet their personal standards. These are QA reviews, or audits. Each programmer and writer tests or inspects his or her own work, and these are verification and validation processes.
A project’s formal QA program includes the assurance processes that each team member goes through, but it involves planning and establishing project-wide standards, rather than relying on personal standards and processes. The extent and formality of project QA activities are decisions that the client, project manager, and the QA department make based on their assessment of the project and its risks.
QA Concepts and Definitions
Quality assurance is the planned and systematic set of activities that ensures that software processes and products conform to requirements, standards, and procedures.
- Processes include all of the activities involved in designing, developing, enhancing, and maintaining software.
- Products include the software, associated data, its documentation, and all supporting and reporting paperwork.
- QA includes the process of assuring that standards and procedures are established and are followed throughout the software development lifecycle.
- Standards are the established criteria to which the software products are compared.
- Procedures are the established criteria to which the development and control processes are compared.
Compliance with established requirements, standards, and procedures is evaluated through process monitoring, product evaluation, audits, and testing.
The three mutually supportive activities involved in the software development lifecycle are management, engineering, and quality assurance.
- Software management is the set of activities involved in planning, controlling, and directing the software project.
- Software engineering is the set of activities that analyzes requirements, develops Designs, writes code, and structures databases.
Quality Assurance ensures that the management and engineering efforts result in a product that meets all of its requirements.
RELATED POST
UNIT TESTING PART ONE
UNIT TESTING PART TWO
UNIT TESTING PART THREE
GUI TESTING
WINDOWS COMPLIANCE GUI TESTING PART ONE
WINDOWS COMPLIANCE GUI TESTING PART TWO
WINDOWS COMPLIANCE GUI TESTING PART THREE
WINDOWS COMPLIANCE GUI TESTING PART FOUR VALIDATION TESTING
WINDOWS COMPLIANCE GUI TESTING PART FIVE CONDITION TESTING
WINDOWS COMPLIANCE GUI TESTING PART SIX GENERAL CONDITION TESTING
CONDITION TESTING
TESTING CONDITIONS PART ONE
TESTING CONDITIONS PART TWO
TESTING CONDITIONS PART THREE
TESTING CONDITIONS PART FOUR
SPECIFIC FIELD TESTING
USABILITY TESTING
INTEGRATION TESTING
INTEGRATION TESTING PART ONE
INTEGRATION TESTING PART TWO
INTEGRATION TESTING PART THREE
INTEGRATION TESTING PART FOUR
INTEGRATION TESTING PART FIVE
INTEGRATION TEST STANDARDS
INTEGRATION TEST STANDARDS PART TWO
No comments:
Post a Comment