Requirement and Design Trade-offs in Hackystat: An In-Process Software Engineering Measurement and Analysis System

First International Symposium on Empirical Software Engineering and Measurement (ESEM 2007) Pub Date : 2007-09-20 DOI:10.1109/ESEM.2007.36

Philip M. Johnson

{"title":"Requirement and Design Trade-offs in Hackystat: An In-Process Software Engineering Measurement and Analysis System","authors":"Philip M. Johnson","doi":"10.1109/ESEM.2007.36","DOIUrl":null,"url":null,"abstract":"For five years, the Hackystat project has incremen tally developed and evaluated a generic framework for in process software engineering measurement and analysis (ISEMA). At least five other independent ISEMA system development projects have been initiated during this time, indicating growing interest and investment in this approach by the software engineering community. This pa per presents 12 important requirement and design trade offs made in the Hackystat system, some of their implications for organizations wishing to introduce ISEMA, and six directions for future research and development. The three goals of this paper are to: (1) help potential users of ISEMA systems to better evaluate the relative strengths and weaknesses of current and future systems, (2) help potential developers of ISEMA systems to better understand some of the important requirement and design tradeoffs that they must make, and (3) help accelerate progress in ISEMA by identifying promising directions for future research and development.","PeriodicalId":124420,"journal":{"name":"First International Symposium on Empirical Software Engineering and Measurement (ESEM 2007)","volume":"13 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2007-09-20","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"49","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"First International Symposium on Empirical Software Engineering and Measurement (ESEM 2007)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ESEM.2007.36","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}

引用次数: 49

Abstract

For five years, the Hackystat project has incremen tally developed and evaluated a generic framework for in process software engineering measurement and analysis (ISEMA). At least five other independent ISEMA system development projects have been initiated during this time, indicating growing interest and investment in this approach by the software engineering community. This pa per presents 12 important requirement and design trade offs made in the Hackystat system, some of their implications for organizations wishing to introduce ISEMA, and six directions for future research and development. The three goals of this paper are to: (1) help potential users of ISEMA systems to better evaluate the relative strengths and weaknesses of current and future systems, (2) help potential developers of ISEMA systems to better understand some of the important requirement and design tradeoffs that they must make, and (3) help accelerate progress in ISEMA by identifying promising directions for future research and development.

查看原文

微信好友朋友圈 QQ好友复制链接

本刊更多论文

Hackystat中的需求与设计权衡:一个过程中的软件工程测量与分析系统

五年来，Hackystat项目已经逐步开发和评估了过程中软件工程测量和分析(ISEMA)的通用框架。在此期间，至少有五个其他独立的ISEMA系统开发项目已经启动，这表明软件工程社区对该方法的兴趣和投资正在增长。本文提出了Hackystat系统中的12个重要要求和设计权衡，它们对希望引入ISEMA的组织的一些影响，以及未来研究和发展的六个方向。本文的三个目标是:(1)帮助ISEMA系统的潜在用户更好地评估当前和未来系统的相对优势和劣势;(2)帮助ISEMA系统的潜在开发人员更好地理解他们必须做出的一些重要要求和设计权衡;(3)通过确定未来研究和开发的有前途的方向，帮助加快ISEMA的进展。

本文章由计算机程序翻译，如有差异，请以英文原文为准。

求助全文

约1分钟内获得全文去求助

来源期刊

First International Symposium on Empirical Software Engineering and Measurement (ESEM 2007)

自引率

0.00%

发文量

期刊最新文献

Comparing Model Generated with Expert Generated IV&V Activity Plans Decision Support with EMPEROR A cost effectiveness indicator for software development Fine-Grained Software Metrics in Practice Automated Information Extraction from Empirical Software Engineering Literature: Is that possible?