Based on Module 04, Section A of the course handouts, what are Process Action Teams (PATs), and how is their team composition structured?
A.PATs are individual teams created to address specific process improvements, and they consist of technical staff from throughout the organization.
B.PATs are external, independent auditing committees made up entirely of certified lead auditors and domain experts.
C.PATs are dedicated customer support groups responsible for monitoring Level 1 and Level 2 post-deployment support requests.
D.PATs are executive project boards responsible for tracking earned value metrics such as SPI and CPI.
Under the CMMI Requirement Management (REQM) process area, what is the primary objective of the 'Understanding Requirement' practice, and with whom is this understanding developed?
A.To develop an understanding with the software configuration managers on the compiler flags and automated deployment scripts used in the project.
B.To develop an understanding with the requirements providers on the meaning of the requirements.
C.To negotiate the final sales budget and contract terms with the client's executive financial officers.
D.To train the testing team on executing stress and security checklists using third-party automated tools.
Based on the Technical Solutions guidelines in Module 04, Section I of the course handouts, which of the following is true regarding design-requirement alignment and the usage of wireframes?
A.Designs should be developed independently of the requirements document to maximize programmer creativity.
B.The selected solution should produce the required output (requirement), and wireframes are considered, though partially, to visualize the technical design.
C.Wireframes are fully executable software prototypes that completely eliminate the need for writing unit test cases.
D.Technical designs are drafted by the customer and must not undergo any form of peer review or SQA audit.
According to the CMMI standards in Module 04, Section O of the course handouts, what are the two major goals established for the Software Verification process area?
A.Select Product Component Solutions and Develop the Design.
B.Prepare for Verification and Verify Selected Work Products.
C.Prepare for Product Integration and Ensure Interface Compatibility.
D.Prepare for Validation and Validate Product or Product Components.
According to Module 04, Section S of the course handouts, why do audits become particularly important in volatile working environments?
A.Because they automatically freeze all software changes and block customer requirements.
B.Because they keep a check and balance on organizational processes and practices, providing a starting point for process improvement and valuable insights into conformance.
C.Because they allow the development team to completely bypass configuration management and unit testing.
D.Because they increase the project's Schedule Performance Index (SPI) by eliminating peer reviews.
In the context of CMMI and the Example of Software Verification on Page 31, what are the three specific sample requirements that the QA team must verify are working properly in the software shipment?
A.1. Database backup. 2. UI colors. 3. System performance.
B.1. Admin (Employee) login. 2. Employee registration. 3. Daily attendance marking.
C.1. SCM branching. 2. EPG process definition. 3. PAT template design.
D.1. Budget estimation. 2. Timeline calculation. 3. SPI/CPI scheduling.
According to Module 04 of the course handouts, which of the following lists the six engineering-specific process areas that are covered in this course?
A.Requirement Management Process Area, Requirement Development Process Area, Technical Solution Process Area, Product Integration Process Area, Software Validation Process Area, Software Verification Process Area.
B.Project Planning, Project Monitoring and Control, Risk Management, Supplier Agreement Management, Configuration Management, Software Quality Assurance.
C.Quantitative Process Management, Organizational Innovation and Deployment, Process Action Teams, Engineering Process Group, Audits, Appraisals.
D.Defect Prevention, Defect Reduction, Defect Containment, Inspection, Software Testing, Hot Fixes.
Based on Module 04, Sections C and D of the course handouts, why must a Process Action Team (PAT) care about different stakeholders when working on process improvements?
A.Because stakeholders possess the master decryption keys for testing repositories.
B.Because for improvement initiatives, PAT needs to take care of different stakeholders for different process areas to ensure alignment and consistency.
C.Because stakeholders are responsible for conducting first-party internal code reviews independently of the EPG.
D.Because stakeholders determine the exact quantitative boundaries and variation targets under Maturity Level 4.
According to Module 04, Section K of the course handouts, what represents a major failure and a significant risk in the Product Integration process area?
A.The customer failing to approve the SRS document during the initial project kickoff meeting.
B.Components failing to integrate with each other or only partially integrating, resulting in defects due to misaligned interfaces; and a heterogeneous development environment.
C.A lack of regression testing during the initial unit and statement coverage evaluation phases.
D.Using symbolic constants instead of magic numbers in the source code files.
Based on Module 04, Section M of the course handouts, what is the key conceptual objective of Software Validation, and what is its relationship with code execution?
A.To run structural path and branch debugging coverage; code compilation and execution is mandatory.
B.To capture client requirements correctly and meet them (building the right thing); no code is required for software validation itself.
C.To automate the continuous integration and deployment pipelines; shell script execution is required.
D.To execute stress and load testing on multi-tier servers; quantitative load script execution is required.
