TY - GEN
T1 - Support of scenario creation by generating event lists from conceptual models
AU - Goto, Kenta
AU - Ogata, Shinpei
AU - Shirogane, Junko
AU - Nakatani, Takako
AU - Fukazawa, Yoshiaki
PY - 2015/1/1
Y1 - 2015/1/1
N2 - In the requirements definition phase, conceptual models are used to understand the developing software. Although scenarios are often described on the basis of conceptual models, there are cases that necessary requirements are omitted in the scenarios when the scenarios are created manually. Herein we propose an approach to support scenario creation from conceptual models where event lists of scenarios, which include checkpoints to define requirements, are generated from conceptual models automatically. The conceptual models represent the core resources of the software, the owner of the core resources, and use cases as class diagrams. Then software engineers and their clients arrange the event lists and define requirements as scenarios on the basis of the checkpoints. Our approach can support describing scenarios with all the necessary requirements from conceptual models. To confirm the effectiveness of our approach, we compared our approach to the all-manual approach.
AB - In the requirements definition phase, conceptual models are used to understand the developing software. Although scenarios are often described on the basis of conceptual models, there are cases that necessary requirements are omitted in the scenarios when the scenarios are created manually. Herein we propose an approach to support scenario creation from conceptual models where event lists of scenarios, which include checkpoints to define requirements, are generated from conceptual models automatically. The conceptual models represent the core resources of the software, the owner of the core resources, and use cases as class diagrams. Then software engineers and their clients arrange the event lists and define requirements as scenarios on the basis of the checkpoints. Our approach can support describing scenarios with all the necessary requirements from conceptual models. To confirm the effectiveness of our approach, we compared our approach to the all-manual approach.
KW - Conceptual model
KW - Requirements definition
KW - Scenario
KW - Use case
UR - http://www.scopus.com/inward/record.url?scp=84939475837&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=84939475837&partnerID=8YFLogxK
U2 - 10.5220/0005327803760383
DO - 10.5220/0005327803760383
M3 - Conference contribution
AN - SCOPUS:84939475837
T3 - MODELSWARD 2015 - 3rd International Conference on Model-Driven Engineering and Software Development, Proceedings
SP - 376
EP - 383
BT - MODELSWARD 2015 - 3rd International Conference on Model-Driven Engineering and Software Development, Proceedings
A2 - Hammoudi, Slimane
A2 - Pires, Luis Ferreira
A2 - Desfray, Philippe
A2 - Filipe, Joaquim
A2 - Filipe, Joaquim
PB - SciTePress
T2 - 3rd International Conference on Model-Driven Engineering and Software Development, MODELSWARD 2015
Y2 - 9 February 2015 through 11 February 2015
ER -