1995
DOI: 10.1109/2.467576
|View full text |Cite
|
Sign up to set email alerts
|

Transition to a legacy- and reuse-based software life cycle

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
6
0

Year Published

1996
1996
2015
2015

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 22 publications
(6 citation statements)
references
References 7 publications
0
6
0
Order By: Relevance
“…The conventional research is broadly divided into two methods, namely, a method in which an entire program is re-created in a top-down manner and a method in which reusable parts are extracted from legacy software as components to reconstruct a system in a bottom-up manner based on those components [2]. In both cases, the entire program had to be analyzed and relatively large-scale development had to be performed while domain experts and developers cooperated by using special-purpose analysis tools or knowledge bases.…”
Section: Improvement Of Legacy Softwarementioning
confidence: 99%
“…The conventional research is broadly divided into two methods, namely, a method in which an entire program is re-created in a top-down manner and a method in which reusable parts are extracted from legacy software as components to reconstruct a system in a bottom-up manner based on those components [2]. In both cases, the entire program had to be analyzed and relatively large-scale development had to be performed while domain experts and developers cooperated by using special-purpose analysis tools or knowledge bases.…”
Section: Improvement Of Legacy Softwarementioning
confidence: 99%
“…These include Motorola [2], Boeing [3], Philips [4], Hewlett Packard [5], First Boston Corporation [6], US Air Force[Tl.…”
Section: Reusable Software Developmentmentioning
confidence: 99%
“…The organization that has experience in developing software, but not yet used the software reuse concept, there exists extra cost to develop the reusable components from scratch to build and strengthen their reusable software reservoir [7,8] . The cost of developing the software from scratch can be saved by identifying and extracting the reusable components from already developed and existing software systems or legacy systems [9,10] . Tracz in [11] observed that for programmers to reuse software they must first find it useful.…”
Section: Introductionmentioning
confidence: 99%