Software change impacts-an evolving perspective

Bohner, Shawn A.

doi:10.1109/icsm.2002.1167777

Cited by 75 publications

(56 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The work of Bohner [37], [172] is concerned with impact analysis in systems, which are composed of existing solutions, as more software is build upon middleware and other preexisting components. The author proposes the use of a dependency graph and a dependency matrix, which are combined with a distance measure to limit the impact propagation.…”

Section: F Combined Scopesmentioning

confidence: 99%

A taxonomy for software change impact analysis

Lehnert

2011

Proceedings of the 12th International Workshop on Principles of Software Evolution and the 7th Annual ERCIM Workshop on Softwar

View full text Add to dashboard Cite

Abstract-Change impact analysis is required for constantly evolving systems to support the comprehension, implementation, and evaluation of changes. A lot of research effort has been spent on this subject over the last twenty years, and many approaches were published likewise. However, there has not been an extensive attempt made to summarize and review published approaches as a base for further research in the area. Therefore, we present the results of a comprehensive investigation of software change impact analysis, which is based on a literature review and a taxonomy for impact analysis. The contribution of this review is threefold. First, approaches proposed for impact analysis are explained regarding their motivation and methodology. They are further classified according to the criteria of the taxonomy to enable the comparison and evaluation of approaches proposed in literature. We perform an evaluation of our taxonomy regarding the coverage of its classification criteria in studied literature, which is the second contribution. Last, we address and discuss yet unsolved problems, research areas, and challenges of impact analysis, which were discovered by our review to illustrate possible directions for further research.

show abstract

Section: F Combined Scopesmentioning

confidence: 99%

A taxonomy for software change impact analysis

Lehnert

2011

Proceedings of the 12th International Workshop on Principles of Software Evolution and the 7th Annual ERCIM Workshop on Softwar

View full text Add to dashboard Cite

show abstract

“…Moreover, the relationship between artifacts and entities can be direct, where an artifact or an entity is directly affected by the change, or indirect, where an artifact or an entity may be affected indirectly due to its relationship to other artifacts and entities that are affected directly by the proposed change (Strens and Sugden, 1996). This phenomenon is sometimes termed as "ripple effect", and the chain of this ripple effect may not be limited to only one level but to a number of levels with different degree of effect (Bohner, 2002, De Lucia et al, 2008, Ramzan and Ikram, 2005. (Leffingwell and Widrig, 2003).…”

Section: Figure 5 Ripple Effect On Artifacts and Phases Due Tomentioning

confidence: 99%

“…It shall be kept in mind that this impact set is not always accurate in the sense that it may not be able to include all the possible artifacts and entities, and accordingly some of them might be left out (termed as false negatives). Additionally, the impact set may include some artifacts and entities which may in reality not be affected by this change (termed as false positives) (Bohner, 2002). The effectiveness of a given technique for impact analysis and traceability matrix is mostly judged considering these false positives and false negatives.…”

Section: Figure 5 Ripple Effect On Artifacts and Phases Due Tomentioning

confidence: 99%

Design Requirements in Software and Engineering Systems

Eleiche

Ahmad²,

Elish³

2012

Industrial Engineering and Management Systems

View full text Add to dashboard Cite

The subject of "Design Requirements" (DR) is central to the design of software and engineering systems. The main reason for this is that quality aspects are usually closely tied to requirements, among other things. In this review paper, we consider how the subject of requirements is being managed in these two seemingly different design disciplines. Two important aspects are covered, namely: (a) requirements development, describing various activities leading to requirements documentation, and (b) requirements change management, describing various activities needed for the proper treatment of the inevitable changes in requirements. Similarities and differences on how these two aspects are handled in software and engineering systems are highlighted. It is concluded from this literature survey that the management of software requirements is quite coherent and well established as a science. On the other hand, management of engineering systems requirements suffer from being unstructured, in particular when requirements changes are involved. Important gaps and future important research areas are identified.

show abstract

“…To perform impact analysis different search algorithms are identified. Each of these algorithms has been presented in at least one paper [52]:…”

Section: ) Impact Analysismentioning

confidence: 99%

TSSR: A Proposed Tool for Secure Software Requirement Management

Bokhari¹,

Siddiqui²

2014

IJITCS

View full text Add to dashboard Cite

Abstract-This paper provides a unified framework in which entire design of the project can be captured right from the beginning of the software development. This paper discusses about the requirements which should be included in the development of the requirement management tools. As the requirements, criteria which have been discussed, we introduce a requirement management tool known as TSSR (Tool for Secure Software Requirement). This tool manages risk analysis, system requirements, security of the system and project, users/group restriction, encrypted database, traceability and extension of the tool to interact with external requirement management tools. The aim of this paper is to describe the TSSR framework and its four components: Planner, Modeller, Prover and Documenter which will be helpful in interacting and managing requirements with arbitrary number of external tools for secure software development.

show abstract

Software change impacts-an evolving perspective

Cited by 75 publications

References 10 publications

A taxonomy for software change impact analysis

A taxonomy for software change impact analysis

Design Requirements in Software and Engineering Systems

TSSR: A Proposed Tool for Secure Software Requirement Management

Contact Info

Product

Resources

About