{"title":"使用依赖关系图弥合分析和设计之间的差距","authors":"S. Vasilache, J. Tanaka","doi":"10.1109/SERA.2005.27","DOIUrl":null,"url":null,"abstract":"Requirements specifications often make use of a number of scenarios that are interrelated and that depend on each other in many ways. However, they are often treated separately, one by one. We propose a new type of diagrams, named dependency diagrams, which are able to illustrate the various kinds of relationships existing between scenarios. We make use of a scenario matrix for each scenario and we describe the transformation process of scenarios into state machines, based on the information in the scenario matrices, and that in the dependency diagrams. The result is a number of state machines that can be used for detailed design models and code can further be generated from them. Using our approach, we can bridge the gap between analysis and design and we can bring the developer one step closer to the implementation.","PeriodicalId":424175,"journal":{"name":"Third ACIS Int'l Conference on Software Engineering Research, Management and Applications (SERA'05)","volume":"39 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2005-08-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"2","resultStr":"{\"title\":\"Bridging the gap between analysis and design using dependency diagrams\",\"authors\":\"S. Vasilache, J. Tanaka\",\"doi\":\"10.1109/SERA.2005.27\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Requirements specifications often make use of a number of scenarios that are interrelated and that depend on each other in many ways. However, they are often treated separately, one by one. We propose a new type of diagrams, named dependency diagrams, which are able to illustrate the various kinds of relationships existing between scenarios. We make use of a scenario matrix for each scenario and we describe the transformation process of scenarios into state machines, based on the information in the scenario matrices, and that in the dependency diagrams. The result is a number of state machines that can be used for detailed design models and code can further be generated from them. Using our approach, we can bridge the gap between analysis and design and we can bring the developer one step closer to the implementation.\",\"PeriodicalId\":424175,\"journal\":{\"name\":\"Third ACIS Int'l Conference on Software Engineering Research, Management and Applications (SERA'05)\",\"volume\":\"39 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2005-08-11\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"2\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Third ACIS Int'l Conference on Software Engineering Research, Management and Applications (SERA'05)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/SERA.2005.27\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Third ACIS Int'l Conference on Software Engineering Research, Management and Applications (SERA'05)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/SERA.2005.27","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Bridging the gap between analysis and design using dependency diagrams
Requirements specifications often make use of a number of scenarios that are interrelated and that depend on each other in many ways. However, they are often treated separately, one by one. We propose a new type of diagrams, named dependency diagrams, which are able to illustrate the various kinds of relationships existing between scenarios. We make use of a scenario matrix for each scenario and we describe the transformation process of scenarios into state machines, based on the information in the scenario matrices, and that in the dependency diagrams. The result is a number of state machines that can be used for detailed design models and code can further be generated from them. Using our approach, we can bridge the gap between analysis and design and we can bring the developer one step closer to the implementation.