{"title":"将功能点分析扩展到面向对象的需求规范","authors":"Vahan Harput, H. Kaindl, Stefan Kramer","doi":"10.1109/METRICS.2005.25","DOIUrl":null,"url":null,"abstract":"In practice, it is very important to determine the size of a proposed software system yet to be built based on its requirements, i.e., early in the development life cycle. Given a size estimate, it is usually possible to estimate the effort that will be needed to build this system. The most widely used approach to size estimation is function point analysis (FPA). It is not clear, however, how function points can be reasonably counted for object-oriented requirements specifications. We found that this cannot be done fully automatically, since several constructs of such a representation can be interpreted in various ways in the spirit of FPA, depending on the context. For applying FPA to object-oriented requirements specifications, we defined rules that specify a semi-automatic transformation from an object-oriented requirements model to an FPA model","PeriodicalId":402415,"journal":{"name":"11th IEEE International Software Metrics Symposium (METRICS'05)","volume":"47 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2005-09-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"27","resultStr":"{\"title\":\"Extending function point analysis to object-oriented requirements specifications\",\"authors\":\"Vahan Harput, H. Kaindl, Stefan Kramer\",\"doi\":\"10.1109/METRICS.2005.25\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"In practice, it is very important to determine the size of a proposed software system yet to be built based on its requirements, i.e., early in the development life cycle. Given a size estimate, it is usually possible to estimate the effort that will be needed to build this system. The most widely used approach to size estimation is function point analysis (FPA). It is not clear, however, how function points can be reasonably counted for object-oriented requirements specifications. We found that this cannot be done fully automatically, since several constructs of such a representation can be interpreted in various ways in the spirit of FPA, depending on the context. For applying FPA to object-oriented requirements specifications, we defined rules that specify a semi-automatic transformation from an object-oriented requirements model to an FPA model\",\"PeriodicalId\":402415,\"journal\":{\"name\":\"11th IEEE International Software Metrics Symposium (METRICS'05)\",\"volume\":\"47 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2005-09-19\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"27\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"11th IEEE International Software Metrics Symposium (METRICS'05)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/METRICS.2005.25\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"11th IEEE International Software Metrics Symposium (METRICS'05)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/METRICS.2005.25","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Extending function point analysis to object-oriented requirements specifications
In practice, it is very important to determine the size of a proposed software system yet to be built based on its requirements, i.e., early in the development life cycle. Given a size estimate, it is usually possible to estimate the effort that will be needed to build this system. The most widely used approach to size estimation is function point analysis (FPA). It is not clear, however, how function points can be reasonably counted for object-oriented requirements specifications. We found that this cannot be done fully automatically, since several constructs of such a representation can be interpreted in various ways in the spirit of FPA, depending on the context. For applying FPA to object-oriented requirements specifications, we defined rules that specify a semi-automatic transformation from an object-oriented requirements model to an FPA model