Under Module 06, Example-2 (Register new patient), what is the 'Alternative Path' if the actor decides not to complete the patient registration?
A.The system automatically deletes all temporary cache logs and locks the database.
B.If the actor doesn't want to register the patient, he will press the 'Cancel Registration' button and the system redirects the actor to its home page.
C.The system prompts the receptionist to answer three mandatory security questions.
D.The system redirects the user to the social media login configuration panel.
According to Module 06 of the course handouts, how are functional requirements defined, and what role do they play in software development?
A.They define what the system should do and how it should behave under certain situations, describing the core functionality of the application and driving the application architecture.
B.They specify organization-wide compliance processes, such as CMMI maturity levels and process benchmarking metrics.
C.They outline project management budgets and schedule guidelines like CPI and SPI calculations.
D.They describe only the graphical user interface elements such as color schemes, fonts, and layout alignment rules.
In the 'Example of Verifiable' in Module 06, why is the requirement 'Loading time of the website should be as minimum as possible' problematic, and what suggestion is provided to resolve it?
A.It is problematic because loading times are SCM configuration issues; the suggestion is to remove performance bounds from the SRS.
B.It is problematic because 'minimum' is not quantitatively defined, making SQA testing impossible and creating team conflicts; the suggestion is to specify a numeric value like 'at most 200 milliseconds'.
C.It is problematic because it does not use the word 'shall'; the suggestion is to rewrite it as 'The website shall load instantly'.
D.It is problematic because clients cannot measure website speeds; the suggestion is to let developers estimate speed guidelines during coding.
Under CMMI and modern SQA best practices outlined in Module 06, what is the primary benefit of involving the QA team in the initial stages of a project?
A.It allows QA to assume the role of the technical writer and write the product release notes independently.
B.It ensures QA is fully aware of what is being built and how it is being built, enabling them to prepare quality assurance activities in a planned and organized way.
C.It eliminates the need for developers to write unit tests or execute code reviews before sanity testing.
D.It allows the PM to bypass client approval gates and baseline requirements automatically.
According to the SQA guidelines in Module 06, what critical action must be performed before development begins in order to prevent costly rework?
A.The development team must complete unit testing of all database schemas.
B.Requirements should be validated and approved by QA and all stakeholders before development.
C.The sales team must negotiate an open-budget contract extension with the client.
D.An independent auditor must conduct a third-party CMMI Maturity Level 3 appraisal.
According to Module 06 of the course handouts, why does modern software quality engineering mandate that QA resources must review software requirements before they are finalized?
A.To allow the SCM team to lock the database schema and automate developer code branches.
B.To ensure requirements are unambiguous, write test cases against all use cases, and act as a major stakeholder in the requirement finalization stage.
C.To calculate financial metrics such as Cost Performance Index (CPI) and Schedule Performance Index (SPI) for the Sales team.
D.To completely replace white box and statement-level testing during the code implementation phase.
Which of the following guidelines represents the recommended best practice for writing a 'Correct' software requirement according to Module 06?
A.It should be written in a single line, must not exceed 30 to 50 words, and must avoid open-ended or subjective terms.
B.It should be highly comprehensive, spanning multiple pages, and include nested pseudo-code blocks.
C.It should use flexible, open-ended terms like 'etc.' and 'assumed' to allow developers maximum design freedom.
D.It must be written exclusively by the customer support team without any SQA review or developer input.
According to Chapter 6 of the CS611 handouts, what are the specific project dimensions that are negatively affected if the requirements phase is neglected?
A.Only the database indexing speeds and the physical network routing tables.
B.Only SCM repository commit access rights and developer compiler versions.
C.Quality, cost/budget, deliverables, meeting customer requirements, and revenue.
D.Client introductory Skype meetings and internal sales team commission rates.
According to Module 06 of the course handouts, what defines a 'Feasible' software requirement under CMMI standards, and what is the recommended best practice to verify it?
A.It can be compiled using object-oriented libraries without warnings; the best practice is to involve the software configuration management team.
B.It is possible to implement or satisfy it within the project's scope, budget, and physical limitations; the best practice is to involve and engage developer(s) for technical insights.
C.It requires zero bugs in production; the best practice is to have the marketing team approve the specification.
D.It is written in a single line of exactly 30 to 50 words; the best practice is to involve the client support team exclusively.
According to Module 06 of the course handouts, what critical information must be contained within a software 'Release Note' document distributed as part of the final build?
A.Source code-level variable naming dictionaries, logical compiler logs, and database password schemas.
B.Information about the scope of the software product, performance benchmarks, features added/delivered, and the known issues that the customer might face.
C.EVM statistics including the planned value, actual value, earned value, SPI, and CPI metrics of each phase.
D.A copy of the signed client contract, project team salary breakdowns, and daily scrum meeting schedules.
