IMPROVING SOFTWARE TEST STRATEGY WITH A METHOD TO SPECIFY TEST CASES (MSTC)

Edumilis Méndez, María Pérez, Luis E. Mendoza

2008

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 request of a software developing company of the Venezuelan public sector.

References

  1. Kruchten P., The Rational Unified Process as Introduction (2nd Edition, Addison - Wesley, 2000.
  2. Leffingwell D. and Widrig D., 2006. Managing Software Requirements, a Use Case Approach (Second Edition, Addison-Wesley, Pearson Education, 2006.
  3. Grimán A., Pérez, M. and Mendoza L., 2003. Estrategia de pruebas para software OO que garantiza requerimientos no funcionales. III Workshop de Ingeniería de Software, Chillán, Chile. 1-10.
  4. Lewis W. 2000. Software testing and continuous quality improvement 000 by CRC Press LLC Auerbach is an Publisher of CRC Press LLC.
  5. Perry W. 2006. Effective Methods for Software Testing. Wiley. Third Edition.
  6. Pfleeger S. 1998, Software Engineering, Theory and Practice, Pretice-Hall.
  7. Pinkster I., Burgt B., Janssen D. and Veenendaal E. 2006. Successful Test Management. Springer and Logicacmg.
  8. Pressman R. 2002. Ingeniería del Software: Un enfoque Práctico, McGraw Hill, 2002).
  9. Sommerville I. 2000. Software Engineering. Pearson Education.
  10. SWEBOK. 2004. Guide to the Software Engineering Body of Knowledge 2004 Version. IEEE Computer Society.
  11. UML Testing Profile Version 1.0 formal/05-07-07. This is a testing profile for UML 2.0.
  12. Utting M. and Legeard B. 2007. Practical Model-based Testing. Morgan Kaufmann and Elsevier Publisher.
Download


Paper Citation


in Harvard Style

Méndez E., Pérez M. and E. Mendoza L. (2008). IMPROVING SOFTWARE TEST STRATEGY WITH A METHOD TO SPECIFY TEST CASES (MSTC) . In Proceedings of the Tenth International Conference on Enterprise Information Systems - Volume 1: ICEIS, ISBN 978-989-8111-36-4, pages 159-164. DOI: 10.5220/0001686501590164


in Bibtex Style

@conference{iceis08,
author={Edumilis Méndez and María Pérez and Luis E. Mendoza},
title={IMPROVING SOFTWARE TEST STRATEGY WITH A METHOD TO SPECIFY TEST CASES (MSTC)},
booktitle={Proceedings of the Tenth International Conference on Enterprise Information Systems - Volume 1: ICEIS,},
year={2008},
pages={159-164},
publisher={SciTePress},
organization={INSTICC},
doi={10.5220/0001686501590164},
isbn={978-989-8111-36-4},
}


in EndNote Style

TY - CONF
JO - Proceedings of the Tenth International Conference on Enterprise Information Systems - Volume 1: ICEIS,
TI - IMPROVING SOFTWARE TEST STRATEGY WITH A METHOD TO SPECIFY TEST CASES (MSTC)
SN - 978-989-8111-36-4
AU - Méndez E.
AU - Pérez M.
AU - E. Mendoza L.
PY - 2008
SP - 159
EP - 164
DO - 10.5220/0001686501590164