LEADER 05279nam 2200673 450 001 9910813257703321 005 20200520144314.0 010 $a1-119-07314-6 010 $a1-119-07308-1 035 $a(CKB)3710000000331931 035 $a(EBL)1895354 035 $a(SSID)ssj0001433109 035 $a(PQKBManifestationID)11844480 035 $a(PQKBTitleCode)TC0001433109 035 $a(PQKBWorkID)11413538 035 $a(PQKB)10480817 035 $a(MiAaPQ)EBC1895354 035 $a(Au-PeEL)EBL1895354 035 $a(CaPaEBR)ebr11004215 035 $a(CaONFJC)MIL690591 035 $a(OCoLC)899739128 035 $a(PPN)191911992 035 $a(EXLCZ)993710000000331931 100 $a20150123h20152015 uy 0 101 0 $aeng 135 $aur|n|---||||| 181 $ctxt 182 $cc 183 $acr 200 10$aCOBOL software modernization $efrom principles to iplementation with the BLU AGE ® method /$fFranck Barbier, Jean-Luc Recoussine 210 1$aLondon, England ; :$cHoboken, New Jersey :$cISTE :$cWiley,$d2015. 210 4$d©2015 215 $a1 online resource (282 p.) 225 1 $aComputer Engineering Series 300 $aDescription based upon print version of record. 311 $a1-84821-760-9 320 $aIncludes bibliographical references and index. 327 $aCover; Title Page; Copyright; Contents; Acknowledgments; Acronyms; Introduction; I.1. Behind software modernization is "modernization": the car metaphor; I.2. COBOL; I.3. Why the Cloud?; I.4. Legacy2Cloud; I.5. Human weight on successful modernization; I.6. This book's structure; 1: Software Modernization: a Business Vision; 1.1. Software-based business; 1.2. Information-driven business; 1.2.1. Adaptation to business; 1.3. The case of tourism industry; 1.4. IT progress acceleration; 1.5. Legacy world; 1.5.1. Exiting the legacy world; 1.5.2. Legacy world professionals; 1.6. Conclusions 327 $a2: Software Modernization: Technical Environment2.1. Legacy system; 2.2. Modernization; 2.2.1. Replacement; 2.2.2. Migration; 2.2.3. Modernization versus migration; 2.2.4. The superiority of white-box modernization; 2.3. Software engineering principles underpinning modernization; 2.3.1. Re-engineering in action; 2.3.2. Re-engineering challenges; 2.4. Conclusions; 3: Status of COBOL Legacy Applications; 3.1. OLTP versus batch programs; 3.2. Mainframes; 3.3. Data-driven design; 3.4. COBOL degeneration principle; 3.5. COBOL pitfalls; 3.6. Middleware for COBOL 327 $a3.7. Moving COBOL OLTP/batch programs to Java3.8. COBOL is not a friend of Java, and vice versa; 3.9. Spaghetti code; 3.9.1. Spaghetti code sample; 3.9.2. Code comprehension; 3.10. No longer COBOL?; 3.11. Conclusions; 4: Service-Oriented Architecture (SOA); 4.1. Software architecture versus information system urbanization; 4.2. Software architecture evolution; 4.3. COBOL own style of software architecture; 4.4. The one-way road to SOA; 4.5. Characterization of SOA; 4.5.1. Preliminary note; 4.5.2. From objects to components and services; 4.5.3. Type versus instance 327 $a4.5.4. Distribution concerns4.5.5. Functional grouping; 4.5.6. Granularity; 4.5.7. Technology-centrism; 4.5.8. Composition at design time (... is definitely modeling); 4.5.9. Composition at runtime; 4.6. Conclusions; 5: SOA in Action; 5.1. Service as materialized component; 5.2. Service as Internet resource; 5.2.1. Pay-per-use service; 5.2.2. Free service; 5.2.3. Data feed service; 5.3. High-end SOA; 5.4. SOA challenges; 5.5. The Cloud; 5.5.1. COBOL in the Cloud; 5.5.2. Computing is just resource consumption; 5.5.3. Cloud computing is also resource consumption, but... 327 $a5.5.4. Everything as a service5.5.5. SOA in the Cloud; 5.5.6. The cloud counterparts; 5.6. Conclusions; 6: Model-Driven Development (MDD); 6.1. Why MDD?; 6.2. Models, intuitively; 6.3. Models, formally; 6.4. Models as computerized objects; 6.5. Model-based productivity; 6.6. Openness through standards; 6.6.1. Model-Driven Architecture (MDA); 6.7. Models and people; 6.8. Metamodeling; 6.8.1. Metamodeling, put simply; 6.9. Model transformation; 6.10. Model transformation by example; 6.11. From contemplative to executable models; 6.12. Model execution in action 327 $a6.13. Toward Domain-Specific Modeling Languages (DSMLs) 330 $a Nowadays, billions of lines of code are in the COBOL programming language. This book is an analysis, a diagnosis, a strategy, a MDD method and a tool to transform legacy COBOL into modernized applications that comply with Internet computing, Service-Oriented Architecture (SOA) and the Cloud. It serves as a blueprint for those in charge of finding solutions to this considerable challenge. 410 0$aComputer engineering series (London, England) 606 $aCOBOL (Computer program language) 606 $aSoftware architecture 615 0$aCOBOL (Computer program language) 615 0$aSoftware architecture. 676 $a005.133 700 $aBarbier$b Franck$01601249 702 $aRecoussine$b Jean-Luc 801 0$bMiAaPQ 801 1$bMiAaPQ 801 2$bMiAaPQ 906 $aBOOK 912 $a9910813257703321 996 $aCOBOL software modernization$93924782 997 $aUNINA