DAU ISA 101 Module 7 Test

DAU ISA 101 Module 7 Test IT/Software Quality Management Exam Here is your test result.The dots represent the choices you have made. The highlighted questions are the questions you have missed. Remediation Accessed shows whether you accessed those links.'N' represents links not visited and 'Y' represents visited links. Back to Status page contains 7 Questions 1) What is the purpose of Software Quality Assurance? (Select all that apply.) [24.101.1.1 Define the purpose of Software Quality Assurance (SQA)] Reviews and audits the software products and activities to verify that they comply with the applicable procedures and standards. Identifies software product lines that are not meeting the organization's mission and objectives, and establishes procedures to retire these systems. Provides management with appropriate visibility into the process being used by the software project and of the products being built.  Provides confidence that quality requirements will be fulfilled. Establishes intra-organizational connections to ensure open lines of communication across the enterprise. 2) Which SQA task involves the software designer gathering information using methods such as interviews and FAST? [24.101.1.2 Identify the components (activities and events) of an effective Software Quality Assurance (SQA) program.] Applying software engineering techniques Controlling change Performing SQA audits Keeping records and audits 3) Problems in the DESIGN phase of software development include: Errors, Failures and . [24.101.1.3 Identify examples of common defects injected into a software development during the various phases of lifecycle development.] Defects Bugs Issues Breaks 4) Which of the following is NOT considered to be a software quality "ility"? [24.101.1.4 Identify software quality factors.] Wearability: the ability of the system to perform without degradation in a classified information operations environment. Flexibility: ease of effort required to modify an operational program. Verifiability: the relative effort to verify the specified software operation and performance. Correctness: the extent to which a program satisfies its specifications and fulfills the user's mission objectives. 5) In determining which software quality factors to select, what is a key consideration? [24.101.1.17 Recognize the influences for choosing specific software quality factors.] Factors and attributes that are relevant to a project. University in all situations. Priority for contract review. Funding execution. 6) The formula for calculation of Defect (Error) Density is: [24.101.1.5 Identify common measures used to track product and process quality in software development efforts.] Divide the number of defects (errors) found by testing by software size. Divide the defect (error) rate recorded during beta by existing lines of code. Divide the software size by the number of defects (errors) found during testing. Divide the lines of code by the number of defects (errors) found in execution. 7) Match the product attributes of the Kano model to the attribute's customer characteristics. [24.101.1.16 Given a list of quality factors and their descriptions, match the factor with its description (ISO 9126 vs Kano Model).] a) Performance / Linear b) Threshold / Basic c) Exciters / Delighters The customer's satisfaction is directly related to the attribute. Therefore, higher quality means more satisfaction and lower quality means less satisfaction. Customers assume that these attributes will be present. If they are not present (or of low quality), customers will be dissatisfied. However, if the attributes are present, the customer's satisfaction will not increase. Customers don't expect these attributes, but if they are present customer satisfaction increases. On the other hand, if the attributes are missing, customers are not more dissatisfied.