G. Stark, P. Oman
{"title":"Software maintenance management strategies: observations from the field","authors":"G. Stark, P. Oman","doi":"10.1002/(SICI)1096-908X(199711/12)9:6%3C365::AID-SMR160%3E3.0.CO;2-J","DOIUrl":null,"url":null,"abstract":"There is much literature describing software maintenance process models, but few comparative studies on the approaches used by managers in the field. This paper describes three software maintenance management strategies currently implemented by six organizations. The strategies are compared on the attributes of performance, economics, efficiency and end-product quality. The paper defines operational measurements for each attribute and describes the data collected over the past two years. \n \n \n \nThe three strategies investigated were labelled the fixed staff/variable schedule, variable staff/fixed schedule and the variable staff/variable schedule. Each strategy has attributes that make it appealing for implementation by a software maintenance project manager. The fixed staff/variable schedule strategy had the fastest priority change response time, the variable staff/fixed schedule strategy had the highest throughput and the best on-schedule performance, and the variable staff/variable schedule had the lowest cost and highest quality. Thus, the key task for a manager is defining the attribute that they would most like to optimize and choosing a strategy that supports that goal. © 1997 John Wiley & Sons, Ltd.","PeriodicalId":383619,"journal":{"name":"J. Softw. Maintenance Res. Pract.","volume":"45 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1997-11-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"13","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"J. Softw. Maintenance Res. Pract.","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1002/(SICI)1096-908X(199711/12)9:6%3C365::AID-SMR160%3E3.0.CO;2-J","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 13
软件维护管理策略:从现场观察
描述软件维护过程模型的文献很多,但对管理人员在该领域使用的方法的比较研究很少。本文描述了目前由六个组织实施的三种软件维护管理策略。从性能、经济性、效率和最终产品质量等方面对两种策略进行了比较。本文定义了每个属性的操作度量,并描述了过去两年中收集的数据。所调查的三种策略被标记为固定人员/可变时间表,可变人员/固定时间表和可变人员/可变时间表。每个策略都有一些属性,使其对软件维护项目经理的实现具有吸引力。固定人员/可变进度策略具有最快的优先级变更响应时间,可变人员/固定进度策略具有最高的吞吐量和最佳的准时性,可变人员/可变进度策略具有最低的成本和最高的质量。因此,管理者的关键任务是定义他们最想优化的属性,并选择支持该目标的策略。©1997 John Wiley & Sons, Ltd
本文章由计算机程序翻译,如有差异,请以英文原文为准。