{"title":"如何编写软件规格说明","authors":"Philip H. Hartman, D. H. Owens","doi":"10.1145/1465611.1465713","DOIUrl":null,"url":null,"abstract":"In general, computer software is getting more complicated at an increasing rate. Unfortunately, the people who have to develop this software have been at it for only a relatively short time. The result is predictable: ever-larger software troubles. This, in turn, leads many people to feel insecure about software development, to think of it as a modern \"black art\" for which even the most able practitioners lose the recipe every few months.","PeriodicalId":265740,"journal":{"name":"AFIPS '67 (Fall)","volume":"243 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1967-11-14","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"3","resultStr":"{\"title\":\"How to write software specifications\",\"authors\":\"Philip H. Hartman, D. H. Owens\",\"doi\":\"10.1145/1465611.1465713\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"In general, computer software is getting more complicated at an increasing rate. Unfortunately, the people who have to develop this software have been at it for only a relatively short time. The result is predictable: ever-larger software troubles. This, in turn, leads many people to feel insecure about software development, to think of it as a modern \\\"black art\\\" for which even the most able practitioners lose the recipe every few months.\",\"PeriodicalId\":265740,\"journal\":{\"name\":\"AFIPS '67 (Fall)\",\"volume\":\"243 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1967-11-14\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"3\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"AFIPS '67 (Fall)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1145/1465611.1465713\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"AFIPS '67 (Fall)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/1465611.1465713","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
In general, computer software is getting more complicated at an increasing rate. Unfortunately, the people who have to develop this software have been at it for only a relatively short time. The result is predictable: ever-larger software troubles. This, in turn, leads many people to feel insecure about software development, to think of it as a modern "black art" for which even the most able practitioners lose the recipe every few months.