{"title":"电子商务系统的需求工程:将Jackson问题图与目标建模和BPM集成","authors":"S. Bleistein, Karl Cox, J. Verner","doi":"10.1109/APSEC.2004.84","DOIUrl":null,"url":null,"abstract":"Jackson problem diagrams, goal modeling, and business process modeling (BPM) are employed in a requirements engineering approach that captures both business strategy and process requirements for e-business systems. As a means of linking abstract, high-level business requirements to low-level system requirements, we leverage the paradigm of projection in both problem diagrams and goal models simultaneously. We use Jackson context diagram to describe the business model domain context while goal modeling is used to represent both requirements and to describe the objectives of business strategy. Role activity diagrams are used to describe business processes in detail where needed. The feasibility of our approach is shown by a proof-of-concept case study.","PeriodicalId":213849,"journal":{"name":"11th Asia-Pacific Software Engineering Conference","volume":"828 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2004-11-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"29","resultStr":"{\"title\":\"Requirements engineering for e-business systems: integrating Jackson problem diagrams with goal modeling and BPM\",\"authors\":\"S. Bleistein, Karl Cox, J. Verner\",\"doi\":\"10.1109/APSEC.2004.84\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Jackson problem diagrams, goal modeling, and business process modeling (BPM) are employed in a requirements engineering approach that captures both business strategy and process requirements for e-business systems. As a means of linking abstract, high-level business requirements to low-level system requirements, we leverage the paradigm of projection in both problem diagrams and goal models simultaneously. We use Jackson context diagram to describe the business model domain context while goal modeling is used to represent both requirements and to describe the objectives of business strategy. Role activity diagrams are used to describe business processes in detail where needed. The feasibility of our approach is shown by a proof-of-concept case study.\",\"PeriodicalId\":213849,\"journal\":{\"name\":\"11th Asia-Pacific Software Engineering Conference\",\"volume\":\"828 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2004-11-30\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"29\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"11th Asia-Pacific Software Engineering Conference\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/APSEC.2004.84\",\"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 Asia-Pacific Software Engineering Conference","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/APSEC.2004.84","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Requirements engineering for e-business systems: integrating Jackson problem diagrams with goal modeling and BPM
Jackson problem diagrams, goal modeling, and business process modeling (BPM) are employed in a requirements engineering approach that captures both business strategy and process requirements for e-business systems. As a means of linking abstract, high-level business requirements to low-level system requirements, we leverage the paradigm of projection in both problem diagrams and goal models simultaneously. We use Jackson context diagram to describe the business model domain context while goal modeling is used to represent both requirements and to describe the objectives of business strategy. Role activity diagrams are used to describe business processes in detail where needed. The feasibility of our approach is shown by a proof-of-concept case study.