Search

SOFTWARE REDUCES HEAT BUILDUP IN PRINTERS New software developed at the University of Michigan reduces harmful heat buildup in laser powder bed fusion printers. The printers use a laser to [...]

What is of the greatest importance in war is speed. (1) --Sun Tzu Amateurs talk about tactics, but professionals study logistics. (2) --General Robert H. Barrow, USMC TABLE OF CONTENTS [...]

Problem statement: Estimation models in software engineering are used to predict some important attributes of future entities such as development effort, software reliability and programmers productivity. Among these models, those estimating software effort have motivated considerable research in recent years. Approach: In this study we discussed an available work on the effort estimation methods and also proposed a hybrid method for effort estimation process. As an initial approach to hybrid technology, we developed a simple approach to SEE based on use case models: The 'use case point's method'. This method is not new, but has not become popular although it is easy to understand and implement. We therefore investigated this promising method, which was inspired by function points analysis. Results: Reliable estimates can be calculated by using our method in a short time with the aid of a spreadsheet. Conclusion: We are planning to extend its applicability to estimate risk and benchmarking measures. Key words: Effort estimation, effort refinement, function points, use case points, risk assessment, hybrid method, INTRODUCTION The planning, monitoring and control of software development projects require that effort and costs be adequately estimated. However, some forty years after the term 'Software Engineering' was coined (27), [...]

Problem statement: Program testing is expensive and labor intensive, often consuming more than half of the total development costs, and yet it is frequently not done well and the results are not always satisfactory. The objective of this paper is to present an automatic test data generation tool that aims to completely automate unit testing of JavaScript functions. The methodology: In order to use the proposed tool, the tester annotates the files that contain the class to be tested. Moreover, the tester must specify the test data coverage criterion to be used, either branch coverage or mutation analysis. However, the tool is then integrated into the JavaScript compiler and test generation is invoked by a command line option. Also, the code to be tested is parsed into an abstract syntax tree from which the test tool generates a program dependency graph for the function under test. However, if mutation analysis coverage is required, the abstract syntax tree for a meta-mutant program is also generated. To provide guidance for the test data search, the function under test instrumented in accordance with the coverage criterion. Branch predicate expressions are always instrumented, in the case of mutation coverage, mutated statements are also instrumented. Compilation then continues from the modified abstract syntax tree to generate instrumented executables that were loaded into the test data search module. Results: The experiment done in our study by using the proposed tool for branch coverage shows that the most effective result for string equality was obtained using the edit distance fitness function, while no significant difference was found in the fitness function for string ordering. Through exhaustive mulation coverage 8% are found to be equivalent. Conclusion: By having a complete automation it reduces the cost of software testing dramatically and also facilitates continuous testing. It is reported that at least 50% of the total software development costs is due to testing, and 10-15% of development time is wasted due to frequent stops for regression testing. Automation will also help get rid of cognitive biases that have been found in human testers. Acknowledgment: The researcher would like to express their gratitude to the anonymous referees for their valuable and helpful comments and suggestions in improving the study. Key words: Software testing, white box, black box, genetic algorithms, mutation testing., INTRODUCTION Software testing is as old as the hills in the history of digital computers. The testing of software is an important means of assessing the software to determine its [...]

To link to full-text access for this article, visit this link: http://dx.doi.org/10.1016/j.jss.2007.01.013 Byline: Richard D. Corbin (a), Christopher B. Dunbar (b), Qiuming Zhu (c) Keywords: Knowledge management; Software engineering process; Software system support; Technology innovation; Human and system interaction Abstract: To ensure smooth and successful transition of software innovations to enterprise systems, it is critical to maintain proper levels of knowledge about the system configuration, the operational environment, and the technology in both existing and new systems. We present a three-tier knowledge management scheme through a systematic planning of actions spanning the transition processes in levels from conceptual exploration to prototype development, experimentation, and product evaluation. The three-tier scheme is an integrated effort for bridging the development and operation communities, maintaining stability to the operational performance, and adapting swiftly to software technology innovations. The scheme combines experiences of academic researches and industrial practitioners to provide necessary technical expertise and qualifications for knowledge management in software engineering support (SES) processes. Author Affiliation: (a) Northrop Grumman, Defense Mission Systems, Bellevue, NE 68005, United States (b) FGM Inc., Omaha, NE 68142, United States (c) College of Information Science and Technology, University of Nebraska at Omaha, Omaha, NE 68182, United States Article History: Received 9 September 2006; Revised 28 December 2006; Accepted 5 January 2007 Article Note: (footnote) [star] An earlier version of this paper was presented at the 2006 Command and Control Research and Technology Symposium (CCRTS), San Diego, CA, June 20-22, 2006.

We present a static analysis technique for nontermination inference of logic programs. Our framework relies on an extension of the subsumption test, where some specific argument positions can be instantiated while others are generalized. We give syntactic criteria to statically identify such argument positions from the text of a program. Atomic left looping queries are generated bottom-up from selected subsets of the binary unfoldings of the program of interest. We propose a set of correct algorithms for automating the approach. Then, nontermination inference is tailored to attempt proofs of optimality of left termination conditions computed by a termination inference tool. An experimental evaluation is reported and the analyzers can be tried online at http://www.univ-reunion.fr/~gcc. When termination and nontermination analysis produce complementary results for a logic procedure, then with respect to the leftmost selection rule and the language used to describe sets of atomic queries, each analysis is optimal and together, they induce a characterization of the operational behavior of the logic procedure. Categories and Subject Descriptors: D.2.4 [Software Engineering]: Software/Program Verification--Validation General Terms: Languages, Verification Additional Key Words and Phrases: Logic programming, static analysis, nontermination analysis, optimal termination condition

Computer programming is assumed to be an art requiring craftsmanship without ignoring best practices as the idea of software craftsmanship offers a solution to the problem by advancing the art of software development one generation at a time. The progression of a programmer from apprentice to journeyman to master within the telecommunications domain is discussed.

The Software Technology Center (STC) in Bell Labs Advanced Technologies has defined performance-engineering best practices that help a project meet the performance and capacity requirements for its product. A detailed description of the role of the performance engineer, which is essential to the best practices, is provided.