{"title":"用例建模指南","authors":"D. Firesmith","doi":"10.1109/TOOLS.1999.787548","DOIUrl":null,"url":null,"abstract":"Use case modeling has become the most popular de facto standard technique for performing software requirements analysis and specification. However, use case modeling has its well known problems, and different requirements engineers typically perform use case modeling differently. The paper provides a hierarchically organized set of detailed guidelines for use case modeling.","PeriodicalId":147966,"journal":{"name":"Proceedings of Technology of Object-Oriented Languages and Systems - TOOLS 30 (Cat. No.PR00278)","volume":"61 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1999-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"36","resultStr":"{\"title\":\"Use case modeling guidelines\",\"authors\":\"D. Firesmith\",\"doi\":\"10.1109/TOOLS.1999.787548\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Use case modeling has become the most popular de facto standard technique for performing software requirements analysis and specification. However, use case modeling has its well known problems, and different requirements engineers typically perform use case modeling differently. The paper provides a hierarchically organized set of detailed guidelines for use case modeling.\",\"PeriodicalId\":147966,\"journal\":{\"name\":\"Proceedings of Technology of Object-Oriented Languages and Systems - TOOLS 30 (Cat. No.PR00278)\",\"volume\":\"61 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1999-08-01\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"36\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Proceedings of Technology of Object-Oriented Languages and Systems - TOOLS 30 (Cat. No.PR00278)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/TOOLS.1999.787548\",\"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 of Technology of Object-Oriented Languages and Systems - TOOLS 30 (Cat. No.PR00278)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/TOOLS.1999.787548","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Use case modeling has become the most popular de facto standard technique for performing software requirements analysis and specification. However, use case modeling has its well known problems, and different requirements engineers typically perform use case modeling differently. The paper provides a hierarchically organized set of detailed guidelines for use case modeling.