Delphi study of software maintenance problems

Dekleva, Sasa M.

doi:10.1109/icsm.1992.242564

Cited by 42 publications

(15 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The 9% postponed or cancelled maintenance tasks indicate that a great deal of time is spent on starting and stopping maintenance tasks, and on unfinished tasks. In fact, change in a task's priority was identified as the most serious problem in software maintenance in a delphi study of software maintenance problems (Dekleva, 1992b). Knows what to do, believes that this task is similar to another one recently camed out.…”

Section: The Resultsmentioning

confidence: 99%

An empirical study of software maintenance tasks

Jørgensen¹

1995

J. Softw. Maint: Res. Pract.

View full text Add to dashboard Cite

An empirical study of software maintenance tasks was carried out in a large Norwegian organization in the period 1992–93. More than one hundred randomly selected maintenance tasks were studied through interviews with the maintainers performing the tasks immediately before they started the tasks and immediately after they had completed the tasks. The collected data is used to develop distributions and to test 33 hypotheses about software maintenance. The findings from the study indicate, for example, that Application system documentation plays only a minor role as maintenance information source. The maintenance productivity, measured in LOC/effort, is predicted by the size of the task and type of change in the source code, but seems rather independent of language level, maintainer experience, application age and application size. There is an economy of scale for software maintenance tasks. The type of programming language does not correlate with proportion of unexpected maintenance problems, task complexity or task size. The proportion of corrective maintenance decreases with increasing age of the application.

show abstract

Section: The Resultsmentioning

confidence: 99%

An empirical study of software maintenance tasks

Jørgensen¹

1995

J. Softw. Maint: Res. Pract.

View full text Add to dashboard Cite

show abstract

“…Three surveys conducted in 1977, 1983, and 1984, strongly suggest that a lack of documentation is one of the biggest problems in code maintenance (Dekleva 1992). In order to ensure that code artifacts maximize knowledge transfer, developers must ensure that they are documented well.…”

Section: Echoeditmentioning

confidence: 98%

Leveraging temporal and spatial separations with the 24-hour knowledge factory paradigm

2010

View full text Add to dashboard Cite

The 24-H Knowledge Factory facilitates collaboration between geographically and temporally distributed teams. The teams themselves form a strategic partnership whose joint efforts contribute to the completion of a project. Project-related tasks are likewise distributed, allowing tasks to be completed on a continuous basis, regardless of the constraints of any one team's working hours. However, distributing a single task between multiple teams necessitates a handoff process, where one team's development efforts and task planning are communicated from one team ending their shift to the next that will continue the effort. Data management is, therefore, critical to the success of this business model. Efficiency in data management is achieved through a strategic leveraging of key tools, models, and concepts.

show abstract

“…The cost of software maintenance in Western Europe was estimated to be E26.5 billion in 1990 (Goodwin 1991). Dekleva (1992) identified lack of maintenance methodologies, as being one of the top ten problems in software maintenance. However, the delphi study of software maintenance performed by Dekleva, involved three sequential questionnaire surveys of the same group of 67 software professionals over a period of time.…”

Section: Introductionmentioning

confidence: 99%

Methodologies and Software Maintenance

Taylor

Wood-Harper

1996

J. Softw. Maint: Res. Pract.

View full text Add to dashboard Cite

SUMMARYThere are a multitude of information systems methodologies available to practitioners to aid them in the development of new sytstems. In contrast, however, there are very few information systems methodologies aimed specifically at software maintenance, and of the systems development methodologies few pay much attention to software maintenance. This paper is based on case studies in 31 UK IT departments. The research reported in this paper aimed to uncover how information systems methodologies are applied to software maintenance in current practice. The different approaches to applying methodologies to software maintenance are examined together with the reasons for and against using such approaches. Overall methodologies were found to be applied with less rigour and less consistency in software maintenance than in software development. In addition, government and academic initiatives to improve the software maintenance process such as TickiT and the SEI process maturity model appeared to have made little impact on the organizations studied.

show abstract

Delphi study of software maintenance problems

Cited by 42 publications

References 3 publications

An empirical study of software maintenance tasks

An empirical study of software maintenance tasks

Leveraging temporal and spatial separations with the 24-hour knowledge factory paradigm

Methodologies and Software Maintenance

Contact Info

Product

Resources

About