{"title":"开发一套结构化的标准(软件工程)","authors":"R. Stevens, A. Scheffer","doi":"10.1109/SESS.1993.263969","DOIUrl":null,"url":null,"abstract":"Standards need to be short, coherent, readable and easy to change. In practice, these goals are hard to achieve, because the underlying information is complex and interrelated. Common mistakes in developing standards include over-large documents, unreadable style, mixed levels of abstraction, lack of structure across sets of documents, and repetition of information across different standards. The European Space Agency (ESA) has been developing a structured set of software engineering standards, and the experience is abstracted to help future standards writers. Many principles were followed subconsciously while developing the ESA standard, but have become clearer in retrospect. A systematic approach should make for a better product with less effort.<<ETX>>","PeriodicalId":145783,"journal":{"name":"Proceedings 1993 Software Engineering Standards Symposium","volume":"47 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1993-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"Developing a structured set of standards (software engineering)\",\"authors\":\"R. Stevens, A. Scheffer\",\"doi\":\"10.1109/SESS.1993.263969\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Standards need to be short, coherent, readable and easy to change. In practice, these goals are hard to achieve, because the underlying information is complex and interrelated. Common mistakes in developing standards include over-large documents, unreadable style, mixed levels of abstraction, lack of structure across sets of documents, and repetition of information across different standards. The European Space Agency (ESA) has been developing a structured set of software engineering standards, and the experience is abstracted to help future standards writers. Many principles were followed subconsciously while developing the ESA standard, but have become clearer in retrospect. A systematic approach should make for a better product with less effort.<<ETX>>\",\"PeriodicalId\":145783,\"journal\":{\"name\":\"Proceedings 1993 Software Engineering Standards Symposium\",\"volume\":\"47 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1993-08-30\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Proceedings 1993 Software Engineering Standards Symposium\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/SESS.1993.263969\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings 1993 Software Engineering Standards Symposium","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/SESS.1993.263969","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Developing a structured set of standards (software engineering)
Standards need to be short, coherent, readable and easy to change. In practice, these goals are hard to achieve, because the underlying information is complex and interrelated. Common mistakes in developing standards include over-large documents, unreadable style, mixed levels of abstraction, lack of structure across sets of documents, and repetition of information across different standards. The European Space Agency (ESA) has been developing a structured set of software engineering standards, and the experience is abstracted to help future standards writers. Many principles were followed subconsciously while developing the ESA standard, but have become clearer in retrospect. A systematic approach should make for a better product with less effort.<>