Software Component Testing

Method Purpose Short description of the method's purpose and main benefits

Method description A detailed description of the method

Boundary and structure-based tests are to be executed to detect specific software errors. Depending on the Hardware/Software design, unit testing might be taken into account, too, with several different classes of testing, such as equivalence class and input partition, model-based test case generation and so on. The latter testing class that will be performed is the performance testing (stress tests, response timings, etc.), to ensure that the working capacity of the system is sufficient to meet the specified requirements

Method Strengths A listof the strengths of the method

Enabler of Continuous Integration
Enable Regression Tests
Design and implementation faults detection
Avoids poor coding related unexpected behaviours

Method Limitations The limitations of the method

Code overhead
Time consuming
Test personnel must be different from develop

Method References Bibliography references to papers about the method.

Kim HK., Kwon OH. (2005) SCTE: Software Component Testing Environments. In: Gervasi O. et al. (eds) Computational Science and Its Applications – ICCSA 2005. ICCSA 2005. Lecture Notes in Computer Science, vol 3481. Springer, Berlin, Heidelberg. https://doi.org/10.1007/11424826_15

Franz F. (2008) Experiences with Evolutionary Timing Test of Automotive Software Components. In: Margaria T., Steffen B. (eds) Leveraging Applications of Formal Methods, Verification and Validation. ISoLA 2008. Communications in Computer and Information Science, vol 17. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-88479-8_29

Gao J.Z., Wu Y. (2004) Testing Component-Based Software – Issues, Challenges, and Solutions. In: Kazman R., Port D. (eds) COTS-Based Software Systems. ICCBSS 2004. Lecture Notes in Computer Science, vol 2959. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-24645-9_2

Method Dimensions

Evaluation Environment Type Type of environment where the method is applied. It can be more than one type of environment. (Dimension 1)

Evaluation Type Type of evaluation performed with that method. If a method is hybrid, more than one type can be selected. (Dimension 2)

Type of Component Under Evaluation Type of components that can be evaluated with that method. It can be more than one type. (Dimension 3)

Evaluation Stage The evaluation stage where the method is used. (Dimension 5)

Purpose of the Component Under Evaluation The type of purpose that can be evaluated by a method. It can be more than one type. (Dimension 6)

Type of Requirement Under Evaluation The type of requirements that a method is able to evaluate. It can be more than one type. (Dimension 7)

Evaluation Performance Indicator The type of evaluation criteria or KPI that a method is able to improve. It can be more than one type. (Dimension 8)

Relations

Related Methods A method could be related to other methods.

Tools A method can use zero or more tools.

Part Method A method (when it is a combination: Combination of method artefact that is a specialization of a V&V Method) could be composed of a set of V&V Methods.

Test Case or Verification and Validation activity Test Case or V&V activity performed in a Use Case. We will link to the method to the test cases where the method is used.

Standards A method can be linked with standards.

Context

Workflow

Contents

There are currently no items in this folder.