Authors:
Edumilis Méndez
;
María Pérez
and
Luis E. Mendoza
Affiliation:
Universidad Simón Bolívar, Venezuela
Keyword(s):
Software testing, Test cases, Method, Test strategy, Use cases, Software test.
Related
Ontology
Subjects/Areas/Topics:
Enterprise Information Systems
;
Information Systems Analysis and Specification
;
Software Engineering
Abstract:
An interesting difference between tests and other disciplines of the software development process is that they constitute a task that essentially identifies and evidences the weaknesses of the software product. Four relevant elements are considered when defining tests namely, reliability, cost, time and quality. Time and cost shall increase to the extent reliable tests and quality software are desired, but what does it take to make actors understand that tests should be seen as a security network? If quality is not there before starting the tests, it will not be there upon their completion. Accordingly, how can we lay out a trace between tests and functional and non-functional requirements of the software system? This Article is aimed at proposing a method that allows for specifying test cases based on use cases, by incorporating elements to verify and validate traceability among requirements management, analysis & design, and tests. This initiative originated as a response to the re
quest of a software developing company of the Venezuelan public sector.
(More)