Integration and evolution method of scenarios from different viewpoints
Z. Hui, and A. Ohnishi. International Workshop on Principles of Software Evolution, page 183--188. (2003)
Abstract
Scenarios that describe concrete behaviors of software play an important
role in software development and especially in requirements engineering.
Scenario details should vary in content when described from different
viewpoints. In such a case, scenarios from different viewpoints
may result in inconsistencies. It is hard to detect the inconsistency
between scenarios automatically, when scenarios are described informally.
Furthermore, scenarios are evolutionary, and it requires a great
deal of labor to evolve each scenario. We present an integration
method to detect the inconsistency between scenarios from different
viewpoints and to provide support for scenario evolution by generating
new scenarios from an integrated scenario. We illustrate them using
the example of program chair's job.
International Workshop on Principles of Software Evolution
year
2003
journal
Software Evolution, 2003. Proceedings. Sixth International Workshop
on Principles of
pages
183--188
comment
- support scenario integration - support evolution of various scenarios
- scenarios are sequences of actions - why are "events within the
action frame independent of a certain viewpoint"? Isn't this the
very point of scenarios? That the actions involved aren't independent?
- evolve: either the merged scenarios as a whole, or one by one
(obviously). A is faster.
%0 Conference Paper
%1 hui03c
%A Hui, Z. H.
%A Ohnishi, A.
%B International Workshop on Principles of Software Evolution
%D 2003
%J Software Evolution, 2003. Proceedings. Sixth International Workshop
on Principles of
%K viewpoints evolution requirements
%P 183--188
%T Integration and evolution method of scenarios from different viewpoints
%U http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=1231225
%X Scenarios that describe concrete behaviors of software play an important
role in software development and especially in requirements engineering.
Scenario details should vary in content when described from different
viewpoints. In such a case, scenarios from different viewpoints
may result in inconsistencies. It is hard to detect the inconsistency
between scenarios automatically, when scenarios are described informally.
Furthermore, scenarios are evolutionary, and it requires a great
deal of labor to evolve each scenario. We present an integration
method to detect the inconsistency between scenarios from different
viewpoints and to provide support for scenario evolution by generating
new scenarios from an integrated scenario. We illustrate them using
the example of program chair's job.
@inproceedings{hui03c,
abstract = {Scenarios that describe concrete behaviors of software play an important
role in software development and especially in requirements engineering.
Scenario details should vary in content when described from different
viewpoints. In such a case, scenarios from different viewpoints
may result in inconsistencies. It is hard to detect the inconsistency
between scenarios automatically, when scenarios are described informally.
Furthermore, scenarios are evolutionary, and it requires a great
deal of labor to evolve each scenario. We present an integration
method to detect the inconsistency between scenarios from different
viewpoints and to provide support for scenario evolution by generating
new scenarios from an integrated scenario. We illustrate them using
the example of program chair's job.},
added-at = {2006-09-18T06:26:07.000+0200},
author = {Hui, Z. H. and Ohnishi, A.},
biburl = {https://www.bibsonomy.org/bibtex/2c7be5353cc79cda570fcfff3d5d568a4/neilernst},
booktitle = {International Workshop on Principles of Software Evolution},
citeulike-article-id = {638231},
comment = {- support scenario integration - support evolution of various scenarios
- scenarios are sequences of actions - why are "events within the
action frame independent of a certain viewpoint"? Isn't this the
very point of scenarios? That the actions involved aren't independent?
- evolve: either the merged scenarios as a whole, or one by one
(obviously). A is faster.},
description = {Not previously uploaded},
interhash = {8cb65c1af1ed21fdf67eca8402e4feed},
intrahash = {c7be5353cc79cda570fcfff3d5d568a4},
journal = {Software Evolution, 2003. Proceedings. Sixth International Workshop
on Principles of},
keywords = {viewpoints evolution requirements},
pages = {183--188},
priority = {0},
timestamp = {2006-09-18T06:26:07.000+0200},
title = {Integration and evolution method of scenarios from different viewpoints},
url = {http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=1231225},
year = 2003
}