软件过程模型元素的重复实例

G. Chroust
{"title":"软件过程模型元素的重复实例","authors":"G. Chroust","doi":"10.1145/75110.75116","DOIUrl":null,"url":null,"abstract":"At the end of any software project one could, at least in theory, draw a data flow diagram of all the activities performed, together with the respective inputs and outputs. We could consider such a description as a “trace” of the software project’s history. To arrive at a Software Process Model, one has to abstract from the individual processes (“traces”) to derive a generally applicable basic framework. In this paper we will adopt the terminology of ADPS [IBM_871 where the term “activity type” is used for activity descriptions in the model and “activity” for one instance of an activity type. The term “work item” is used for both inputs and results and “work item type” for the descriptions of work items in the model.","PeriodicalId":414925,"journal":{"name":"International Software Process Workshop","volume":"77 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1988-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"8","resultStr":"{\"title\":\"Duplicate instances of elements of a software process model\",\"authors\":\"G. Chroust\",\"doi\":\"10.1145/75110.75116\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"At the end of any software project one could, at least in theory, draw a data flow diagram of all the activities performed, together with the respective inputs and outputs. We could consider such a description as a “trace” of the software project’s history. To arrive at a Software Process Model, one has to abstract from the individual processes (“traces”) to derive a generally applicable basic framework. In this paper we will adopt the terminology of ADPS [IBM_871 where the term “activity type” is used for activity descriptions in the model and “activity” for one instance of an activity type. The term “work item” is used for both inputs and results and “work item type” for the descriptions of work items in the model.\",\"PeriodicalId\":414925,\"journal\":{\"name\":\"International Software Process Workshop\",\"volume\":\"77 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1988-04-01\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"8\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"International Software Process Workshop\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1145/75110.75116\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"International Software Process Workshop","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/75110.75116","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 8

摘要

在任何软件项目结束时,至少在理论上,可以绘制所有执行活动的数据流图,以及各自的输入和输出。我们可以将这样的描述视为软件项目历史的“跟踪”。要得到软件过程模型,必须从单个过程(“跟踪”)中抽象出来,以派生出一个普遍适用的基本框架。在本文中,我们将采用ADPS [IBM_871]的术语,其中术语“活动类型”用于模型中的活动描述,“活动”用于活动类型的一个实例。术语“工作项”用于输入和结果,“工作项类型”用于模型中工作项的描述。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
Duplicate instances of elements of a software process model
At the end of any software project one could, at least in theory, draw a data flow diagram of all the activities performed, together with the respective inputs and outputs. We could consider such a description as a “trace” of the software project’s history. To arrive at a Software Process Model, one has to abstract from the individual processes (“traces”) to derive a generally applicable basic framework. In this paper we will adopt the terminology of ADPS [IBM_871 where the term “activity type” is used for activity descriptions in the model and “activity” for one instance of an activity type. The term “work item” is used for both inputs and results and “work item type” for the descriptions of work items in the model.
求助全文
通过发布文献求助,成功后即可免费获取论文全文。 去求助
来源期刊
自引率
0.00%
发文量
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
copy
已复制链接
快去分享给好友吧!
我知道了
右上角分享
点击右上角分享
0
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:481959085
Book学术官方微信