Upgrade to remove ads
Only $35.99/year

EX2 Ch 12 Software Quality Assurance and Testing

Terms in this set (18)

Software Quality Assurance
X involves the entire software development PROCESS - monitoring and improving the process, making sure that any agreed-upon standards and procedures are followed, and ensuring that problems are found and dealt with.

It is oriented to prevent software defects.
Why is quality important?
Reduce the cost of rework by identifying defects earlier in the development lifecycle.
Employ consistent procedures for successful software delivery and validation of platform configuration.
Improve product time to market by using repeatable and automated testing methods.
Quality Assurance
A set of activities designed to evaluate the process by which the products are developed or manufactured.
A planned and systematic pattern of all actions necessary to provide adequate confidence that an item or product conforms to established technical requirements.
Testing
X is a concurrent lifecycle process of executing a program or system in order to measure and improve the quality of the software being tested. It is a phase of SDLC and a subset of the QA processes.

is the last defense in assuring software quality.
Unit Testing - Developer
Lowest level of testing, software component testing to ensure reliable program units
"Unit" is the smallest piece of code that has an identity. In object-oriented languages, this unit is a class. In "structured" languages, this unit is a function.

who engages?
Integration Testing - Development
Demonstrate that the software modules interact in a correct, stable, and coherent manner.
Integration testing is really a continuation of component testing and there is no firm dividing line between the two. In X every component has to be tested again once a new component is integrated into the whole.

who engages?
System Testing - Development and QA
X is conducted when all components of a system or subsystem are in place. In effect, system testing is a kind of "dress rehearsal" before it is shown to the paying clients.

who engages?
Functional Testing - QA
Demonstrate that the software performs according to the functional requirements.

who engages?
Regression Testing - QA
Retesting previously tested features to ensure that a change or bug fix has not introduced new problems.

who engages?
Load/Performance/Benchmark Testing - QA
Confirm that the system operates under full load and determine performance benchmarks to indicate performance degradation points.

who engages?
Failure/Failover Testing - QA
Confirm that the application will fail properly in the event that a component fails.

who engages?
Acceptance Testing (UAT) - Client
Confirm that the system meets its business requirements and provide confidence that the system works correctly.
A product passes acceptance testing when the people who have paid for its development accept it.
Controls
the plan of organization and all the methods and measures to safeguard its assets, check the accuracy and reliability of its accounting data, promote operational efficiency, and encourage adherence to prescribed managerial policies
They can be preventive, detective or corrective
They can be manual or automated
Too many controls will reduce efficiency; too few controls will reduce effectiveness
Traditional Control Mechanisms
Separation of duties
Controlling access to assets (e.g., lock and key)
Audit trail (capture of materials and data)
Capture and storage of events in multiple locations and time periods (duplication)
They are primarily physical or manual controls, requires human intervention, error prone
They may not be adequate for modern computer-based systems
General (Management) Controls
Relate to the policies and procedures of data, program, hardware, security, and administrative management
Systems Development Controls
Standardization of development methodology, Enforcement of documentation, Use of CASE tools, Specification of deliverables after each phase, Contracts between developers and client
Programming Controls
Use of structured programming, Cohesion and coupling principles, Single entry - single exit points for a module, Use of structured testing procedures
Data Resource Management Controls
Access rights policies, backup and recovery procedures
Sets found in the same folder