Search results

The purpose of the paper is to propose a semantic model for describing open source software (OSS) in a machine–human understandable format. The model is extracted to support source code reusing and revising as the two primary targets of OSS through a systematic review of related documents.

Conducting a systematic review, all the software reusing criteria are identified and introduced to the web of data by an ontology for OSS (O4OSS). The software semantic model introduced in this paper explores OSS through triple expressions in which the O4OSS properties are predicates.

This model improves the quality of web data by describing software in a structured machine–human readable profile, which is linked to the related data that was previously published on the web. Evaluating the OSS semantic model is accomplished through comparing it with previous approaches, comparing the software structured metadata with profile index of software in some well-known repositories, calculating the software retrieval rank and surveying domain experts.

Considering context-specific information and authority levels, the proposed software model would be applicable to any open and close software. Using this model to publish software provides an infrastructure of connected meaningful data and helps developers overcome some specific challenges. By navigating software data, many questions which can be answered only through reading multiple documents can be automatically responded on the web of data.

The purpose of the present work is to mathematically model the reliability growth of a multi-version software system that is affected by infected patches.

The work presents a mathematical model that studies the reliability change due to the insertion of an infected patch in multi-version software. Various distribution functions have been considered to highlight the varied aspects of the model. Furthermore, weighted criteria approach has been discussed to facilitate the choice of the model.

The model presented here is able to quantify the effect of an infected patch on multi-version software. The model captures the hike in bug content due to an infected patch.

Multi-version systems have been studied widely, but the role of an infected patch has not been yet explored. The effect of an infected patch has been quantified by modeling the extra bugs generated in the system. This bug count would prove helpful in further studies for optimal resource allocation and testing effort allocation.

The purpose of this paper is to develop a new software reliability growth model considering different fault distribution function before and after the change point.

In this paper, the authors have developed a framework to incorporate change-point in developing a hybrid software reliability growth model by considering different distribution functions before and after the change point.

Numerical illustration suggests that the proposed model gives better results in comparison to the existing models.

The existing literature on change point-based software reliability growth model assumes that the fault correction trend before and after the change is governed by the same distribution. This seems impractical as after the change in the testing environment, the trend of fault detection or correction may not follow the same trend; hence, the assumption of same distribution function may fail to predict the potential number of faults. The modelling framework assumes different distributions before and after change point in developing a software reliability growth model.

Most of the existing software reliability models assume time between failures to follow an exponential distribution. Develops a reliability growth model based on non‐homogeneous Poisson process with intensity function given by the power law, to predict the reliability of a software. Several authors have suggested the use of the non‐homogeneous Poisson process to assess the reliability growth of software and to predict their failure behaviour. Inference procedures considered by these authors have been Bayesian in nature. Uses an unbiased estimate of the failure rate for prediction. Compares the performance of this model with Bayes empirical‐Bayes models and a time series model. The model developed is realistic, easy to use, and gives a better prediction of reliability of a software.

Non‐homogeneous Poisson process (NHPP) models, as the stochastic models frequently employed in reliability engineering, have been successfully used in the reliability study of software systems. The software reliability based on NHPP models was proposed by Goel and Okumoto. In general, the software reliability will increase along with the correction of the software errors. This idea gives rise to a hypothesis: extending the time on the software reliability test could result in obtaining a higher reliability. Nevertheless, the scheme was found to be discrepant for some NHPP models, which are utilized in the analysis. As this often occurs in practice, the reliability outcome could differ from its appropriate estimation when the test procedures are intentionally terminated prior to the end of the required testing time span. An “above average software reliability” is proposed in this paper to accomplish the inconsistency. Under the investigation of “average software reliability”, a higher software reliability can be achieved as long as the testing time increases. Also, in this paper, an optimal software release policy is proposed to explore the issue of compromising the expenses on software development and software reliability improvement.

The use of software is overpowering our modern society. Advancement in technology is directly proportional to an increase in user demand which further leads to an increase in the burden on software firms to develop high-quality and reliable software. To meet the demands, software firms need to upgrade existing versions. The upgrade process of software may lead to additional faults in successive versions of the software. The faults that remain undetected in the previous version are passed on to the new release. As this process is complicated and time-consuming, it is important for firms to allocate resources optimally during the testing phase of software development life cycle (SDLC). Resource allocation task becomes more challenging when the testing is carried out in a dynamic nature.

The model presented in this paper explains the methodology to estimate the testing efforts in a dynamic environment with the assumption that debugging cost corresponding to each release follows learning curve phenomenon. We have used optimal control theoretic approach to find the optimal policies and genetic algorithm to estimate the testing effort. Further, numerical illustration has been given to validate the applicability of the proposed model using a real-life software failure data set.

The paper yields several substantive insights for software managers. The study shows that estimated testing efforts as well as the faults detected for both the releases are closer to the real data set.

We have proposed a dynamic resource allocation model for multirelease of software with the objective to minimize the total testing cost using the flexible software reliability growth model (SRGM).

The purpose of this paper is to find good values of onsite-offshore team strength; number of hours of communication between business users and onsite team and between onsite and offshore team so as to reduce project cost and improve schedule in a global software development (GSD) environment for software development project.

This study employs system dynamics simulation approach to study software project characteristics in both co-located and distributed development environments. The authors consulted 14 experts from Indian software outsourcing industry during our model construction and validation.

The study results show that there is a drop in overall team productivity in outsourcing environment by considering the offshore options. But the project cost can be reduced by employing the offshore team for coding and testing work only with minimal training for imparting business knowledge. The research results show that there is a potential to save project cost by being flexible in project schedule.

The implication of the study is that the project management team should be careful not to keep high percentage of manpower at offshore location in distributed software environment. A large offshore team can increase project cost and schedule due to higher training overhead, lower productivity and higher error proneness. In GSD, the management effort should be to keep requirement analysis and design work at onsite location and involves the offshore team in coding and testing work.

The software project manager can use the model results to divide the software team between onsite and offshore location during various phases of software development in distributed environment.

The study is novel as there is little attempt at finding the team distribution between onsite and offshore location in GSD environment.

This paper is focused at studying the current state of research involving the four dimensions of defect management strategy, i.e. software defect analysis, software quality, software reliability and software development cost/effort.

The methodology developed by Kitchenham (2007) is followed in planning, conducting and reporting of the systematic review. Out of 625 research papers, nearly 100 primary studies related to our research domain are considered. The study attempted to find the various techniques, metrics, data sets and performance validation measures used by researchers.

The study revealed the need for integrating the four dimensions of defect management and studying its effect on software performance. This integrated approach can lead to optimal use of resources in software development process.

There are many dimensions in defect management studies. The authors have considered only vital few based on the practical experiences of software engineers. Most of the research work cited in this review used public data repositories to validate their methodology and there is a need to apply these research methods on real datasets from industry to realize the actual potential of these techniques.

The authors believe that this paper provides a comprehensive insight into the various aspects of state-of-the-art research in software defect management. The authors feel that this is the only research article that delves into the four facets namely software defect analysis, software quality, software reliability and software development cost/effort.

The purpose of this paper is to investigate the development of software pricing, following the advent of cloud-based business intelligence & analytics (BI & A) Software. A value-based conceptual software model is developed to ignite and structure further research.

A two-step research approach is applied. In step one, the available literature is screened and evaluated, and this is followed by ten semi-structured expert interviews. With that input, a conceptual software pricing model is designed. In step two, this model is validated and refined through discussions with representatives of the five leading business intelligence suites.

The paper sheds light on the value perception of customers and suggests a clear focus on the interaction between customers and vendors, and less on technical issues. The developed customer-centric, value-based pricing framework helps to improve pricing techniques and strategies.

The research is focused on the pricing strategy of software houses and excludes differentiations of technical specifications and functionalities.

The research can support practitioners in the field of BI & A in rethinking their pricing methods. Placing the customer at center stage can lead to lower customer churn rates, higher customer satisfaction and more pricing flexibility.

This empirical study reveals the importance of a customer-centric pricing approach in the specific case of BI & A. It can also be applied to other fast-developing sectors of the software industry.

The purpose of this paper is to investigate how to incorporate the exponentiated Weibull (EW) testing‐effort function (TEF) into inflection S‐shaped software reliability growth models (SRGMs) based on non‐homogeneous Poisson process (NHPP). The aim is also to present a more flexible SRGM with imperfect debugging.

This paper reviews the EW TEFs and discusses inflection S‐shaped SRGM with EW testing‐effort to get a better description of the software fault detection phenomenon. The SRGM parameters are estimated by weighted least square estimation (WLSE) and maximum‐likelihood estimation (MLE) methods. Furthermore, the proposed models are also discussed under imperfect debugging environment.

Experimental results from three actual data applications are analyzed and compared with the other existing models. The findings reveal that the proposed SRGM has better performance and prediction capability. Results also confirm that the EW TEF is suitable for incorporating into inflection S‐shaped NHPP growth models.

This paper presents the WLSE results with equal weight. Future research may be carried out for unequal weights.

Software reliability modeling and estimation are a major concern in the software development process, particularly during the software testing phase, as unreliable software can cause a failure in the computer system that can be hazardous. The results obtained in this paper may facilitate the software engineers, scientists, and managers in improving the software testing process.

The proposed SRGM has a flexible structure and may capture features of both exponential and S‐shaped NHPP growth models for failure phenomenon.