Gotowe bibliografie tematyczne / Legacy Systems

Gotowa bibliografia na temat „Legacy Systems”

Autor: Grafiati
Data publikacji: 4 czerwca 2021
Data aktualizacji: 27 kwietnia 2022

Utwórz poprawne odniesienie w stylach APA, MLA, Chicago, Harvard i wielu innych

Wybierz rodzaj źródła:

Spis treści

Zobacz listy aktualnych artykułów, książek, rozpraw, streszczeń i innych źródeł naukowych na temat „Legacy Systems”.

Przycisk „Dodaj do bibliografii” jest dostępny obok każdej pracy w bibliografii. Użyj go – a my automatycznie utworzymy odniesienie bibliograficzne do wybranej pracy w stylu cytowania, którego potrzebujesz: APA, MLA, Harvard, Chicago, Vancouver itp.

Możesz również pobrać pełny tekst publikacji naukowej w formacie „.pdf” i przeczytać adnotację do pracy online, jeśli odpowiednie parametry są dostępne w metadanych.

Artykuły w czasopismach na temat "Legacy Systems"

1

Tett, Matt. "Legacy Telecommunication Systems". Australian Journal of Telecommunications and the Digital Economy 3, nr 4 (29.12.2015): 63. http://dx.doi.org/10.18080/ajtde.v3n4.40.

Pełny tekst źródła
Streszczenie:
The subject of legacy telecommunication systems is often overlooked in the pursuit of technological advancement, yet somehow the result is often less than graceful with end users left walking a tightrope between technology they are familiar with, and the evolving replacement systems.
Style APA, Harvard, Vancouver, ISO itp.
2

Tett, Matt. "Legacy Telecommunication Systems". Journal of Telecommunications and the Digital Economy 3, nr 4 (29.12.2015): 63–65. http://dx.doi.org/10.18080/jtde.v3n4.40.

Pełny tekst źródła
Streszczenie:
The subject of legacy telecommunication systems is often overlooked in the pursuit of technological advancement, yet somehow the result is often less than graceful with end users left walking a tightrope between technology they are familiar with, and the evolving replacement systems.
Style APA, Harvard, Vancouver, ISO itp.
3

Vijaya, Aparna, i Neelanarayanan Venkataraman. "Modernizing Legacy Systems". International Journal of Web Portals 10, nr 2 (lipiec 2018): 50–60. http://dx.doi.org/10.4018/ijwp.2018070104.

Pełny tekst źródła
Streszczenie:
Cloud computing is a paradigm which has changed the way organizations develop, manage, and deploy their applications. Most of the resources are available at low costs in this technology and it creates new opportunities for organizations to move their existing applications to the cloud for modernization. But this modernization also comes at a price. The authors present a model-driven approach to address the challenges in application modernization and focus on the application migration to cloud. Most of the cloud applications are very specific to a particular vendor's features or services. The proposed methodology addresses the challenge of vendor lock-in also. The authors present their theoretical details and experience with two pilot projects where they have applied the proposed approach.
Style APA, Harvard, Vancouver, ISO itp.
4

Aiken, Peter, Alice Muntz i Russ Richards. "DoD legacy systems". Communications of the ACM 37, nr 5 (maj 1994): 26–41. http://dx.doi.org/10.1145/175290.175292.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
5

Valverde, Raul, i Malleswara Talla. "Reengineering of Legacy Systems into Supply Chain Systems". International Journal of Organizational and Collective Intelligence 7, nr 2 (kwiecień 2017): 1–12. http://dx.doi.org/10.4018/ijoci.2017040101.

Pełny tekst źródła
Streszczenie:
The paper presents data oriented and process oriented models of legacy systems. It discusses the details of systems development and evolution models mainly aiming at an ongoing reengineering of legacy systems into supply chain systems. It proposes few strategies for reengineering of both data oriented model and process oriented models. The legacy systems often miss automatic interfaces to supply chain systems, so the article presents a strategy focusing on automatic update of data of the system. Likewise, the article also presents a strategy for process reengineering in order to integrate these legacy systems into supply chain systems. Finally, a legacy system is envisioned as a comprehensive mix of both data and process oriented, while proposing a gradual ongoing reengineering of both data structures and process methods.
Style APA, Harvard, Vancouver, ISO itp.
6

Singh, Valdew. "Systems integration ‐ coping with legacy systems". Integrated Manufacturing Systems 8, nr 1 (luty 1997): 24–28. http://dx.doi.org/10.1108/09576069710158763.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
7

Wilson, Mark L. "NAVY LEGACY SYSTEMS REENGINEERING". INCOSE International Symposium 6, nr 1 (lipiec 1996): 1166–69. http://dx.doi.org/10.1002/j.2334-5837.1996.tb02137.x.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
8

Kim, Young-Gul. "Improving Legacy Systems Maintainability". Information Systems Management 14, nr 1 (styczeń 1997): 7–11. http://dx.doi.org/10.1080/10580539708907023.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
9

Madisetti, V. K., Y. K. Jung, M. H. Khan, J. Kim i T. Finnessy. "Reengineering legacy embedded systems". IEEE Design & Test of Computers 16, nr 2 (1999): 38–47. http://dx.doi.org/10.1109/54.765202.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
10

Bennett, K. H., M. Ramage i M. Munro. "Decision model for legacy systems". IEE Proceedings - Software 146, nr 3 (1999): 153. http://dx.doi.org/10.1049/ip-sen:19990617.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
Więcej źródeł

Rozprawy doktorskie na temat "Legacy Systems"

1

Kuipers, Tobias. "Techniques for understanding legacy software systems". [S.l. : Amsterdam : s.n.] ; Universiteit van Amsterdam [Host], 2002. http://dare.uva.nl/document/65858.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
2

Newton, Todd A., Myron L. Moodie, Ryan J. Thibodeaux i Maria S. Araujo. "Network System Integration: Migrating Legacy Systems into Network-Based Architectures". International Foundation for Telemetering, 2010. http://hdl.handle.net/10150/604308.

Pełny tekst źródła
Streszczenie:
ITC/USA 2010 Conference Proceedings / The Forty-Sixth Annual International Telemetering Conference and Technical Exhibition / October 25-28, 2010 / Town and Country Resort & Convention Center, San Diego, California
The direction of future data acquisition systems is rapidly moving toward a network-based architecture. There is a handful of these network-based flight test systems already operating, and the current trend is catching on all over the flight test community. As vendors are churning out a whole new product line for networking capabilities, system engineers are left asking, "What do I do with all of this non-networked, legacy equipment?" Before overhauling an entire test system, one should look for a way to incorporate the legacy system components into the modern network architecture. Finding a way to integrate the two generations of systems can provide substantial savings in both cost and application development time. This paper discusses the advantages of integrating legacy equipment into a network-based architecture with examples from systems where this approach was utilized.
Style APA, Harvard, Vancouver, ISO itp.
3

Jakobsson, Rikard, i Jakob Molin. "Tidsfördelning vid vidareutveckling av "legacy" system". Thesis, KTH, Skolan för elektroteknik och datavetenskap (EECS), 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-279097.

Pełny tekst źródła
Streszczenie:
Att arbeta med ett äldre så kallat legacy-system är en vanlig uppgift bland dagens programmerare men det saknas data om hur arbetsinsatsen är fördelad. Denna data vore användbar för att utvärdera hur kostsamt det är att vidareutveckla ett system kontra en omskrivning eller migration. För att åtgärda detta bidrar den här undersökningen med data som visar arbetsinsatsfördelningen vid migration av ett mindre legacy-system. Frågan som undersöks är ”Hur fördelas kostnaden i tid när man utvärderar och bygger om ett legacy-system?. Grunden för data i denna undersökning kommer ifrån utvecklingen av ett litet studentutvecklat system som använts på KTH och som var i stort behov av uppdatering. Det fanns mycket dokumentation om systemets krav och design, men den kod som fanns var ej användbar då den ej var dokumenterad och saknade klar struktur. Detta ledde till en omskrivning av systemet enligt de krav som tidigare formulerats. I det här projektet användes en vetenskaplig fallstudie med en kvantitativ metod för att få fram resultat. Tiden som lades ned på de moment som identifierats innan uppstart mättes och användes för att beräkna arbetsinsatsfördelningen. Resultatet av denna undersökning är en samling data som kan användas för uppskattningen av arbetsinsatsfördelningen vid omskrivningen av ett mindre legacy-system. I denna undersökning redovisas arbetsinsatsfördelningen som uppmätts under migrationen av ett legacy-system till en ny teknologi, då det existerande systemet inte betraktades som värt att uppdatera. Undersökningens slutsats är att om det finns ett bra förarbete som går att använda för att bygga om systemet så kommer majoriteten av arbetsarbetsinsatsen att läggas på implementeringen av systemet i kod.
Working with legacy-systems is a common task for programmers, and the development of these requires a great effort, but data regarding the distribution of this effort is scarce. This data would be valuable when evaluating the cost of continued development of a system compared to a rewrite or migration. To rectify this, we aim to provide a datapoint regarding the effort distribution for the migration of a small legacy-system. Our question is “How is the cost in time distributed when a legacy-system is evaluated and rebuilt?”. The data presented in this thesis comes from the development of a legacy-system developed by students at KTH. The system needed an update since it had ceased to function. There was a great amount of documentation with regards to requirement specifications and application design which could be used when redeveloping the system. The code, however, lacked any substantial documentation and structure, so it was decided early on that rewriting the system according to the existing documentation was going to be more efficient than working with the code for the current system. A scientific case study built on quantitative methods was used to collect data. To measure effort the time spent on each predefined moment was counted in minutes, and this was used to calculate the distribution of effort. The result of this thesis is a table of data and a review of the distribution of effort when working on a small legacy-system with clear requirements. The data produced in this thesis is based on the effort spent on rewriting a system that was not worth updating. The conclusion of this thesis is that most of the effort will be spent on implementing the code when a clearly defined system is rewritten from the ground up.
Style APA, Harvard, Vancouver, ISO itp.
4

Beijert, Lotte. "Designating Legacy Status to IT Systems : A framework in relation to a future-oriented perspective on legacy systems". Thesis, Internationella Handelshögskolan, Högskolan i Jönköping, IHH, Informatik, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-30337.

Pełny tekst źródła
Streszczenie:
Organizations that have come to depend on legacy systems face quite a paradoxical problem. Maintaining the system might prove ineffective in accommodating necessary changes, but a system migration project is expensive and incurs a high amount of risk. Organizations are therefore hesitant to respond to the legacy system problem by undertaking action. Legacy system are often not causing their organization any problems at present, but a focus on the future with regard to the legacy system problem is lacking. This results in IT systems reaching an end-of-life state. The research therefore set out to explore a future-oriented perspective on legacy systems by means of observation, a literature review and a survey. The researcher found the key concept of a future-oriented perspective to be that any system that is limiting an organization to grow and innovate can be regarded as a legacy system. A framework to designate legacy status to IT systems is proposed in order to guide practitioners to acknowledge a problematic IT system to facilitate appropriate response at the right time. In relation to a future-oriented perspective, when to designate legacy status is best determined according to the system’s flexibility towards change and the alignment of the system with the business. In that regard, IT systems are end-of-life systems when they are too inflexible to change, and as a result become unaligned with either current operations or a future business opportunity or need.
Style APA, Harvard, Vancouver, ISO itp.
5

Narang, Sonia. "Integrating legacy systems with enterprise data store". Thesis, National Library of Canada = Bibliothèque nationale du Canada, 2000. http://www.collectionscanada.ca/obj/s4/f2/dsk1/tape3/PQDD_0022/MQ51775.pdf.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
6

O’Connell, Tim. "PACKET-BASED TELEMETRY NETWORKS OVER LEGACY SYSTEMS". International Foundation for Telemetering, 2005. http://hdl.handle.net/10150/604806.

Pełny tekst źródła
Streszczenie:
ITC/USA 2005 Conference Proceedings / The Forty-First Annual International Telemetering Conference and Technical Exhibition / October 24-27, 2005 / Riviera Hotel & Convention Center, Las Vegas, Nevada
The telemetry industry anticipates the tremendous potential value of adding full networking capability to telemetry systems. However, much of this potential can be realized while working with legacy equipment. By adding modules that interface transparently to existing equipment, continuous telemetry data can be encapsulated in discrete packets for over the air transmission. Packet fields can include header, sequence number and bytes for error detection and correction. The RF packet is transmitted without gaps through a standard serial interface and rate adjusted for the packet overhead – effectively making packetization transparent to a legacy system. The receiver unit performs packet synchronization, error correction, extraction of stream quality metrics and re-encapsulation of the payload data into an internet protocol (IP) packet. These standard packets can then be sent over the existing network transport system to the range control center. At the range control center, the extracted stream quality metrics are used to select the best telemetry source in real-time. This paper provides a general discussion of the path to a fully realized, packet-based telemetry network and a brief but comprehensive overview of the Hypernet system architecture as a case study.
Style APA, Harvard, Vancouver, ISO itp.
7

Burstein, Leah. "Legacy Student Information System: Replacement or Enhancement?" Digital Commons at Loyola Marymount University and Loyola Law School, 2016. https://digitalcommons.lmu.edu/etd/376.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
8

Mickens, Leah M. "Rescuing the legacy project". Thesis, Atlanta, Ga. : Georgia Institute of Technology, 2009. http://hdl.handle.net/1853/28239.

Pełny tekst źródła
Streszczenie:
Thesis (M. S.)--Digital Media, Georgia Institute of Technology, 2009.
Committee Chair: Knoespel, Kenneth; Committee Member: Burnett, Rebecca; Committee Member: Fox Harrell; Committee Member: TyAnna Herrington.
Style APA, Harvard, Vancouver, ISO itp.
9

Onyino, Walter. "Rearchitecting legacy information systems : a service based method". Thesis, Lancaster University, 2001. http://eprints.lancs.ac.uk/11941/.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
10

Tigerström, Viktor, i John Fahlgren. "Migrering av transaktionstunga legacy-system : En fallstudie hos Handelsbanken". Thesis, Uppsala universitet, Institutionen för informatik och media, 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-226766.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
Więcej źródeł

Książki na temat "Legacy Systems"

1

Reengineering legacy software systems. Boston: Digital Press, 1998.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
2

Hoffmeyer, Jesper, red. A Legacy for Living Systems. Dordrecht: Springer Netherlands, 2008. http://dx.doi.org/10.1007/978-1-4020-6706-8.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
3

Warren, Ian. The Renaissance of Legacy Systems. London: Springer London, 1999. http://dx.doi.org/10.1007/978-1-4471-0817-7.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
4

Abuhelgha, Mohammed Ibrahim. Mining legacy systems for reusable components. Leicester: De Montfort University, 2002.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
5

Warren, Ian. The Renaissance of Legacy Systems: Method Support for Software-System Evolution. London: Springer London, 1999.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
6

The renaissance of legacy systems: Method support for software-system evolution. New York: Springer, 1999.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
7

Zhengru, Tang. Mining components from legacy systems through reverse engineering. Leicester: De Montfort University, 1999.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
8

Michael, Stonebraker, red. Migrating legacy systems: Gateways, interfaces & the incremental approach. San Francisco, Calif: Morgan Kaufmann Publishers, 1995.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
9

The scientific legacy of Poincaré. Providence, R.I: American Mathematical Society, 2010.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
10

Panopoulos, G. Re-engineering of legacy systems using reusable object capsules. Manchester: UMIST, 1995.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
Więcej źródeł

Części książek na temat "Legacy Systems"

1

Langer, Arthur M. "Transforming Legacy Systems". W Analysis and Design of Next-Generation Software Architectures, 201–38. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-36899-9_10.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
2

Langer, Arthur M. "Legacy Systems and Integration". W Guide to Software Development, 179–213. London: Springer London, 2016. http://dx.doi.org/10.1007/978-1-4471-6799-0_10.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
3

Langer, Arthur M. "Legacy Systems and Integration". W Guide to Software Development, 179–212. London: Springer London, 2011. http://dx.doi.org/10.1007/978-1-4471-2300-2_10.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
4

El-Ramly, Mohammad, Eleni Stroulia i Hani Samir. "Legacy Systems Interaction Reengineering". W Human-Centered Software Engineering, 316–33. London: Springer London, 2009. http://dx.doi.org/10.1007/978-1-84800-907-3_15.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
5

Sinko, Ann L. "Legacy Burdens". W Innovations and Elaborations in Internal Family Systems Therapy, 164–78. New York, NY : Routledge, 2016. Includes bibliographical: Routledge, 2016. http://dx.doi.org/10.4324/9781315775784-11.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
6

Edwards, Paul, Andrew Furse i Andrew Vickers. "Independently Assessing Legacy Safety Systems". W The Safety of Systems, 163–78. London: Springer London, 2007. http://dx.doi.org/10.1007/978-1-84628-806-7_11.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
7

Hainaut, Jean-Luc, Anthony Cleve, Jean Henrard i Jean-Marc Hick. "Migration of Legacy Information Systems". W Software Evolution, 105–38. Berlin, Heidelberg: Springer Berlin Heidelberg, 2008. http://dx.doi.org/10.1007/978-3-540-76440-3_6.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
8

Albuquerque, Adriano Bessa, i Vinicius Lima Cruz. "Implementing DevOps in Legacy Systems". W Intelligent Systems in Cybernetics and Automation Control Theory, 143–61. Cham: Springer International Publishing, 2018. http://dx.doi.org/10.1007/978-3-030-00184-1_14.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
9

Ramage, Magnus. "Global Perspectives on Legacy Systems". W Systems Engineering for Business Process Change: New Directions, 309–16. London: Springer London, 2002. http://dx.doi.org/10.1007/978-1-4471-0135-2_19.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
10

Sédillot, Simone, i Jian Liang. "Legacy Transactional Systems Integration Framework". W OOIS’97, 131–41. London: Springer London, 1998. http://dx.doi.org/10.1007/978-1-4471-1525-0_12.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.

Streszczenia konferencji na temat "Legacy Systems"

1

Mulcahy, James J., Shihong Huang i Andrew B. Veghte. "Leveraging service-oriented architecture to extend a legacy commerce system". W 2010 4th Annual IEEE Systems Conference. IEEE, 2010. http://dx.doi.org/10.1109/systems.2010.5482334.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
2

Dodsworth, K. "Interfacing to legacy systems". W IET Professional Development Course on Railway Signalling and Control Systems (RSCS 2008). IEE, 2008. http://dx.doi.org/10.1049/ic:20080383.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
3

Brubaker, Jed R., i Vanessa Callison-Burch. "Legacy Contact". W CHI'16: CHI Conference on Human Factors in Computing Systems. New York, NY, USA: ACM, 2016. http://dx.doi.org/10.1145/2858036.2858254.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
4

Ramos, Marcelo A., Paulo C. Masiero, Rosana T. V. Braga i Rosangela A. D. Penteado. "Reengineering legacy systems towards system of systems development". W 2012 IEEE 13th International Conference on Information Reuse & Integration (IRI). IEEE, 2012. http://dx.doi.org/10.1109/iri.2012.6303067.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
5

Chiang, Chia-Chu, i Coskun Bayrak. "Legacy Software Modernization". W 2006 IEEE International Conference on Systems, Man and Cybernetics. IEEE, 2006. http://dx.doi.org/10.1109/icsmc.2006.384895.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
6

Brubaker, Jed R., Lynn S. Dombrowski, Anita M. Gilbert, Nafiri Kusumakaulika i Gillian R. Hayes. "Stewarding a legacy". W CHI '14: CHI Conference on Human Factors in Computing Systems. New York, NY, USA: ACM, 2014. http://dx.doi.org/10.1145/2556288.2557059.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
7

Ruan, Wenjia, Trilok Vyas, Yujie Liu i Michael Spear. "Transactionalizing legacy code". W ASPLOS '14: Architectural Support for Programming Languages and Operating Systems. New York, NY, USA: ACM, 2014. http://dx.doi.org/10.1145/2541940.2541960.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
8

Jones, Larry. "Sustainment of Legacy Propulsion Systems". W AIAA International Air and Space Symposium and Exposition: The Next 100 Years. Reston, Virigina: American Institute of Aeronautics and Astronautics, 2003. http://dx.doi.org/10.2514/6.2003-2625.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
9

Bosch, Jan. "Achieving Speed in Legacy Systems". W 2011 15th International Software Product Line Conference (SPLC). IEEE, 2011. http://dx.doi.org/10.1109/splc.2011.59.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
10

Jang, Yeona. "Legacy systems and object technology". W Addendum to the proceedings of the 10th annual conference. New York, New York, USA: ACM Press, 1995. http://dx.doi.org/10.1145/260094.260275.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.

Raporty organizacyjne na temat "Legacy Systems"

1

Comella-Dorda, Santiago, Grace A. Lewis, Pat Place, Dan Plakosh i Robert C. Seacord. Incremental Modernization of Legacy Systems. Fort Belvoir, VA: Defense Technical Information Center, lipiec 2001. http://dx.doi.org/10.21236/ada443480.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
2

Kaiser, Gail, Phil Gross, Gaurav Kc, Janak Parekh i Giuseppe Valetto. An Approach to Autonomizing Legacy Systems. Fort Belvoir, VA: Defense Technical Information Center, styczeń 2005. http://dx.doi.org/10.21236/ada437473.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
3

Parekh, Janak, Gail Kaiser, Philip Gross i Giuseppe Valetto. Retrofitting Autonomic Capabilities Onto Legacy Systems. Fort Belvoir, VA: Defense Technical Information Center, styczeń 2005. http://dx.doi.org/10.21236/ada437499.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
4

McNerney, Catherine A. Transforming the Army's Legacy Personnel Systems. Fort Belvoir, VA: Defense Technical Information Center, kwiecień 2003. http://dx.doi.org/10.21236/ada414511.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
5

Winter, Don, David Corman, Pat Goertzen, Tom Herm i John Shackleton. Incremental Upgrade of Legacy Systems (IULS). Fort Belvoir, VA: Defense Technical Information Center, kwiecień 2001. http://dx.doi.org/10.21236/ada406346.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
6

Corman, David E., Thomas Herm, Kirby Keller i Charles Satterthwaite. Transforming Legacy Systems to Obtain Information Superiority. Fort Belvoir, VA: Defense Technical Information Center, styczeń 2001. http://dx.doi.org/10.21236/ada457962.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
7

Bergey, John K., Linda M. Northrop i Dennis B. Smith. Enterprise Framework for the Disciplined Evolution of Legacy Systems. Fort Belvoir, VA: Defense Technical Information Center, październik 1997. http://dx.doi.org/10.21236/ada330880.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
8

Greze, Jean-Denis, Gail E. Kaiser i Gaurav S. Ke. Survivor: An Approach for Adding Dependability to Legacy Workflow Systems. Fort Belvoir, VA: Defense Technical Information Center, styczeń 2005. http://dx.doi.org/10.21236/ada437389.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
9

MacKenzie, Ronald R. Integrating Newer Technology Software Systems into the SLAC Legacy Control System - Two Case Histories and New CMLOG Developments. Office of Scientific and Technical Information (OSTI), grudzień 2001. http://dx.doi.org/10.2172/798940.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
10

Atluri, Venkata. A PASSIVE NETWORK CYBER THREAT INTELLIGENCE FRAMEWORK FOR LEGACY CRITICAL CONTROL SYSTEMS USING MACHINE LEARNING - REPORT. Office of Scientific and Technical Information (OSTI), sierpień 2019. http://dx.doi.org/10.2172/1547280.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
Możesz być także zainteresowany rozszerzonymi bibliografiami na temat „Legacy Systems” dla poszczególnych typów źródeł:
Artykuły w czasopismach Rozprawy doktorskie Książki
Oferujemy zniżki na wszystkie plany premium dla autorów, których prace zostały uwzględnione w tematycznych zestawieniach literatury. Skontaktuj się z nami, aby uzyskać unikalny kod promocyjny!

Do bibliografii