Impacto De Analisis

Impact Analysis Checklist for Requirements Changes

Implications of the Proposed Change

Identify any existing requirements in the baseline that conflict with the proposed change.

Identify anyother 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 theproposed change?

Will the proposed change adversely affect performance requirements or other quality attributes?

Will the change affect any system component that affects critical propertiessuch 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?

Willthe 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 theproposed 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 byincreasing third-party product licensing fees?

Will the change affect any marketing, manufacturing, training, or customer support plans?

System Elements Affected by the Proposed ChangeIdentify 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 thatmust 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....