Software Quality and Testing Standards Quiz

Study Notes

Overview of Software Quality and Testing Standards

Software quality is the degree to which a product meets established requirements, accurately representing stakeholder needs, wants, and expectations.
The classification of software error causes includes faulty definition of requirements, client-developer communication failures, deliberate deviations from software requirements, logical design errors, coding errors, noncompliance with documentation and coding instructions, disintegrated testing process, user interface and procedure errors, and documentation errors.
Software quality planning involves producing a project-level quality plan to identify relevant quality standards and regulations, defining quality requirements and goals, selecting applicable software quality procedures, and supporting the introduction and utilization of new procedures and tools for software quality assurance.
Software quality assurance involves defining and evaluating software processes to ensure relevant quality standards are met, fulfilling technical requirements and stakeholder considerations, and considering external factors such as schedule and budget.
Software quality control involves a set of procedures to ensure that the software meets its quality goals, supporting systematic checking, functional and non-functional requirements, and leading to verification, validation, and software testing.
IEEE 730-2014 standard defines the requirements for initiating, planning, controlling, and executing software quality assurance processes of a software development or maintenance project, applicable to standalone software products and software products part of a system, and aids in software process improvement efforts and consistency maintenance for quality management systems.
ISO/IEC 25010:2011 standard defines the necessary and desired quality characteristics required in a software product, focusing on the representation of stakeholders' needs, consisting of two models of software quality: Quality In Use and System/Software Product Quality.
A software requirements specification is a document that clearly defines the system under development, covering system needs, a high-level description of the system functionality, goals of the system, definition of terms and acronyms, and referencing existing systems, procedures, and requirements.
Key characteristics of a software requirements specification include being complete, traceable, precise, understandable, unambiguous, organized, verifiable, correct, consistent, concise, modifiable, and usable.
Benefits of having a software requirements specification include providing a basis for costs and schedules estimations, a baseline for validation and verification, mitigating problems of language barriers and confusion, preventing mixing of functional and non-functional requirements, reducing development efforts, and serving as a basis for enhancement.
IEEE 830-2009 standard defines the contents and characteristics of a good software requirements specification, including introduction, overall description, specific requirements, and supporting information, and key characteristics of being unambiguous, complete, modifiable, traceable, verifiable, consistent, and usable.
Software testing is an important means of assessing software quality, systematically exercising the software in controlled circumstances to affirm its quality, and measuring according to attributes or product characteristics in need.
ISO/IEC/IEEE 29119 standard provides standards for organizational test policy and strategy, project test management, non-functional testing, and system and acceptance testing techniques, applicableSoftware Testing and Quality Engineering: Definitions, Approaches, and Methodologies
A comprehensive spreadsheet of all use cases should be used to organize and track ongoing testing.
A software test plan is a document that describes the objectives, scope, approach, and focus of software testing.
A software test plan validates the acceptability of a software product, focuses on the intended audience, and covers all requirements specifications.
Integration testing involves combining two or more components into a larger structure for testing and is widely recommended for software testing programs.
Integration testing can be carried out via parallel testing in a microservice landscape, making it easier to identify and contain bugs.
Finite state machines are a model for describing the dynamic behavior of an object over a period of time.
Finite state machines consist of states, transitions, inputs, and outputs and can be represented in multiple formats.
Markov chains are finite state machines with stochastic transitions described with probability values.
Microsoft used finite state machines to model asynchronous callbacks in software systems, improving the performance and reliability of their software systems.
The Agile Software Development Framework supports constant dialogue between “possible” and “desirable,” small releases, simple designs, and constant refactoring.
Agile software development values individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan.
Oracle Agile PLM is a solution that helps businesses manage their product value chain and supports cross-functional teams, agile product governance, collaboration, cost, and analytics.