A Multi-Process Quality Model: Identification of Key Processes in the Integration Approach

Abstract—In this paper we investigate the use of multiprocessquality model in the adoption of process improvementframeworks. We analyze an improvement effort based onmultiple process quality models adoption. At present, there is apossibility of a software development organization to adoptmulti-quality and improvement models in order to remaincompetitive in the IT market place. Various quality modelsemerge to satisfy different improvement objective such as toimprove capability of models, quality management and serve asIT government purpose. The heterogeneity characteristics ofthe models require further research on dealing with multipleprocess models at a time. We discuss on the concept of softwareprocess and overview on software maintenance and evolutionwhich are important elements in the quality models. Theconcepts related to process quality model and improvementmodels are discussed. The research outlined in this paper showsthat software processes, maintenance, evolution, quality andimprovement have become really important in softwareengineering. The synergy among the multi-focused processquality model is examined with respect to processimprovement. The research outcome is to determine keyprocesses vital to the implementation of multi-process qualitymodel

Towards a unified software attack model to assess software protections

Attackers can tamper with programs to break usage conditions. Different software protection techniques have been proposed to limit the possibility of tampering. Some of them just limit the possibility to understand the (binary) code, others react more actively when a change attempt is detected. However, the validation of the software protection techniques has been always conducted without taking into consideration a unified process adopted by attackers to tamper with programs. In this paper we present an extension of the mini-cycle of change, initially proposed to model the process of changing program for maintenance, to describe the process faced by an attacker to defeat software protections. This paper also shows how this new model should support a developer when considering what are the most appropriate protections to deplo

On Broadening Software Development Productivity Research to Serve Better Software Engineering Management

The unresolved problems of improving software engineering management require a broader systemic approach of investigating related issues like software development productivity. The paper links software engineering management to research on software cost estimation and on factors affecting software development productivity. It examines ways for the systemic incorporation of all issues influencing a software project through application of combination of methods from diverse paradigms

How Information Systems Evolve by and for Use

Few studies have examined dynamic interactions between IT change and organizational change during information system evolution (ISE). We propose a dynamic model of ISE which characterizes ISE related change in four dimensions: 1) planned, 2) improvised, 3) organizational, and 4) IT related. The model- generated inductively through theory-building case studies - enables us narrate a more comprehensive explanation of ISE over time- in particular how such evolution is orchestrated by both planned and improvised change, which tacks between technical and organizational modifications. The model thus recognizes dynamic interactions between organizational and IT change by showing how incremental/improvised changes in IT or organizational processes evolve into pervasive and permanent change when organizations institutionalize these improvisations into new permanent IT designs and revised organizational routines. We demonstrate the analytical value of the proposed evolution model by investigating ISE processes in two manufacturing organizations implementing the same inter-organizational system over a period of two years. This multi-site case study research allows us to more systematically characterize significant socio-technical changes triggered by user improvisation. Our model and associated empirical analysis moves explorations of organizational and IT change towards a more unified understanding of how both mutually affect the form, function and evolution of the other

Comparison and Evaluation of Clone Detection Tools

Many techniques for detecting duplicated source code (software clones) have been proposed in the past. However, it is not yet clear how these techniques compare in terms of recall and precision as well as space and time requirements. This paper presents an experiment that evaluates six clone detectors based on eight large C and Java programs (altogether almost 850 KLOC). Their clone candidates were evaluated by one of the authors as an independent third party. The selected techniques cover the whole spectrum of the state-of-the-art in clone detection. The techniques work on text, lexical and syntactic information, software metrics, and program dependency graphs

Experience in teaching a software reengineering course

Software engineering curricula emphasize developing new software systems. Little attention is given to how to change and modernize existing systems, i.e., the theory and practice of software maintenance and reengineering. This paper presents the author’s experience in teaching software reengineering in a masters-level course at University of Leicester, UK. It presents the course objectives, outline and the lessons learned. The main lessons are: first, there is a big shortage of educational materials for teaching software reengineering. Second, selecting the suitable materials (that balance theory and practice) and the right tool(s) for the level of students and depth of coverage required is a difficult task. Third, teaching reengineering using toy exercises and assignments does not convey the practical aspects of the subject. While, teaching with real, even small size, exercises and assignments, is almost infeasible. Getting the balance right requires careful consideration and experimentation. Finally, students understand and appreciate this topic much more if they have previous industrial experience and when they are presented with real industrial case studies