Traceability relationships help stakeholders understand the many associations and
dependencies that exist among software artifacts created during a software development …

Although the benefits of requirements traceability are widely recognized, the actual practice
of maintaining a traceability scheme is not always entirely successful. The traceability …

Requirements tracing is inevitable. We do tracing when we search information and it is
difficult to imagine a software development environment without some tracing aids. For …

The ability to trace new and changed requirements to their impacted components provides
critical support for managing change in an evolving software system. Unfortunately …

Non-functional requirements, describing quality concerns such as performance, security,
and availability, often exhibit complex interdependencies and trade-offs and have broad …

Nonfunctional requirements (NFRs) are critical to the successful implementation of almost
every nontrivial software system. This is evidenced by the fact that many documented system …

Current impact analysis techniques tend to focus on assessing the impact of change upon
the system's functionality, whilst a consideration of performance related requirements is …

Operational risk management (ORM) is a process of critical importance to organizations. It
refers to the systematic identification, assessment and mitigation of operational risks, ie risks …

Making changes safely to programs requires program comprehension and satisfaction of the
information needs of software maintainers. In this paper we provide insights into improving …

Software traceability is the ability to provide trace information on requirements, design, and
implementation of a system. It helps stakeholders understand the many associations of …