Content uploaded by Vijay Kumar Damera
Author content
All content in this area was uploaded by Vijay Kumar Damera on Apr 21, 2023
Content may be subject to copyright.
Int’l Conf. on Computer & Communication TechnologyŇICCCT’10Ň
__________________________________
978-1-4244-9034-/10/$26.00©2010 IEEE 562
A Systematic Literature Survey of Integration Testing in Component-Based
Software Engineering
S Phani Shashank
Student: dept. of CSSE
Andhra University
Vizag, India
Saripalli.phani@gmail.com
Praneeth Chakka
Student: dept. of CSSE
Andhra University
Vizag, India
praneethch@gmail.com
D Vijay Kumar
Assistant Professor
MGIT
Hyderabad, India
dameravijay@yahoo.com
Abstract— Component-based software engineering (CBSE)
has emerged as an approach that offers rapid
development of system using fewer resources and effort.
The core idea of reuse and cutting down the development
costs can be achieved if the components offer reliable
services. Thus, integration components and testing become an
important phase in CBSE. Integration of components is a
very important activity. This involves understanding
communication and coordination between the components.
Developers are not provided with sufficient information
on these components. As a result of this,
understanding data flow while integrating these components is
a challenge. Component-based software facilitates
development of complex systems by allowing integration of
reusable components. Testing components is a challenging area
of research. There have been troubles integrating the
components. This in turn affects the quality and reliability of
the software. Our research aims at finding the existing
integration testing and challenges in CBSE. The systematic
literature survey is based on 49 articles collected from
multiple-stage selection process. These articles have been
published within the time span of 1995-2009.
I. I
NTRODUCTION
Testing, like inspection is often done as part of
verification. During the development of a system, 50
percent of the time and more than 50 percent of the
total cost are expended for testing [35]. So it is of utmost
importance to test a system to cut unnecessary cost and time.
In the recent past, Component Based Software Engineering
(CBSE) has gained a very high importance. This is attributed
to the reduction of cost and time in building the software
using reusable components. A component is generally
defined as a piece of executable software with a published
interface [28]. The identified advantages of CBSE:
Reduced lead time, enhanced quality, Maintenance of
Component-based applications are explained in [30].
Developers are not provided with sufficient
information on these components [31]. Reliance
of components introduces problems of testing [19]. Testing
components is a challenging area of research. Existing body
of knowledge in this field tells there are problems in
integrating the component [29]. Overall our research
mission is to find and scrutinize the current techniques and
issues in Integration Testing in CBSE. This will be a good
starting point in furthering the research. In this research we
aim at conducting a systematic literature survey of the state
of the art in Integration Testing in CBSE. The most crucial
aspect for a researcher is to have adequate knowledge of
what has been produced in the area of interest. Performing a
literature search helps define an unsolved problem [51]. We
will follow the Research process explained in [51]. In
section 2, we describe the method we followed for
systematic survey. It includes our research questions, search
strategy, inclusion/exclusion criteria in selection of
the articles, and quality assessment of the articles. In Section
3 we discuss our results. Sections 4 and 5 contain discussion
on future work and validity threats in our research.
Conclusions are presented in Section 6.
II. R
ESEARCH METHOD
In doing the systematic literature survey we followed the
guidelines provided by Kitchenham [50]. According to [50],
a systematic literature survey is a systematic process of
finding and assessing the available research related to
particular questions of interest. An important reason for
undertaking such a study is to identify areas of further
investigation/research.
A. Research Questions we formulated the following
objectives.
1) Survey of existing integration testing techniques for
CBSE.
2) Understand the issues and challenges in CBSE.
3) Compare the existing techniques and find scope for
overcoming the challenges.
4) Identify the issues in determining the testability of
components.
5) A document containing a formal report of the above
mentioned objectives.
To get good understanding of the above mentioned, we
formulated research questions. These are as follows.
Int’l Conf. on Computer & Communication TechnologyŇICCCT’10Ň
563
RQ1) What is the state of art in integration testing of
software components?
SQ1) What are the different phases in testing CBSE?
SQ2) What are the existing techniques?
SQ3) What are the challenges in integrated testing in
CBSE?
RQ2) How is testability of components determined?
SQ4) What data is needed to understand the behavior of
the components?
SQ5) What are the key issues and challenges in analyzing
the components interaction?
B. Search Strategy
Our search strategy is based on the following.
1) Identification of search terms to find articles that relate to
our research questions. The search terms alternate words
and synonyms. The following search terms are used in our
search strategy – component-based software, component
based software, integration testing, integration testing
techniques, COTS, components, challenges, testing
challenges, testability, components behavior(u)r, interaction,
components interaction.
2) Use of Boolean AND to join the search terms and use of
Boolean OR to join synonyms/alternate words.
3) We used a multiple-phase strategy for searching. Firstly,
we searched electronic databases. We chose the 1995 as the
starting year of search. We searched within the following
two electronic databases:
- IEEEXplore.
- ACM Digital Library.
To limit the number of articles in every search, we selected
the articles available in full text. We then selected the
articles based on abstract. In the second stage, we scanned
references and selected a few that were available in the
above mentioned journals only.
C. Inclusion/Exclusion criteria
CBSE is a vast field of research. To limit our
research to software testing, i.e. in accordance with our
research questions we formulated criteria to include and
exclude articles in our study. We applied the following
inclusion criteria.
- Published within the time span of 1995 – 2009
- Article available in full text
- Articles can be on controlled experiments, literature survey
or industrial practice
- Articles on models or frameworks for testing
- Articles evaluating on existing models or extending the
models
We applied the following exclusion criteria.
- Articles not related to Software Engineering/Computer
Science
- Articles that do not match the inclusion criteria
- Articles not related to Software Testing
- Articles on test plan
- Articles on Metrics
- Articles on Maintenance
- Articles on Service oriented software systems, Object-
oriented software systems
- Articles on software testing tools
Table 1 shows the results of our preliminary search before
applying inclusion criteria is
TABLE I. P
RELIMINARY SEARCH RESULT
Journal Count
IEEE 820
ACM 769
After applying detailed Inclusion/Exclusion criteria we were
left with 32 articles. Table 2 shows the distribution of the
papers.
TABLE II. S
EARCH RESULT AFTER
E
XCLUSION
/I
NCLUSION CRITERIA
Journal Count
IEEE 20
ACM 12
In the second stage of the search, we scanned the references
and we selected 17 articles. Table 3 shows the distribution
of the papers.
TABLE III. F
INAL S EARCH RESUL T
Journal Count
IEEE 15
ACM 2
D. Quality assessment
Quality data is essential in synthesis of the results [50]. We
applied the following criteria to select studies of good
quality.
- Is the reader able to understand the aims of the research?
- Is the context of study clearly stated?
- Is the study verified/ assumptions proved?
- Is the research useful to software industry/research
community?
- Are the conclusions related to the aim and the very purpose
of the goal of the research?
III. R
ESULTS
In this section, we describe the results of our search. We
classified the results into four parts. These are –
1) Testing Techniques
2) Testing Challenges
3) Testability
4) Challenges in Testability
Tables 4, 5, 6 and 7 show the distribution of papers
pertaining to the above classifications.
TABLE IV. D
ISTRIBUTION OF ARTICLES FOR
T
ESTING
T
ECHNIQUES
Author Year
ZHENYI ET AL. 1995 [52]
ZHENYI ET AL. 1996 [7]
HARTMANN ET AL. 2000 [36]
Int’l Conf. on Computer & Communication TechnologyŇICCCT’10Ň
564
YE ET AL. 2000 [53]
DELAMARO ET AL. 2001 [5]
WU ET AL. 2001 [19]
BEYDEDA ET AL. 2001 [54]
ATKINSON ET AL. 2002 [4]
BEYDEDA ET AL. 2003 [24]
BLUNDELL ET AL. 2005 [48]
GAO ET AL. 2005 [25]
CHENGYING ET AL. 2005 [20]
VALENTINI ET AL. 2005 [11]
LI ET AL. 2006 [8]
LIANGLI ET AL. 2006 [55]
BRENNER ET AL. 2006 [17]
GAO ET AL. 2006 [18]
BEYDEDA ET AL. 2006 [23]
VAěEKOVÁ ET AL. 2007 [49]
BENZ 2007 [43]
HOU ET AL. 2007 [21]
WEIQUN ET AL. 2007 [10]
MACHADO ET AL. 2007 [3]
GUO ET AL. 2007 [56]
CHENGYING ET AL. 2007 [57]
LIANGLI ET AL. 2007 [2]
BOUAZIZ ET AL. 2008 [16]
ZHENG ET AL. 2008 [22]
PACHECO ET AL. 2008 [46]
PACHECO ET AL. 2009 [44]
PIEL ET AL. 2009 [37]
NIEBUHR ET AL. 2009 [58]
BORNER ET AL. 2009 [9]
TABLE V. D
ISTRIBUTION OF ARTICLES FOR
T
ESTING
C
HALLENGES
AND
I
SSUES
Author Year
WEYUKER ET AL. 1998 [29]
DASIEWICZ ET AL. 1999 [12]
ULRICH ET AL. 1999 [39]
ALLESANDRO ET AL. 2001 [26]
WU ET AL. 2001 [19]
GAO ET AL. 2003 [27]
BEYDEDA ET AL. 2003 [59]
GAO ET AL. 2004 [42]
ZHENG ET AL. 2005 [41]
BEYDEDA ET AL. 2005 [60]
PAVLOVA ET AL. 2006 [40]
GAO ET AL. 2006 [18]
MACHADO ET AL. 2007 [3]
GILL ET AL. 2007 [47]
WEIQM ET AL. 2008 [61]
Authors Year
DELAMARO ET AL. 1996 [62]
WANG ET AL. 1997 [32]
ZHENYI ET AL. 1999 [7]
DASIEWICZ ET AL. 1999 [12]
HARTMANN ET AL. 2000 [36]
BERTOLINO ET AL. 2002 [34]
HADDOX ET AL. 2002 [15]
JUNGMAYR ET AL. 2002 [14]
GAO ET AL. 2003 [27]
EDWARDS ET AL. 2004 [35]
BARBIER ET AL. 2005 [33]
YING ET AL. 2005 [63]
LI ET AL. 2005 [45]
LI ET AL. 2006 [8]
LIANGLI ET AL. 2006 [6]
LIANGLI ET AL. 2006 [64]
WEIQUN ET AL. 2007 [10]
LIANGLI ET AL. 2007 [2]
FULIANG ET AL. 2007 [1]
BENZ 2007 [43]
CHENGYING ET AL. 2007 [65]
GONZALEZ ET AL. 2009 [13]
NIEBUHR ET AL. 2009 [38]
TABLE VI.
D
ISTRIBUTION OF ARTICLES FOR
T
ESTABILITY
TABLE VII. D
ISTRIBUTION OF ARTICLES FOR
C
HALLENGES IN
T
ESTABILITY
Authors Year
FULIANG ET AL. 2007 [1]
A. Existing Technique
Our search resulted in 33 articles. Out of them 25 were
published in IEEE and the rest 8 were published in
ACM Digital Library. The summary of the techniques is
given in Table 8.
TABLE VIII. S
UMMARY OF
T
ESTING
T
ECHNIQUES
Techniques References
Using Grouped-Metadata Object
(Model)
[2]
UML based models [3, 10, 36]
Contract based Testing [4, 11, 22]
Coupling based Testing [12, 52]
State Machine based Testing [8, 16, 56]
Interface Mutation Testing [5, 21]
API – based [18, 25]
Component Interaction Graph
(CIG) Model
[19]
Regression Testing [20, 21, 57]
Self-Testing Method [23, 24]
Data-flow Testing [3, 55]
Component Testing Model [44, 53, 54]
Feedback-Random Testing [46]
Assume-Guarantee Testing [48]
Verification Model [49, 58]
We found 25 studies related to Testing Techniques in
CBSE. Out of these 9 were extensions of already developed
models. Article [3] presents an UML based approach to
integration testing using Object Constraint Language. In
[10] the work was further extended to develop a
model-based based approach using three techniques
namely Scenario-based, contract-based and Component
Test Mapping Technique. Article [36] is design-based
testing approach that discusses generating test-cases
automatically. Another popular approach is Contract-based
testing. Article [11] gives a framework called CrashIt. It is
based on contract-checkers that verifies the information
between the component producer and the user. In [22] this
technique was furthered by combining with UML-based
testing at the modeling level rather than design level.
4 The article [18] discusses a Regression testing based on
API changes and their corresponding impacts. API based
approach for validation of the software is explained in [25].
Int’l Conf. on Computer & Communication TechnologyŇICCCT’10Ň
565
The idea of Metamorphic-Testing [24] is extended in [23].
Components are augmented with specific functionalities. In
absence of formal models testing based on Scenarios is
a key point. Integration Testing based on scenarios using
Finite State Machine is discussed in [8]. In [16] the work
was furthered to test real time component-based systems. A
case study of Feedback-Random Testing done on a .Net
component at Microsoft is explained in [40]. Article [44]
presents an approach to test aiming to reduce the gap
between component producer and the user. Article [37]
presents an approach when the component-base system is
evolving at run-time. This approach is based on virtual
components based on data-flow behavior
B. Key Challenges and Issues
We found 15 studies exclusively on key challenges and
issues in testing component-based software systems resulted
15 studies. Out of them 11 were published in IEEEXplore
and the rest 4 in ACM Digital Library. Major challenges
include [3, 41, and 47]
1) Lack of Source code
2) Heterogeneity of specifications and technology
3) Incomplete interface specifications
4) Difficulty in identifying the dependencies.
Challenges in testing component-based embedded systems
are explained in [40]. Lack of component standardization is
major challenge in testing component-based systems [47].
Reusability of environment for testing is another major
challenge [47]. There are no systematic methods and tools
that support analysis of component change, impact
analysis, and automatic test case selection [18]. Article
[29] generalizes problems resulted from a system
made of reusable components. This can be highlighted
as focus point on overcoming challenges.
C. Testability
We identified 23 papers that dealt with Testability
answering understanding behaviour of the components
and their interactions. Of these 19 were published in
IEEEXplore and 4 in ACM Digital Library. Summary of the
results are given in Table 9.
TABLE IX. S
UMMARY OF
T
ESTABILITY
Feature Article
INTERIOR INFORMATION OF A
COMPONENT. NOTION OF
TESTABILITY
[1]
IMPROVING TESTABILITY USING
METADATA
[2]
IDENTIFICATION OF
DEPENDENCY CODE BASED
APPROACH & SCENARIO BASED
APPROACH
[6]
DEFINING COUPLING-BASED TEST
CRITERIA
[7]
IDENTIFYING DEPENDENCIES
USING SCENARIOS & TEST DATA
GENERATION
[8]
DEFINING TEST CRITERIA USING [10]
COMPONENT TEST MAPPING
TECHNIQUE
MATHEMATICAL MODEL TO
MODEL INTERACTIONS AMONG
COMPONENTS
[12]
MEASURING TESTABILITY AT
RUNTIME
[13]
TESTABILITY FROM THE POINT
OF VIEW OF ARCHITECTURE
[14,65]
IMPROVING TESTABILITY [27, 32, 33, 34, 35]
WRAPPING METHOD TO TEST
INTERACTION OF COMPONENTS
[15]
DEFINING BEHAVIOR OF
COMPONENTS USING UML
[36]
DETECTING INCOMPATIBILITY OF
COMPONENTS AT RUNTIME
[38, 63]
INTERACTION MODELING
COVERING ERROR PRONE
SCENARIOS
[43, 62]
MATRIX-BASED APPROACH TO
ANALYZE DEPENDENCIES
[45, 64]
D. Testability Challenges
We found only one article (source: IEEEXplore) [1]
through the search criteria. Authors of the article say the
characteristics of components, as described in [1] are not
usually found. This lack of information is a challenge in
understanding testability.
IV. D
ISSCUSION AND FUTURE WORK
In our study of exiting testing techniques and model
for integrating component-based software systems,
research is focused on techniques based on contracts,
UML and finite state machine. Considering the number of
articles produced, testing of real-time systems occupies little
portion. Also, it is interesting to investigate on the issues
like time to test, effort to be invested in testing, and the role
of metrics in testing and also in component interaction
models. Our studies also show evidence of CBSE and
testing in the field of embedded systems. There is good
coverage in terms of research in understanding the
behaviour of components, interactions and compatibility of
components. We present ideas of future work in the form of
following questions/points.
1) Is CBSE suitable when there are frequently changing
requirements (i.e. I Agile fashion)?
2) Testing tools in CBSE.
3) Investigation/case study of CBSE in Software industry?
4) How to achieve common component standardization and
environmental characteristics?
V.
LIMITATIONS AND VALIDITY THREATS
Our study is not free from limitations and validity threats.
Firstly, we searched only two journals (IEEEXplore and
ACM Digital Library). We could not search other important
journals like Springer Link and Science Direct, as planned,
on account of time constraint. However, we found there is a
considerate body of knowledge in the journals we covered.
We describe different validity threats to our study.
Conclusion Validity refers to the biasness in applying data
Int’l Conf. on Computer & Communication TechnologyŇICCCT’10Ň
566
extraction [31]. We defined Inclusion/Exclusion criteria and
did a qualitative assessment in order to include the articles in
our study. This is done to minimize the affect of biasness.
We deliberately chose IEEEXplore and ACM Digital Library
as the journals of primary interest and research. Internal
Validity refers to causal relationship between a treatment and
outcome. This may come from unpublished articles and
journals/conferences we do not have access to. Another
source of Internal Validity may come from the journals we
did not search. Construct Validity refers to the ability of a
researcher in measuring what he/she intends to measure [31].
It is the relationship between theory and application.
Exclusion of articles on Object-oriented and service-oriented
technologies, test plan and metrics was done deliberately.
We adhered strictly to the keywords for search. External
Validity refers to the generalization of results outside the
scope of study [31]. We believed we followed our search
strategy and it represented our overall goal. We scanned
references and we found articles that were published in
Springer Link. These articles are [33, 34]. This was done to
minimize the External Validity threat.
VI.
CONCLUSIONS
The systematic Literature survey investigated existing
integration testing techniques, understanding the behavior of
components and their interactions. We also presented
challenges in this area. As seen from the year of publication
of the articles, it can be understood that the research was
rather dull until the year 2001. There were 8 articles
published. From the year 2001 research geared up and more
than 4 articles were published on an average. There exists a
need to establish requirements traceability and behaviour of
evolving or changing components. The research also points
investigate into automation of testing in CBSE.
We believe further research in the field of automated
testing of components, testing at run-time and approaches to
generate test-cases for evolving components would be
beneficial. However non-functional aspects in a system
composed of components could be analyzed and tested has a
great potential.
R
EFERENCES
[1] Guo Fuliang; Ma Liangli, "A Metadata Configuration Model for
Component-Based Software Integration Testing," Computational
Intelligence and Security Workshops, 2007. CISW 2007. International
Conference on , vol., no., pp.898-901, 15-19 Dec. 2007
[2] Ma Liangli; Wang Houxiang; Li Yongjie, "A Reference Model of
Grouped-Metadata Object and a Change Model based on it Appling
for Component-based Software Integration Testing," Computer
Systems and Applications, 2007. AICCSA '07. IEEE/ACS
International Conference on , vol., no., pp.32-39, 13-16 May 2007
[3] Machado, P.D.L.; Figueiredo, J.C.A.; Lima, E.F.A.; Barbosa, A.E.V.;
Lima, H.S., "Component-based integration testing from UML
interaction diagrams," Systems, Man and Cybernetics, 2007. ISIC.
IEEE International Conference on , vol., no., pp.2679-2686, 7-10
Oct. 2007
[4] C. Atkinson and H.-G. Gross, “Built-in contract testing in
modeldriven,component-based development,” in ICSR Work. on
Component-Based Develop. Processes, 2002.
[5] Delamaro, M. E., Maldonado, J. C., and Mathur, A. P.,Interface
Mutation: an approach to integration testing, IEEE TSE, Vol. 27, No.
3, March 2001, pp228-247.
[6] Ma Liangli; Wang Houxiang; Li Yongjie, "Using Component
Metadata based on Dependency Relationships Matrix to improve the
Testability of Component-based Software," Digital Information
Management, 2006 1st International Conference on , vol., no., pp.13-
18, 6-6 Dec. 2006
[7] Zhenyi Jin; Offutt, A.J., "Coupling-based integration testing,"
Engineering of Complex Computer Systems, 1996. Proceedings.,
Second IEEE International Conference on , vol., no., pp.10-17, 21-25
Oct 1996
[8] Li, K.; Groz, R.; Shahbaz, M., "Integration Testing of Components
Guided by Incremental State Machine Learning," Testing: Academic
and Industrial Conference - Practice And Research Techniques,
2006. TAIC PART 2006. Proceedings , vol., no., pp.59-70, 29-31
Aug. 2006
[9] Borner, Lars; Paech, Barbara, "Integration Test Order Strategies to
Consider Test Focus and Simulation Effort," Advances in System
Testing and Validation Lifecycle, 2009. VALID '09. First
International Conference on , vol., no., pp.80-85, 20-25 Sept. 2009
[10] Weiqun Zheng; Bundell, G., "Model-Based Software Component
Testing: A UML-Based Approach," Computer and Information
Science, 2007. ICIS 2007. 6th IEEE/ACIS International Conference
on , vol., no., pp.891-899, 11-13 July 2007
[11] Valentini, E.; Fliess, G.; Haselwanter, E., "A framework for efficient
contract-based testing of software components," Computer Software
and Applications Conference, 2005. COMPSAC 2005. 29th Annual
International , vol.2, no., pp. 219-222 Vol. 1, 26-28 July 2005
[12] Liu, W.; Dasiewicz, P., "Formal test requirements for component
interactions," Electrical and Computer Engineering, 1999 IEEE
Canadian Conference on , vol.1, no., pp.295-299 vol.1, 1999
[13] Gonzalez, A.; Piel, E.; Gross, H.-G., "A Model for the Measurement
of the Runtime Testability of Component-Based Systems," Software
Testing, Verification and Validation Workshops, 2009. ICSTW '09.
International Conference on , vol., no., pp.19-28, 1-4 April 2009
[14] S. Jungmayr. Identifying test-critical dependencies. InICSM ’02:
Proceedings of the International Conference on Software
Maintenance (ICSM’02), pages 404–413, Washington, DC, USA,
2002. IEEE Computer Society.
[15] Haddox, J.M.; Kapfhammer, G.M., "An approach for
understanding and testing third party software components,"
Reliability and Maintainability Symposium, 2002. Proceedings.
Annual , vol., no., pp.293-299, 2002
[16] Bouaziz, R.; Berrada, I., "Testing Component-Based Real Time
Systems," Software Engineering, Artificial Intelligence, Networking,
and Parallel/Distributed Computing, 2008. SNPD '08. Ninth ACIS
International Conference on , vol., no., pp.888-894, 6-8 Aug. 2008
[17] Brenner, D., "Enabling Run-Time System Verification through Built-
In Testing," Testing: Academic and Industrial Conference - Practice
AndResearch Techniques, 2006. TAIC PART 2006.
Proceedings , vol., no., Applications FIDJI 2002, Luxembourg,
28–29 November 2002. LNCS 2604,pp.131-136, 29-31 Aug. 2006
pp. 165–174, Springer, 2002.
[18] Gao, J.; Gopinathan, D.; Quan Mai San; He, J., "A Systematic
Regression Testing Method and Tool For Software Components,"
Computer Software and Applications Conference, 2006. COMPSAC
'06. 30th Annual International , vol.1, no., pp.455-466, 17-21 Sept.
2006
[19] Ye Wu; Dai Pan; Mei-Hwa Chen, Techniques for testing component-
based software, In procedings Engineering of Complex Computer
Systems, 2001. 17th IEEE International Conference , vol., no.,
pp.222-232, 2001.
[20] Chengying Mao; Yansheng Lu, "Regression testing for component-
based software systems by enhancing change information," Software
Engineering Conference, 2005. APSEC '05. 12th Asia-Pacific , vol.,
no., pp. 8 pp.-, 15-17 Dec. 2005
Int’l Conf. on Computer & Communication TechnologyŇICCCT’10Ň
567
[21] Shan-Shan Hou; Lu Zhang; Tao Xie; Hong Mei; Jia-Su Sun,
"Applying Interface-Contract Mutation in Regression Testing of
Component-Based Software," Software Maintenance, 2007. ICSM
2007. IEEE International Conference on , vol., no., pp.174-183, 2-5
Oct. 2007
[22] Weiqun Zheng; Bundell, G., "Test by Contract for UML-Based
Software Component Testing," Computer Science and its
Applications, 2008. CSA '08. International Symposium on , vol., no.,
pp.377-382, 13-15 Oct. 2008
[23] Beydeda, S., "Self-Metamorphic-Testing Components," Computer
Software and Applications Conference, 2006. COMPSAC '06. 30th
Annual International , vol.2, no., pp.265-272,17-21Sept.2006
[24] S. Beydeda and V. Gruhn. Merging components and testing tools:
The self-testing COTS components (STECC) strategy. In
EUROMICRO Conference - Component-based Software Engineering
Track (EUROMICRO), pages 107–114. IEEE Computer Society
Press, 2003.
[25] Jerry Gao, Raquel Espinoza, and Jingsha He, “Testing Coverage
Analysis for Software Component Validation”, Proceedings of
COMPSAC 2005,Edinburgh, Scotland, July 26-28, 2005
[26] Allesandro Orso, Mary Jean Harrold, D. Rosenblum, Greg
Rothermel, "Using component metacontents to support the regression
testing of Component-Based Software". Proceedings from the ICSE
workshop in Component Based Software Engineering. 2001 (Jan 7
2005).
[27] Jerry Gao, Jacob Tsao, and Ye Wu (2003). Testing and Quality
Assurance for Component-Based Software Massachusetts: Artech
House, Inc.
[28] Hopkins, J. Component Primer. Commun. ACM 43, 10, 27-30, Oct.
2000.
[29] E.J Weyuker. Testing component-based software:a cautionary tale.
IEEE Sofware, 15(5):54-59, SeptembedOctober 1998.
[30] P. Vitharana. Risks and Challenges of Component-Based Software
Development. Comm. ACM, vol. 46, no. 8, pp. 67-72, Aug 2003.
[31] Pour, G. Moving toward component-based software development
approach. Technology of Object-Oriented Languages, 1998. TOOLS
27. Proceedings, vol., no., pp.296-300, 22-25 Sep 1998.
[32] Y. Wang, G. King, I. Court, M. Ross, and G. Staples, “On
TestableObject-Oriented Programming,” ACM SIGSOFT Software
Engineering Notes, vol. 22 no. 4, pp. 84–90, July 1997.
[33] F. Barbier. COTS Component Testing through Built-In Test. In Sami
Beydeda & Volker Gruhn (Eds.), Testing Commercial-offthe-Shelf
Components and Systems. pp. 55–70, Springer, 2005.
[34] A. Bertolino and A. Polini. WCT: A Wrapper for Component
Testing International Workshop on Scientific Engineering
for Distributed Java Applications FIDJI 2002, Luxembourg, 28–29
November 2002. LNCS 2604, pp. 165–174, Springer, 2002.
[35] S Reid. The art of software testing (2nd Edition). Glenfor J. Mayers
revised and updated by Tom Badgett and Todd M. Thomas, with
Corey Sandler. John wile and sons, 2005.
[36] Hartmann, J., Imoberdorf, C., and Meisinger, M. 2000. UML-Based
integration testing. In Proceedings of the 2000 ACM SIGSOFT
international Symposium on Software Testing and Analysis (Portland,
Oregon, United States, August 21 - 24, 2000). M. J. Harold, Ed.
ISSTA '00. ACM, New York, NY, 60-70.
[37] Piel, É. and Gonzalez-Sanchez, A. 2009. Data-flow integration testing
adapted to runtime evolution in component-based systems. In
Proceedings of the 2009 ESEC/FSE Workshop on Software
integration and Evolution @ Runtime (Amsterdam, The Netherlands,
August 25 - 25, 2009). SINTER '09. ACM, New York, NY, 3-10.
[38] Niebuhr, D. and Rausch, A. 2009. Guaranteeing correctness of
component bindings in dynamic adaptive systems based on runtime
testing. InProceedings of the 4th international Workshop on Services
integration in Pervasive Environments (London, United Kingdom,
July 13 - 17, 2009). SIPE 09. ACM, New York, NY, 7-12.
[39] Ulrich, A. and Chrobok-Diening, G. 1999. International Workshop on
Testing Distributed Component-Based Systems. SIGSOFT Softw.
Eng. Notes 24, 4 (Jul. 1999), 43-46.
[40] Pavlova, I., Åkerholm, M., and Fredriksson, J. 2006. Application of
built-in-testing in component-based embedded systems. In
Proceedings of the ISSTA 2006 Workshop on Role of Software
Architecture For Testing and Analysis (Portland, Maine, July 17 - 20,
2006). ROSATEA '06. ACM, New York, NY, 51-52.
[41] Zheng, J., Robinson, B., Williams, L., and Smiley, K. 2005. A
process for identifying changes when source code is not available. In
Proceedings of the Second internationa l Workshop on Models and
Processes For the Evaluation of off-the-Shelf Components (St. Louis,
Missouri, May 21 - 21, 2005). MPEC '05. ACM, New York, NY, 1-4.
[42] Gao, J. and Wu, Y., "Testing Component-Based Software - Issues,
Challenges, and Solutions," in 3rd International Conference on
COTS-Based Software Systems. Redondo Beach, Jan. 2004.
[43] Benz, S. 2007. Combining test case generation for component and
integration testing. In Proceedings of the 3rd international Workshop
onAdvances in Model-Based Testing (London, United Kingdom, July
09 - 12, 2007). A-MOST '07. ACM, New York, NY, 23-33.
[44] Silva, F. R., Almeida, E. S., and Meira, S. R. 2009. An approach for
component testing and its empirical validation. In Proceedings of the
2009 ACM Symposium on Applied Computing (Honolulu, Hawaii).
SAC '09. ACM, New York, NY, 574-581.
[45] Li, B., Zhou, Y., Wang, Y., and Mo, J. 2005. Matrix-based
component dependence representation and its applications in software
quality assurance. SIGPLAN Not. 40, 11 (Nov. 2005), 29-36.
[46] D. Hamlet. Random testing. In Encyclopedia of Software
Engineering. John Wiley and Sons, 1994.
[47] Gill, N. S. and Tomar, P. 2007. CBS testing requirements and
test case process documentation revisited. SIGSOFT Softw. Eng.
Notes 32, 2 (Mar. 2007), 1-4.
[48] Blundell, C., Giannakopoulou, D., and Pӽsӽreanu, C. S. 2005.
Assume-guarantee testing. In Proceedings of the 2005 Conference on
Specification and Verification of Component-Based Systems (Lisbon,
Portugal, September 05 - 06, 2005). SAVCBS '05. ACM, New York,
NY, 1.
[49] VaĜeková, P., Moravec, P., ýerná, I., and Zimmerova, B. 2007.
Effective verification of systems with a dynamic number
of components. In Proceedings of the 2007 Conference on
Specification and Verification of Component-Based Systems: 6th
Joint Meeting of the European Conference on Software Engineering
and the ACM SIGSOFT Symposium on the Foundations of Software
Engineering (Dubrovnik, Croatia, September 03 - 04, 2007).
SAVCBS '07. ACM, New York, NY, 3-13.
[50] Kitchenham's Guidelines to Systematic Review.
Available:http://www.idi.ntnu.no/emner/empse/papers/kitchenham_2
004.pdf
[51] Reed, L.E., Performing a literature review, 28th Annual Frontiers in
Education Conference (FIE '98), pages.380-383 vol.1, 4-7 Nov 1998.
[52] Zhenyi Jin; Offutt, A.J.; , "Integration testing based on software
couplings," Computer Assurance, 1995. COMPASS '95. 'Systems
Integrity, Software Safety and Process Security'. Proceedings of the
Tenth Annual Conference on , vol., no., pp.13-23, 25-29 Jun 1995
[53] Ye Wu; Dai Pan; Mei-Hwa Chen; , "Techniques of maintaining
evolving component-based software," Software Maintenance, 2000.
Proceedings. International Conference on , vol., no., pp.236-246,
2000
[54] Beydeda, S.; Gruhn, V.; , "An integrated testing technique for
component-based software," Computer Systems and Applications,
ACS/IEEE International Conference on. 2001 , vol., no., pp.328-334,
2001
[55] Ma Liangli; Wang Houxiang; Lu Yansheng; , "The Design of
Dependency Relationships Matrix to improve the testability of
Component-based Software," Quality Software, 2006. QSIC 2006.
Sixth International Conference on , vol., no., pp.93-98, 27-28 Oct.
2006
Int’l Conf. on Computer & Communication TechnologyŇICCCT’10Ň
568
[56] Guo Fuliang; Ma Liangli; , "A Metadata Configuration Model for
Component-Based Software Integration Testing," Computational
Intelligence and Security Workshops, 2007. CISW 2007. International
Conference on , vol., no., pp.898-901, 15-19 Dec. 2007
[57] Chengying Mao; , "Built-in Regression Testing for Component-based
Software Systems," Computer Software and Applications Conference,
2007. COMPSAC 2007. 31st Annual International , vol.2, no.,
pp.723-728, 24-27 July 2007
[58] Niebuhr, D.; Rausch, A.; Klein, C.; Reichmann, J.; Schmid, R.; ,
"Achieving Dependable Component Bindings in Dynamic Adaptive
Systems - A Runtime Testing Approach," Self-Adaptive and Self-
Organizing Systems, 2009. SASO '09. Third IEEE International
Conference on , vol., no., pp.186-197, 14-18 Sept. 2009
[59] Beydeda, S.; Gruhn, V.; , "Merging components and testing tools: the
self-testing COTS components (STECC) strategy," Euromicro
Conference, 2003. Proceedings. 29th , vol., no., pp. 107- 114, 1-6
Sept. 2003
[60] Beydeda, S.; , "Research in testing COTS components - built-in
testing approaches," Computer Systems and Applications, 2005. The
3rd ACS/IEEE International Conference on , vol., no., pp. 101, 2005
[61] Weiqun Zheng; Bundell, G.; , "Test by Contract for UML-Based
Software Component Testing," Computer Science and its
Applications, 2008. CSA '08. International Symposium on , vol., no.,
pp.377-382, 13-15 Oct. 2008
[62] Delamaro, M.E.; Maldonado, J.C.; Mathur, A.P.; , "Integration testing
using interface mutation," Software Reliability Engineering, 1996.
Proceedings., Seventh International Symposium on , vol., no., pp.112-
121, 30 Oct-2 Nov 1996
[63] Ying Jiang; Shan-Shan Hou; Jin-Hui Shan; Lu Zhang; Bing Xie; ,
"Contract-based mutation for testing components," Software
Maintenance, 2005. ICSM'05. Proceedings of the 21st IEEE
International Conference on , vol., no., pp. 483- 492, 26-29 Sept.
2005
[64] Ma Liangli; Wang Houxiang; Li Yongjie; , "Using Component
Metadata based on Dependency Relationships Matrix to improve the
Testability of Component-based Software," Digital Information
Management, 2006 1st International Conference on , vol., no., pp.13-
18, 6-6 Dec. 2006
[65] Chengying Mao; , "AOP-based Testability Improvement for
Component-based Software," Computer Software and Applications
Conference, 2007. COMPSAC 2007. 31st Annual International ,
vol.2, no., pp.547-552, 24-27 July 2007