Using the software process model to analyze a software project

Proceedings., Fourteenth Annual International Computer Software and Applications Conference Pub Date : 1990-10-31 DOI:10.1109/CMPSAC.1990.139378

I. Sue Ranft, D. Gustafson

{"title":"Using the software process model to analyze a software project","authors":"I. Sue Ranft, D. Gustafson","doi":"10.1109/CMPSAC.1990.139378","DOIUrl":null,"url":null,"abstract":"Attention is given to the software process model (SPM), which was introduced by A.L. Baker et al. (1987). The SPM models software development by modeling the evolution of the full set of documents produced in software development. The authors show the usefulness of the SPM as a management tool by applying it to a software project. Since the SPM shows patterns of the software product development in greater detail than the current tools available, it provides management with a more effective means of visualizing and controlling software projects. The SPM has the capability to alert management to problems during the development process. This was illustrated when the SPM indicated a problem during the design phase. The problem was made known by the pattern generated by the continuous changes to design specifications when initial code was completed. It was shown that the SPM can be used to ensure consistencies between documents. By plotting changes in documents, both developers and managers are alerted as to whether or not a change is incorporated in other documents.<<ETX>>","PeriodicalId":127509,"journal":{"name":"Proceedings., Fourteenth Annual International Computer Software and Applications Conference","volume":"116 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1990-10-31","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings., Fourteenth Annual International Computer Software and Applications Conference","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/CMPSAC.1990.139378","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}

引用次数: 0

Abstract

Attention is given to the software process model (SPM), which was introduced by A.L. Baker et al. (1987). The SPM models software development by modeling the evolution of the full set of documents produced in software development. The authors show the usefulness of the SPM as a management tool by applying it to a software project. Since the SPM shows patterns of the software product development in greater detail than the current tools available, it provides management with a more effective means of visualizing and controlling software projects. The SPM has the capability to alert management to problems during the development process. This was illustrated when the SPM indicated a problem during the design phase. The problem was made known by the pattern generated by the continuous changes to design specifications when initial code was completed. It was shown that the SPM can be used to ensure consistencies between documents. By plotting changes in documents, both developers and managers are alerted as to whether or not a change is incorporated in other documents.<>

查看原文本刊更多论文

使用软件过程模型分析软件项目

重点是软件过程模型(SPM)，它是由A.L. Baker等人(1987)引入的。SPM通过对软件开发过程中产生的全套文档的演变进行建模来为软件开发建模。作者通过将SPM应用于软件项目，展示了它作为一种管理工具的实用性。由于SPM比当前可用的工具更详细地显示了软件产品开发的模式，因此它为管理人员提供了一种更有效的可视化和控制软件项目的方法。SPM具有在开发过程中提醒管理层注意问题的能力。当SPM在设计阶段指出问题时，就说明了这一点。当初始代码完成时，通过对设计规范的持续更改所生成的模式可以知道问题。结果表明，SPM可以用于保证文件之间的一致性。通过绘制文档中的更改，开发人员和管理人员都可以注意到是否将更改合并到其他文档中。

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

求助全文

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

来源期刊

Proceedings., Fourteenth Annual International Computer Software and Applications Conference

自引率

0.00%

发文量