Yau, S. and J. Collofello, Some Stability Measures for Software Maintenance. tse, 1980. SE-6: p. 545--552.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....test suite selection can be aggressive or conservative. An aggressive approach tries to minimize the need for regression testing and is appropriate for systems with high existing reliability and for systems where the effect of the changes are small. e.g. as assessed by code impact metrics like [17]. A conservative approach leads to more extensive regression test suites and in domain based testing considers more aspects of domain changes in identifying regression test needs. Thus, a minimal regression testing rule is to rerun all test suites that had to be updated in the previous step. This ....

S.S. Yau and J. Collofello. "Some Stability Measures for Software Maintenance," IEEE Transactions on Software Engineering, Vol SE-6(6), pp. 545-552, November 1980.

.... efficiency is better) 7 As with many other software engineering projects, it is extremely difficult to quantify the benefits of using AOP without a large experimental study, involving multiple programmers using both AOP and traditional techniques to develop and maintain different applications [6, 21, 36]. Such a study has been beyond the scope of our work to date, although we hope to do one in the future. In the meantime, we have developed one initial measure of the degree to which applying AOP techniques can simplify an application. This measure compares suggests that in fact it isn t [9, 10, ....

Yau S. and Collofello J., Some Stability Measures for Software Maintenance, in tse, vol. SE-6: 545--552, 1980.

....analysis. Some experiments on a subset of the system we are studying (23 KLOC) are discussed. They give very promising results. 1 Introduction While maintaining legacy applications, a large portion of the software engineers effort is spent in trying to understand the program and data [11]. To help the software engineers in this task, we have built a tool to let them easily browse through the code and find what they are looking for. A component of this browsing tool is an object oriented browser : a browser which will present the (procedural) code as a hierarchy of classes. A ....

S.S. Yau and J.S. Collofello. Some stability measures for software maintenance. IEEE Transactions on Software Engineering, 6(11):545--552, nov. 1980. 10

....approach have also had a big impact on software robustness, as we will see in the next section. 6 IMPACT ANALYSIS Light analysis, for its approximation character, usually tests for requirements that are stronger than the original one. This gives nice connections with impact analysis (see e.g. [20, 24]) since the software verified with light analysis is stabler with respect to the given requirement R: the losser the lightening, the stabler the software. One can also practically define using light analysis an impact metric measuring the robustness of a software w.r.t. the given requirement R, ....

Yau, S.S., and Collofello, J.S. Some stability measures for software maintenance. IEEE Transactions on Software Engineering 6, 6 (1980), 545--552.

....of the components resulting from the method correspond to meaningful system abstractions. 1. Introduction It is well known that programmer efforts are mostly devoted to maintaining systems [Corb89, Somm92] A large portion of that maintenance effort is spent in understanding the program and data [Yau80]. Within this context, helping maintainers to understand the legacy systems they have to maintain could greatly ease their job. One important first step to assist the maintainer is to provide him her with a global overview of the system. This overview should indicate the main components of the ....

S.S. Yau and J. S. Collofello. Some Stability Measures for Software Maintenance. IEEE Transactions on Software Engineering, 6:545--552, November 1980.

....predict the number of changes required to stabilise a system during maintenance, and determine a strategy for staging releases of a system. The technique relied on manually provided subjective probabilities thereby reducing its usefulness; it also assumed that system requirements were frozen. Yau [Yau80] identifies general problems of the early measures proposed by Haney and those of Myers [Myers79] such as their assumption that all modifications to a module have the same ripple effect, and an assumption of symmetry (that if a change to module a impacts on module b, then the reverse must be ....

S. S. Yau and J. S. Collofello, "Some Stability Measures for Software Maintenance," IEEE Transactions on Software Engineering, vol. SE-6, no. 6, pp. 545-552, 1980.

....rather than by referring to each other s internal elements. Similar to the quantitative measures, these qualitative values are useful only when correlated with desirable qualities. Many researchers have proposed structural complexity metrics, including McClure [McClure 1978] Yau and Collofello [Yau and Collofello 1980], and Henry and Kafura [Henry and Kafura 1981] Although these metrics may be useful in identifying parts of a system that are likely to be difficult to change [Kafura and Reddy 1987] they do not help an engineer answer many of the questions of interest in this dissertation, such as which parts ....

Yau, S. and Collofello, J. 1980. Some stability measures for software maintenance.

No context found.

Yau, S. and J. Collofello, Some Stability Measures for Software Maintenance. tse, 1980. SE-6: p. 545--552.

No context found.

Yau S.S., Collofello J.S. (1980). Some Stability Measures for Software Maintenance, IEEE Transactions on Software Engineering, Vol. SE-6, No. 6, November 1980, 545 - 552.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC