Software diagnosis

From Wikipedia, the free encyclopedia
Jump to: navigation, search

Software diagnosis (also: software diagnostics) refers to concepts, techniques, and tools that allow for obtaining findings, conclusions, and evaluations about software systems and their implementation, composition, behavior, and evolution. It serves as means to monitor, steer, observe and optimize software development, software maintenance, and software reengineering in the sense of a business intelligence approach specific to software systems. It is generally based on the automatic extraction, analysis, and visualization of corresponding information sources of the software system.

Applications[edit]

Software diagnosis supports all branches of software engineering, in particular project management, quality management, risk management as well as implementation and test. Its main strength is to support all stakeholders of software projects (in particular during software maintenance and for software reengineering tasks[1]) and to provide effective communication means for software development projects. For example, software diagnosis facilitates "bridging an essential information gap between management and development, improve awareness, and serve as early risk detection instrument".[2] Software diagnosis includes assement methods for "perfective maintenance" that, for example, apply "visual analysis techniques to combine multiple indicators for low maintainability, including code complexity and entanglement with other parts of the system, and recent changes applied to the code".[3]

Characteristics[edit]

In contrast to manifold approaches and techniques in software engineering, software diagnosis does not depend on programming languages, modeling techniques, software development processes or the specific techniques used in the various stages of the software development process. Instead, software diagnosis aims at analyzing and evaluating the software system in its as-is state and based on system-generated information to bybass any subjective or potentially outdated information sources (e.g., initial software models). For it, software diagnosis combines and relates sources of information that are typically not directly linked. Examples:

  • Source-code metrics are related with software developer activity to gain insight into developer-specific effects on software code quality.[4]
  • System structure and run-time execution traces are correlated to facilitate program comprehension through dynamic analysis in software maintenance tasks.[5]

Principles[edit]

The core principle of software diagnosis is to automatically extract information from all available information sources of a given software projects such as source code base, project repository, code metrics, execution traces,[6] test results, etc. To combine information, software-specific data mining, analysis, and visualization techniques are applied. Its strength results, among various reasons, from integrating decoupled information spaces in the scope of a typical software project, for example development and developer activities (recorded by the repository) and code and quality metrics (derived by analyzing source code) or key performance indicators (KPIs).

Examples[edit]

Examples of software diagnosis tools include software maps and software metrics.

Critics[edit]

Software diagnosis—in contrast to many approaches in software engineering—does not assume that developer capabilities, development methods, programming or modeling languages are right or wrong (or better or worse compared to each other): Software diagnosis aims at giving insight into a given software system and its status regardless of the methods, languages, or models used to create and maintain the system.

Related subjects[edit]

References[edit]

  1. ^ Martin Beck, Jonas Trümper, Jürgen Döllner: "A Visual Analysis and Design Tool for Planning Software Reengineerings". Proceedings of the 6th IEEE International Workshop on Visualizing Software for Understanding and Analysis, IEEE Computer Society, pp. 54-61, 2011.
  2. ^ Johannes Bohnet, Jürgen Döllner: "Monitoring Code Quality and Development Activity by Software Maps". Proceedings of the IEEE ACM ICSE Workshop on Managing Technical Debt, pp. 9-16, 2011.
  3. ^ Jonas Trümper et al.: "A Visual Analysis Approach to Support Perfective Software Maintenance". Proceedings of the 16th International Conference on Information Visualisation, IEEE Computer Society, pp. 308-315, 2012.
  4. ^ Daniel Limberger et al.: "Interactive Software Maps for Web-Based Source Code Analysis". Proceedings of the International Web3D Conference, ACM, pp. 8, 2013.
  5. ^ Jonas Trümper et al.: "ViewFusion: Correlating Structure and Activity Views for Execution Traces". Proceedings of the 10th Theory and Practice of Computer Graphics Conference, European Association for Computer Graphics, pp. 45-52, 2012.
  6. ^ Johannes Bohnet: "Visualization of Execution Traces and its Application to Software Maintenance". PhD thesis, Hasso-Plattner-Institut, University of Potsdam, 2011.

External links[edit]