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.15. PA: Example of Software ValidationMediumโญ๐ก๐๐VU๐๏ธVU
In Module 04, Section N of the course handouts, which of the following is NOT listed under the three sample requirements used to illustrate an 'Example of Software Validation'?
A.Admin (Employee) should be able to login
B.Employee should be able to register another employee in the organization
C.Employee should be able to mark the attendance on daily basis
D.System must run high-performance stress and load testing with 500 concurrent connections
Q162
โ MCQ๐ CS611๐ Lec 4๐ท๏ธ 04.25. Process ReviewsEasyโญ๐ก๐๐VU๐๏ธVU
According to Module 04, Section X of the course handouts, why are 'Process Reviews' frequently carried out in software organizations?
A.To evaluate the graphical user interface elements of off-the-shelf plugins.
B.To measure the effectiveness of the process and to ensure that it is being completely followed.
D.To update the project budget when the cost performance index (CPI) falls below 1.0.
Q163
โ MCQ๐ CS611๐ Lec 4๐ท๏ธ 04.18. Engineering Process Group (EPG)Mediumโญ๐ก๐๐VU๐๏ธVU
According to Module 04, Section Q of the course handouts, what is the primary role and responsibility of the Engineering Process Group (EPG)?
A.To write unit tests for the development team and maintain branch code repositories.
B.To serve as the organization's focal point for implementing software processes to ensure compliance with quality standards, and act as an oversight committee.
C.To manage customer billing contracts and invoice releases in coordination with the finance department.
D.To execute database disaster recovery plans during live runtime failures.
According to Module 04, Section Y of the course handouts, why is a software process considered 'useless without review'?
A.Because without reviews, the Software Configuration Management (SCM) team cannot compile binary shipments or generate release notes.
B.Because no environment is static and no requirements are static; reviews ensure the process adapts to dynamic changes.
C.Because reviews are the only phase where the customer is allowed to request new paid features or wishlist items.
D.Because the Engineering Process Group (EPG) requires review metrics to calculate the weekly cost performance index (CPI).
Q166
โ MCQ๐ CS611๐ Lec 4๐ท๏ธ 04.27. Bench Marking of Process ReviewsEasyโญ๐ก๐๐VU๐๏ธVU
According to Module 04, Section Z of the course handouts, what is the primary benefit to an organization of adopting an already developed benchmarked solution from another organization or literature?
A.It completely eliminates the need for software quality assurance and testing.
B.It saves the organization a lot of time and effort after making some amendments.
C.It automatically upgrades the organization to CMMI Maturity Level 5 without appraisals.
D.It guarantees that the client will never request change orders during SDLC.
According to Module 04, Section E of the course handouts, what five specific practices must be followed to satisfy the 'Manage Requirements' goal of the Requirement Management (REQM) process area?
A.Understanding Requirement, Obtain Commitment to Requirements, Manage Requirements Changes, Maintain Bidirectional Traceability of Requirements, and Identify Inconsistencies.
How does CMMI distinguish the philosophical objective of Software Verification from Software Validation as described in Module 04, Sections M and O of the course handouts?
A.Verification is concerned with 'building the right product' (usefulness), while Validation is concerned with 'building the product the right way' (inspections).
B.Verification is concerned with 'building the product the right way' (ensuring it is well-engineered and error-free), whereas Validation is concerned with 'building the right thing' (ensuring usefulness when deployed).
C.Verification is entirely a manual peer walkthrough activity, while Validation is purely an automated regression test suite.
D.Verification evaluates the usefulness of the system in the client's active operations environment, while Validation ignores the operating environment.