FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W116455940> ?p ?o ?g. }

• W116455940 startingPage "182" @default.
• W116455940 abstract "The IT community is slowly coming to terms with the fact that no company, big or small, will ever be able to build a fully homogeneous and coherent IT infrastructure. IT people will always be developing new platforms, packages, and tools, and companies will always be seeking new business opportunities. Together, they will ensure that the perfect IT solution remains an ever-moving target. Even the company that scraps its messy systems and invests in a sleek replacement has no guarantee that the result will be compatible with the systems operated by a company it might acquire some time in the future. Companies must therefore turn their minds to how their present systems can adapt to the technological developments and new business challenges that Lie ahead. Several approaches exist that involve bolting a new system on to old ones to create a user interface that integrates the data and functionalities of multiple existing systems. Such approaches are likely to deliver business value much faster than those that entail replacing or completely redesigning established systems, and industry experts increasingly see them as the way forward. However, some front-end approaches are better than others. The difference lies in the way in which the old and new systems are glued together. Some methods are simply a temporary patch on an incomplete system; others, a permanent enhancement that will enable a business to stay ahead of the competition. Technical experts and CEOs alike need to be aware of the options. THE FILE COPY APPROACH The simplest way to connect old and new is to files of data from the various legacy systems to each new system that the business requires. Suppose a company has set up a call center to deal with customers who fail to pay their bills. To allow operators to chase missing payments, it copies files containing default invoices, product data, and customers' addresses and phone numbers from the relevant legacy systems to the call center system. The drawback of this copy approach is that it can act only as a temporary solution for a dynamic company. As the demand for data files from different user groups grows, the system architecture will start to look like spaghetti. Not just the call center but the audit department will want data files; so will production planning and marketing. If this improvised, case-by-case integration continues, life will become miserable for the IT department and frustrating for the rest of the business, as everything is glued to everything else in a typically undocumented fashion. Needless to say, the cost of change will rise constantly. THE DATA WAREHOUSE APPROACH To avoid undue fragmentation, the IT community has begun to introduce data warehouses. As in the file approach, these provide buffered connectivity between old and new systems, but this time at corporate level to deal with data demands from all a company's various users. With such a warehouse, a user can collate read-only data from any system, be it marketing, production planning, or auditing. And when the IT department wants to replace one of the systems, it must simply ensure that the new one delivers the same data to the warehouse; other applications will not be affected. The data warehouse thus acts as an overall layer of insulation between different systems. The problem with the data warehouse is that it is a read-only resource, adequate for decision-making purposes but of no value in operations that call for functionality and intelligence in both read and write modes. For such uses, a real-time glue is required to allow new applications to communicate directly with existing systems. THE DIRECT ONLINE APPROACH Many tools exist for this purpose, including message exchange, direct database query techniques, and screen scrapers (a software robot controlled by the new application that types on the terminal interface of the existing system and reads the answer from the reply screens). …" @default.
• W116455940 created "2016-06-24" @default.
• W116455940 creator A5041814450 @default.
• W116455940 date "1996-01-01" @default.
• W116455940 modified "2023-09-23" @default.
• W116455940 title "Current Research: Sticking Together: How Best to Connect IT Systems" @default.
• W116455940 hasPublicationYear "1996" @default.
• W116455940 type Work @default.
• W116455940 sameAs 116455940 @default.
• W116455940 citedByCount "0" @default.
• W116455940 crossrefType "journal-article" @default.
• W116455940 hasAuthorship W116455940A5041814450 @default.
• W116455940 hasConcept C144133560 @default.
• W116455940 hasConcept C162853370 @default.
• W116455940 hasConcept C18903297 @default.
• W116455940 hasConcept C195094911 @default.
• W116455940 hasConcept C41008148 @default.
• W116455940 hasConcept C4216890 @default.
• W116455940 hasConcept C57252376 @default.
• W116455940 hasConcept C86803240 @default.
• W116455940 hasConcept C91306197 @default.
• W116455940 hasConceptScore W116455940C144133560 @default.
• W116455940 hasConceptScore W116455940C162853370 @default.
• W116455940 hasConceptScore W116455940C18903297 @default.
• W116455940 hasConceptScore W116455940C195094911 @default.
• W116455940 hasConceptScore W116455940C41008148 @default.
• W116455940 hasConceptScore W116455940C4216890 @default.
• W116455940 hasConceptScore W116455940C57252376 @default.
• W116455940 hasConceptScore W116455940C86803240 @default.
• W116455940 hasConceptScore W116455940C91306197 @default.
• W116455940 hasIssue "1" @default.
• W116455940 hasLocation W1164559401 @default.
• W116455940 hasOpenAccess W116455940 @default.
• W116455940 hasPrimaryLocation W1164559401 @default.
• W116455940 hasRelatedWork W159726073 @default.
• W116455940 hasRelatedWork W179193715 @default.
• W116455940 hasRelatedWork W1977958656 @default.
• W116455940 hasRelatedWork W2023277635 @default.
• W116455940 hasRelatedWork W22211832 @default.
• W116455940 hasRelatedWork W22229519 @default.
• W116455940 hasRelatedWork W248350135 @default.
• W116455940 hasRelatedWork W2612579588 @default.
• W116455940 hasRelatedWork W272037733 @default.
• W116455940 hasRelatedWork W281375546 @default.
• W116455940 hasRelatedWork W284826590 @default.
• W116455940 hasRelatedWork W290190855 @default.
• W116455940 hasRelatedWork W3165570514 @default.
• W116455940 hasRelatedWork W3182773432 @default.
• W116455940 hasRelatedWork W3194316973 @default.
• W116455940 hasRelatedWork W639257816 @default.
• W116455940 hasRelatedWork W96906523 @default.
• W116455940 hasRelatedWork W2274987722 @default.
• W116455940 hasRelatedWork W2600934400 @default.
• W116455940 hasRelatedWork W2966141639 @default.
• W116455940 isParatext "false" @default.
• W116455940 isRetracted "false" @default.
• W116455940 magId "116455940" @default.
• W116455940 workType "article" @default.