Softwarequalität durch Meßtools

Dumke, Reiner R.; Foltin, Erik; Koeppe, R.; Winkler, Achim

doi:10.1007/978-3-322-87242-5

Cited by 15 publications

(3 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Leaning against the Goal Question Metric Method (GQM) wise questions and metrics need to be derived from these aspects. Suitable questions have to be selected and then necessary ordinal measures (at present only 'Yes' or 'No') need to be determined for a quantified answer of these questions [3]. In this contribution, selected questions of the perspectives organization, project management, process management and technology are listed in a questionnaire catalog.…”

Section: Figure 1 Maturity Levels Of Performance Engineering Processesmentioning

confidence: 99%

Evaluating the performance engineering process

Schmietendorf¹,

Scholz²,

Rautenstrauch³

2000

Proceedings of the 2nd International Workshop on Software and Performance

View full text Add to dashboard Cite

This contribution presents a model for process improvement in the area of performance engineering, which is called performance engineering maturity model. The use of this model allows the evaluation of the level of integration and application of performance engineering. It leans against the well-established capability maturity model from the software engineering institute. The model is based on a questionnaire catalog, which was transferred into a web based evaluation form. The results of this anonymous evaluation are analyzed in this contribution.

show abstract

Section: Figure 1 Maturity Levels Of Performance Engineering Processesmentioning

confidence: 99%

Evaluating the performance engineering process

Schmietendorf¹,

Scholz²,

Rautenstrauch³

2000

Proceedings of the 2nd International Workshop on Software and Performance

View full text Add to dashboard Cite

show abstract

“…There is no lack of existing software metrics. Zuse (1990), Fenton (1991), Dumke et al (1996), Jones (1991) and others have published more than 200 different metrics for measuring software size, complexity and quality. Common metrics for software sizing are adjusted lines of code, functionpoints, feature-points, data-points and object-points (Sneed 1991a).…”

Section: Existing Metrics For Measuring Reusabilitymentioning

confidence: 99%

Measuring reusability of legacy software systems

Sneed

1998

Softw. Process: Improve. Pract.

View full text Add to dashboard Cite

There is an increasing need to reuse existing legacy software systems within the context of a modern software architecture. There are two ways to achieve this, either by re‐engineering or by wrapping. In this paper a pair of metrics are discussed for deciding whether a program is reusable at all, and if so, whether to convert it or to wrap it. Managers should be aware of both alternatives and be able to decide which alternative is best suited for them. The metrics proposed in this paper are intended to support this decision making. The metrics have emerged from the experience of the author in conducting re‐engineering and wrapping projects in the last ten years. Copyright © 1998 John Wiley & Sons, Ltd.

show abstract

“…The application of CAME tools is based on the given measurement framework (see [2], [3], [4], [29]). The integration of CAME tools in the tool supports in the software engineering cycle is given in the The existing CAME tools in the Software Measurement Laboratory at the University of Magdeburg are given in the following table ( [8], [ l l ] , [26], [27]). The market Tools can be obtained at the University of Magdeburg (ftp.cs.uni-magdeburg.de in /pub/metrik).…”

Section: Introductionmentioning

confidence: 99%

CAME tools for an efficient software maintenance

Dumke

Winkler

Proceedings. First Euromicro Conference on Software Maintenance and Reengineering

View full text Add to dashboard Cite

This paper describes the role of the metrics tools as Computer Assisted Software Measurement and Evaluation (CAME) tools in the sojhare life cycle, especially in the maintenance phase. The most CAME tools are designed for code analysis and measurement. They are predestined to be applied to the implementation and maintenance development phases. But, more and more tools are developed for the earlier phases of software development to estimate the effort, complexity, and size of the software that will be created. This paper will provide an overview of the present situation on the area of the CAME tools and discuss their eflcient use in the sofhvare maintenance.

show abstract

Softwarequalität durch Meßtools

Cited by 15 publications

References 0 publications

Evaluating the performance engineering process

Evaluating the performance engineering process

Measuring reusability of legacy software systems

CAME tools for an efficient software maintenance

Contact Info

Product

Resources

About