军用通信系统SHINCOM的软件开发经验

Graham C. Ginsberg, Bernard Vince
{"title":"军用通信系统SHINCOM的软件开发经验","authors":"Graham C. Ginsberg, Bernard Vince","doi":"10.1109/MILCOM.1986.4805752","DOIUrl":null,"url":null,"abstract":"In February 1982, Leigh Instruments was awarded a contract by the Canadian Department of National Defence for the development of the SHINCOM* system, a SHipboard INtegrated COMmunication system. By the summer of that year, the software program had evolved from a relatively straightforward subcontract management function, to a major software development program. At short notice we were required to pull together a relatively large software team and put tools in place to enable us to meet tight schedule and budget constraints. Could we do it? Did we have the tools, or could we acquire them? Did we have the people or did we have to recruit them? The technical challenge of developing a complex communications system was a major challenge in its own right. Only good people, good luck, and strict adherence to standards saw us through. What did we do that worked, what did not, and what would we do differently if we had to do it again? This paper attempts to answer some of those questions.","PeriodicalId":126184,"journal":{"name":"MILCOM 1986 - IEEE Military Communications Conference: Communications-Computers: Teamed for the 90's","volume":"38 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1986-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"Software Experiences in the Development of SHINCOM, a Military Communication System\",\"authors\":\"Graham C. Ginsberg, Bernard Vince\",\"doi\":\"10.1109/MILCOM.1986.4805752\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"In February 1982, Leigh Instruments was awarded a contract by the Canadian Department of National Defence for the development of the SHINCOM* system, a SHipboard INtegrated COMmunication system. By the summer of that year, the software program had evolved from a relatively straightforward subcontract management function, to a major software development program. At short notice we were required to pull together a relatively large software team and put tools in place to enable us to meet tight schedule and budget constraints. Could we do it? Did we have the tools, or could we acquire them? Did we have the people or did we have to recruit them? The technical challenge of developing a complex communications system was a major challenge in its own right. Only good people, good luck, and strict adherence to standards saw us through. What did we do that worked, what did not, and what would we do differently if we had to do it again? This paper attempts to answer some of those questions.\",\"PeriodicalId\":126184,\"journal\":{\"name\":\"MILCOM 1986 - IEEE Military Communications Conference: Communications-Computers: Teamed for the 90's\",\"volume\":\"38 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1986-10-01\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"MILCOM 1986 - IEEE Military Communications Conference: Communications-Computers: Teamed for the 90's\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/MILCOM.1986.4805752\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"MILCOM 1986 - IEEE Military Communications Conference: Communications-Computers: Teamed for the 90's","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/MILCOM.1986.4805752","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 0

摘要

1982年2月,Leigh仪器公司被加拿大国防部授予一份合同,用于发展SHINCOM*系统,一种舰载综合通信系统。到那年夏天,软件程序已经从一个相对直接的分包管理功能,发展成为一个主要的软件开发程序。在很短的时间内,我们需要召集一个相对较大的软件团队,并将工具放置到位,以使我们能够满足紧迫的时间表和预算限制。我们能做到吗?我们是否拥有这些工具,或者我们能否获得这些工具?我们有人手吗,还是需要招募人手?发展一个复杂的通信系统的技术挑战本身就是一项重大挑战。只有好人、好运和严格遵守标准,我们才能度过难关。我们做了哪些有效的事情,哪些没有,如果我们必须再做一次,我们会做哪些不同的事情?本文试图回答其中的一些问题。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
Software Experiences in the Development of SHINCOM, a Military Communication System
In February 1982, Leigh Instruments was awarded a contract by the Canadian Department of National Defence for the development of the SHINCOM* system, a SHipboard INtegrated COMmunication system. By the summer of that year, the software program had evolved from a relatively straightforward subcontract management function, to a major software development program. At short notice we were required to pull together a relatively large software team and put tools in place to enable us to meet tight schedule and budget constraints. Could we do it? Did we have the tools, or could we acquire them? Did we have the people or did we have to recruit them? The technical challenge of developing a complex communications system was a major challenge in its own right. Only good people, good luck, and strict adherence to standards saw us through. What did we do that worked, what did not, and what would we do differently if we had to do it again? This paper attempts to answer some of those questions.
求助全文
通过发布文献求助,成功后即可免费获取论文全文。 去求助
来源期刊
自引率
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学术官方微信