|
|
|
|
LEADER |
00000cam a2200000 a 4500 |
001 |
OR_on1242408156 |
003 |
OCoLC |
005 |
20231017213018.0 |
006 |
m o d |
007 |
cr |n||||||||| |
008 |
210319s2021 xxu ob 001 0 eng d |
040 |
|
|
|a YDX
|b eng
|e pn
|c YDX
|d EBLCP
|d DCT
|d GW5XE
|d OCLCO
|d OCLCF
|d VT2
|d LIP
|d UKAHL
|d K6U
|d OCLCO
|d OCLCQ
|
019 |
|
|
|a 1243545917
|a 1244118377
|a 1253413623
|
020 |
|
|
|a 9781484267110
|q (electronic bk.)
|
020 |
|
|
|a 1484267117
|q (electronic bk.)
|
020 |
|
|
|a 9781484267127
|q (print)
|
020 |
|
|
|a 1484267125
|
020 |
|
|
|z 1484267109
|
020 |
|
|
|z 9781484267103
|
024 |
7 |
|
|a 10.1007/978-1-4842-6711-0
|2 doi
|
029 |
1 |
|
|a AU@
|b 000068961999
|
029 |
1 |
|
|a AU@
|b 000069136953
|
035 |
|
|
|a (OCoLC)1242408156
|z (OCoLC)1243545917
|z (OCoLC)1244118377
|z (OCoLC)1253413623
|
037 |
|
|
|b Springer
|
050 |
|
4 |
|a QA76.73.A12
|
072 |
|
7 |
|a COM000000
|2 bisacsh
|
072 |
|
7 |
|a U
|2 bicssc
|
072 |
|
7 |
|a UX
|2 thema
|
082 |
0 |
4 |
|a 005.13/3
|2 23
|
082 |
0 |
4 |
|a 004
|2 23
|
049 |
|
|
|a UAMI
|
100 |
1 |
|
|a Hardy, Paul David.
|
245 |
1 |
0 |
|a Improving the quality of ABAP code :
|b striving for perfection /
|c Paul David Hardy.
|
260 |
|
|
|a [Place of publication not identified] :
|b Apress,
|c 2021.
|
300 |
|
|
|a 1 online resource
|
336 |
|
|
|a text
|b txt
|2 rdacontent
|
337 |
|
|
|a computer
|b c
|2 rdamedia
|
338 |
|
|
|a online resource
|b cr
|2 rdacarrier
|
347 |
|
|
|a text file
|
347 |
|
|
|b PDF
|
505 |
0 |
|
|a Intro -- Table of Contents -- About the Author -- About the Technical Reviewer -- Acknowledgments -- Introduction -- Chapter 1: Why Object-Oriented Programming Is a Must for Code Quality -- Why OO Has Never Taken Off in ABAP World -- OO Benefits: The Theory -- Describing OO Programs: UML -- Describing OO Programs: BON -- Seamlessness/Reversibility -- Seamlessness via an Automated Tool -- Seamlessness via Naming Conventions -- Design by Contract -- Design by Unit Tests -- Designing a Worldwide OO Program -- What Is the Existing System State? -- Why Is the Existing System State Not Portable?
|
505 |
8 |
|
|a What Can Be Done About Fixing That Problem? -- Breaking Dependencies in General -- Breaking Dependencies via Packages -- Breaking Dependencies via Interfaces -- What Is an Interface in OO Terms? -- How SAP Uses Interfaces to Manage User Exits -- Not Breaking the System -- My Journey to OO Happiness -- OO Happiness: The Theory -- The Clean Coder -- Clean Code -- Head-First Design Patterns -- More on Design Patterns -- OO Happiness: The Reality -- Writing an Interactive Executable Report in OO -- Writing a DYNPRO Program in OO -- Experiment -- Rewriting a Huge, Business-Critical Program in OO
|
505 |
8 |
|
|a Slowly Transforming a Huge, Business-Critical Program to OO -- OO Benefits: The Reality -- Soft Benefits -- Design Thinking -- Ease of Maintenance -- No One Goes Back -- Hard Benefits -- Avoidance of Syntax Errors -- Parameter Handling -- IMPORTING -- EXPORTING -- TABLES -- RETURNING -- OPTIONAL -- NAMES -- TYPES -- FORMULAS -- Reuse -- Making Code Testable -- Conclusion -- Recommended Reading -- Articles -- Books -- Chapter 2: Why Test-Driven Development Is a Must for Code Quality -- TDD Theory -- Fragile Code -- Legacy Code -- Automated Regression Tests -- Dependencies and How to Break Them
|
505 |
8 |
|
|a The TDD Development Cycle: RED/GREEN/BLUE -- My Journey to TDD Happiness -- Testing After the Event -- Testing Before the Event -- TDD Workflow in Eclipse -- Creating Test Doubles -- Creating a New Test Method -- Coding the Test Method -- Coding the THEN Method -- Coding the GIVEN Method -- Coding the WHEN Method -- Writing the Production Code -- The BLUE Phase -- Does This Actually Give You a Benefit? -- From a Gut Feeling ... -- ... to a Concrete Example -- Some Unit Tests Might Seem Pointless ... -- It's Too Short to Test -- It's Too Simple to Test -- ... but They Are Not!
|
505 |
8 |
|
|a Message in a Model -- You Can't Get There from Here -- Simpler but Wrong -- Why TDD Has Never Taken Off -- I Already Have an Automated Testing Framework -- My Program Is Too Complicated for TDD -- My Program Is Too Simple for TDD -- TDD Is Far Too Expensive -- TDD Reduces Development Costs -- TDD Reduces the Cost of Fixing Bugs -- TDD Reduces the Financial Risk of Failure -- Conclusion -- Recommended Reading -- Chapter 3: Clarity: The First Pillar of Code Quality -- Refactoring: Automated and Manual Checks -- Automated Checks -- Syntax Check -- Extended Program Check -- Code Inspector
|
520 |
|
|
|a Gain an in-depth understanding of the large number of common problems found in ABAP programs and have a robust methodology for fixing problems when you find them. This book also shows you how to prevent them from occurring in new programs. A large chunk of the world's biggest organizations use SAP software and virtually all of them have very large amounts of custom code. However, a lot of that custom code is not as good as it could be. In this book we look at why object-oriented programming is the basic building block for improved program quality and at the test-driven development that this enables. We cover the three pillars of clarity, stability, and high performance on which a high-quality ABAP program stands. You will then move on to the user interface, which needs its own set of standards for high quality. In the final chapters, you will learn about specialist topics such as user exits, making sure code will run on the latest releases of SAP, and how to add your own automated custom code quality checks. You will: Know why object-oriented programming and test-driven development are the cornerstones of high-quality custom code Ensure that the three pillars of clarity, stability, and high performance are fulfilled Make sure your applications are user friendly Ensure that your custom code works on newer SAP releases Create your own custom code quality checks.
|
504 |
|
|
|a Includes bibliographical references and index.
|
590 |
|
|
|a O'Reilly
|b O'Reilly Online Learning: Academic/Public Library Edition
|
650 |
|
0 |
|a ABAP/4 (Computer program language)
|
650 |
|
0 |
|a Computer software.
|
650 |
|
2 |
|a Software
|
650 |
|
6 |
|a ABAP/4 (Langage de programmation)
|
650 |
|
6 |
|a Logiciels.
|
650 |
|
7 |
|a software.
|2 aat
|
650 |
|
7 |
|a ABAP/4 (Computer program language)
|2 fast
|0 (OCoLC)fst00793777
|
650 |
|
7 |
|a Computer software.
|2 fast
|0 (OCoLC)fst00872527
|
776 |
0 |
8 |
|i Print version:
|a Hardy, Paul David.
|t Improving the quality of ABAP code.
|d [Place of publication not identified] : Apress, 2021
|z 1484267109
|z 9781484267103
|w (OCoLC)1206224214
|
856 |
4 |
0 |
|u https://learning.oreilly.com/library/view/~/9781484267110/?ar
|z Texto completo (Requiere registro previo con correo institucional)
|
938 |
|
|
|a Askews and Holts Library Services
|b ASKH
|n AH38627741
|
938 |
|
|
|a ProQuest Ebook Central
|b EBLB
|n EBL6521539
|
938 |
|
|
|a YBP Library Services
|b YANK
|n 301998053
|
994 |
|
|
|a 92
|b IZTAP
|