Optimization for software release and crash

Software testing is a process to detect faults in the completeness and quality of developed computer software. Testing is a key process in assuring quality by identifying defects in software, and possibly fixing them, before it is delivered to end-users. A major decision to make during this software testing is, to determine whether to continue testing and eventually releasing the software, or when to stop the test and ‘crash’ it. Such a decision needs to be made to optimally balance the tradeoff between the cost of development and the reliability of the software. In this paper, a new optimal strategy is developed based on a conditional non-homogeneous Poisson process (Conditional-NHPP) on a continuous time horizon to determine when the optimal time is to release or crash the software

Search based software engineering: Trends, techniques and applications

© ACM, 2012. This is the author's version of the work. It is posted here by permission of ACM for your personal use. Not for redistribution. The definitive version is available from the link below.In the past five years there has been a dramatic increase in work on Search-Based Software Engineering (SBSE), an approach to Software Engineering (SE) in which Search-Based Optimization (SBO) algorithms are used to address problems in SE. SBSE has been applied to problems throughout the SE lifecycle, from requirements and project planning to maintenance and reengineering. The approach is attractive because it offers a suite of adaptive automated and semiautomated solutions in situations typified by large complex problem spaces with multiple competing and conflicting objectives. This article provides a review and classification of literature on SBSE. The work identifies research trends and relationships between the techniques applied and the applications to which they have been applied and highlights gaps in the literature and avenues for further research.EPSRC and E

Emulation is the most sincere form of flattery : retro videogames, rom distribution and copyright

The Internet has made it possible for amateur game creators to collaborate on projects irrespective of geographical location. The success of projects such as Minecraft, and even CounterStrike, demonstrates that ‘indie’ developers can create entertainment products just as popular and successful as mainstream developers with huge budgets. However, many individuals instead are more interested in the old than the new – reliving past experiences through the playing of old videogames that are no longer commercially sold. Through the creation of emulators, and the ripping of ROM images (data that allows for the playing of an emulated videogame, such as Super Mario Bros. on the Super Nintendo), games with nostalgic value can be easily distributed, played and replayed. In addition, this allows for the preservation of legacy content that may otherwise be consigned to the ‘dustbin of history’. However, irrespective of the effort and ingenuity that goes into the creation of emulation software, and the effort involved in ripping ROM data to make old games playable, are these pursuits entirely legal? The purpose of this paper is to consider the compatibility of such projects with pre-existing norms of intellectual property law, comparing and contrasting the approaches of US and EU IP regimes in their handling of emulators and ROMS. The paper will analyse the issue under pre-existing legislation and with regard to relevant case law, seeking to draw conclusions on whether the existing regimes in copyright law are compatible and satisfactorily balance the right of videogame publishers to seek fair remuneration for their work with the desire by enthusiasts to preserve and relive a form of creative culture

Robust Dynamic Selection of Tested Modules in Software Testing for Maximizing Delivered Reliability

Software testing is aimed to improve the delivered reliability of the users. Delivered reliability is the reliability of using the software after it is delivered to the users. Usually the software consists of many modules. Thus, the delivered reliability is dependent on the operational profile which specifies how the users will use these modules as well as the defect number remaining in each module. Therefore, a good testing policy should take the operational profile into account and dynamically select tested modules according to the current state of the software during the testing process. This paper discusses how to dynamically select tested modules in order to maximize delivered reliability by formulating the selection problem as a dynamic programming problem. As the testing process is performed only once, risk must be considered during the testing process, which is described by the tester's utility function in this paper. Besides, since usually the tester has no accurate estimate of the operational profile, by employing robust optimization technique, we analysis the selection problem in the worst case, given the uncertainty set of operational profile. By numerical examples, we show the necessity of maximizing delivered reliability directly and using robust optimization technique when the tester has no clear idea of the operational profile. Moreover, it is shown that the risk averse behavior of the tester has a major influence on the delivered reliability.Comment: 19 pages, 4 figure