1,721,053 research outputs found
Reuse Reengineering and Validation Via Concept Assignment
No full textThe first step in a software reuse reengineering process is to analyze the structural characteristics of the existing software so as to produce software component sets, each of which is a candidate for clustering and reengineering into a reusable module. This step is founded on one or more candidature criteria and the cost of the following steps depends on their quality. The notions of completeness and adequacy as applied to candidature criteria are introduced, the need for an adequacy validation process before they are applied on a software system is outlined. An adequate validation process founded on the assignment of a concept to the candidate modules is proposed, and the results of an application of this process are described and discusse
A New Methodological Proposal For Program Maintenance
No full textThis paper proposes a methodology relating to the design and implementation of code changes in the code modification phase of the software maintenace cycle. This methodology aims at maintaining the structurization of the control flow. Also illustrated are the characteristics of a tool which supports the methodology proposed and calculates the variation of entropy, considered as the complexity of the control-flow, induced in a program by a maintenance operation
Software Model for Impact Analysis: a Validation Experiment
No full textImpact analysis is the process of identifying software work-products that may be affected by proposed changes. This requires a software representation model that can formalize the knowledge about the various dependencies between work-products.This study was carried out with the aim of objectively assessing whether the effectiveness of an impact analysis approach depends on the software dependency model employed. ANALYST, a tool for impact analysis, was used to implement different impact analysis approaches. The results show that the nature of the components and the traceability relationships employed for impact analysis influence the effectiveness of the approach, but different traceability models affect the various aspects of effectiveness differently. Moreover, this influence is independent of the software development approach, but is sensitive to software quality decay
Note per servire allo studio del complesso paleocristiano di S. Felice a Cimitile (Nola)
No full textPasquale Testini, Note per servire allo studio del complesso paleocristiano di S. Felice a Cimitile (Nota), p. 329-371.
Revisione critica di quanto si è pubblicato intorno ai risultati delle campagne di scavo dirette da G. Chierici a Cimitile (Nola). Si dimostra l'inconsistenza di molte interpretazioni diventate opinioni correnti negli studi successivi, e per la prima volta si tenta una valutazione integrale dei dati a disposizione. I punti di revisione sono: 1. Origine, consistenza e datazione dell'area funeraria, specie nell'uso da parte dei cristiani. - 2. La tomba di s. Felice e sua presunta individuazione. - 3. L'ipotesi fantasiosa di un martyrium collettivo. - 4. La basilica vetus o prepaoliniana. -5. L'abside di ponente e la c.d. iconostasi. - 6. Problema del numero delle «basiliche» trovate da Paolino. - 7. Ruolo della basilica nuova o maior. -8. La cronotassi episcopale alla luce delle nuove acquisizioni. - 9. Il culto di s. Felice nolano e papa Damaso. - 10. Le iscrizioni cristiane di Nola. -11. La cattedrale di Nola urbana o suburbana?Testini Pasquale. Note per servire allo studio del complesso paleocristiano di S. Felice a Cimitile (Nola). In: Mélanges de l'École française de Rome. Antiquité, tome 97, n°1. 1985. pp. 329-371
Evaluating Performances of Pair Designing in Industry
No full textPair programming has attracted an increasing interest from practitioners and researchers: there is initial empirical evidence that it has positive effects on quality and overall delivery time, as demonstrated by several controlled experiments. The practice does not only regard coding, since it can be applied to any other phase of the software process: analysis, design, and testing. Because of the asymmetry between design and coding, applying pair programming to the design phase might not produce the same benefits as those it produces in the development phase. In this paper, we report the findings of a controlled experiment on pair programming, applied to the design phase and performed in a software company. The results of the experiment suggest that pair programming slows down the task, yet improves quality. Furthermore we compare our results with those of a previous exploratory experiment involving students, and we demonstrate how the outcomes exhibit very similar trends
- …
