{"title":"A pattern language for use case modeling","authors":"A. M. D. Cruz","doi":"10.5220/0004720204080414","DOIUrl":null,"url":null,"abstract":"Use case driven software development typically starts with abstract problem domain descriptions of how the users see themselves using the system being developed, and entails a series of iterative refinement steps that incrementally detail the user stories/use case model, in order to bring those descriptions to the solution domain. This process tends to produce overcrowded detailed use case models that are difficult to read, but that are essential to maintain a use case driven approach, during software construction/coding activities. Business applications typically comprise a set of functions that the users can make on the system. When a use case driven approach is used to develop business applications those typical business applications' functions pop-up as use case patterns. This paper presents a set of use case patterns that can be found in data-centered business applications, and proposes a use case pattern language that can be used together with standard UML use case language to facilitate the understanding of detailed use case models.","PeriodicalId":336046,"journal":{"name":"2014 2nd International Conference on Model-Driven Engineering and Software Development (MODELSWARD)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2014-01-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"9","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2014 2nd International Conference on Model-Driven Engineering and Software Development (MODELSWARD)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.5220/0004720204080414","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 9
Abstract
Use case driven software development typically starts with abstract problem domain descriptions of how the users see themselves using the system being developed, and entails a series of iterative refinement steps that incrementally detail the user stories/use case model, in order to bring those descriptions to the solution domain. This process tends to produce overcrowded detailed use case models that are difficult to read, but that are essential to maintain a use case driven approach, during software construction/coding activities. Business applications typically comprise a set of functions that the users can make on the system. When a use case driven approach is used to develop business applications those typical business applications' functions pop-up as use case patterns. This paper presents a set of use case patterns that can be found in data-centered business applications, and proposes a use case pattern language that can be used together with standard UML use case language to facilitate the understanding of detailed use case models.