Customizing GQM Models for Software Project Monitoring

Monden, Akito; Matsumura, Tomoko; Barker, Mike; Torii, Koji; Basili, Victor R.

doi:10.1587/transinf.e95.d.2169

Cited by 11 publications

(4 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Automatic measurement tools that do not require a context switch have been proposed, for example hackystat [17], EPM [18], [19] and Ginger2 [20]. These can be used to collect detailed data at a lower cost.…”

Section: Background and Related Workmentioning

confidence: 99%

Industry Application of Software Development Task Measurement System: TaskPit

Suthipornopas

Leelaprute

Monden

et al. 2017

IEICE Trans. Inf. & Syst.

Self Cite

View full text Add to dashboard Cite

SUMMARYTo identify problems in a software development process, we have been developing an automated measurement tool called TaskPit, which monitors software development tasks such as programming, testing and documentation based on the execution history of software applications. This paper introduces the system requirements, design and implementation of TaskPit; then, presents two real-world case studies applying TaskPit to actual software development. In the first case study, we applied TaskPit to 12 software developers in a certain software development division. As a result, several concerns (to be improved) have been revealed such as (a) a project leader spent too much time on development tasks while he was supposed to be a manager rather than a developer, (b) several developers rarely used e-mails despite the company's instruction to use e-mail as much as possible to leave communication records during development, and (c) several developers wrote too long e-mails to their customers. In the second case study, we have recorded the planned, actual, and self reported time of development tasks. As a result, we found that (d) there were unplanned tasks in more than half of days, and (e) the declared time became closer day by day to the actual time measured by TaskPit. These findings suggest that TaskPit is useful not only for a project manager who is responsible for process monitoring and improvement but also for a developer who wants to improve by him/herself. key words: processs measurement, system development, case study

show abstract

Section: Background and Related Workmentioning

confidence: 99%

Industry Application of Software Development Task Measurement System: TaskPit

Suthipornopas

Leelaprute

Monden

et al. 2017

IEICE Trans. Inf. & Syst.

Self Cite

View full text Add to dashboard Cite

show abstract

“…EPM analyzes and visualizes these data and feedbacks to project stakeholders. In [14], Monden creates the model of detecting causes of main software project delay using the GQM method and EPM. Using EPM involves in using other tools.…”

Section: Relatedworkmentioning

confidence: 99%

Initial Industrial Experience of GQM-Based Product-Focused Project Monitoring with Trend Patterns

Nakai

Honda

Washizaki

et al. 2014

2014 21st Asia-Pacific Software Engineering Conference

View full text Add to dashboard Cite

It is important for project stakeholders to identify the states of projects and quality of products. Although metrics are useful for identifying them, it is difficult for project stakeholders to select appropriate metrics and determine the purpose of measuring metrics. We propose an approach that defines the measured metrics by GQM method to identify tendency in projects and products based on Trend Pattern. Additionally, we implement a tool as a Jenkins Plugin to visualize an evaluation results based on GQM method. We perform an industrial case study, which objects are two software development projects. In our industrial case study, we can identify the problem that product contains. As our future work, we will adopt our approach and GQM Plugin to software development project continuously to assess their effectiveness in the long term.

show abstract

“…Here, in order to have a concrete way to compute the metrics, they also gave techniques associated with them. Various authors have addressed the usage of the GQM approach and its advantages as explained in [4]- [13].…”

Section:  Quantitative Level (Metric)mentioning

confidence: 99%

“…Processing GQM consisting of performing six important steps as explained in many articles [4][5][6][7][8][9][10][11][12][13]. These steps are as follows.…”

Section: Steps Of Gqm Measurementmentioning

confidence: 99%

A Quantitative Measurement of Software Requirement Factors using Goal Question Metric (GQM) Approach

Raju¹,

Uma²

2014

IOSRJCE

View full text Add to dashboard Cite

Every application software that we propose to develop can be thought of a group or collection of related requirements specified by the user and these requirements are the foundation from which the quality of the software is measured. Until now there is no concrete measurement methodology for measuring the requirements of any application software. A new value driven quantitative measurement approach is presented in this research work. These values associated with each of the requirements are collectively called as Requirement Factor Values (RFV). This new measurement method uses the Goal-Question-Metric (GQM) approach and it is one of the most powerful approaches available for metrics measurement. In this work, seven factors-customer priority of requirements, implementation complexity, changes in requirements, fault impact of requirements, completeness traceability and execution time are considered to be the primary ingredients of every requirement of the software and every requirement is characterized by the numerical values of these factors. A Java based application system has been developed that takes questionnaires, various parameters/values associated with each of the requirements and generates these factor values for each requirement of the software. These requirement factor values can be used in many ways such as measuring the quality of the software, test case design and optimization, test case prioritization.

show abstract

Customizing GQM Models for Software Project Monitoring

Cited by 11 publications

References 8 publications

Industry Application of Software Development Task Measurement System: TaskPit

Industry Application of Software Development Task Measurement System: TaskPit

Initial Industrial Experience of GQM-Based Product-Focused Project Monitoring with Trend Patterns

A Quantitative Measurement of Software Requirement Factors using Goal Question Metric (GQM) Approach

Contact Info

Product

Resources

About