Pub Date : 2012-07-05DOI: 10.1049/iet-sen.2011.0061
Siraj Muhammad, O. Maqbool, Abdul Qudus Abbasi
Various techniques have been proposed for the automatic modularisation and architecture recovery of software systems. These techniques usually employ an algorithm to form clusters of similar entities. Similarity between entities is based on their characteristics, and is often determined by the relationships that exist between them. When using automatic techniques, selecting a suitable algorithm and appropriate relationships are challenging issues, and have a significant influence on the quality of results. Although researchers have employed different algorithms for modularising object-oriented software systems, there has been relatively little work to determine which relationships produce better modularisation results. The authors evaluate in this study a large number of relationships that may exist between entities in an object-oriented system, by dividing the relationships into different categories. For modularisation, experiments are conducted using multiple hierarchical clustering algorithms. The experimental results indicate the relationships that improve the quality of results for the algorithms, and thus may be considered more important for software clustering.
{"title":"Evaluating relationship categories for clustering object-oriented software systems","authors":"Siraj Muhammad, O. Maqbool, Abdul Qudus Abbasi","doi":"10.1049/iet-sen.2011.0061","DOIUrl":"https://doi.org/10.1049/iet-sen.2011.0061","url":null,"abstract":"Various techniques have been proposed for the automatic modularisation and architecture recovery of software systems. These techniques usually employ an algorithm to form clusters of similar entities. Similarity between entities is based on their characteristics, and is often determined by the relationships that exist between them. When using automatic techniques, selecting a suitable algorithm and appropriate relationships are challenging issues, and have a significant influence on the quality of results. Although researchers have employed different algorithms for modularising object-oriented software systems, there has been relatively little work to determine which relationships produce better modularisation results. The authors evaluate in this study a large number of relationships that may exist between entities in an object-oriented system, by dividing the relationships into different categories. For modularisation, experiments are conducted using multiple hierarchical clustering algorithms. The experimental results indicate the relationships that improve the quality of results for the algorithms, and thus may be considered more important for software clustering.","PeriodicalId":13395,"journal":{"name":"IET Softw.","volume":"52 1","pages":"260-274"},"PeriodicalIF":0.0,"publicationDate":"2012-07-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"75947219","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2012-07-05DOI: 10.1049/IET-SEN.2011.0077
Ramón R. Palacio, A. Morán, Víctor M. González, A. Vizcaíno
The software industry is facing a recent trend called distributed software development (DSD), in which distributed teams require continuous support in their communication and coordination. However, there is a lack of communication tools that actually support the coordination of DSD activities. Current communication mechanisms appear to favour the issuer of an interaction, because the context of the receiver is not always considered. In this study, the authors introduce selective availability (SA), a mechanism with which to provide information about the current activities of the members in a distributed team, in order to motivate a more suitable means to initiate interactions, thus facilitating the communication and coordination of DSD activities. Moreover, the authors describe the CWS-IM tool, an extended instant messaging application that supports SA, by notifying collaborators about each of their colleague's activities. Therefore, issuers can decide whether the time is right to start the interaction. The results of an evaluation of the actual use of the tool in a DSD software development company are also presented. These results indicate that developers perceive CWS-IM to be more useful and easier to use than other traditional instant messaging applications when initiating collaboration in DSD environments.
{"title":"Selective availability: Coordinating interaction initiation in distributed software development","authors":"Ramón R. Palacio, A. Morán, Víctor M. González, A. Vizcaíno","doi":"10.1049/IET-SEN.2011.0077","DOIUrl":"https://doi.org/10.1049/IET-SEN.2011.0077","url":null,"abstract":"The software industry is facing a recent trend called distributed software development (DSD), in which distributed teams require continuous support in their communication and coordination. However, there is a lack of communication tools that actually support the coordination of DSD activities. Current communication mechanisms appear to favour the issuer of an interaction, because the context of the receiver is not always considered. In this study, the authors introduce selective availability (SA), a mechanism with which to provide information about the current activities of the members in a distributed team, in order to motivate a more suitable means to initiate interactions, thus facilitating the communication and coordination of DSD activities. Moreover, the authors describe the CWS-IM tool, an extended instant messaging application that supports SA, by notifying collaborators about each of their colleague's activities. Therefore, issuers can decide whether the time is right to start the interaction. The results of an evaluation of the actual use of the tool in a DSD software development company are also presented. These results indicate that developers perceive CWS-IM to be more useful and easier to use than other traditional instant messaging applications when initiating collaboration in DSD environments.","PeriodicalId":13395,"journal":{"name":"IET Softw.","volume":"7 1","pages":"185-198"},"PeriodicalIF":0.0,"publicationDate":"2012-07-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"72995972","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2012-07-05DOI: 10.1049/iet-sen.2011.0105
A. Raza, Luiz Fernando Capretz, F. Ahmed
The unlimited number of open-source software (OSS) users and the importance of end users' experience in determining software quality make usability an even more critical quality attribute for OSS than it is for proprietary software. The research model of this study establishes the relationship between usability errors in OSS and online public forums. The results of this empirical analysis provide evidence about active management of usability-related issues in OSS. To conduct this research, the authors used a dataset consisting of 1753 OSS projects, covering a broad range of categories. The results of the study show that online forums play a significant role in identifying and fixing usability bugs in OSS.
{"title":"Usability bugs in open-source software and online forums","authors":"A. Raza, Luiz Fernando Capretz, F. Ahmed","doi":"10.1049/iet-sen.2011.0105","DOIUrl":"https://doi.org/10.1049/iet-sen.2011.0105","url":null,"abstract":"The unlimited number of open-source software (OSS) users and the importance of end users' experience in determining software quality make usability an even more critical quality attribute for OSS than it is for proprietary software. The research model of this study establishes the relationship between usability errors in OSS and online public forums. The results of this empirical analysis provide evidence about active management of usability-related issues in OSS. To conduct this research, the authors used a dataset consisting of 1753 OSS projects, covering a broad range of categories. The results of the study show that online forums play a significant role in identifying and fixing usability bugs in OSS.","PeriodicalId":13395,"journal":{"name":"IET Softw.","volume":"5 1","pages":"226-230"},"PeriodicalIF":0.0,"publicationDate":"2012-07-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"73057622","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2012-07-05DOI: 10.1049/IET-SEN.2010.0160
Miguel García, D. Llewellyn-Jones, Francisco Ortin, M. Merabti
Distributed systems are commonly required to be flexible and scalable, as the number and arrangement of their (potentially mobile) devices may easily change. Security in distributed systems is a complex issue which can produce several problems such as eavesdropping, phishing or denial of service. To overcome these problems, there are various security measures that can be applied. This study proposes the use of dynamic aspect-oriented software development (AOSD) to implement security mechanisms in distributed systems. By applying dynamic separation of concerns using AOSD, it becomes possible to adapt the security measures of distributed systems, even when their sizes and arrangements change, without compromising global security. These changes can be applied when a distributed system is running, without requiring its execution to be stopped or interrupted. Using the dynamic and static aspect weaving AOSD platform, the authors have implemented solutions for two common security problems in distributed systems: (i) access control and data flow and (ii) encryption of transmissions. Moreover, the proposed approach has been tested in a real client-server FTP scenario. Qualitative and quantitative evaluations of both implementations are presented to estimate the pros and cons of using dynamic AOSD in the development of security measures of distributed systems.
{"title":"Applying dynamic separation of aspects to distributed systems security: A case study","authors":"Miguel García, D. Llewellyn-Jones, Francisco Ortin, M. Merabti","doi":"10.1049/IET-SEN.2010.0160","DOIUrl":"https://doi.org/10.1049/IET-SEN.2010.0160","url":null,"abstract":"Distributed systems are commonly required to be flexible and scalable, as the number and arrangement of their (potentially mobile) devices may easily change. Security in distributed systems is a complex issue which can produce several problems such as eavesdropping, phishing or denial of service. To overcome these problems, there are various security measures that can be applied. This study proposes the use of dynamic aspect-oriented software development (AOSD) to implement security mechanisms in distributed systems. By applying dynamic separation of concerns using AOSD, it becomes possible to adapt the security measures of distributed systems, even when their sizes and arrangements change, without compromising global security. These changes can be applied when a distributed system is running, without requiring its execution to be stopped or interrupted. Using the dynamic and static aspect weaving AOSD platform, the authors have implemented solutions for two common security problems in distributed systems: (i) access control and data flow and (ii) encryption of transmissions. Moreover, the proposed approach has been tested in a real client-server FTP scenario. Qualitative and quantitative evaluations of both implementations are presented to estimate the pros and cons of using dynamic AOSD in the development of security measures of distributed systems.","PeriodicalId":13395,"journal":{"name":"IET Softw.","volume":"5 1","pages":"231-248"},"PeriodicalIF":0.0,"publicationDate":"2012-07-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"78499051","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2012-07-05DOI: 10.1049/IET-SEN.2011.0087
A. Vizcaíno, Félix García, I. Caballero, J. M. Villar, M. Piattini
As planning an R&D project named ORIGIN addressing global software development (GSD) foundations, the authors soon became aware of the need for all the participants to share the same vision of GSD projects. The authors therefore reached the conclusion that one of the first steps should be to set up a shared and consistent GSD project-related vocabulary, since this would help to improve communication between the five companies involved in ORIGIN. After analysing existing GSD initiatives, the authors discovered that none of them really satisfied our specific needs. As a consequence, they decided to develop a new ontology, which was named O-GSD. This paper describes not only how the ontology was developed -including the reasons which led us to include each term in O-GSD- but also its usage in real contexts -what allowed us to extract some insights to refine and validate the ontology. The main contribution of this paper is the O-GSD ontology which is used and to be used in real GSD projects with the aim of helping project managers to better describe their particular GSD projects.
{"title":"Towards an ontology for global software development","authors":"A. Vizcaíno, Félix García, I. Caballero, J. M. Villar, M. Piattini","doi":"10.1049/IET-SEN.2011.0087","DOIUrl":"https://doi.org/10.1049/IET-SEN.2011.0087","url":null,"abstract":"As planning an R&D project named ORIGIN addressing global software development (GSD) foundations, the authors soon became aware of the need for all the participants to share the same vision of GSD projects. The authors therefore reached the conclusion that one of the first steps should be to set up a shared and consistent GSD project-related vocabulary, since this would help to improve communication between the five companies involved in ORIGIN. After analysing existing GSD initiatives, the authors discovered that none of them really satisfied our specific needs. As a consequence, they decided to develop a new ontology, which was named O-GSD. This paper describes not only how the ontology was developed -including the reasons which led us to include each term in O-GSD- but also its usage in real contexts -what allowed us to extract some insights to refine and validate the ontology. The main contribution of this paper is the O-GSD ontology which is used and to be used in real GSD projects with the aim of helping project managers to better describe their particular GSD projects.","PeriodicalId":13395,"journal":{"name":"IET Softw.","volume":"56 1","pages":"214-225"},"PeriodicalIF":0.0,"publicationDate":"2012-07-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"80303331","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2012-07-05DOI: 10.1049/iet-sen.2011.0066
Jihyun Lee, Sungwon Kang, Danhyung Lee
To develop high-quality software, it is essential to use software testing methods and tools (STMTs) effectively and efficiently. The authors conducted a survey with a wide variety of companies and experts that are involved in software testing in order to identify the current practices and opportunities for improvement of STMTs. The survey results revealed five important findings regarding the current practices of STMTs and opportunities for improvement: low usage rate of STMTs, difficulties owing to alack of STMTs, use of testing tools in a limited manner, demand for interoperability support between methods and tools of software development and testing, and need for guidance to evaluate STMTs or to describe the capabilities of STMTs. These findings and other related results from the survey will be useful for improving STMTs practices and developing software testing tools.
{"title":"Survey on software testing practices","authors":"Jihyun Lee, Sungwon Kang, Danhyung Lee","doi":"10.1049/iet-sen.2011.0066","DOIUrl":"https://doi.org/10.1049/iet-sen.2011.0066","url":null,"abstract":"To develop high-quality software, it is essential to use software testing methods and tools (STMTs) effectively and efficiently. The authors conducted a survey with a wide variety of companies and experts that are involved in software testing in order to identify the current practices and opportunities for improvement of STMTs. The survey results revealed five important findings regarding the current practices of STMTs and opportunities for improvement: low usage rate of STMTs, difficulties owing to alack of STMTs, use of testing tools in a limited manner, demand for interoperability support between methods and tools of software development and testing, and need for guidance to evaluate STMTs or to describe the capabilities of STMTs. These findings and other related results from the survey will be useful for improving STMTs practices and developing software testing tools.","PeriodicalId":13395,"journal":{"name":"IET Softw.","volume":"1995 1","pages":"275-282"},"PeriodicalIF":0.0,"publicationDate":"2012-07-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"89098563","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2012-07-05DOI: 10.1049/iet-sen.2011.0104
Tihana Galinac Grbac, Z. Car, D. Huljenic
Many researchers have reported the defect growth within the evolutionary-developed large-scale systems, and increased fault slips from the early verification stages into late. This suggests that improvement in the early defect detection process control is needed. This study focuses on evaluation of adding inspection effort early in the development process. Based on the examination of the existing metrics used in defect detection process, the authors establish metrics to quantify its value from the quality and cost-benefit perspective. The effect of adding inspection effort early in the development process is evaluated in a case study using industrial data from history and an ongoing project involving three geographically distributed sites of the same globally distributed software development organisation with around 300 developers. The findings show that the expert-based decision criteria for additional investment are mostly based on quality and reliability issues, and less on costs. Consequently, the additional inspection improves significantly the quality, while the cost-benefit was not statistically significant. This leads to the conclusion that better decision criteria that would incorporate the costs and not only quality perceptions are the key for improving the product reliability, as well as the overall software life-cycle cost-efficiency. This study is motivated by the real industrial environment, and thus, contributes to both research and practice by presenting the empirical evidence.
{"title":"Quantifying value of adding inspection effort early in the development process: A case study","authors":"Tihana Galinac Grbac, Z. Car, D. Huljenic","doi":"10.1049/iet-sen.2011.0104","DOIUrl":"https://doi.org/10.1049/iet-sen.2011.0104","url":null,"abstract":"Many researchers have reported the defect growth within the evolutionary-developed large-scale systems, and increased fault slips from the early verification stages into late. This suggests that improvement in the early defect detection process control is needed. This study focuses on evaluation of adding inspection effort early in the development process. Based on the examination of the existing metrics used in defect detection process, the authors establish metrics to quantify its value from the quality and cost-benefit perspective. The effect of adding inspection effort early in the development process is evaluated in a case study using industrial data from history and an ongoing project involving three geographically distributed sites of the same globally distributed software development organisation with around 300 developers. The findings show that the expert-based decision criteria for additional investment are mostly based on quality and reliability issues, and less on costs. Consequently, the additional inspection improves significantly the quality, while the cost-benefit was not statistically significant. This leads to the conclusion that better decision criteria that would incorporate the costs and not only quality perceptions are the key for improving the product reliability, as well as the overall software life-cycle cost-efficiency. This study is motivated by the real industrial environment, and thus, contributes to both research and practice by presenting the empirical evidence.","PeriodicalId":13395,"journal":{"name":"IET Softw.","volume":"18 1","pages":"249-259"},"PeriodicalIF":0.0,"publicationDate":"2012-07-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"78988126","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2012-07-05DOI: 10.1049/iet-sen.2011.0044
D. Tuffley
The globalisation of the software development industry has solved one set of problems and created a new set. Skills shortages in the host organisation can be solved by Global Software Development, yet the effective management of virtual teams is a new challenge. This study proposes a process reference model (PRM) and assessment model for the leadership of project teams, including complex virtual teams. Using modelling techniques from Software Engineering, the Leadership PRM describes the attributes that a project manager should possess, and the activities they should perform if they are to be perceived by those around them as leaders. The developed model contains the essential leadership characteristics. Leadership is difficult to define since it is situationally expressed. The context determines the outward form that leadership takes in a given situation. A manager who innately embodies these essential leadership qualities will be perceived as a leader by those around them. Leadership is a skill that can be learned and developed over time to a higher level of competence. Managers coordinate the activities of team members in the pursuit of goals, while leaders extend this management capability by knowing how to motivate team members to want to do what it is the leader wants them to do.
{"title":"Optimising virtual team leadership in global software development","authors":"D. Tuffley","doi":"10.1049/iet-sen.2011.0044","DOIUrl":"https://doi.org/10.1049/iet-sen.2011.0044","url":null,"abstract":"The globalisation of the software development industry has solved one set of problems and created a new set. Skills shortages in the host organisation can be solved by Global Software Development, yet the effective management of virtual teams is a new challenge. This study proposes a process reference model (PRM) and assessment model for the leadership of project teams, including complex virtual teams. Using modelling techniques from Software Engineering, the Leadership PRM describes the attributes that a project manager should possess, and the activities they should perform if they are to be perceived by those around them as leaders. The developed model contains the essential leadership characteristics. Leadership is difficult to define since it is situationally expressed. The context determines the outward form that leadership takes in a given situation. A manager who innately embodies these essential leadership qualities will be perceived as a leader by those around them. Leadership is a skill that can be learned and developed over time to a higher level of competence. Managers coordinate the activities of team members in the pursuit of goals, while leaders extend this management capability by knowing how to motivate team members to want to do what it is the leader wants them to do.","PeriodicalId":13395,"journal":{"name":"IET Softw.","volume":"13 1","pages":"176-184"},"PeriodicalIF":0.0,"publicationDate":"2012-07-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"91540459","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2012-05-17DOI: 10.1049/iet-sen.2011.0027
Bertrand Verlaine, Y. Dubois, Ivan Jureta, Stéphane Faulkner
The engineering of a service-oriented system requires the specification of functions that Web services (WSs) should provide, before WSs are built or selected. Written in a service description language, the service specification instantiates concepts different than those used for requirement engineering (RE): the former speaks in terms of operations, metrics and bindings, whereas the latter manipulates, goals, evaluations and domain assumptions. It is, however, clear that functions expected of WSs to select or build will be relevant to the stakeholders if they satisfy the stakeholders' requirements. As a result, there is a gap between the two specifications which must be bridged in order to ensure that the WS system is adequate w.r.t. requirements. This study proposes mappings between the concepts of requirements ontology and those of service taxonomy induced by the WSLD and the WSLA languages. A working prototype is presented that implements the mappings and is used to translate the instances of RE concepts into instances of WSLD and WSLA concepts. The mappings and the prototype facilitate the engineering of WS systems, as fragments of WS descriptions can be generated from requirements as a first specification of a service request.
{"title":"Towards conceptual foundations for service-oriented requirements engineering: bridging requirements and services ontologies","authors":"Bertrand Verlaine, Y. Dubois, Ivan Jureta, Stéphane Faulkner","doi":"10.1049/iet-sen.2011.0027","DOIUrl":"https://doi.org/10.1049/iet-sen.2011.0027","url":null,"abstract":"The engineering of a service-oriented system requires the specification of functions that Web services (WSs) should provide, before WSs are built or selected. Written in a service description language, the service specification instantiates concepts different than those used for requirement engineering (RE): the former speaks in terms of operations, metrics and bindings, whereas the latter manipulates, goals, evaluations and domain assumptions. It is, however, clear that functions expected of WSs to select or build will be relevant to the stakeholders if they satisfy the stakeholders' requirements. As a result, there is a gap between the two specifications which must be bridged in order to ensure that the WS system is adequate w.r.t. requirements. This study proposes mappings between the concepts of requirements ontology and those of service taxonomy induced by the WSLD and the WSLA languages. A working prototype is presented that implements the mappings and is used to translate the instances of RE concepts into instances of WSLD and WSLA concepts. The mappings and the prototype facilitate the engineering of WS systems, as fragments of WS descriptions can be generated from requirements as a first specification of a service request.","PeriodicalId":13395,"journal":{"name":"IET Softw.","volume":"71 1","pages":"85-102"},"PeriodicalIF":0.0,"publicationDate":"2012-05-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"86570892","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2012-05-17DOI: 10.1049/iet-sen.2011.0059
Sajjad Mahmood
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.
{"title":"Usefulness of acceptance testing information for component-based system maintenance","authors":"Sajjad Mahmood","doi":"10.1049/iet-sen.2011.0059","DOIUrl":"https://doi.org/10.1049/iet-sen.2011.0059","url":null,"abstract":"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.","PeriodicalId":13395,"journal":{"name":"IET Softw.","volume":"21 1","pages":"155-163"},"PeriodicalIF":0.0,"publicationDate":"2012-05-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"75047828","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}