Technical study of CMMI engineering process areas, establishing baseline requirements, bidirectional traceability, technical solution design, and continuous product integration workflows.
414 Questions414 MCQs0 Short Questions0 Long Questions
๐ฏ Exam Practice Papers
SEMESTER PASS
CS611 - Software Quality Engineering Examination Practice
Timed practice exam simulation for CS611 - Software Quality Engineering.
๐ VU MID TERM EXAMLectures 1 to 22
โฑ๏ธ 60 Mins
Mid Term Examination
Covers syllabus of Lectures 1 to 22 with 30 high-yield MCQs in a timed exam environment.
โ MCQ๐ CS611๐ Lec 4๐ท๏ธ 04.20. Rationale for AuditsMedium๐ก๐๐VU๐๏ธVU
Audit outcomes can identify specific areas where corrective actions or enhancements are needed. According to the course handouts, which of the following is NOT an area where audits can pinpoint needed improvements?
A.Process design or process implementation.
B.Working conditions or the staff who are required to follow the process.
C.The compiler's execution speed for processing recursive algorithms.
D.The specific resources and training provided to the employees.
Through a formal 'Review Policy', what two critical parameters do organizations explicitly define to govern their quality processes?
A.Who writes the source code and which IDE compiler is utilized.
B.What to review and when to review.
C.How much budget is spent on features and how much is spent on marketing.
D.The number of active users on staging and the SQL server version to deploy.
Q93
โ MCQ๐ CS611๐ Lec 4๐ท๏ธ 04.4. Task List of PATEasy๐โญ๐ก๐๐VU๐๏ธVU
According to Module 04 of the course handouts, what are the primary deliverables that a Process Action Team (PAT) is tasked to generate as part of process improvement initiatives?
A.Process improvement documentation, policies, processes, procedures, charters, and Action Plans.
B.Static compilation logs, automated Unit and Integration tests, and database schema diagrams.
What is the primary difference in focus between Software Validation and Software Verification under CMMI?
A.Validation is focused on building the product the right way (error-free code), whereas Verification is focused on building the right thing (meeting user needs).
B.Validation is focused on building the right thing (satisfying client needs in the intended environment), whereas Verification is concerned with building the product the right way (well-engineered and error-free).
C.Validation requires exhaustive unit testing by developers, while Verification is only conducted via manual client audits.
D.Validation is a one-time event at the start of the project, while Verification is performed incrementally after deployment.