{"title":"开发标准的关键问题(软件度量)","authors":"R.N. Sulgrove","doi":"10.1109/SESAW.1991.151551","DOIUrl":null,"url":null,"abstract":"Developing an IEEE standard is an involved process; it is much more than merely preparing a document for ballot. Many content issues must be addressed before a consensus for the document can be obtained. Many administrative issues must be handled. These are non-trivial tasks, especially since the working group preparing the document is a volunteer group that functions for several years. This paper explores the key issues encountered by the software productivity metrics working group, and proposes ways that other working groups might handle similar issues encountered. Its goal is to alert new standards groups to possible issues. Being able to anticipate a problem may reduce its disruptive impact and help to make things progress more smoothly.<<ETX>>","PeriodicalId":342960,"journal":{"name":"[1991 Proceedings] Fourth Software Engineering Standards Application Workshop","volume":"4 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1991-05-20","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"Key issues in developing a standard (software metrics)\",\"authors\":\"R.N. Sulgrove\",\"doi\":\"10.1109/SESAW.1991.151551\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Developing an IEEE standard is an involved process; it is much more than merely preparing a document for ballot. Many content issues must be addressed before a consensus for the document can be obtained. Many administrative issues must be handled. These are non-trivial tasks, especially since the working group preparing the document is a volunteer group that functions for several years. This paper explores the key issues encountered by the software productivity metrics working group, and proposes ways that other working groups might handle similar issues encountered. Its goal is to alert new standards groups to possible issues. Being able to anticipate a problem may reduce its disruptive impact and help to make things progress more smoothly.<<ETX>>\",\"PeriodicalId\":342960,\"journal\":{\"name\":\"[1991 Proceedings] Fourth Software Engineering Standards Application Workshop\",\"volume\":\"4 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1991-05-20\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"[1991 Proceedings] Fourth Software Engineering Standards Application Workshop\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/SESAW.1991.151551\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"[1991 Proceedings] Fourth Software Engineering Standards Application Workshop","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/SESAW.1991.151551","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Key issues in developing a standard (software metrics)
Developing an IEEE standard is an involved process; it is much more than merely preparing a document for ballot. Many content issues must be addressed before a consensus for the document can be obtained. Many administrative issues must be handled. These are non-trivial tasks, especially since the working group preparing the document is a volunteer group that functions for several years. This paper explores the key issues encountered by the software productivity metrics working group, and proposes ways that other working groups might handle similar issues encountered. Its goal is to alert new standards groups to possible issues. Being able to anticipate a problem may reduce its disruptive impact and help to make things progress more smoothly.<>