software quality assurance Includes the following details: +An SQA process +Specific quality assurance and software
software quality assurance Includes the following details: +An SQA process +Specific quality assurance and
quality control tasks +Effective software engineering practice +Control of all software work products and the
changes made +A procedure to ensure compliance with software development standards +Measurement and
reporting mechanisms Elements of software quality assurance +Standards +Reviews and Audits +Testing
+Error/Defect Collection and Analysis +Change Management +Education +Vendor Management +Security
Management +Safety +Risk Management Sqa tasks +Prepares an SQA plan for a project +Participates in the
development of the project’s software process description +Reviews software engineering activities to verify
compliance with the defined software process +Audits designated software work products to verify compliance
with those defined as part of the software process +Ensures that deviations in software work and work products
are documented and handled according to a documented procedure +Records any noncompliance and reports
to senior management Sqa goals+Requirements Quality +Design Quality +Code Quality +Quality Control
Effectiveness Sqa reviews +Check the quality of the project deliverables +Involves examining the software,
documentation and records of the process to discover errors and omissions Sqa plans +Provides a road map
for instituting software quality assurance +Developed by SQA group to serve as a template for SQA activities
that are instituted for each software project SQA structure identifies the following: +The purpose and scope of
the plans +Description of all software engineering work products for SQA +All applicable standards and
practices that are applied during software process +SQA actions and tasks +Tools and methods that support
SQA actions +Software configuration management, procedures +Methods for assembling, safeguarding, and
maintaining all SQA-related records +Organizational roles and responsibilities relative to product quality Testing
goals +Demonstrate to the developer and the customer that the software meets its requirements +Discover
situations in which the behavior of the software is incorrect, undesirable, or does not conform to
itsspecification Stages of testing +Development Testing +Release Testing +User Testing +Acceptance Testing
software testing options +Unit Testing +Incremental Integration Testing +Integration Testing +Functional
Testing +System Testing SOFTWARE TESTING TYPES +End-to-end Testing +Sanity Testing +Regression Testing
+Acceptance Testing +Load Testing +Performance Testing +Usability Testing +Install-Uninstall Testing
+Recovery Testing +Security Testing +Compatibility Testing +Comparison Testing +Maintenance Testing
+Globalization Testing +Interoperability Testing +Exploratory Testing +Confirmation Testing +Smoke Testing
+Alpha Testing +Beta Testing Software testing criteria +Intuition +Specification +Code +Faults Kinds of test plan
+Test Suite +Test Cases
Activities in software configuration management +Change Management +Version Management +System
Building +Release Management Elements of a software configuration management system +Component
Elements +Process Elements +Construction Elements +Human Elements What is software configuration
management process? Defines a series of tasks that have four primary objectives: +Identify all items that
collectively define the software configuration +Manage changes to one or more items +Facilitate the
construction of different versions of an application +Ensure that software quality is maintained as the
configuration evolves over time Questions involve in scm process +How does a software team identify the
discrete elements of a software configuration? +How does an organization manage the existing versions of a
program that will enable change? +How does an organization control changes before and after software
released to a customer? +How does an organization assess the impact of change and manage the impact
effectively?
What is change request form? +A form where clients or customers input bug report, the symptoms of the bug
are described, or a request for additional functionality to be added to the system +Record information that is
shared between all groups involved in change management+Include a section where a developer outlines how
the change may be implemented Factors for implementing change management +The consequences of not
making the change +The benefits of the change +The number of users affected by the change +The costs of
making the change +The product release cycle Version management systems +Version and Release
Identification +Storage Management System building platforms +Development System +Build Server +Target
Environment What is release management? +Version of a software system that is distributed to customers +A
system released must be documented to ensure that it can be re-created exactly in the future +Record the
specific versions of the source code components that were used to create the executable code Types of release
management +Major Release +Minor Release
Changes during software maintenance +Correct coding errors +Extensive changes to correct design errors
+Significant enhancements to correct specification errors +Accommodate new requirements Types of software
maintenance +Fault Repairs +Environmental Adaptation +Functionality Addition +Types of Software
Maintenance Distribution +Corrective Maintenance +Adaptive Maintenance +Perfective Maintenance
+Preventive Maintenance + Higher Quality +Anticipating Changes +Better Tuning to User Needs +Less Code
Laws about software evolution +Continuing Change +Increasing Complexity +Conversation of Familiarity
+Continuing Growth +Declining Quality +Feedback System +Large Program Evolution+ Organizational Stability
Software evolution approaches +Software Maintenance + Architectural Transformation what is software
maintenance prediction? +Estimates the overall maintenance costs for a system in a given time period +Expects
the number of change requests for a system +Understands the relationship between the system and its external
environment Software maintenance prediction relationships +The number of complexity of system interfaces
+The number of inherently volatile system requirements +The business processes in which the system is use
Metrics for assessing maintainability +Number of requests for corrective maintenance +Average time required
for impact analysis +Average time taken to implement a change request +Number of outstanding change
request What is change request? +Request for system changes from users, customers, and management +All
requests should be carefully analyzed as part of the maintenance process and then implemented Software
maintenance coding activities +Isolation +Modification +Testing Problematic factors in managing software
maintenance +Changing priorities +Inadequate testing methods +Performance measurement difficulties
+Incomplete or non-existent system documentation +Rapidly changing business environment Software
maintenance cost factors +Team Stability +Contractual Responsibility +Staff Skills +Program Age and Structure
What is Software maintenance side effect? +An error or undesirable behavior that occurs as the result of
modification Software maintenance side effects +Code +Data Structure +Documentation
software quality assurance Includes the following details: +An SQA process +Specific quality assurance and
quality control tasks +Effective software engineering practice +Control of all software work products and the
changes made +A procedure to ensure compliance with software development standards +Measurement and
reporting mechanisms Elements of software quality assurance +Standards +Reviews and Audits +Testing
+Error/Defect Collection and Analysis +Change Management +Education +Vendor Management +Security
Management +Safety +Risk Management Sqa tasks +Prepares an SQA plan for a project +Participates in the
development of the project’s software process description +Reviews software engineering activities to verify
compliance with the defined software process +Audits designated software work products to verify compliance
with those defined as part of the software process +Ensures that deviations in software work and work products
are documented and handled according to a documented procedure +Records any noncompliance and reports
to senior management Sqa goals+Requirements Quality +Design Quality +Code Quality +Quality Control
Effectiveness Sqa reviews +Check the quality of the project deliverables +Involves examining the software,
documentation and records of the process to discover errors and omissions Sqa plans +Provides a road map
for instituting software quality assurance +Developed by SQA group to serve as a template for SQA activities
that are instituted for each software project SQA structure identifies the following: +The purpose and scope of
the plans +Description of all software engineering work products for SQA +All applicable standards and
practices that are applied during software process +SQA actions and tasks +Tools and methods that support
SQA actions +Software configuration management, procedures +Methods for assembling, safeguarding, and
maintaining all SQA-related records +Organizational roles and responsibilities relative to product quality Testing
goals +Demonstrate to the developer and the customer that the software meets its requirements +Discover
situations in which the behavior of the software is incorrect, undesirable, or does not conform to
itsspecification Stages of testing +Development Testing +Release Testing +User Testing +Acceptance Testing
software testing options +Unit Testing +Incremental Integration Testing +Integration Testing +Functional
Testing +System Testing SOFTWARE TESTING TYPES +End-to-end Testing +Sanity Testing +Regression Testing
+Acceptance Testing +Load Testing +Performance Testing +Usability Testing +Install-Uninstall Testing
+Recovery Testing +Security Testing +Compatibility Testing +Comparison Testing +Maintenance Testing
+Globalization Testing +Interoperability Testing +Exploratory Testing +Confirmation Testing +Smoke Testing
+Alpha Testing +Beta Testing Software testing criteria +Intuition +Specification +Code +Faults Kinds of test plan
+Test Suite +Test Cases
Activities in software configuration management +Change Management +Version Management +System
Building +Release Management Elements of a software configuration management system +Component
Elements +Process Elements +Construction Elements +Human Elements What is software configuration
management process? Defines a series of tasks that have four primary objectives: +Identify all items that
collectively define the software configuration +Manage changes to one or more items +Facilitate the
construction of different versions of an application +Ensure that software quality is maintained as the
configuration evolves over time Questions involve in scm process +How does a software team identify the
discrete elements of a software configuration? +How does an organization manage the existing versions of a
program that will enable change? +How does an organization control changes before and after software
released to a customer? +How does an organization assess the impact of change and manage the impact
effectively?
What is change request form? +A form where clients or customers input bug report, the symptoms of the bug
are described, or a request for additional functionality to be added to the system +Record information that is
shared between all groups involved in change management+Include a section where a developer outlines how
the change may be implemented Factors for implementing change management +The consequences of not
making the change +The benefits of the change +The number of users affected by the change +The costs of
making the change +The product release cycle Version management systems +Version and Release
Identification +Storage Management System building platforms +Development System +Build Server +Target
Environment What is release management? +Version of a software system that is distributed to customers +A
system released must be documented to ensure that it can be re-created exactly in the future +Record the
specific versions of the source code components that were used to create the executable code Types of release
management +Major Release +Minor Release
Changes during software maintenance +Correct coding errors +Extensive changes to correct design errors
+Significant enhancements to correct specification errors +Accommodate new requirements Types of software
maintenance +Fault Repairs +Environmental Adaptation +Functionality Addition +Types of Software
Maintenance Distribution +Corrective Maintenance +Adaptive Maintenance +Perfective Maintenance
+Preventive Maintenance + Higher Quality +Anticipating Changes +Better Tuning to User Needs +Less Code
Laws about software evolution +Continuing Change +Increasing Complexity +Conversation of Familiarity
+Continuing Growth +Declining Quality +Feedback System +Large Program Evolution+ Organizational Stability
Software evolution approaches +Software Maintenance + Architectural Transformation what is software
maintenance prediction? +Estimates the overall maintenance costs for a system in a given time period +Expects
the number of change requests for a system +Understands the relationship between the system and its external
environment Software maintenance prediction relationships +The number of complexity of system interfaces
+The number of inherently volatile system requirements +The business processes in which the system is use
Metrics for assessing maintainability +Number of requests for corrective maintenance +Average time required
for impact analysis +Average time taken to implement a change request +Number of outstanding change
request What is change request? +Request for system changes from users, customers, and management +All
requests should be carefully analyzed as part of the maintenance process and then implemented Software
maintenance coding activities +Isolation +Modification +Testing Problematic factors in managing software
maintenance +Changing priorities +Inadequate testing methods +Performance measurement difficulties
+Incomplete or non-existent system documentation +Rapidly changing business environment Software
maintenance cost factors +Team Stability +Contractual Responsibility +Staff Skills +Program Age and Structure
What is Software maintenance side effect? +An error or undesirable behavior that occurs as the result of
modification Software maintenance side effects +Code +Data Structure +Documentation
quality control tasks +Effective software engineering practice +Control of all software work products and the
changes made +A procedure to ensure compliance with software development standards +Measurement and
reporting mechanisms Elements of software quality assurance +Standards +Reviews and Audits +Testing
+Error/Defect Collection and Analysis +Change Management +Education +Vendor Management +Security
Management +Safety +Risk Management Sqa tasks +Prepares an SQA plan for a project +Participates in the
development of the project’s software process description +Reviews software engineering activities to verify
compliance with the defined software process +Audits designated software work products to verify compliance
with those defined as part of the software process +Ensures that deviations in software work and work products
are documented and handled according to a documented procedure +Records any noncompliance and reports
to senior management Sqa goals+Requirements Quality +Design Quality +Code Quality +Quality Control
Effectiveness Sqa reviews +Check the quality of the project deliverables +Involves examining the software,
documentation and records of the process to discover errors and omissions Sqa plans +Provides a road map
for instituting software quality assurance +Developed by SQA group to serve as a template for SQA activities
that are instituted for each software project SQA structure identifies the following: +The purpose and scope of
the plans +Description of all software engineering work products for SQA +All applicable standards and
practices that are applied during software process +SQA actions and tasks +Tools and methods that support
SQA actions +Software configuration management, procedures +Methods for assembling, safeguarding, and
maintaining all SQA-related records +Organizational roles and responsibilities relative to product quality Testing
goals +Demonstrate to the developer and the customer that the software meets its requirements +Discover
situations in which the behavior of the software is incorrect, undesirable, or does not conform to
itsspecification Stages of testing +Development Testing +Release Testing +User Testing +Acceptance Testing
software testing options +Unit Testing +Incremental Integration Testing +Integration Testing +Functional
Testing +System Testing SOFTWARE TESTING TYPES +End-to-end Testing +Sanity Testing +Regression Testing
+Acceptance Testing +Load Testing +Performance Testing +Usability Testing +Install-Uninstall Testing
+Recovery Testing +Security Testing +Compatibility Testing +Comparison Testing +Maintenance Testing
+Globalization Testing +Interoperability Testing +Exploratory Testing +Confirmation Testing +Smoke Testing
+Alpha Testing +Beta Testing Software testing criteria +Intuition +Specification +Code +Faults Kinds of test plan
+Test Suite +Test Cases
Activities in software configuration management +Change Management +Version Management +System
Building +Release Management Elements of a software configuration management system +Component
Elements +Process Elements +Construction Elements +Human Elements What is software configuration
management process? Defines a series of tasks that have four primary objectives: +Identify all items that
collectively define the software configuration +Manage changes to one or more items +Facilitate the
construction of different versions of an application +Ensure that software quality is maintained as the
configuration evolves over time Questions involve in scm process +How does a software team identify the
discrete elements of a software configuration? +How does an organization manage the existing versions of a
program that will enable change? +How does an organization control changes before and after software
released to a customer? +How does an organization assess the impact of change and manage the impact
effectively?
What is change request form? +A form where clients or customers input bug report, the symptoms of the bug
are described, or a request for additional functionality to be added to the system +Record information that is
shared between all groups involved in change management+Include a section where a developer outlines how
the change may be implemented Factors for implementing change management +The consequences of not
making the change +The benefits of the change +The number of users affected by the change +The costs of
making the change +The product release cycle Version management systems +Version and Release
Identification +Storage Management System building platforms +Development System +Build Server +Target
Environment What is release management? +Version of a software system that is distributed to customers +A
system released must be documented to ensure that it can be re-created exactly in the future +Record the
specific versions of the source code components that were used to create the executable code Types of release
management +Major Release +Minor Release
Changes during software maintenance +Correct coding errors +Extensive changes to correct design errors
+Significant enhancements to correct specification errors +Accommodate new requirements Types of software
maintenance +Fault Repairs +Environmental Adaptation +Functionality Addition +Types of Software
Maintenance Distribution +Corrective Maintenance +Adaptive Maintenance +Perfective Maintenance
+Preventive Maintenance + Higher Quality +Anticipating Changes +Better Tuning to User Needs +Less Code
Laws about software evolution +Continuing Change +Increasing Complexity +Conversation of Familiarity
+Continuing Growth +Declining Quality +Feedback System +Large Program Evolution+ Organizational Stability
Software evolution approaches +Software Maintenance + Architectural Transformation what is software
maintenance prediction? +Estimates the overall maintenance costs for a system in a given time period +Expects
the number of change requests for a system +Understands the relationship between the system and its external
environment Software maintenance prediction relationships +The number of complexity of system interfaces
+The number of inherently volatile system requirements +The business processes in which the system is use
Metrics for assessing maintainability +Number of requests for corrective maintenance +Average time required
for impact analysis +Average time taken to implement a change request +Number of outstanding change
request What is change request? +Request for system changes from users, customers, and management +All
requests should be carefully analyzed as part of the maintenance process and then implemented Software
maintenance coding activities +Isolation +Modification +Testing Problematic factors in managing software
maintenance +Changing priorities +Inadequate testing methods +Performance measurement difficulties
+Incomplete or non-existent system documentation +Rapidly changing business environment Software
maintenance cost factors +Team Stability +Contractual Responsibility +Staff Skills +Program Age and Structure
What is Software maintenance side effect? +An error or undesirable behavior that occurs as the result of
modification Software maintenance side effects +Code +Data Structure +Documentation