Search

This study generalizes some of the symptoms of ageing of a legacy system. Each symptom is specified by metrics and the results of the measurements made suggest what operations should be undertaken to renew the software. The study is based on retrospective analysis of data collected during the execution of a large renewal process of a very old legacy system. It therefore provides evidence of the expected efficacy of such renewal processes and can be used to decide how best to plan them and manage them in order to increase their efficacy. It can also be used to define the reengineering requirements to ensure long life to the system despite successive evolutions of the application and the operation domain. The metrics can provide a basis for monitoring a software system to ensure that its quality does not degrade to such an extent that the most costly and risky renewal processes then have to be performed to improve it. Finally, the paper points out the problems with renewal processes that still remain open. [ABSTRACT FROM AUTHOR]

To improve a working process, one or more process components can be replaced by innovative ones. The literature provides a possible source of innovative process components. However, it is often difficult to evaluate whether a particular innovative process component satisfying an improvement goal can be introduced to replace a process component in the working software process to be improved. In previous works, the authors of this paper proposed a characterization and evaluation framework to address the above problem. To improve the usability of the framework, a scenario was defined for each question to help the user answer it methodically. The experiment presented in this paper aims to verify if a scenario-based reading technique improves the usability of the framework. The results obtained show that the technique proposed makes assessment of which process components of a working process are candidates for making innovation more reliable. Moreover, the scenario-based reading technique is user independent and only a little training may be sufficient to sensibly improve the effectiveness of use of the scenarios. The trustworthy results of this technique and its independence of the user's previous knowledge and ability ensure that it can be applied methodically. [ABSTRACT FROM AUTHOR]

This work is based on a retrospective analysis of a renewal process applied to a very aged, highly degraded software system. Some parts of the results are generalized to define a method for determining the technical and economic qualities of software system components. The work also presents a decision model for identifying the most suitable renewal process to be applied, based on the quality of the components and the aims of the renewal process. With the model presented, decision making on the renewal process is specialized to each component of the software system, thus ensuring greater benefits from the process as a whole. The same model can be used to monitor software system quality decay and thus avoid the need to use the most costly renewal processes. [ABSTRACT FROM AUTHOR]

Provides information on the Prometheus model, which integrates data on process modeling, manages process execution and captures process and product evolution in software development. Benefits of the model; Elements of Prometheus; Description of structured planning.

An alternative approach to developing reusable components from scratch is to recover them from existing systems. In this paper, we apply program slicing, a program decomposition method, to the problem of extracting reusable functions from illstructured programs. As with conventional slicing first described by Weiser, a slice is obtained by iteratively solving data flow equations based on a program flow graph. We extend the definition of program slice to a transform slice, one that includes statements which contribute directly or indirectly to transform a set of input variables into a set of output variables. Unlike conventional program slicing, these statements do not include either the statements necessary to get input data or the statements which test the binding conditions of the function. Transform slicing presupposes the knowledge that a function is performed in the code and its partial specification, only in terms of input and output data. Using domain knowledge we discuss how to formulate expectations of the functions implemented in the code. In addition to the input/output parameters of the function, the slicing criterion depends on an initial statement, which is difficult to obtain for large programs. Using the notions of decomposition slice and concept validation we show how to produce a set of candidate functions, which are independent of line numbers but must be evaluated with respect to the expected behavior. Although human interaction is required, the limited size of candidate functions makes this task easier than looking for the last function instruction in the original source code. [ABSTRACT FROM AUTHOR]

The article discusses various topics published within the issue, including one by Karl Cox, Mahmood Niazi, and June Verner on engineering practices, another by Valerie Maxville, Jocelyn Armarego, and Chiou Peng Lam on software selection, and another by Lerina Aversano, Luigi Cerulo, and Massimiliano Di Penta on open source projects.

This paper examines the cloud computing for education (CCE) literature, and analyzes if the research is developing scientifically with adequate empirical validation. All aspects of empirical investigations covered in the literature are shown as weak, hence, the necessary scientific development of CCE requires extending its scope of interest, and involving scholars synergistically to create and maintain a “common research agenda.” Background: A need to develop research on CCE has been recognized, and considerable efforts made to create an accurate understanding of the development of its scope of interest, in terms of supporting pedagogical developments and processes for better quality of studies. Research Questions: This paper has three main aims: 1) to evaluate the scope of interest in the literature for CCE with specific reference to pedagogy and educational processes; 2) to analyze the characteristics of papers, specifically empirical studies, from the various points of view of the daily improvement activities of teachers and learners at all levels of education; and 3) to identify eventual research gaps to consider and stimulate new topics or further investigations. Methodology: This systematic mapping study review followed a rigorous, replicable process to collect and analyze representative studies of CCE. Findings: Differences are found across geographic areas in applying CCE infrastructure and technologies in educational institutions; few studies address CCE’s impact on pedagogic processes. The scope of interest in CCE is only partially covered; with empirical research being very shallow. Suggestions are made for more effective research on concerning the production and use of content. [ABSTRACT FROM AUTHOR]

ISO has recently published Part 7 of the ISO/IEC 15504 standard, with the aim of determining the extent to which an organization consistently implements processes that contribute to achievement of its business goals. This new Part 7 of ISO/IEC 15504 has addressed issues related to the assessment of organizational maturity, as the CMMI-DEV model also does. Recently, growing interest has been shown towards the need to harmonize different improvement models or standards, thereby presenting an integrated vision about them. All this being so and in an effort to offer information on how the maturity levels described in these two models are related, we have carried out the harmonization of these two models. It is based, firstly, on a mapping between processes of ISO 12207:08 and process areas of CMMI-DEV, and in second place, on a matching between processes of ISO 12207:08 and ISO 15504-5. For this work, we have taken into account the latest versions of the models, and defined a suitable process to carry out the mapping in a systematic way. We established differences and similarities between the maturity levels (and their processes) described in these models, our goal being to support organizations which are interested in tackling organizational maturity. Copyright © 2009 John Wiley & Sons, Ltd. [ABSTRACT FROM AUTHOR]

During its life, a legacy system is subjected to many maintenance activities, which cause degradation of the quality of the system: When this degradation exceeds a critical threshold, the legacy system needs to be reengineered. In order to preserve the asset represented by the legacy system, the familiarity with it gained by the system's maintainers and users, and the continuity of execution of current operations during the reengineering process, the system needs to be reengineered gradually. Moreover, each program needs to be reengineered within a short period of time. The paper proposes a reengineering process model, which is applied to an in-use legacy system to confirm that the process satisfies previous requirements and to measure its effectiveness. The reengineered system replaced the legacy one to the satisfaction of all the stakeholders; the reengineering process also had a satisfactory impact on the quality of the system. Finally, this paper contributes to validate the cause-effect relationship between the reengineering process and overcoming the aging symptoms of a software system. [ABSTRACT FROM AUTHOR]