The DOI matches its Crossref record.
Leveraging legacy system dollars for e-business
Abstract
Although many firms have rapidly and enthusiastically adopted distributed architectures, many more are stuck with mainframe based mission-critical systems that continue to isolate them from their partner, supplier, and customer systems. Most companies want to transform their applications to meet new business demands, but because legacy systems tend to be unwieldy, monolithic, and inflexible, many firms regard modernization as somewhere between improbable and impossible. Reeling from the Y2K debacle and saddled with years of application backlog, the most these companies can hope for is to keep their legacy system alive. And keeping it alive is getting more expensive. It is also becoming harder to find qualified personnel to do the maintenance. All of this makes it difficult to add new functionality and keep up with business requirements. The ideal solution is to transform legacy systems to newer, more productive platforms so that companies can exploit faster and cheaper development technologies, like Java and XML (Extensible Markup Language). The focus then shifts to functionality, not the infrastructure, which means a company can respond more quickly to its changing business requirements and technology enhancements. RescueWare, legacy transformation software from Relativity Technologies, breaks business knowledge into stand-alone pieces, or e-components. The e-components are basically collections of objects that perform specific business services, have clearly defined application program interfaces (APIs), and are accessible through modern industry-standard protocols.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cited by
GenProg: A Generic Method for Automatic Software Repair
Le Goues, C., Nguyen, T., Forrest, S., & Weimer, W. (2012) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2011.104 · Cited by 1,085
Revisiting the Impact of Classification Techniques on the Performance of Defect Prediction Models
Ghotra, B., McIntosh, S., & Hassan, A. E. (2015) · 2015 IEEE/ACM 37th IEEE International Conference on Software Engineering · doi:10.1109/icse.2015.91 · Cited by 364
Enabling high-level application development for the Internet of Things
Patel, P., & Cassou, D. (2015) · Journal of Systems and Software · doi:10.1016/j.jss.2015.01.027 · Cited by 252
Code bubbles: a working set-based interface for code understanding and maintenance
Bragdon, A., Zeleznik, R., Reiss, S. P., Karumuri, S., Cheung, W., Kaplan, J., Coleman, C., Adeputra, F., & LaViola, J. J. (2010) · Proceedings of the SIGCHI Conference on Human Factors in Computing Systems · doi:10.1145/1753326.1753706 · Cited by 174
Improving code readability models with textual features
Scalabrino, S., Linares-Vasquez, M., Poshyvanyk, D., & Oliveto, R. (2016) · 2016 IEEE 24th International Conference on Program Comprehension (ICPC) · doi:10.1109/icpc.2016.7503707 · Cited by 114
Seahawk: Stack Overflow in the IDE
Ponzanelli, L., Bacchelli, A., & Lanza, M. (2013) · 2013 35th International Conference on Software Engineering (ICSE) · doi:10.1109/icse.2013.6606701 · Cited by 95
Metadata
- Authors
- Erlikh, L.
- Venue
- IT Professional
- Published
- 2000
- Volume
- 2
- Issue
- 3
- Pages
- 17-23
- ISSN
- 1520-9202 (ISSN-L)
- OpenAlex
- W1990229061
- Cited by
- 400
- References
- 0
- FWCI
- 2.08
- Type
- journal article
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.