{"title":"软件需求规范过程中的度量","authors":"J. Györkös","doi":"10.1016/0165-6074(94)90063-9","DOIUrl":null,"url":null,"abstract":"<div><p>We are seeking to find measures of risk that can be used by management and the developers. We will show which characteristics and constraints could be assessed directly from the requirements specification document in the form of numeric values. These numeric must be normalised and used in a comparative manner with other events in the software development process. The required characteristics — the specific risks — will be expressed by the proposed metrics. The construction of a database with requirements analysis process data is emphasised as a testbed for metrics evaluation. In summary our approach is as follows: First decide what the important areas of risk are, then identify attributes available in a CASE (Computer Aided Software engineering) repository that may give an insight into these risks and then combine these attributes to provide risk measures.</p></div>","PeriodicalId":100927,"journal":{"name":"Microprocessing and Microprogramming","volume":"40 10","pages":"Pages 893-896"},"PeriodicalIF":0.0000,"publicationDate":"1994-12-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"https://sci-hub-pdf.com/10.1016/0165-6074(94)90063-9","citationCount":"4","resultStr":"{\"title\":\"Measurements in software requirements specification process\",\"authors\":\"J. Györkös\",\"doi\":\"10.1016/0165-6074(94)90063-9\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"<div><p>We are seeking to find measures of risk that can be used by management and the developers. We will show which characteristics and constraints could be assessed directly from the requirements specification document in the form of numeric values. These numeric must be normalised and used in a comparative manner with other events in the software development process. The required characteristics — the specific risks — will be expressed by the proposed metrics. The construction of a database with requirements analysis process data is emphasised as a testbed for metrics evaluation. In summary our approach is as follows: First decide what the important areas of risk are, then identify attributes available in a CASE (Computer Aided Software engineering) repository that may give an insight into these risks and then combine these attributes to provide risk measures.</p></div>\",\"PeriodicalId\":100927,\"journal\":{\"name\":\"Microprocessing and Microprogramming\",\"volume\":\"40 10\",\"pages\":\"Pages 893-896\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1994-12-01\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"https://sci-hub-pdf.com/10.1016/0165-6074(94)90063-9\",\"citationCount\":\"4\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Microprocessing and Microprogramming\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://www.sciencedirect.com/science/article/pii/0165607494900639\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Microprocessing and Microprogramming","FirstCategoryId":"1085","ListUrlMain":"https://www.sciencedirect.com/science/article/pii/0165607494900639","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Measurements in software requirements specification process
We are seeking to find measures of risk that can be used by management and the developers. We will show which characteristics and constraints could be assessed directly from the requirements specification document in the form of numeric values. These numeric must be normalised and used in a comparative manner with other events in the software development process. The required characteristics — the specific risks — will be expressed by the proposed metrics. The construction of a database with requirements analysis process data is emphasised as a testbed for metrics evaluation. In summary our approach is as follows: First decide what the important areas of risk are, then identify attributes available in a CASE (Computer Aided Software engineering) repository that may give an insight into these risks and then combine these attributes to provide risk measures.