[2024年10月11日] 最新のCSQE試験の的確なCertified Software Quality EngineerExamのPDF問題
CSQE試験問題を練習するならPassTest顕著なCertified Software Quality EngineerExam試験練習問題集
質問 # 59
Which of the following documents must be under configuration control?
- A. Burn charts
- B. Problem issues
- C. Test procedures
- D. Control chains
正解：C
解説：
Test procedures must be under configuration control to ensure that all testing activities are performed consistently and according to the specified standards. Configuration control involves managing changes systematically so that the integrity and traceability of the testing process are maintained. This helps in ensuring that the tests are repeatable and that any changes in the procedures are documented and approved.
References:
* "Configuration Management Principles and Practice" by Anne Mette Jonassen Hass
* IEEE Standard for Configuration Management in Systems and Software Engineering (IEEE Std
828-2012)
質問 # 60
What type of questions should developers ask customers when discussing requirements at the inception of the project?
- A. multiple-choice
- B. detail-driven
- C. context-free
- D. yes/no
正解：C
解説：
Context-free questions are broad and open-ended, designed to elicit a wide range of information from the customer without leading them towards specific answers.
* Open-Ended: These questions do not presuppose any particular solution or requirement, allowing customers to provide a broad perspective.
* Exploratory: They help in understanding the broader context of the project, the business environment, and the goals of the stakeholders.
* Foundation: Context-free questions lay the groundwork for more detailed and specific discussions later in the requirements gathering process.
Examples of context-free questions might include:
* "What is the main goal of this project?"
* "What are the biggest challenges you are facing?"
質問 # 61
Which of the following aspects of information systems is disaster recovery primarily concerned with protecting?
- A. Integrity
- B. Confidentiality
- C. Authorization
- D. Availability
正解：D
解説：
Disaster recovery is primarily concerned with ensuring that information systems can continue to operate or be quickly restored to operation after a disaster.
* Objective: The main objective of disaster recovery is to ensure that the system remains available, or can be quickly made available, after an interruption or disaster.
* Key Elements: This involves having backups, redundant systems, and recovery plans that can be quickly executed to restore system functionality.
* Focus on Availability: While integrity and confidentiality are also important, the immediate concern of disaster recovery is to ensure that systems are available to users to maintain business continuity.
質問 # 62
Globalization requirements involve
- A. defining problems to be solved or opportunities to be addressed by the software product
- B. looking at the capability of the software product from the perspectives of various stakeholders
- C. defining the required information flow across shared interfaces to external entities
- D. developing software that can be adapted to target markets and customizing software for those markets
正解：D
解説：
Defining Information Flow: More related to system integration and interface requirements.
Problem Definition: Related to initial project scoping and requirements analysis.
Stakeholder Perspectives: Important for gathering requirements but not specific to globalization.
Globalization Requirements: Involves ensuring the software can be adapted for different languages, regions, and cultural contexts. This includes localization (customizing software for specific markets) and internationalization (designing software so it can be easily adapted).
Conclusion: Developing adaptable and customizable software for different target markets is central to globalization requirements. This ensures the product meets the needs of users in various regions, aligning with best practices in global software development.
質問 # 63
Project management has been complaining that code inspections are taking too much time and are not worth the effort. The software manager has to decide whether the inspection program should be continued or disregarded for the upcoming release. Which of the following factors is critical to the manager s decision?
- A. The resources currently available for development
- B. The estimated impact of inspection on the schedule
- C. The cost of additional testing
- D. The cost of not using inspection
正解：D
解説：
The critical factor for the software manager's decision on whether to continue or disregard the inspection program is the cost of not using inspection. Code inspections are a preventive measure to identify defects early in the development process. The cost of not using inspections can include increased defects in the final product, higher costs for post-release fixes, decreased customer satisfaction, and potentially significant impacts on the company's reputation. While resources, schedule impact, and additional testing costs are important considerations, the long-term cost implications of not identifying defects early can be far more detrimental.References:
* Gilb, Tom, and Dorothy Graham. "Software Inspection." Addison-Wesley, 1993.
* IEEE Std 1028-2008, IEEE Standard for Software Reviews and Audits.
質問 # 64
The best way to reduce post-release defect density in future releases is to
- A. provide online help for known defects
- B. evaluate defect arrival rates and analyze defect resolution costs
- C. maintain a responsive helpdesk function to identify recurring problems
- D. categorize defects and perform analyses to uncover their causes
正解：D
解説：
The best way to reduce post-release defect density in future releases is to categorize defects and perform analyses to uncover their causes. By systematically categorizing defects and analyzing their root causes, organizations can identify underlying issues in the development process and implement corrective actions.
This approach helps in preventing similar defects in future releases, leading to improved software quality.
References:
* "Root Cause Analysis: Improving Performance for Bottom-Line Results" by Robert J. Latino and Kenneth C. Latino
* "The Pragmatic Programmer: Your Journey to Mastery" by Andrew Hunt and David Thomas
質問 # 65
Which of the following problem-solving tools is most appropriate for breaking down ideas into progressively greater detail?
- A. Tree diagram
- B. Matrix diagram
- C. Affinity diagram
- D. Relationship diagram
正解：A
解説：
A tree diagram is a tool used to break down broad categories into finer levels of detail. It is particularly useful for:
* Hierarchical Decomposition: Breaking down complex ideas or processes into manageable sub-components.
* Problem Solving: Identifying root causes and exploring solutions systematically.
* Project Planning: Defining tasks and sub-tasks in a structured manner.
The tree diagram starts with a single node and branches out into multiple nodes, each representing a more detailed aspect of the main topic.
References:
* "The Quality Toolbox" by Nancy R. Tague
* "The Memory Jogger II: A Pocket Guide of Tools for Continuous Improvement and Effective Planning" by Michael Brassard and Diane Ritter
質問 # 66
Which of the following cultures would allow an organization's DevOps team to be most effective?
- A. A cross-functional, opaque culture without silos
- B. A cross-functional, transparent culture with silos
- C. An aligned collaborative, transparent culture with silos
- D. An aligned collaborative, transparent culture without silos
正解：D
解説：
An aligned collaborative, transparent culture without silos would allow an organization's DevOps team to be most effective. This type of culture promotes open communication, shared responsibilities, and a unified approach to problem-solving, which are essential for the success of DevOps practices. Eliminating silos ensures that development, operations, and other teams work together seamlessly, fostering a continuous integration and delivery environment.
References:
* "The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win" by Gene Kim, Kevin Behr, and George Spafford
* "Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations" by Nicole Forsgren, Jez Humble, and Gene Kim
質問 # 67
Which of the following information is considered part of the software baseline?
- A. Software metrics and summarized data
- B. Test plan and test cases
- C. User survey and their results
- D. Test logs
正解：B
解説：
A software baseline is a set of documents or files that serve as a reference point for further development.
* Definition: A baseline is a formally reviewed and agreed-upon set of items that serve as a basis for further development and can only be changed through formal change control procedures.
* Components: The test plan and test cases are part of the software baseline because they are essential for verifying and validating the software against its requirements.
* Importance: Including test plans and test cases in the baseline ensures that there is a clear, documented set of criteria and procedures for evaluating the software's performance and compliance with requirements.
質問 # 68
Which of the following software metrics is based on a nominal scale-1
- A. Root cause of defect, logic error data definition, etc
- B. Severing of a defect, critical, major, minor, etc.
- C. Defect density: number per function point, etc.
- D. Defect discovery rate: number detected per day, etc.
正解：A
解説：
Nominal scales are used in measurement to categorize data without any order or priority. They are the simplest form of measurement scale and are used to group items into distinct categories based on names or labels123.
* Root cause of defect (Option A): This fits the nominal scale as it involves categorizing defects based on their root causes, such as logic errors or data definitions. These categories are mutually exclusive and do not have a natural order1.
* Severity of a defect (Option B): This is an example of an ordinal scale, not a nominal scale. The severity levels (critical, major, minor) imply a ranking or order of importance or impact2.
* Defect density (Option C): This metric uses a ratio scale as it involves a quantitative measure (number of defects) relative to the size of the software (function points), which has a true zero point and allows for meaningful comparisons between measurements2.
* Defect discovery rate (Option D): This is also a ratio scale because it measures the rate of defect detection over time (number detected per day), which is a quantitative assessment that allows for arithmetic operations
質問 # 69
Which of the following sources of information would be most appropriate for a company to use to measure and monitor customer satisfaction?
- A. Market analysis reports that incorporate customer preferences when comparing the features of the company's products with those of its key competitors
- B. Comprehensive surveys covering all aspects of the customer experience
- C. Feedback from customers regarding reliability data, especially concerning increases in the mean time to failure in the company's products
- D. Software quality's attributes that have been classified as "critical" by key customers
正解：B
解説：
Comprehensive surveys covering all aspects of the customer experience are the most appropriate source of information for a company to use to measure and monitor customer satisfaction. These surveys provide a holistic view of the customer's interactions with the product and service, covering various dimensions such as product quality, usability, support, and overall satisfaction. By gathering detailed feedback across these areas, companies can identify strengths and areas for improvement, ensuring that customer satisfaction is accurately measured and monitored.References:
* Hill, Nigel, Roche, Greg, and Allen, Rachel."Customer Satisfaction: The Customer Experience Through the Customer's Eyes." Cogent Publishing, 2007.
* ISO 10004:2012, Quality management - Customer satisfaction - Guidelines for monitoring and measuring.
質問 # 70
Under which of the following major Cost of Quality categories would testing a software upgrade be classified?
- A. External failure
- B. Internal failure
- C. Appraisal
- D. Prevention
正解：C
解説：
Testing a software upgrade is classified under the appraisal category of the Cost of Quality. Appraisal costs are associated with evaluating and measuring the quality of products through testing and inspection to ensure they meet quality standards and specifications.
質問 # 71
An environmental monitoring software system is required to measure ambient temperature and sound an alarm if the temperature drops below 19 3C or rises above 21 °C. Which of the following observed test results would be an error for this system?
- A. Temperature Display: Cannot measure Alarm Status: Silent
- B. Temperature Display: 20 CC Alarm Status. Silent
- C. Temperature Display: 21 °C Alarm Status Silent
- D. Temperature Display: 15 °C Alarm Status Ringing
正解：C
解説：
The system is designed to sound an alarm if the temperature is below 19°C or above 21°C. Therefore, if the temperature display shows 21°C, the alarm should be ringing. Since option D indicates that the alarm is silent when the temperature is 21°C, this behavior contradicts thespecified requirements, indicating an error.
質問 # 72
Which of the following baselines is typically established after completion and approval of system requirements?
- A. Allocated
- B. Functional
- C. Product
- D. Development
正解：B
解説：
The functional baseline is typically established after the completion and approval of system requirements. This baseline includes the functional requirements and specifications that describe what the system is supposed to do. It serves as a reference point for further development and testing, ensuring that all subsequent work aligns with the agreed-upon functional requirements.
質問 # 73
Under design control, the design phase should proceed until
- A. the allocated time for system design has been reached
- B. every possible design variation has been explored
- C. system elements of the smallest structure are defined and specified
- D. the developers understand the level of work expected
正解：C
解説：
In the design control phase of software development, it is critical to ensure that the design phase proceeds until system elements of the smallest structure are defined and specified. This ensures that all components of the system are thoroughly planned and documented, which helps in minimizing errors and misunderstandings later in the development process. Detailed design specifications provide a clear roadmap for developers and facilitate better quality control and testing.
References:
* "Software Engineering: A Practitioner's Approach" by Roger S. Pressman
* IEEE Standard 1016-2009 for Information Technology-Systems Design
質問 # 74
Which of the following capabilities of a configuration management system is involved with constructing a specific build of the software?
- A. Release notes
- B. Issue tracking
- C. Project repository
- D. Version management
正解：D
解説：
Version management, also known as version control, is a capability of a configuration management system that deals with tracking and managing changes to software code. It involves creating and maintaining different versions of the software as it is developed and updated. Constructing a specific build of the software relies on selecting the correct versions of the code and other artifacts that are part of that build. Version management ensures that all the changes are properly recorded, and the appropriate versions can be retrieved for constructing specific builds. This capability is essential for reproducibility and consistency in the software development process.References:
* Sommerville, Ian. "Software Engineering." 10th Edition, Addison-Wesley, 2015.
* IEEE Std 828-2012, IEEE Standard for Configuration Management in Systems and Software Engineering.
質問 # 75
Which of the following is an example of a poorly defined project milestone?
- A. Program documentation approved
- B. Program specification completed
- C. Test plan approved by customer
- D. Coding 50% completed
正解：D
解説：
A milestone like "Coding 50% completed" is poorly defined because it is ambiguous and difficult to measure precisely. Here's a detailed explanation:
* Ambiguity: It is unclear what 50% completion means - is it 50% of total lines of code, 50% of modules, or 50% of functionality?
* Measurement Challenges: Determining exact percentages of completion can be subjective and inconsistent.
* Milestone Criteria: Good milestones should be clear, measurable, and verifiable. "Coding completed for module X" is more specific and measurable.
* Project Tracking: Poorly defined milestones can lead to confusion and inaccurate tracking of project progress.
References:
* "Software Project Management" by Bob Hughes, Mike Cotterell, and Rajib Mall.
* "The Art of Project Management" by Scott Berkun.
質問 # 76
Defect prevention should be initiated during the
- A. requirements phase
- B. coding phase
- C. design phase
- D. test phase
正解：A
解説：
Defect prevention should be initiated during the requirements phase. This phase is critical because:
* Early Detection:Identifying and addressing defects early in the requirements phase can prevent downstream defects in design, coding, and testing phases.
* Cost Efficiency:Defects found later in the project lifecycle are more expensive to fix than those found early.
References:
* Software Engineering: A Practitioner's Approach by Roger S. Pressman
* IEEE Standard for Software Reviews and Audits
質問 # 77
In the following control diagram, all paths are feasible and the decisions are not correlated to each other.
How many rests are necessary for branch coverage?
- A. 0
- B. 1
- C. 2
- D. 3
正解：B
解説：
Branch coverage, also known as decision coverage, ensures that every possible branch (i.e., true and false conditions) in the code is executed at least once. To determine the number of tests necessary for branch coverage in the given control flow diagram, we must count the distinct branches resulting from each decision point.
* Decision 1: 2 branches (true and false)
* Decision 2: 2 branches (true and false)
* Decision 3: 2 branches (true and false)
Since each decision has two branches and they are independent of each other, the number of distinct paths that need to be tested is: 2(Decision1)+2(Decision2)+2(Decision3)=6 branches2 (Decision 1) + 2 (Decision 2) + 2 (Decision 3) = 6 \text{ branches}2(Decision1)+2(Decision2)+2(Decision3)=6 branches However, the number of tests needed to cover all branches is the maximum number of branches any path could take, considering that a single test might cover multiple branches. For the given control diagram, 4 tests will suffice to cover all branches:
* Path: A -> Decision 1 (true) -> B
* Path: A -> Decision 1 (false) -> Decision 2 (true) -> C
* Path: A -> Decision 1 (false) -> Decision 2 (false) -> Decision 3 (true) -> D
* Path: A -> Decision 1 (false) -> Decision 2 (false) -> Decision 3 (false) These four tests ensure all branches are covered at least once.
質問 # 78
......
試験問題と解答はCSQE学習ガイド問題解答：https://www.passtest.jp/ASQ/CSQE-shiken.html
練習用CSQEにはPassTest顕著な問題集はあなたをCertified Software Quality EngineerExam試験合格させます合格させる：https://drive.google.com/open?id=1XZoc1fiPjdMei2TJPEZD0XwI98iCzBYk