A framework for business-oriented security audit

Liu, Lianzhong; Jiang, Wen; Huang, Qiang

doi:10.1109/indin.2008.4618082

Cited by 3 publications

(2 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…System that contains a large number of bugs, and/or bugs that fervently intrude with its functionality and operations, is said to be buggy. Reports enumerating bugs in a program are commonly known as bug reports, defect reports, fault reports, problem reports, and so forth [1]. Testers and debuggers have to go through all the code and multiple functions to trace the origin of the bug or say error to fix the system.…”

Section: Coding Instancesmentioning

confidence: 99%

“…The process of debugging a software project may varies form interactive debugging or control flow manipulations. As we know that software systems have become generally more entangled, the various common debugging techniques have dilated with multiple methods to detect anomalies, estimate impact, and give remedy to a system for the given situation [1]. Fig.…”

Section: Coding Instancesmentioning

confidence: 99%

See 1 more Smart Citation

Fault Localization in a Software Project using Back-Tracking Principles of Matrix Dependency

Anand¹,

Ramani²

2014

IJETT

View full text Add to dashboard Cite

Fault identification and testing has always been the most specific concern in the field of software development. To identify and testify the bug we should be aware of the source of the failure or any unwanted issue. In this paper, we are trying to extract the location of failure and trying to cope up with the bug. Using directed graph, we tried to obtain the dependency of multiple activities in live environment to trace the origin of fault. Software development comes up with series of activities and we tried to show the dependency of multiple activities on each other. Critical activities are considered as they cause abnormal functioning of the whole system. The paper discuss about the priorities of activities of dependency of software failure on the critical activities. Matrix representation of activities as part of the software is chosen to determine root of the failure using concept of dependency. It can vary with the topography of network and software environment. When faults occur, the possible symptoms will be reflected in the dependency matrix with high probability in fault itself. Thus, independent faults are located in the main diagonal of dependency matrix.

show abstract

Section: Coding Instancesmentioning

confidence: 99%

Section: Coding Instancesmentioning

confidence: 99%