The EMISQ Method - Expert Based Evaluation of Internal Software Quality

Reinhold Plösch, Harald Gruber, A. Hentschel, Ch. Körner, Gustav Pomberger, Stefan Schiffer, M. Saft, Stefan Storck

Research output: Chapter in Book/Report/Conference proceedingConference proceedingspeer-review

Abstract

Internal software quality, e.g. the quality of code, has great impact on the overall quality of software. Besides well known manual inspection and review techniques more recent approaches utilize tool-based static code for the evaluation of internal software quality. Despite the high potential of static code analyzers the application of tools alone cannot replace well founded expert opinion. Knowledge, experience and fair judgement is indispensable for a valid, reliable quality assessment, which is accepted by software developers and managers. The EMISQ method (Evaluation Method for Internal Software Quality), guides the assessment process for all stakeholders of an evaluation project. The method is supported by a tool that assists evaluators with their analysis and rating tasks and provides support for generating a code quality report. The application of the method in a pilot project has shown its applicability.
Original languageEnglish
Title of host publicationProceedings of 3rd IEEE Systems and Software Week, March 3-8, 2007, Baltimore, IEEE Computer Society Press, 2007
PublisherIEEE
Pages99-108
Number of pages10
ISBN (Print)0769528627, 9780769528625
DOIs
Publication statusPublished - Mar 2007

Publication series

NameProceedings - International Conference on Software Engineering
ISSN (Print)0270-5257

Fields of science

  • 102006 Computer supported cooperative work (CSCW)
  • 102015 Information systems
  • 102016 IT security
  • 102020 Medical informatics
  • 102022 Software development
  • 102027 Web engineering
  • 502032 Quality management
  • 502050 Business informatics
  • 503015 Subject didactics of technical sciences
  • 102034 Cyber-physical systems
  • 509026 Digitalisation research
  • 102040 Quantum computing 

Cite this