Bridging the gap between analysis and design using dependency diagrams

Simona Vasilache, Jiro Tanaka

Research output: Chapter in Book/Report/Conference proceedingConference contribution

1 Citation (Scopus)

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, ne 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.

Original languageEnglish
Title of host publicationProceedings - Third ACIS International Conference on Software Engineering Research, Management and Applications, SERA 2005
Pages407-414
Number of pages8
DOIs
Publication statusPublished - 2005 Dec 1
Externally publishedYes
Event3rd ACIS International Conference on Software Engineering Research, Management and Applications, SERA 2005 - Mount Pleasant, MI, United States
Duration: 2005 Aug 112005 Aug 13

Publication series

NameProceedings - Third ACIS International Conference on Software Engineering Research, Management and Applications, SERA 2005
Volume2005

Other

Other3rd ACIS International Conference on Software Engineering Research, Management and Applications, SERA 2005
CountryUnited States
CityMount Pleasant, MI
Period05/8/1105/8/13

ASJC Scopus subject areas

  • Engineering(all)

Fingerprint Dive into the research topics of 'Bridging the gap between analysis and design using dependency diagrams'. Together they form a unique fingerprint.

Cite this