![](bg8.png)
from activity diagrams, which are generated
intermediate models; intermediate models are built
to identify and refine input and output variables;
these tasks are automated, but they could be
expensive and time consuming; objects created and
changed by activities are considered as test
information. Yan et al. (2006) generated test
scenarios from BPEL (Business Process Execution
Language) specifications; the scenario explosion
problem is solved using path combination and
exclusive paths strategies, communication
interactions are not considered. Katayama et al.
(1999) proposed an approach to generate test cases
based on Event InterActions Graph and Interaction
Sequence Testing Criterion, graph model represents
the behavior of concurrent programs and the
different interactions among unit programs.
Most of approaches to derive test cases are based
on path analysis of semi-formal behaviour models.
There are no systematic approaches to derive test
cases from natural language requirements
descriptions - use cases or scenarios and which use
the relevant words (shared resources) of the
application - lexicon to identify concurrent task
interactions and reduce the test scenarios. Our
approach derives test cases from scenarios, the input
variables, conditions, expected results and
concurrent tasks are identified and described before
the derivation of intermediate models (graphs); and
the reduction of test scenarios number is based on
task interactions by shared resources.
7 CONCLUSIONS
Our approach provides benefits due to the following
reasons: (1), it is capable to detect interaction errors
among concurrent tasks more comprehensively than
the existing approaches. (2), it derives test cases from
requirements descriptions based on semi-structured
natural language, existing approaches are based on
semi-formal models. (3), it reduces the number of
test scenarios generated for concurrent applications.
(4), it starts with the software development process
and these processes are carried out concurrently.
In our approach each concurrent sub-path has a
single action; future work will be considered sub-
paths containing a flow of actions.
In the future, we plan to deal with: (1) Testing of
exceptions and non-functional requirements
(constraints/conditions on resources); in this work
was shown some criteria for mapping exceptions and
non-functional requirements descriptions to behavior
models and testing. (2) Reduction of test scenarios
number based on precedence (interleaving); our
approach make explicit the interactions among
concurrent tasks; however, shared resources could
enforces a precedence order, e.g., when a task
depends on a signal sent from other task to notify
that a variable was updated (communications). (3)
An automated tool that implements our approach is
being developed (C&L - http://pes.inf.puc-rio.br/cel)
to support the proposed strategy.
REFERENCES
Binder, R. V., 2000. Testing object-oriented systems.
Addison-Wesley.
Cockburn, A.,2001. Writing Effective Use Cases.
Addison-Wesley.
Damas, C., Lambeau, B., Dupont, P. and Lamsweerde, A.
v., 2005. Generating annotated behavior models from
end-user scenarios. IEEE TSE, volume 31, number 12.
Debasish, K. and Debasis, S., 2009. A novel approach to
generate test cases from UML activity diagrams.
Journal of Object Technology, volume 8, number 3.
Denger, C. and Medina, M., 2003. Test Case Derived from
Requirement Specifications, Fraunhofer IESE Report.
Gutiérez, J. J., Escalona, M. J., Mejías, M. and Torres, J.,
2006. An approach to generate test cases from use
cases, Proceedings of the 6th International Conference
on Web Engineering, pages 113-114.
Heitmeyer, C., 2007. Formal methods for specifying,
validating, and verifying requirements. J Univ Comput
Sci, volume 13, number 5, pages 607-618.
Heumann, J.,2001 Generating test Cases from use cases IBM
Katayama, T., Itoh, E. and Furukawa, Z., 1999. Test-case
generation for concurrent programs with the testing
criteria using interaction sequences. Asia-Pacific
Software Engineering Conference.
Khandai, M., Acharya, A. and Mohapatra, D., 2011. A
Novel Approach of Test Case Generation for
Concurrent Systems Using UML Sequence Diagram.
ICECT, 6, pages 157-161.
Kim, H., Kang, S., Baik, J., Ko, I., 2007. Test Cases
Generation from UML Activity Diagrams. In 8
th
ACIS
International Conference on Software Engineering,
Artificial Intelligence, Networking, and Parallel/
Distributed Computing, pages 556-561.
Leite, J. C. S. P., Hadad, G., Doorn, J. and Kaplan, G.,
2000. A scenario construction process. Requirements
Engineering Journal, Springer-Verlag London Limited,
volume 5, number 1, pages 38-61.
Letier, E., Kramer, J., Magee, J. and Uchitel, S., 2005.
Monitoring and Control in Scenario-based
Requirements Analysis. ICSE.
Sabharwal, S., Sibal, R. and Sharma, C., 2011. "Applying
Genetic Algorithm for Prioritization of Test Case
Scenarios Derived from UML Diagrams". IJCSI, 8.
Sapna, P. G. and Hrushikesha, M., 2008. Automated
Scenario Generation Based on UML Activity
ICEIS2014-16thInternationalConferenceonEnterpriseInformationSystems
346