CSIS 471 Final Exam Liberty University 2025

• 80-20 Rule - Correct Ans-20% development 80% maintenance • Adaptive Maintenance - Correct Ans-changing a software product to port it to new environments (or adjust for revised hardware / peripherals) - 25% of maintenance • Alpha Test - Correct Ans-In-house testing • Beta Test - Correct Ans-Customer pilot test • Bottom-up Integration - Correct Ans-Start at the bottom modules, and then evaluate higher up modules that the sub modules are a part of. • Checklists - Correct Ans-Inspections are driven by checklists, which contains specific detailed questions about the work product that each inspector must answer. • Consumer Reuse - Correct Ans-Re-use components initially developed for other projects • Corrective Maintenance - Correct Ans-Corrective: changing a software product to remove errors (what you normally think of) - 21% of maintenance • Design by Contract - Correct Ans-a particular design documentation approach that uses the documentation not only to capture the design but encourage interaction among developers. Every component has a document. • Environmental Tests - Correct Ans-Test on how the product handles heat, motion, and other environmental changes. (TEMPEST) • Failure - Correct Ans-An observable departure from required behavior. • Fault - Correct Ans-The result of human error • Fault identification - Correct Ans-Process of identifying what fault caused the failure • Fault correction - Correct Ans-Process of making changes to the system so that faults are removed • Frameworks - Correct Ans-A reusable design (models and/or code) that can be refined (specialized) and extended to provide some portion of the overall functionality of many applications • Human Factors Test - Correct Ans-Test how usable the product is to a human. • Impact analysis - Correct Ans-Identification of all systems and software products that change request affects and development of an estimate of the resources needed to accomplish the change • Inspection - Correct Ans-A visual examination of a software product to detect and identify software anomalies, including errors and deviations from standards and specifications. • Maintainability - Correct Ans-The ease with which a software system or component can be modified to change or add capabilities, correct faults or defects, improve performance or other attributes, or adapt to a changed environment • Maintenance tests - Correct Ans-Test on diagnostic tools and procedures • Parallel testing - Correct Ans-Test to see if new system operates in parallel with the old system • Perfective maintenance - Correct Ans-changing a software product to better meet the needs and desires of customers and maintainers - 50% of maintenance • Preventive maintenance - Correct Ans-changing a software product to enhance maintainability - 4% of maintenance • Producer reuse - Correct Ans-Create components designed to be reused in future applications • Pseudocode - Correct Ans-Not the initial specifics of a command, Less writing to make pseudocode easier to rearrange • Recovery Test - Correct Ans-Test the loss of resources • Re-documentation - Correct Ans-Static analysis of source code to produce system documentation • Re-engineering - Correct Ans-The examination and alteration of software to reconstitute it in a new form, including the subsequent implementation of the new form • Refactoring - Correct Ans-The disciplined technique for restructuring an existing body of code, altering its internal structure without changing its external behavior. • Reliability - Correct Ans-The ability of a system or component to perform its required functions under stated conditions for a specified period of time. • Review - Correct Ans-A critical examination or evaluation of a work product or process by qualified individuals or teams. • Reverse Engineering - Correct Ans-A software engineering approach that derives a system's design or requirements from its code. • Synchronization - Correct Ans-To pull the changes made in a parent branch into its (evolving) child (for example, feature) branch • Software capability evaluation - Correct Ans-a formal way to determine an organization's software process maturity framework and generally measure its software development competence