{"title":"Integrating Use Cases and Organizational Modeling","authors":"V. Santander, J. Castro","doi":"10.5753/sbes.2002.23949","DOIUrl":null,"url":null,"abstract":"The object oriented development paradigm has attracted many supporters in the Software Engineering community. One of the most important advances was the Unified Language Modeling (UML), a standard for visual modeling. Use Case Diagrams have been used for capturing system functional requirements. However, the system development occurs in a context where organization processes are well established. Therefore, we need to capture organizational requirements to define how the system fulfils the organization’s goals, why it is necessary, what are the possible alternatives, what are the implications to the involved parts, etc. Unfortunately, UML is ill equipped for modeling organizational requirements. We need other techniques, such as i*, to represent these aspects. Nevertheless, organizational requirements must be related to functional requirements represented as Use Cases. In this paper we present some guidelines to assist requirement engineers in the development of Use Cases from the organizational models represented by the i* technique.","PeriodicalId":219161,"journal":{"name":"Anais do XVI Simpósio Brasileiro de Engenharia de Software (SBES 2002)","volume":"4 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2002-10-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"1","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Anais do XVI Simpósio Brasileiro de Engenharia de Software (SBES 2002)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.5753/sbes.2002.23949","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 1
Abstract
The object oriented development paradigm has attracted many supporters in the Software Engineering community. One of the most important advances was the Unified Language Modeling (UML), a standard for visual modeling. Use Case Diagrams have been used for capturing system functional requirements. However, the system development occurs in a context where organization processes are well established. Therefore, we need to capture organizational requirements to define how the system fulfils the organization’s goals, why it is necessary, what are the possible alternatives, what are the implications to the involved parts, etc. Unfortunately, UML is ill equipped for modeling organizational requirements. We need other techniques, such as i*, to represent these aspects. Nevertheless, organizational requirements must be related to functional requirements represented as Use Cases. In this paper we present some guidelines to assist requirement engineers in the development of Use Cases from the organizational models represented by the i* technique.