{"title":"通过使用用例概念向面向对象的需求规范迈进","authors":"B. Dano, H. Briand, F. Barbier","doi":"10.1109/ECBS.1996.494573","DOIUrl":null,"url":null,"abstract":"The paper describes an approach to support the requirements engineering process. The proposed approach is based on the concept of use case which serves as a basis for the acquisition and the conceptualization of requirements not yet elaborated, the goal being to establish object-oriented requirements specifications and more precisely dynamic ones. The approach is \"domain expert-oriented\" in the sense that the domain expert can actively participate during the acquisition activity by identifying and by describing the use cases. In order to help the analyst understand the use cases and to assist him during the conceptualization activity, a formalization of the use case concept is proposed. Some solutions to detect incomplete and inconsistent requirements are also presented.","PeriodicalId":244671,"journal":{"name":"Proceedings IEEE Symposium and Workshop on Engineering of Computer-Based Systems","volume":"59 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1996-03-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"11","resultStr":"{\"title\":\"Progressing towards object-oriented requirements specifications by using the use case concept\",\"authors\":\"B. Dano, H. Briand, F. Barbier\",\"doi\":\"10.1109/ECBS.1996.494573\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"The paper describes an approach to support the requirements engineering process. The proposed approach is based on the concept of use case which serves as a basis for the acquisition and the conceptualization of requirements not yet elaborated, the goal being to establish object-oriented requirements specifications and more precisely dynamic ones. The approach is \\\"domain expert-oriented\\\" in the sense that the domain expert can actively participate during the acquisition activity by identifying and by describing the use cases. In order to help the analyst understand the use cases and to assist him during the conceptualization activity, a formalization of the use case concept is proposed. Some solutions to detect incomplete and inconsistent requirements are also presented.\",\"PeriodicalId\":244671,\"journal\":{\"name\":\"Proceedings IEEE Symposium and Workshop on Engineering of Computer-Based Systems\",\"volume\":\"59 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1996-03-11\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"11\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Proceedings IEEE Symposium and Workshop on Engineering of Computer-Based Systems\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/ECBS.1996.494573\",\"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 IEEE Symposium and Workshop on Engineering of Computer-Based Systems","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ECBS.1996.494573","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Progressing towards object-oriented requirements specifications by using the use case concept
The paper describes an approach to support the requirements engineering process. The proposed approach is based on the concept of use case which serves as a basis for the acquisition and the conceptualization of requirements not yet elaborated, the goal being to establish object-oriented requirements specifications and more precisely dynamic ones. The approach is "domain expert-oriented" in the sense that the domain expert can actively participate during the acquisition activity by identifying and by describing the use cases. In order to help the analyst understand the use cases and to assist him during the conceptualization activity, a formalization of the use case concept is proposed. Some solutions to detect incomplete and inconsistent requirements are also presented.