New Version Of Software Research Articles

Multi‐upgradation software reliability growth model with dependency of faults under change point and imperfect debugging

AbstractWith the improvement of innovation, software developers consistently build up a new version of software by adding new features in the previously existing version of the software. In resent day's competitive market, the reliability and release time of multi‐upgradation software are very important issues to both: customers and developers. Many researchers have proposed various software reliability growth models (SRGMs) to improve the precision of assessing the reliability of programming. For reliability estimation, a detailed study is necessary to know the characteristics of different types of faults. It has been noticed that some faults present in software remove independently at the same time some faults remove some other faults. During upgradation, new faults generate due to many reasons. Though dependency of faults is an important issue, there is no such SRGM exist for multi‐release problem. Hence, an SRGM has been proposed for multi‐release problems here with the dependency of faults under the imperfect debugging phenomenon. The effect of change point has been incorporated in SRGM due to changes in testing strategy, changes in testing environments, and so forth, during up‐gradation. Based on datasets, it can be said the performance of the proposed model is better than some other existing models. Also, it is very important for software companies to know the optimal time of release a new version of software. As testing charges change with time, it cannot be constant throughout testing phase. Hence, a new random cost model has also been proposed for release time analysis in case of a multi‐release problem.

Mahtab: Phase-wise acceleration of regression testing for C

Software regression testing consists of offline, online, and execution phases which are executed sequentially. The offline phase involves code instrumentation and test-coverage collection. Subsequently, the online phase performs program differencing, test-suite selection and prioritization. Finally, the selected test-cases are executed against the new version of software for its re-validation. Regression testing is a time-consuming process and is often on the critical path of the project. To improve the turn-around time of software development cycle, our goal is to reduce regression testing time across all phases using multi-core parallelization. This poses several challenges that stem from I/O, dependence on third-party libraries, and inherently sequential components in the overall testing process. We propose parallelization test-windows to effectively partition test-cases across threads. To measure the benefit of prioritization coupled with multi-threaded execution, we propose a new metric, EPSilon, for rewarding failure observation frequency in the timeline of test-execution. To measure the rate of code-change coverage due to regression test prioritization, we introduce ECC, a variant of the widely used APFD metric. We illustrate the effectiveness of our approach using the popular Software-artifact Infrastructure Repository (SIR) and five real-world projects from GitHub.

Software Announcement: Multichoice as a New Software for Decision Making with Analytic Network Process

This paper describes main features of Multichoice, a new version of software for multi-criteria decision analysis with ANP/AHP. Multichoice has been developed by authors at the Central Institute of Economics and Mathematics of the Russian Academy of Science in Moscow in 2016, and is the first software for ANP in Russia (available in Russian and English). The paper outlines the main steps of ANP technology: model constructing, relative and absolute evaluating, synthesizing, visualizing and importing the results, and sensitivity analysis. The authors also discuss further development of implementation of ANP-algorithms.

Finding Proneness of S/W using Class Hierarchy Method

When it is requiring, releasing a new version of software it is helpful to take reference of old version. If developers know in advance which classes or methods of software may be change or will cause faults then developers can focus more on these classes. It is require identifying classes at earlier stages of development which may cause changes or faults in other classes, so that those classes can be given special attention. The technique presented here improves the quality and reliability of the software. To achieve corrective and adaptive maintenance we require making changes during the software evolution. It is important to analyze the frequency of changes in individual classes and also to identify and show related changes in multiple classes as these changes are key components of software. Prediction of change-prone and fault prone classes of a software is an active topic under research in the area of software engineering. Such prediction can be used to predict changes and faults in different classes of a system from one release to the next release of software. Finding the change-prone and fault prone classes from software in advance can help the developers to focus more attention on these classes. The proposed model presenting a technique for finding dependency of software, change-prone classes and fault-prone classes of Object Oriented Software.

SU‐GG‐T‐159: Has IMRT Delivery Improved in the Last 5 Years?

Purpose: To determine whether institutions that participate in clinical trials are delivering IMRT more accurately than they were five years ago. Method and Materials: Anthropomorphic head phantoms were mailed to institutions wishing to participate in national clinical trials using IMRT. The phantoms consisted of an imagable insert containing a primary PTV, a secondary PTV and an OAR. The insert also housed TLD and radiochromic film. The institutions imaged the phantom and planned and delivered an IMRT treatment as though it were a patient. The phantom was returned and the TLD and film were analyzed. The delivered dose distribution was compared with the institutions' treatment plans and the results judged against 7% dose and 4 mm DTA criteria developed by the RPC and the RTOG. Results: Between 2001 and 2007 the phantom was irradiated 475 times. The overall pass rate was 76%. The pass rate prior to 2005 was 70%. The pass rate for 2005 was 76% and the pass rates for 2006 and 2007 were 76% and 80% respectively. Conclusion: Institutions interested in participating in NCI sponsored IMRT protocols are delivering IMRT more accurately than they were 4 years ago. One of the reasons for this is improved modeling capabilities in treatment planning systems. One of the most common treatment machine/planning system combinations has shown an improvement in pass rates since a new version of software became available. Other reasons could include improvements in the tools for patient‐specific QA and improvements in the commissioning of IMRT systems. Though there has been improvement, there is still room for more. 20% of the irradiations are still failures. Adequate IMRT quality assurance and commissioning is essential now as always. Conflict of Interest: Work supported by PHS grant CA10953 and CA081647 from the NCI, DHHS.

A technique for the selective revalidation of OO software

The object-orientated paradigm provides the power for software development but at the same time introduces some brand new problems. One of these problems is that the relationships among classes are more complex and difficult to identify than those in the traditional paradigm. This problem becomes a major obstacle for regression testing of OO software, in which the relationships among classes as well as those between test cases and classes, must be determined a priori. In this paper we propose a new method to select only a fraction of the test cases from the entire test suite to revalidate an OO software system. This method is based on the concepts of class firewall and of marking all the classes ‘touched’ by a test case. From the class firewall, we can identify all of the affected classes after a new version of software is released. Together with the markings, we can also identify all the test cases in the test suite that need to be retested after the software change. A step-by-step process is proposed to identify the relationships between classes and test cases, compute the class firewall, and select only the appropriate test cases for retesting. © 1997 John Wiley & Sons, Ltd.

EDuced

New versions of telecommunication software usually spell trouble for those of us who've established routines for access to remote systems such as OCLC. Over the years, I've become accustomed to the keyboard gymnastics often needed to generate proper responses while searching OCLC and editing bibliographic records. I certainly have become a more careful typist, to avoid retyping the long or complicated field changes that accommodate the cataloging idiosyncrasies of my library. But given the choice between charting the unknown of a new version of software or continuing my familiar, if contorted, drills using all of my available digits in a coordinated keyboard dance, I opt for the more complicated safety of a familiar stream of fixed and variable fields rather than risk eliciting the “Message not clear” warning.

Cataloging CD-ROMs at the Ohio State University

Wang is serials cataloger at the Ohio State University Libraries in Columbus, Ohio. The new information storage and distribution medium CD-ROM (Compact Disc Read-Only Memory) has changed the Ohio State University Libraries in a visible way. Since October 1986, seven departmental libraries have provided CD-ROM workstations for public access to various CD-ROM databases to which the libraries subscribe. The bibliographic information for these databases is also accessible in the online public access catalog, the Library Control System (LCS). It is a challenge :to catalog this versatile medium, CD-ROM, for it requires an ongoing effort to keep abreast of the product's technical characteristics and specifications. The technology is developing so rapidly that some producers provide a new version of software with each quarterly cumulative disk. The system requirements are constantly changing because of system enhancements, and so are the cataloging rules. In October 1986, we cataloged according to Chapter 9 of the second edition of the Anglo-American Cataloging Rules (AACR2), the Guidelines for Using AACR2 Chapter 9 for Cataloging Microcomputer Software, and the first edition of the Machine-Readable Data Files Format. Presently, we catalog according to the Anglo-American Cataloging Rules, Second Edition. Chapter 9, Computer Files (Draft Revision) and the second edition of Machine-Readable Data Files Format (MRDF). The changes prescribed by Chapter 9 (draft revision) are not included, however, in the revision pages of the second edition of the MRDF format, which were issued in March 1987. The multiple variations of hardware and software of this volatile medium present problems for bibliographic control. Much has been written on the