Approaches analyzed. Title References Key

Transcription

1 Approaches analyzed. Title References Key Requirements to Testing in a Natural Way [Boddu04], [Henriksen95] RETNA Requirements by Contract [Nebut03], [Nebut04] RBC PLUTO y Category Partition Method [Bertolino02], [Bertolino03], PLUTO [Bertolino03], [Ostrand88], [Balcer90] A UML-Based Approach to System Testing [Labiche02] TOTEM Derivation of Domain Test Scenarios from Activity [Reuys03], [Ruder04], [Ruder04-02] TDEUML Diagrams. Automated Test Case Generation from Dynamic Models [Frölich00], [Fikes71], [Frölich99] ATCGDM Test Cases from Use Cases [Heumann02] TCUC Scenario-Based Validation and Test of Software (SCENT) [Ryser03], [Glinz99], [Itschner98] SCENT Requirement Base Testing [Mogyorodi01], [Mogyorodi02], RBC [Mogyorodi03]. Software Requirements and Acceptance Testing [Hsia94], [Hsia95], [Hsia97] AT Testing from Use Cases Using Path Analysis Technique [Naresh02] UCPA Use Case Derived Test Cases [Wood02] UCDTC Extended Use Case Test Design Patter [Binder00] EUC

2 ATCGDM SCENT TCUC UCPA PLUTO RBC TOTEM RBT EUC AT UCDTC TDEUML RETNA Starting point Use cases User needs Use cases Use cases Use cases (17) Use cases Several (13) Use cases Use cases User needs Use cases Use cases User needs New notation No Yes No Yes No Yes (11) Yes (12) No No Yes (2) No Yes (3) No Graphical Yes Yes No Yes No Yes Yes Yes No Yes No Yes No notation Case study No Yes No No No No No No No Yes No No No Use of standards Yes No No No No Yes Yes Yes (8) No No Yes Yes Yes Tools Yes (14) No No No Yes (15) Yes No Yes (9) No No No Yes (9) Yes Practical cases Yes Yes Yes Yes Yes Yes Yes No Yes Yes Yes Yes Yes Coverage Several (6) Path analysis Path analysis Path analysis Category Several Several No (10) Path analysis Several Path analysis Several Path analysis criterion partition Test values No No No No Yes No No No Yes No No Yes No Test case selection No No No Yes Yes Yes No No IEEE** No No No No Use case Yes Yes No No Yes Yes Yes No No Yes No No Not indicated dependences Behavioural Yes Yes No Yes No Yes Yes Yes No Yes No Yes Yes model Use case priority No No No Yes Yes No Yes No No No No Yes Yes Active approach (5)? No??? Yes No???? Yes No Starting time Requirements Requirements Requirements Requirements Requirements Requirements Analysis Requirements Requirements (18) Requirements (16) Requirements Requirements Requirements Results Test scenarios for each use Transition sequences Test models and test cases Test models Executable test scripts Executable test scripts case language language language language among use cases language language language Quality of Medium Medium Medium Medium Medium Medium High (7) Low Medium Low Low Medium (4) Low documentation Test case implementation * Previous experience * Use case format * Activities (1)

3 Year / / * - Not included in the original report.. ** - Included in Binder s book and [Srivastaba97].

4 (1) 15 activities to derive scenarios and 3 activities to derive test cases. (2) A notation for use trees and another for finite state machines. (3) It defines its own stereotypes for UML activity diagrams. (4) Although there is enough documentation, the approach has been designed to be used with supporting tools. (5)? means that we cannot contact with authors. (6) All status or all transitions. (7) However is hard to put it in practices due documentation is incomplete. (8) We assume that cause-effect diagrams are a wide used tool. (9) It is not available an evaluation or educative version. (10) Coverage criterion have been directly implemented into supporting tool. We have not find any rereference to that criterion. (11) Use-case transition diagrams. (12) It defines a textual notation to represent sequences of use case executions. (13) UML Use case diagrams, textual descriptions of use cases, sequence diagrams or collaboration for every use case, domain classes diagram, data dictionary with descriptions for every class, method and attribute and restriction in OCL. (14) Planning tools base don STRIPS. (15) Tools to generate test templates. (16) Alter elicitation, verification and validation of requirements. (17) For product families (18) Stable requirements.

5 Investigation institutes International Institute for Software Technology. Istituto di Scienza e Tecnologie dell'informazione "Alessandro Faedo" Fraunhofer Institute Computer Architecture and Software Technology Publications [STJ] The Journal of Software Testing, Verification and Reliability. [StickyMinds] StickyMinds Website. [BetterSoftware] The Better Software Magazine. [JournalSoftware] The Journal of Software Testing Professionals. References [Balcer90] M. Balcer, W. Hasling, and T. Ostrand Automatic Generation of Test Scripts from Formal Test Specifications. Proceedings of ACM SIGSOFT'89 - Third Symposium on Software Testing, Verification, and Analysis (TAVS-3), ACM Press, pp [Bertolino02] Bertolino, A., Fantechi, A., Gnesi, S., Lami, G., Maccari, A. Use Case Description of Requirements for Product Lines, REPL 02, Essen, Germany, Avaya Labs Tech. Rep. ALR [Bertolino03] Bertolino, A., Gnesi, S Use Case-based Testing of Product Lines. ESEC/FSE 03. Helsinki, Finland.

6 [Bertolino04] Bertolino, A., Gnesi, S PLUTO: A Test Methodology for Product Families. Lecture Notes in Computer Science. Springer-Verlag Heidelberg / pp [Binder00] Robert V. Binder. Testing Object-Oriented Systems. Addison-Wesley. USA. [Boddu04] Boddu R., Guo L., Mukhopadhyay S RETNA: From Requirements to Testing in Natural Way. 12th IEEE International Requirements Engineering RE 04. [Fikes71] R. E, Fikes, N. J. Nilsson. STRIPS: a new approach to the application of theorem proving to problem solving. Artificial Intelligence 2, [Fröhlich00] Fröhlich, P, Link, J Automated Test Case Generation from Dynamic Models. ECOOP pp [Fröhlich99] Fröhlich, P, Link, J Modelling Dynamic Behaviour Based on Use Cases. Proceedings of Quality Week Europe. Brussels. [Glinz99] Martin Glinz, Johannes Ryser A Practical Approach to Validating and Testing Software Systems Using Scenarios Quality. Week Europe QWE'99 in Brussels, Institut für Informatik, Universität Zürich. [Henriksen95] Henriksen J. G., el-al Mona: Monadic Second-Order Login in Practice. TACAS 95. [Heumann02] Heumann, Jim, Generating Test Cases from Use Cases. Journal of Software Testing Professionals. [Hsia94] Hsia, P, et-al A Formal Approach to Scenario Analysis. IEEE Software 11, 2, [Hsia95] Hsia, P, et-al A Usage-Model Based Approach to Test the Therac-25. Safety and Reliability in Emerging Control Technologies. IFAC Workshop. Pp Florida. USA. [Hsia97] Hsia, P, et-al Software Requirements and Acceptance Testing. Anuals of software Engineering. Pag [Itschner98] R. Itschner, C. Pommerell, M. Rutishauser, "GLASS: Remote Monitoring of Embedded Systems in Power Engineering," IEEE Internet Computing, vol. 2, # 3, pp , [Labiche02] L. Briand, Y. Labiche A UML-Based Approach to System Testing. Carleton University Inner Report. [Mogyorodi01] Gary Mogyorodi Requirements-Based Testing: An Overview. 39th International Conference and Exhibition on Technology of Object- Oriented Languages and Systems (TOOLS39). pp [Mogyorodi02] Gary E. Mogyorodi Requirements-Based Testing: Ambiguity Reviews. Journal of Software Testing Professionals. p [Mogyorodi03] Gary E. Mogyorodi.What Is Requirements-Based Testing?. 15th Annual Software Technology Conference. Apr. 28-May 1. Salt Lake City, USA [Naresh02] Ahlowalia, Naresh Testing From Use Cases Using Path Analysis Technique. International Conference On Software Testing Analysis & Review. [Nebut03] Nebut, C. Fleurey, et-al Requirements by contract allow automated system testing. Procedings of the 14th International symposium of Software Reliability Engineering (ISSRE'03). Denver, Colorado. EEUU.

7 [Nebut04] Nebut, C. Fleurey, et-al A Requirement-Based Approach to Test Product Families. LNCS. pp [Ostrand88] Ostrand, TJ, Balcer, MJ Category-Partition Method. Comunications of the ACM [Denger03] Denger, C. Medina M Test ase Derived from Requirement Specifications. Fraunhofer IESE Report. [RAISE92] The RAISE Language Group. The RAISE Specification Language. BCS Practitioner Series.Prentice Hall, [RAISE95] The RAISE Method Group. The RAISE Development Method. BCS Practitioner Series. Prentice Hall, [RBCTool] UCTSystem. [Riebisch03] Matthias Riebisch, Ilka Philippow, Marco Götze Ilmenau UML-Based Statistical Test Case Generation. Technical University, Ilmenau, Germany [Robinson00] Robinson, Harry Intelligent Test Automation. Software Testing & Quality Engineering. Pp [Ruder04] Axel Ruder et-al A Model-based Approach to Improve System Testing of Interactive Applications. ISSTA 04. Boston, USA. [Ruder04-2] Axel Ruder UML-based Test Generation and Execution. Rückblick Meeting. Berlin. [Ryser03] Johannes Ryser, Martin Glinz Scent: A Method Employing Scenarios to Systematically Derive Test Cases for System Test. Technical Report 2000/03, Institut für Informatik, Universität Zürich. [Srivastaba97] Srivastava V. K Experience with the Use of Standard IEEE on Software Programming. IEEE. Pp [Wood02] Wood D., Reis J Use Cased Derived Test Cases. StickyMind.