Usefulness of acceptance testing information for component-based system maintenance

Usefulness of acceptance testing information for component-based system maintenance

For access to this article, please select a purchase option:

Buy article PDF
(plus tax if applicable)
Buy Knowledge Pack
10 articles for £75.00
(plus taxes if applicable)

IET members benefit from discounts to all IET publications and free access to E&T Magazine. If you are an IET member, log in to your account and the discounts will automatically be applied.

Learn more about IET membership 

Recommend Title Publication to library

You must fill out fields marked with: *

Librarian details
Your details
Why are you recommending this title?
Select reason:
IET Software — Recommend this title to your library

Thank you

Your recommendation has been sent to your librarian.

Component-based system (CBS) development usually involves adapting best-matched components and writing integration code to handle the mismatches between system-to-be needs and available components. CBS presents unique maintenance challenges as a system analyst focuses on integrating existing components to build a software application. The lack of detailed individual component specification has been a key area of concern in CBS development because of its impact on the maintenance phase of a CBS development life cycle. Recent research suggests that the framework for integrated test (Fit) helps to better comprehend systems. In this work, the author presents a study to investigate the usefulness of acceptance test cases (Fit tables) information, when used as a functional specification, during the maintenance process. The mean correct implementation percentage with and without Fit tables were 86.19 and 83.52, respectively. Similarly, the mean times for the Fit tables and without Fit tables were 46.5 and 45.73, respectively. The results show that acceptance test cases help improve the functional correctness of changes with a little more effort during the maintenance process of a CBS.


    1. 1)
      • J. Peters , W. Pedrycz . (2000) Software engineering: an engineering approach.
    2. 2)
    3. 3)
      • J. Kotlarsky , I. Oshri . (2009) Managing component-based development in global teams.
    4. 4)
      • C. Szyperski , D. Gruntz , S. Murer . (2002) Component software – beyond object – oriented programming.
    5. 5)
    6. 6)
      • Cechich, A., Piattini, M., Vallecillo, A.: `Assessing component based systems', Component Based Software Quality, 2003, (LNCS, 2693), p. 1–20.
    7. 7)
      • K. Beck . (2003) Test driven development.
    8. 8)
      • Melnik, G., Read, K., Maurer, F.: `Suitability of fit user acceptance tests for specifying functional requirements: developer perspective’. 2004, (', , p. 60–72.
    9. 9)
      • Marhold, C., Rohleder, C., Salinesi, C., Doerr, J.: `Clarifying non-functional requirements to improve user acceptance – experience at siemens’. 2009, (', , p. 139–146.
    10. 10)
    11. 11)
      • R. Mugridge , W. Cunningham . (2005) Fit for developing software – framework for integrated tests.
    12. 12)
    13. 13)
    14. 14)
    15. 15)
      • Srivastava, B.: `A decision-support framework for component reuse and maintenance in software project management', Proc. Eighth European Conf. Software Maintenance and Reengineering, 2004, p. 125–134.
    16. 16)
      • Wu, Y., Pan, D., Chen, M.-H.: `Techniques of maintaining evolving component based software', Proc. Int. Conf. Software Maintenance, 2000, p. 236–246.
    17. 17)
      • Wu, Y., Offutt, J.: `Maintaining evolving component-based software with UML', Proc. Seventh European Conf. Software Maintenance and Reengineering, 2003, p. 133–142.
    18. 18)
    19. 19)
      • Ardimento, P., Bianchi, A., Visaggio, G.: `Maintenance-oriented selection of software components', Proc. Eighth European Conf. Software Maintenance and Reengineering, 2004, p. 115–124.
    20. 20)
      • Mahmood, S.: `The impact of acceptance tests on analyzing component-based system specifications: an experimental evaluation', Proc. Tenth IEEE Int. Conf. Computer and Information Technology (CIT 2010), 2010, p. 241–248.
    21. 21)
      • Ricca, F., Torchiano, M., Di Penta, M., Ceccato, M., Tonella, P.: `The use of executable fit tables to support maintenance and evolution tasks', Proc. Third Int. ERCIM Symp. on Software Evolution, 2007.
    22. 22)
      • Ricca, F., Di Penta, M., Torchiano, M.: `Guidelines on the use of fit tables in software maintenance tasks: lessons learned from 8 experiments', IEEE Int. Conf. Software Maintenance, 2008, p. 317–326.
    23. 23)
      • C. Wohlin , P. Runenson , M. Hst , M. Ohlsson , B. Regnell , A. Wessln . (2000) Experimentation in software engineering – an introduction.
    24. 24)
      • J. Cheesman , J. Daniels . (2001) UML components a simple process for specifying component based software.
    25. 25)
      • K. Barclay , J. Savage . (2004) Object-oriented design with UML and Java.
    26. 26)
      • P. Ammann , J. Offutt . (2008) Introduction to software testing.
    27. 27)
      • W. Mendenhall , T. Sincich . (2007) Statistics for engineering and the sciences.

Related content

This is a required field
Please enter a valid email address