Software Testing and Quality Assurance Fundamentals

Testers and the testing process require comprehensive access to all system resources: the database for test data and verification, host systems where the application runs, and input/output data files needed for testing. All these permissions are necessary for thorough test execution.

Setting initial and end conditions establishes a clear starting state and expected completion state for the test. This allows the same test to be executed multiple times with predictable behavior. Without defined conditions, tests may produce inconsistent results across iterations.

In QuickTest Professional, the option to display Test Results after each run is configured under Tools -> Options -> Run. This menu path controls test execution settings. The other options listed are not valid menu paths in QTP.

QuickTest Professional offers three modes for saving screenshots: 'Always' saves every capture, 'For errors' saves only when errors occur, and 'On errors and warnings' includes both error and warning states. All three are valid configuration options depending on your testing needs and storage considerations.

QuickTest Professional organizes test objects into classes based on their type and behavior (e.g., Window, WebEdit, Button). This object-oriented classification allows QTP to identify and interact with similar objects consistently across different applications. The class hierarchy is fundamental to QTP's object recognition model.

In QuickTest Professional, the identifying characteristics of an object are called properties. These include attributes like name, class, value, and various other properties that help QTP uniquely identify and interact with the object during test execution. Properties distinguish one object from another in the application.

To solve this question, the user needs to have knowledge of software development and quality management concepts. The user must identify the application of process management and quality improvement concepts to software development and maintenance.

Option A: QS14000 is not a recognized standard in software development. It is a quality management system standard for the automotive industry.

Option B: ISO 9000 is a family of quality management standards that provide guidance and tools for organizations to ensure that their products and services consistently meet customer requirements and that quality is consistently improved. However, it is not specifically focused on software development.

Option C: The Malcolm Baldrige National Quality Award is a US award for performance excellence and quality achievement, but it is not specifically focused on software development.

Option D: The Software Engineering Institute's Capability Maturity Model Integration (SEI/CMMI) is a process improvement framework that provides organizations with the essential elements of effective processes. It is specifically focused on software development and maintenance.

Therefore, the correct answer is:

The Answer is: D) SEI/CMM.

To solve this question, the user needs to know about software development and quality assurance concepts.

The process described in the question is known as Risk Management. Risk management is the process of identifying, assessing, and prioritizing risks that can affect a project or organization. In the case of software development, risk management involves identifying possible software failures or defects and evaluating the likelihood of these failures occurring.

Option A, Contingency Planning, is incorrect. Contingency planning refers to the process of developing a plan of action to respond to unexpected events or situations. While risk management may involve some contingency planning, it is not the same thing.

Option C, Configuration Management, is incorrect. Configuration management is a process that helps organizations manage changes to software, hardware, or other IT assets. While it is an important aspect of software development, it is not the same thing as risk management.

Option D, Process Improvement, is incorrect. Process improvement refers to the ongoing effort to improve the quality and efficiency of software development processes. While it may involve some risk management activities, it is not the same thing.

Therefore, the correct answer is:

The Answer is: B. Risk Management.

By definition, a process or module that consistently experiences a high frequency of defects is classified in software engineering as defect-prone.

Quality is a shared responsibility across the entire development team - developers, testers, product owners, and stakeholders all contribute to quality outcomes. Attributing quality solely to the QA department is an outdated and ineffective mindset. Modern quality practices emphasize quality as everyone's responsibility from requirements through deployment.

Cost of quality models show that the majority of quality costs stem from internal and external failure costs, particularly the cost of rework.

Function points quantify the functionality provided to the user from a business perspective, measuring software size based on user requirements. They do NOT quantify data processing work outputs. Data processing outputs would be measured in terms of throughput, volume, or processing metrics, not function points.

MTBF is a standard reliability metric defined as the expected average time between consecutive failures of a system during operation.

An inspection is a formal, structured type of static review or evaluation technique that relies heavily on visual examination of work products.

The definition provided describes system design or solution design functionality. A fishbone diagram (Ishikawa diagram) is a root cause analysis tool used to identify and visualize the many potential causes of a specific problem or effect. It is NOT the creative part of the design process that defines system functionality. The statement claims it is - this is False.

The statement is overly absolute - while listening is important for a tester analyst, there is no single 'number-one' skill that applies universally. Skills like analytical thinking, technical knowledge, communication, and attention to detail are all critical. The claim that listening is definitively the top skill is false.

Function points are a software size measurement method based on the number and complexity of user-visible functions (inputs, outputs, inquiries, external interfaces, internal files). They do NOT measure lines of code - that would be LOC (Lines of Code) metrics. The two are different measurement approaches.