Copyright 2002 by Karl E. Wiegers. Permission to use, modify, and distribute is granted.Impact Analysis Checklist for Requirements ChangesImplications of the Proposed Change Identify any existing requirements in the baseline that conflict with the proposed change. Identify any other pending requirement changes that conflict with the proposed change. What are the consequences of not making the change? What are possible adverse side effects or other risks of making the proposed change? Will the proposed change adversely affect performance requirements or other quality attributes? Will the change affect any system component that affects critical properties such as safety and security, or involve a product change that triggers recertification of any kind? Is the proposed change feasible within known technical constraints and current staff skills? Will the proposed change place unacceptable demands on any computer resources required for the development, test, or operating environments? Must any tools be acquired to implement and test the change? How will the proposed change affect the sequence, dependencies, effort, or duration of any tasks currently in the project plan? Will prototyping or other user input be required to verify the proposed change? How much effort that has already been invested in the project will be lost if this change is accepted? Will the proposed change cause an increase in product unit cost, such as by increasing third-party product licensing fees? Will the change affect any marketing, manufacturing, training, or customer support plans?System Elements Affected by the Proposed Change Identify any user interface changes, additions, or deletions required. Identify any changes, additions, or deletions required in reports, databases, or data files. Identify the design components that must be created, modified, or deleted. Identify hardware components that must be added, altered, or deleted. Identify the source code files that must be created, modified, or deleted. Identify any changes required in build files. Identify existing unit, integration, system, and acceptance test cases that must be modified or deleted. Estimate the number of new unit, integration, system, and acceptance test cases that will be required. Identify any help screens, user manuals, training materials, or other documentation that must be created or modified. Identify any other systems, applications, libraries, or hardware components affected by the change. Identify any third party software that must be purchased. Identify any impact the proposed change will have on the projects software project management plan, software quality assurance plan, software configuration management plan, or other plans. Quantify any effects the proposed change will have on budgets of scarce resources, such as memory, processing power, network bandwidth, real-time schedule. Identify any impact the proposed change will have on fielded systems if the affected component is not perfectly backward compatible.Copyright 2002 by Karl E. Wiegers. Permission to use, modify, and distribute is granted.Effort Estimation for a Requirements ChangeEffort(Labor Hours) TaskUpdate the SRS or requirements database with the new requirementDevelop and evaluate prototypeCreate new design componentsModify existing design componentsDevelop new user interface componentsModify existing user interface componentsDevelop new user publications and help screensModify existing user publications and help screensDevelop new source codeModify existing source codePurchase and integrate third party softwareIdentify, purchase, and integrate hardware components; qualify vendorModify build filesDevelop new unit and integration testsModify existing unit and integration testsPerform unit and integration testing after implementationWrite new system and acceptance test casesModify existing system and acceptance test casesModify automated test driversPerform regression testing at unit, integration, and system levelsDevelop new reportsModify existing reportsDevelop new database elementsModify existing database elementsDevelop new data filesModify existing data filesModify various project plansUpdate other documentationUpdate requirements traceability matrixReview modified work productsPerform rework following reviews and testingRecertify product as being safe, secure, and compliant with standards.Other additional tasksTOTAL ESTIMATED EFFORTProcedure:1. Identify the subset of the above tasks that will have to be done.2. Allocate resources to tasks.3. Estimate effort required for pertinent tasks listed above, based on assigned resources.4. Total the effort estimates.5. Sequence tasks and identify predecessors.6. Determine whether change is on the projects critical path.7. Estimate schedule and cost impact.Copyright 2002 by Karl E. Wiegers. Permission to use, modify, and distribute is granted.Impact Analysis Report TemplateChange Request ID: _