scispace - formally typeset
Search or ask a question
Topic

Legacy mode

About: Legacy mode is a research topic. Over the lifetime, 51 publications have been published within this topic receiving 693 citations. The topic is also known as: compatibility mode.


Papers
More filters
Book ChapterDOI
08 May 2006
TL;DR: This work has built upon the L2CBD (Legacy to Component Based Development) methodology providing reengineering process including concrete procedures, product-works, guidelines and considerations, and can transform legacy systems into new component system with improved software architecture by adapting L1CBD.
Abstract: Most legacy systems are being pressured to continuously respond to changing requirements, but it is impossible almost to cope with these requests effectively. Because many legacy systems have suffered from lack of standardization and openness, difficulty of change, and absence of distributed architecture. Especially, according as legacy system has been deteriorating from an architectural point of view over the years, we must continually maintain these legacy systems at high cost for applying new technologies and extending their business requirements. For the purposes of transforming a legacy system into component system, we need systematic methodologies and concrete guidelines. Through these, we can share information at different levels of abstraction ranging from code to software architecture, and construct the component system with better component-based architecture. To achieve these goals, we have built upon the L2CBD (Legacy to Component Based Development) methodology providing reengineering process including concrete procedures, product-works, guidelines and considerations. We can transform legacy systems into new component system with improved software architecture by adapting L2CBD.

6 citations

Patent
12 Aug 2010
TL;DR: In this article, an output stage comprising a current mode line driver, a voltage mode driver, and a center-tapped transformer for coupling data provided by the line drivers to a transmission line is provided.
Abstract: An output stage comprising a current mode line driver, a voltage mode line driver, and a center-tapped transformer for coupling data provided by the line drivers to a transmission line is provided herein. The output stage is configured to operate in a backwards compatible Ethernet communication device. For example, the Ethernet communication device is configured to support 10G Ethernet and legacy Ethernet modes of 10BASE-T, 100BASE-T, and 1000BASE-T. The current mode line driver can be utilized while operating in the 10G Ethernet mode to provide high linearity. The voltage mode line driver can be utilized while operating in legacy mode to conserve power. In order to accommodate the use of two different line drivers, a switch and/or a voltage regulator is used to couple/decouple a dc voltage to a center-tap of the transformer based on which of the two different line drivers is currently active.

6 citations

Patent
30 May 2019
TL;DR: In this paper, the authors proposed a backoff counter mechanism for wireless networks consisting of an access point and non-AP stations with traffic queues and associated backoff counters which are decremented over time upon continuously sensing the medium as free during more than respective AIFS durations.
Abstract: The invention relates to wireless network comprising an access point and non-AP stations. The station has traffic queues and associated a backoff counters which are decremented over time upon continuously sensing the medium as free during more than respective AIFS durations. To compensate additional opportunities provided by OFDMA RUs, a queue switches to an MU mode upon transmitting its data in an RU provided by the AP. To restore dynamicity of the backoff counters, frozen in the MU mode in the known techniques, embodiments provide the following at each expiry of one of the queue backoff counters: the current mode of the expiring traffic queue is determined; in case of legacy mode, the station accesses the channel to transmit data from the queue; whereas in case of MU mode, a new backoff value is drawn to reset the expiring backoff counter, without having data from the queue being transmitted.

5 citations

Journal Article
TL;DR: A reverse engineering process based on Model Driven engineering is proposed that presents a solution to provide a normalized relational database which includes the integrity constraints extracted from legacy data.
Abstract: The previous management information systems turning on traditional mainframe environment are often written in COBOL and store their data in files; they are usually large and complex and known as legacy systems. These legacy systems need to be maintained and evolved due to several causes, including correction of anomalies, requirements change, management rules change, new reorganization, etc. But, the maintenance of legacy systems becomes over years extremely complex and highly expensive, In this case, a new or an improved system must replace the previous one. However, replacing those systems completely from scratch is also very expensive and it represents a huge risk. Nevertheless, they should be evolved by profiting from the valuable knowledge embedded in them. This paper proposes a reverse engineering process based on Model Driven engineering that presents a solution to provide a normalized relational database which includes the integrity constraints extracted from legacy data. A CASE tool CETL: (COBOL Extract Transform Load) is developed to support the proposal. Keywords: legacy data, reverse engineering, model driven engineering, COBOL metamodel, domain class diagram, relational database

5 citations

Book ChapterDOI
23 Oct 2011
TL;DR: This paper explains how the RDB-to-RDF platform OntoAccess can be used to transition legacy systems into Semantic Web-enabled applications and exemplifies how it successfully made a bridge between one of its own large-scale legacy systems and its long-term replacement.
Abstract: Business-critical legacy applications often rely on relational databases to sustain daily operations. Introducing Semantic Web technology in newly developed systems is often difficult, as these systems need to run in tandem with their predecessors and cooperatively read and update existing data. A common pattern is to incrementally migrate data from a legacy system to its successor by running the new system in parallel, with a data bridge in between. Existing approaches that can be deployed as a data bridge in theory, restrict Semantic Web-enabled applications to read legacy data in practice, disallowing update operations completely. This paper explains how our RDB-to-RDF platform OntoAccess can be used to transition legacy systems into Semantic Web-enabled applications. By means of a case study, we exemplify how we successfully made a bridge between one of our own large-scale legacy systems and its long-term replacement. We elaborate on challenges we faced during the migration process and how we were able to overcome them.

4 citations

Network Information
Related Topics (5)
Layer (object-oriented design)
5.8K papers, 44.8K citations
83% related
Reference architecture
11K papers, 196.4K citations
81% related
Software measurement
5.3K papers, 129.1K citations
79% related
Darwin (ADL)
4.2K papers, 72.3K citations
79% related
Software design pattern
5.9K papers, 147.8K citations
79% related
Performance
Metrics
No. of papers in the topic in previous years
YearPapers
20211
20191
20182
20172
20163
20152