FRINK Linked Data Fragments server

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

• W100497321 startingPage "118" @default.
• W100497321 abstract "J[ddot{u}]rgen Laartz City planners try to preserve viable old assets, to replace outmoded assets, and to add new assets--all in the context of an infrastructure linking them coherently. IT developers have a good deal to learn from that approach. Companies that want to gain a competitive edge, whether by being the first into a market with new products or by launching an electronic-commerce channel, know how much they depend on information technology architectures to achieve their aims. Usually, though, the architecture is a costly and aging maze of applications, hardware systems, and networks. Far from making it possible to achieve strategic goals, it can make a mockery of them. But by looking at the evolution of another complicated set of systems--those that make up a modern city--senior managers can begin to understand more frilly how the controlled and rational development of an IT architecture can enhance the ability to compete. Stories about companies that stumbled because their IT architectures couldn't accommodate rapid and drastic change are legion. Fast-growing companies are liable to hit a wall when their architectures fail to expand quickly enough to serve new customers cost-efficiently. Long-established companies can lose market share if their architectures lack the flexibility to move products to market as quickly as their competitors do. A leading international bank discovered this problem the hard way. Its strategy involved launching an Internet channel that included an on-line securities brokerage, but its deadlines were so tight that there was no time to integrate the customer interface with the back-end systems where transactions were to be processed. The bank's back-office staff therefore had to input each one by hand, an error-prone process feasible only in the early days of e-brokerage, when volumes were tiny. How could the bank's IT managers have allowed the systems they supervised to undermine rather than advance a strategic goal? The design decisions that had shaped the systems landscape over the years were, individually, sound. The people responsible had focused on delivering the required functionality on time and within budget. But no one had kept an eye on the big picture. The overall systems landscape thus became too complicated, extremely costly, hard to manage, and incapable of responding flexibly to the bank's business needs. Whether chief executives wish to undertake new e-commerce or customer-relationship-management (CRM) initiatives or to replace existing IT systems, they can learn from the way modern cities adapt to the needs of residents and businesses. For, in the same way, a properly conceived and administered IT architecture adapts itself to the diverse and changing needs of the company that deploys it. We could use several cities to make the analogy between city planning and IT architectures, but Paris seems particularly apt. When you walk around Paris, you see a wonderful variety of buildings dating from many centuries; a closer look reveals that a majority of these structures went up in the past hundred years. The infrastructure of Paris, such as its network of roads and bridges, unites these buildings, defining the cityscape and setting the terms in which it has evolved. When Baron Georges-Eug[grave{e}]ne Haussmann was commissioned by Napol[acute{e}]on III to create a new plan for parts of Paris, in the 1850s, he cut boulevards through the existing pattern of streets to facilitate commerce and the movement of troops. Since then, Paris has carefully planned the redevelopment of sections of the city, so that neighborhoods and districts have distinctive social or economic roles. Most office towers, for example, are located outside the historic borders. As a result, the Paris of today, with its Beaubourg and La D[acute{e}]fense, is a modern and highly efficient but unmistakable patchwork of many eras. City planners try to preserve and renovate those old assets that are still viable while replacing others and adding new ones in a coherent way. …" @default.
• W100497321 created "2016-06-24" @default.
• W100497321 creator A5035434994 @default.
• W100497321 creator A5041814450 @default.
• W100497321 creator A5049660769 @default.
• W100497321 date "2000-06-22" @default.
• W100497321 modified "2023-09-23" @default.
• W100497321 title "The Paris Guide to IT Architecture" @default.
• W100497321 hasPublicationYear "2000" @default.
• W100497321 type Work @default.
• W100497321 sameAs 100497321 @default.
• W100497321 citedByCount "6" @default.
• W100497321 crossrefType "journal-article" @default.
• W100497321 hasAuthorship W100497321A5035434994 @default.
• W100497321 hasAuthorship W100497321A5041814450 @default.
• W100497321 hasAuthorship W100497321A5049660769 @default.
• W100497321 hasConcept C123657996 @default.
• W100497321 hasConcept C127576917 @default.
• W100497321 hasConcept C142362112 @default.
• W100497321 hasConcept C144133560 @default.
• W100497321 hasConcept C151730666 @default.
• W100497321 hasConcept C153349607 @default.
• W100497321 hasConcept C162324750 @default.
• W100497321 hasConcept C162853370 @default.
• W100497321 hasConcept C187736073 @default.
• W100497321 hasConcept C2776598745 @default.
• W100497321 hasConcept C2779343474 @default.
• W100497321 hasConcept C2780598303 @default.
• W100497321 hasConcept C40700 @default.
• W100497321 hasConcept C41008148 @default.
• W100497321 hasConcept C54750564 @default.
• W100497321 hasConcept C58546491 @default.
• W100497321 hasConcept C76155785 @default.
• W100497321 hasConcept C86803240 @default.
• W100497321 hasConceptScore W100497321C123657996 @default.
• W100497321 hasConceptScore W100497321C127576917 @default.
• W100497321 hasConceptScore W100497321C142362112 @default.
• W100497321 hasConceptScore W100497321C144133560 @default.
• W100497321 hasConceptScore W100497321C151730666 @default.
• W100497321 hasConceptScore W100497321C153349607 @default.
• W100497321 hasConceptScore W100497321C162324750 @default.
• W100497321 hasConceptScore W100497321C162853370 @default.
• W100497321 hasConceptScore W100497321C187736073 @default.
• W100497321 hasConceptScore W100497321C2776598745 @default.
• W100497321 hasConceptScore W100497321C2779343474 @default.
• W100497321 hasConceptScore W100497321C2780598303 @default.
• W100497321 hasConceptScore W100497321C40700 @default.
• W100497321 hasConceptScore W100497321C41008148 @default.
• W100497321 hasConceptScore W100497321C54750564 @default.
• W100497321 hasConceptScore W100497321C58546491 @default.
• W100497321 hasConceptScore W100497321C76155785 @default.
• W100497321 hasConceptScore W100497321C86803240 @default.
• W100497321 hasLocation W1004973211 @default.
• W100497321 hasOpenAccess W100497321 @default.
• W100497321 hasPrimaryLocation W1004973211 @default.
• W100497321 hasRelatedWork W133774103 @default.
• W100497321 hasRelatedWork W1489534833 @default.
• W100497321 hasRelatedWork W168706578 @default.
• W100497321 hasRelatedWork W17257708 @default.
• W100497321 hasRelatedWork W17345720 @default.
• W100497321 hasRelatedWork W179193715 @default.
• W100497321 hasRelatedWork W200401291 @default.
• W100497321 hasRelatedWork W22211832 @default.
• W100497321 hasRelatedWork W22229519 @default.
• W100497321 hasRelatedWork W227209618 @default.
• W100497321 hasRelatedWork W249641148 @default.
• W100497321 hasRelatedWork W2599736599 @default.
• W100497321 hasRelatedWork W2611824423 @default.
• W100497321 hasRelatedWork W272138956 @default.
• W100497321 hasRelatedWork W298296574 @default.
• W100497321 hasRelatedWork W3039811002 @default.
• W100497321 hasRelatedWork W332144192 @default.
• W100497321 hasRelatedWork W845029957 @default.
• W100497321 hasRelatedWork W96906523 @default.
• W100497321 hasRelatedWork W2600934400 @default.
• W100497321 isParatext "false" @default.
• W100497321 isRetracted "false" @default.
• W100497321 magId "100497321" @default.
• W100497321 workType "article" @default.