Sas Data Analytic Development - Dimensions of Software Quality

Informationen zum Autor TROY MARTIN HUGHES has been a SAS practitioner for more than 15 years, has managed SAS projects in support of federal, state, and local government initiatives, and is a SAS Certified Advanced Programmer, SAS Certified Base Programmer, SAS Certified Clinical Trials Programmer, and SAS Professional V8. He has an MBA in information systems management and additional credentials, including: PMP, PMI-ACP, PMI-PBA, PMI-RMP, CISSP, CSSLP, CSM, CSD, CSPO, CSP, and ITIL v3 Foundation. He has been a frequent presenter and invited speaker at SAS user conferences, including SAS Global Forum, WUSS, MWSUG, SCSUG, SESUG, and PharmaSUG. Troy is a U.S. Navy veteran with two tours of duty in Afghanistan, and in his spare time, a volunteer firefighter and EMT. Klappentext Design quality SAS software and evaluate SAS software qualitySAS Data Analytic Development is the developer's compendium for writing better-performing software and the manager's guide to building comprehensive software performance requirements. The text introduces and parallels the International Organization for Standardization (ISO) software product quality model, demonstrating 15 performance requirements that represent dimensions of software quality, including: reliability, recoverability, robustness, execution efficiency (i.e., speed), efficiency, scalability, portability, security, automation, maintainability, modularity, readability, testability, stability, and reusability. The text is intended to be read cover-to-cover or used as a reference tool to instruct, inspire, deliver, and evaluate software quality.A common fault in many software development environments is a focus on functional requirements--the what and how--to the detriment of performance requirements, which specify instead how well software should function (assessed through software execution) or how easily software should be maintained (assessed through code inspection). Without the definition and communication of performance requirements, developers risk either building software that lacks intended quality or wasting time delivering software that exceeds performance objectives--thus, either underperforming or gold-plating, both of which are undesirable. Managers, customers, and other decision makers should also understand the dimensions of software quality both to define performance requirements at project outset as well as to evaluate whether those objectives were met at software completion.As data analytic software, SAS transforms data into information and ultimately knowledge and data-driven decisions. Not surprisingly, data quality is a central focus and theme of SAS literature; however, code quality is far less commonly described and too often references only the speed or efficiency with which software should execute, omitting other critical dimensions of software quality. SAS(r) software project definitions and technical requirements often fall victim to this paradox, in which rigorous quality requirements exist for data and data products yet not for the software that undergirds them. By demonstrating the cost and benefits of software quality inclusion and the risk of software quality exclusion, stakeholders learn to value, prioritize, implement, and evaluate dimensions of software quality within risk management and project management frameworks of the software development life cycle (SDLC). Thus, SAS Data Analytic Development recalibrates business value, placing code quality on par with data quality, and performance requirements on par with functional requirements. Zusammenfassung Design quality SAS software and evaluate SAS software qualitySAS Data Analytic Development is the developer's compendium for writing better-performing software and the manager's guide to building comprehensive software performance requirements. The text introduces and parallels the International Organization for Standardization (ISO) software product quality model...

List of contents

Preface xiAcknowledgments xviAbout the Author xviiChapter 1 Introduction 1Distinguishing Data Analytic Development 3Software Development Life Cycle (SDLC) 7Risk 14Chapter 2 Quality 21Defining Quality 24Software Product Quality Model 30Quality in the SDLC 40Chapter 3 Communication 49Return Codes 51System Numeric Return Codes 53System Alphanumeric Return Codes 70User-Generated Return Codes 74Parallel Processing Communication 79PART I DYNAMIC PERFORMANCE 85Chapter 4 Reliability 87Defining Reliability 90Paths to Failure 91ACL: The Reliability Triad 102Reliability in the SDLC 108Chapter 5 Recoverability 123Defining Recoverability 125Recoverability toward Reliability 127Recoverability Matrix 131TEACH Recoverability Principles 132SPICIER Recoverability Steps 136Recovering with Checkpoints 148Recoverability in the SDLC 151Chapter 6 Robustness 159Defining Robustness 162Robustness toward Reliability 163Defensive Programming 164Exception Handling 172Robustness in the SDLC 203Chapter 7 Execution Efficiency 207Defining Execution Efficiency 209Factors Affecting Execution Efficiency 210False Dependencies 211Parallel Processing 220Execution Efficiency in the SDLC 232Chapter 8 Efficiency 243Defining Efficiency 246Disambiguating Efficiency 246Defining Resources 249Efficiency in the SDLC 259Chapter 9 Scalability 273Defining Scalability 276The Scalability Triad 276Resource Scalability 278Demand Scalability 279Load Scalability 290Scalability in the SDLC 309Chapter 10 Portability 313Defining Portability 316Disambiguating Portability 3173GL versus 4GL Portability 318Facets of Portability 319Portability in the SDLC 338Chapter 11 Security 341Defining Security 344Confidentiality 344Integrity 345Availability 365Security in the SDLC 379Chapter 12 Automation 383Defining Automation 386Automation in SAS Software 387SAS Processing Modes 388Starting in Interactive Mode 393Starting in Batch Mode 410Automation in the SDLC 415PART II STATIC PERFORMANCE 419Chapter 13 Maintainability 421Defining Maintainability 424Maintenance 425Maintenance in the SDLC 429Failure to Maintain 436Maintainability 440Chapter 14 Modularity 447Defining Modularity 449From Monolithic to Modular 450Modularity Principles 454Benefits of Modularity 474Chapter 15 Readability 477Defining Readability 479Plan to Get Hit by a Bus 480Software Readability 481External Readability 503Chapter 16 Testability 507Defining Testability 510Software Testing 510Testability 538Chapter 17 Stability 541Defining Stability 543Achieving Stability 544Stable Requirements 545Defect-Free Code 546Dynamic Flexibility 546Stability and Beyond 549Modularizing More Than Macros 559Chapter 18 Reusability 577Defining Reusability 579Reuse 580Reusability 588From Reusability to Extensibility 597Index 603

Product details

• Authors: Troy Martin Hughes
• Publisher: Wiley, John and Sons Ltd
• Languages: English
• Product format: Hardback
• Released: 21.10.2016
• EAN: 9781119240761
• ISBN: 978-1-119-24076-1
• No. of pages: 624
• Series: SAS Institute Inc; SAS Institute Inc; Wiley and SAS Business Series; Wiley and SAS Business
• Subjects: Natural sciences, medicine, IT, technology > IT, data processing > Programming languages; Social sciences, law, business > Business > General, dictionaries; Statistik, Datenanalyse, Statistics, SAS, Statistical Software / SAS, Statistiksoftware / SAS