SAS data analytic development: dimensions of software quality
Design quality SAS software and evaluate SAS software quality SAS 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 Intern...
Gespeichert in:
| 1. Verfasser: | |
|---|---|
| Format: | Elektronisch E-Book |
| Sprache: | English |
| Veröffentlicht: |
Hoboken, New Jersey
John Wiley & Sons
2016
|
| Schriftenreihe: | Wiley and SAS business series
|
| Schlagworte: | |
| Online-Zugang: | FRO01 UBG01 URL des Erstveröffentlichers |
| Zusammenfassung: | Design quality SAS software and evaluate SAS software quality SAS 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. |
| Beschreibung: | Includes index Cover; Title Page; Copyright; Contents; Preface; Objectives; Audience; Application of Content; Organization; Acknowledgments; About the Author; Chapter 1 Introduction; Distinguishing Data Analytic Development; Software Development Life Cycle (SDLC); Risk; What's Next?; Notes; Chapter 2 Quality; Defining Quality; Software Product Quality Model; Quality in the SDLC; What's Next?; Notes; Chapter 3 Communication; Return Codes; System Numeric Return Codes; System Alphanumeric Return Codes; User-Generated Return Codes; Parallel Processing Communication; What's Next?; Notes Part I Static PerformanceChapter 4 Reliability; Defining Reliability; Paths to Failure; ACL: The Reliability Triad; Reliability in the SDLC; What's Next?; Notes; Chapter 5 Recoverability; Defining Recoverability; Recoverability toward Reliability; Recoverability Matrix; TEACH Recoverability Principles; SPICIER Recoverability Steps; Recovering with Checkpoints; Recoverability in the SDLC; What's Next?; Notes; Chapter 6 Robustness; Defining Robustness; Robustness toward Reliability; Defensive Programming; Exception Handling; Robustness in the SDLC; What's Next?; Notes Chapter 7 Execution EfficiencyDefining Execution Efficiency; Factors Affecting Execution Efficiency; False Dependencies; Parallel Processing; Execution Efficiency in the SDLC; What's Next?; Notes; Chapter 8 Efficiency; Defining Efficiency; Disambiguating Efficiency; Defining Resources; Efficiency in the SDLC; What's Next?; Notes; Chapter 9 Scalability; Defining Scalability; The Scalability Triad; Resource Scalability; Demand Scalability; Load Scalability; Scalability in the SDLC; What's Next?; Notes; Chapter 10 Portability; Defining Portability; Disambiguating Portability 3GL versus 4GL PortabilityFacets of Portability; Portability in the SDLC; What's Next?; Notes; Chapter 11 Security; Defining Security; Confidentiality; Integrity; Availability; Security in the SDLC; What's Next?; Notes; Chapter 12 Automation; Defining Automation; Automation in SAS Software; SAS Processing Modes; Starting in Interactive Mode; Starting in Batch Mode; Automation in the SDLC; What's Next?; Notes; Part II Dynamic Performance; Chapter 13 Maintainability; Defining Maintainability; Maintenance; Maintenance in the SDLC; Failure to Maintain; Maintainability; What's Next?; Notes Chapter 14 ModularityDefining Modularity; From Monolithic to Modular; Modularity Principles; Benefits of Modularity; What's Next?; Notes; Chapter 15 Readability; Defining Readability; Plan to Get Hit by a Bus; Software Readability; External Readability; What's Next?; Notes; Chapter 16 Testability; Defining Testability; Software Testing; Testability; What's Next?; Notes; Chapter 17 Stability; Defining Stability; Achieving Stability; Stable Requirements; Defect-Free Code; Dynamic Flexibility; Stability and Beyond; Modularizing More Than Macros; What's Next?; Notes; Chapter 18 Reusability. - Includes bibliographical references and index |
| Beschreibung: | 1 online resource |
| ISBN: | 1119255686 1119255708 9781119255680 9781119255703 |
Internformat
MARC
| LEADER | 00000nmm a2200000zc 4500 | ||
|---|---|---|---|
| 001 | BV043854560 | ||
| 003 | DE-604 | ||
| 005 | 00000000000000.0 | ||
| 007 | cr|uuu---uuuuu | ||
| 008 | 161102s2016 |||| o||u| ||||||eng d | ||
| 020 | |a 1119255686 |9 1-119-25568-6 | ||
| 020 | |a 1119255708 |9 1-119-25570-8 | ||
| 020 | |a 9781119255680 |c Online |9 978-1-119-25568-0 | ||
| 020 | |a 9781119255703 |9 978-1-119-25570-3 | ||
| 035 | |a (ZDB-35-WIC)ocn957521276 | ||
| 035 | |a (OCoLC)965503319 | ||
| 035 | |a (DE-599)BVBBV043854560 | ||
| 040 | |a DE-604 |b ger |e rda | ||
| 041 | 0 | |a eng | |
| 049 | |a DE-861 | ||
| 082 | 0 | |a 005.5/5 | |
| 100 | 1 | |a Hughes, Troy Martin |d 1976- |4 aut | |
| 245 | 1 | 0 | |a SAS data analytic development |b dimensions of software quality |c Troy Martin Hughes |
| 264 | 1 | |a Hoboken, New Jersey |b John Wiley & Sons |c 2016 | |
| 300 | |a 1 online resource | ||
| 336 | |b txt |2 rdacontent | ||
| 337 | |b c |2 rdamedia | ||
| 338 | |b cr |2 rdacarrier | ||
| 490 | 0 | |a Wiley and SAS business series | |
| 500 | |a Includes index | ||
| 500 | |a Cover; Title Page; Copyright; Contents; Preface; Objectives; Audience; Application of Content; Organization; Acknowledgments; About the Author; Chapter 1 Introduction; Distinguishing Data Analytic Development; Software Development Life Cycle (SDLC); Risk; What's Next?; Notes; Chapter 2 Quality; Defining Quality; Software Product Quality Model; Quality in the SDLC; What's Next?; Notes; Chapter 3 Communication; Return Codes; System Numeric Return Codes; System Alphanumeric Return Codes; User-Generated Return Codes; Parallel Processing Communication; What's Next?; Notes | ||
| 500 | |a Part I Static PerformanceChapter 4 Reliability; Defining Reliability; Paths to Failure; ACL: The Reliability Triad; Reliability in the SDLC; What's Next?; Notes; Chapter 5 Recoverability; Defining Recoverability; Recoverability toward Reliability; Recoverability Matrix; TEACH Recoverability Principles; SPICIER Recoverability Steps; Recovering with Checkpoints; Recoverability in the SDLC; What's Next?; Notes; Chapter 6 Robustness; Defining Robustness; Robustness toward Reliability; Defensive Programming; Exception Handling; Robustness in the SDLC; What's Next?; Notes | ||
| 500 | |a Chapter 7 Execution EfficiencyDefining Execution Efficiency; Factors Affecting Execution Efficiency; False Dependencies; Parallel Processing; Execution Efficiency in the SDLC; What's Next?; Notes; Chapter 8 Efficiency; Defining Efficiency; Disambiguating Efficiency; Defining Resources; Efficiency in the SDLC; What's Next?; Notes; Chapter 9 Scalability; Defining Scalability; The Scalability Triad; Resource Scalability; Demand Scalability; Load Scalability; Scalability in the SDLC; What's Next?; Notes; Chapter 10 Portability; Defining Portability; Disambiguating Portability | ||
| 500 | |a 3GL versus 4GL PortabilityFacets of Portability; Portability in the SDLC; What's Next?; Notes; Chapter 11 Security; Defining Security; Confidentiality; Integrity; Availability; Security in the SDLC; What's Next?; Notes; Chapter 12 Automation; Defining Automation; Automation in SAS Software; SAS Processing Modes; Starting in Interactive Mode; Starting in Batch Mode; Automation in the SDLC; What's Next?; Notes; Part II Dynamic Performance; Chapter 13 Maintainability; Defining Maintainability; Maintenance; Maintenance in the SDLC; Failure to Maintain; Maintainability; What's Next?; Notes | ||
| 500 | |a Chapter 14 ModularityDefining Modularity; From Monolithic to Modular; Modularity Principles; Benefits of Modularity; What's Next?; Notes; Chapter 15 Readability; Defining Readability; Plan to Get Hit by a Bus; Software Readability; External Readability; What's Next?; Notes; Chapter 16 Testability; Defining Testability; Software Testing; Testability; What's Next?; Notes; Chapter 17 Stability; Defining Stability; Achieving Stability; Stable Requirements; Defect-Free Code; Dynamic Flexibility; Stability and Beyond; Modularizing More Than Macros; What's Next?; Notes; Chapter 18 Reusability. - Includes bibliographical references and index | ||
| 520 | |a Design quality SAS software and evaluate SAS software quality SAS 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. | ||
| 630 | 0 | 4 | |a SAS (Computer file) |
| 650 | 7 | |a COMPUTERS / Programming / General |2 bisacsh | |
| 650 | 4 | |a Datenverarbeitung | |
| 650 | 4 | |a Quantitative research / Data processing | |
| 776 | 0 | 8 | |i Erscheint auch als |n Druckausgabe |z 978-1-119-24076-1 |
| 856 | 4 | 0 | |u https://onlinelibrary.wiley.com/doi/book/10.1002/9781119255680 |x Verlag |z URL des Erstveröffentlichers |3 Volltext |
| 912 | |a ZDB-35-WIC | ||
| 940 | 1 | |q UBG_PDA_WIC | |
| 999 | |a oai:aleph.bib-bvb.de:BVB01-029264793 | ||
| 966 | e | |u https://onlinelibrary.wiley.com/doi/book/10.1002/9781119255680 |l FRO01 |p ZDB-35-WIC |q FRO_PDA_WIC |x Verlag |3 Volltext | |
| 966 | e | |u https://onlinelibrary.wiley.com/doi/book/10.1002/9781119255680 |l UBG01 |p ZDB-35-WIC |q UBG_PDA_WIC |x Verlag |3 Volltext | |
Datensatz im Suchindex
| _version_ | 1804176730020118528 |
|---|---|
| any_adam_object | |
| author | Hughes, Troy Martin 1976- |
| author_facet | Hughes, Troy Martin 1976- |
| author_role | aut |
| author_sort | Hughes, Troy Martin 1976- |
| author_variant | t m h tm tmh |
| building | Verbundindex |
| bvnumber | BV043854560 |
| collection | ZDB-35-WIC |
| ctrlnum | (ZDB-35-WIC)ocn957521276 (OCoLC)965503319 (DE-599)BVBBV043854560 |
| dewey-full | 005.5/5 |
| dewey-hundreds | 000 - Computer science, information, general works |
| dewey-ones | 005 - Computer programming, programs, data, security |
| dewey-raw | 005.5/5 |
| dewey-search | 005.5/5 |
| dewey-sort | 15.5 15 |
| dewey-tens | 000 - Computer science, information, general works |
| discipline | Informatik |
| format | Electronic eBook |
| fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>06599nmm a2200529zc 4500</leader><controlfield tag="001">BV043854560</controlfield><controlfield tag="003">DE-604</controlfield><controlfield tag="005">00000000000000.0</controlfield><controlfield tag="007">cr|uuu---uuuuu</controlfield><controlfield tag="008">161102s2016 |||| o||u| ||||||eng d</controlfield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">1119255686</subfield><subfield code="9">1-119-25568-6</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">1119255708</subfield><subfield code="9">1-119-25570-8</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9781119255680</subfield><subfield code="c">Online</subfield><subfield code="9">978-1-119-25568-0</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9781119255703</subfield><subfield code="9">978-1-119-25570-3</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(ZDB-35-WIC)ocn957521276</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(OCoLC)965503319</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)BVBBV043854560</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-604</subfield><subfield code="b">ger</subfield><subfield code="e">rda</subfield></datafield><datafield tag="041" ind1="0" ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">DE-861</subfield></datafield><datafield tag="082" ind1="0" ind2=" "><subfield code="a">005.5/5</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Hughes, Troy Martin</subfield><subfield code="d">1976-</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">SAS data analytic development</subfield><subfield code="b">dimensions of software quality</subfield><subfield code="c">Troy Martin Hughes</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">Hoboken, New Jersey</subfield><subfield code="b">John Wiley & Sons</subfield><subfield code="c">2016</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">1 online resource</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="b">c</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="b">cr</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="490" ind1="0" ind2=" "><subfield code="a">Wiley and SAS business series</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">Includes index</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">Cover; Title Page; Copyright; Contents; Preface; Objectives; Audience; Application of Content; Organization; Acknowledgments; About the Author; Chapter 1 Introduction; Distinguishing Data Analytic Development; Software Development Life Cycle (SDLC); Risk; What's Next?; Notes; Chapter 2 Quality; Defining Quality; Software Product Quality Model; Quality in the SDLC; What's Next?; Notes; Chapter 3 Communication; Return Codes; System Numeric Return Codes; System Alphanumeric Return Codes; User-Generated Return Codes; Parallel Processing Communication; What's Next?; Notes</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">Part I Static PerformanceChapter 4 Reliability; Defining Reliability; Paths to Failure; ACL: The Reliability Triad; Reliability in the SDLC; What's Next?; Notes; Chapter 5 Recoverability; Defining Recoverability; Recoverability toward Reliability; Recoverability Matrix; TEACH Recoverability Principles; SPICIER Recoverability Steps; Recovering with Checkpoints; Recoverability in the SDLC; What's Next?; Notes; Chapter 6 Robustness; Defining Robustness; Robustness toward Reliability; Defensive Programming; Exception Handling; Robustness in the SDLC; What's Next?; Notes</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">Chapter 7 Execution EfficiencyDefining Execution Efficiency; Factors Affecting Execution Efficiency; False Dependencies; Parallel Processing; Execution Efficiency in the SDLC; What's Next?; Notes; Chapter 8 Efficiency; Defining Efficiency; Disambiguating Efficiency; Defining Resources; Efficiency in the SDLC; What's Next?; Notes; Chapter 9 Scalability; Defining Scalability; The Scalability Triad; Resource Scalability; Demand Scalability; Load Scalability; Scalability in the SDLC; What's Next?; Notes; Chapter 10 Portability; Defining Portability; Disambiguating Portability</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">3GL versus 4GL PortabilityFacets of Portability; Portability in the SDLC; What's Next?; Notes; Chapter 11 Security; Defining Security; Confidentiality; Integrity; Availability; Security in the SDLC; What's Next?; Notes; Chapter 12 Automation; Defining Automation; Automation in SAS Software; SAS Processing Modes; Starting in Interactive Mode; Starting in Batch Mode; Automation in the SDLC; What's Next?; Notes; Part II Dynamic Performance; Chapter 13 Maintainability; Defining Maintainability; Maintenance; Maintenance in the SDLC; Failure to Maintain; Maintainability; What's Next?; Notes</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">Chapter 14 ModularityDefining Modularity; From Monolithic to Modular; Modularity Principles; Benefits of Modularity; What's Next?; Notes; Chapter 15 Readability; Defining Readability; Plan to Get Hit by a Bus; Software Readability; External Readability; What's Next?; Notes; Chapter 16 Testability; Defining Testability; Software Testing; Testability; What's Next?; Notes; Chapter 17 Stability; Defining Stability; Achieving Stability; Stable Requirements; Defect-Free Code; Dynamic Flexibility; Stability and Beyond; Modularizing More Than Macros; What's Next?; Notes; Chapter 18 Reusability. - Includes bibliographical references and index</subfield></datafield><datafield tag="520" ind1=" " ind2=" "><subfield code="a">Design quality SAS software and evaluate SAS software quality SAS 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.</subfield></datafield><datafield tag="630" ind1="0" ind2="4"><subfield code="a">SAS (Computer file)</subfield></datafield><datafield tag="650" ind1=" " ind2="7"><subfield code="a">COMPUTERS / Programming / General</subfield><subfield code="2">bisacsh</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Datenverarbeitung</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Quantitative research / Data processing</subfield></datafield><datafield tag="776" ind1="0" ind2="8"><subfield code="i">Erscheint auch als</subfield><subfield code="n">Druckausgabe</subfield><subfield code="z">978-1-119-24076-1</subfield></datafield><datafield tag="856" ind1="4" ind2="0"><subfield code="u">https://onlinelibrary.wiley.com/doi/book/10.1002/9781119255680</subfield><subfield code="x">Verlag</subfield><subfield code="z">URL des Erstveröffentlichers</subfield><subfield code="3">Volltext</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">ZDB-35-WIC</subfield></datafield><datafield tag="940" ind1="1" ind2=" "><subfield code="q">UBG_PDA_WIC</subfield></datafield><datafield tag="999" ind1=" " ind2=" "><subfield code="a">oai:aleph.bib-bvb.de:BVB01-029264793</subfield></datafield><datafield tag="966" ind1="e" ind2=" "><subfield code="u">https://onlinelibrary.wiley.com/doi/book/10.1002/9781119255680</subfield><subfield code="l">FRO01</subfield><subfield code="p">ZDB-35-WIC</subfield><subfield code="q">FRO_PDA_WIC</subfield><subfield code="x">Verlag</subfield><subfield code="3">Volltext</subfield></datafield><datafield tag="966" ind1="e" ind2=" "><subfield code="u">https://onlinelibrary.wiley.com/doi/book/10.1002/9781119255680</subfield><subfield code="l">UBG01</subfield><subfield code="p">ZDB-35-WIC</subfield><subfield code="q">UBG_PDA_WIC</subfield><subfield code="x">Verlag</subfield><subfield code="3">Volltext</subfield></datafield></record></collection> |
| id | DE-604.BV043854560 |
| illustrated | Not Illustrated |
| indexdate | 2024-07-10T07:36:49Z |
| institution | BVB |
| isbn | 1119255686 1119255708 9781119255680 9781119255703 |
| language | English |
| oai_aleph_id | oai:aleph.bib-bvb.de:BVB01-029264793 |
| oclc_num | 957521276 965503319 |
| open_access_boolean | |
| owner | DE-861 |
| owner_facet | DE-861 |
| physical | 1 online resource |
| psigel | ZDB-35-WIC UBG_PDA_WIC ZDB-35-WIC FRO_PDA_WIC ZDB-35-WIC UBG_PDA_WIC |
| publishDate | 2016 |
| publishDateSearch | 2016 |
| publishDateSort | 2016 |
| publisher | John Wiley & Sons |
| record_format | marc |
| series2 | Wiley and SAS business series |
| spelling | Hughes, Troy Martin 1976- aut SAS data analytic development dimensions of software quality Troy Martin Hughes Hoboken, New Jersey John Wiley & Sons 2016 1 online resource txt rdacontent c rdamedia cr rdacarrier Wiley and SAS business series Includes index Cover; Title Page; Copyright; Contents; Preface; Objectives; Audience; Application of Content; Organization; Acknowledgments; About the Author; Chapter 1 Introduction; Distinguishing Data Analytic Development; Software Development Life Cycle (SDLC); Risk; What's Next?; Notes; Chapter 2 Quality; Defining Quality; Software Product Quality Model; Quality in the SDLC; What's Next?; Notes; Chapter 3 Communication; Return Codes; System Numeric Return Codes; System Alphanumeric Return Codes; User-Generated Return Codes; Parallel Processing Communication; What's Next?; Notes Part I Static PerformanceChapter 4 Reliability; Defining Reliability; Paths to Failure; ACL: The Reliability Triad; Reliability in the SDLC; What's Next?; Notes; Chapter 5 Recoverability; Defining Recoverability; Recoverability toward Reliability; Recoverability Matrix; TEACH Recoverability Principles; SPICIER Recoverability Steps; Recovering with Checkpoints; Recoverability in the SDLC; What's Next?; Notes; Chapter 6 Robustness; Defining Robustness; Robustness toward Reliability; Defensive Programming; Exception Handling; Robustness in the SDLC; What's Next?; Notes Chapter 7 Execution EfficiencyDefining Execution Efficiency; Factors Affecting Execution Efficiency; False Dependencies; Parallel Processing; Execution Efficiency in the SDLC; What's Next?; Notes; Chapter 8 Efficiency; Defining Efficiency; Disambiguating Efficiency; Defining Resources; Efficiency in the SDLC; What's Next?; Notes; Chapter 9 Scalability; Defining Scalability; The Scalability Triad; Resource Scalability; Demand Scalability; Load Scalability; Scalability in the SDLC; What's Next?; Notes; Chapter 10 Portability; Defining Portability; Disambiguating Portability 3GL versus 4GL PortabilityFacets of Portability; Portability in the SDLC; What's Next?; Notes; Chapter 11 Security; Defining Security; Confidentiality; Integrity; Availability; Security in the SDLC; What's Next?; Notes; Chapter 12 Automation; Defining Automation; Automation in SAS Software; SAS Processing Modes; Starting in Interactive Mode; Starting in Batch Mode; Automation in the SDLC; What's Next?; Notes; Part II Dynamic Performance; Chapter 13 Maintainability; Defining Maintainability; Maintenance; Maintenance in the SDLC; Failure to Maintain; Maintainability; What's Next?; Notes Chapter 14 ModularityDefining Modularity; From Monolithic to Modular; Modularity Principles; Benefits of Modularity; What's Next?; Notes; Chapter 15 Readability; Defining Readability; Plan to Get Hit by a Bus; Software Readability; External Readability; What's Next?; Notes; Chapter 16 Testability; Defining Testability; Software Testing; Testability; What's Next?; Notes; Chapter 17 Stability; Defining Stability; Achieving Stability; Stable Requirements; Defect-Free Code; Dynamic Flexibility; Stability and Beyond; Modularizing More Than Macros; What's Next?; Notes; Chapter 18 Reusability. - Includes bibliographical references and index Design quality SAS software and evaluate SAS software quality SAS 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. SAS (Computer file) COMPUTERS / Programming / General bisacsh Datenverarbeitung Quantitative research / Data processing Erscheint auch als Druckausgabe 978-1-119-24076-1 https://onlinelibrary.wiley.com/doi/book/10.1002/9781119255680 Verlag URL des Erstveröffentlichers Volltext |
| spellingShingle | Hughes, Troy Martin 1976- SAS data analytic development dimensions of software quality SAS (Computer file) COMPUTERS / Programming / General bisacsh Datenverarbeitung Quantitative research / Data processing |
| title | SAS data analytic development dimensions of software quality |
| title_auth | SAS data analytic development dimensions of software quality |
| title_exact_search | SAS data analytic development dimensions of software quality |
| title_full | SAS data analytic development dimensions of software quality Troy Martin Hughes |
| title_fullStr | SAS data analytic development dimensions of software quality Troy Martin Hughes |
| title_full_unstemmed | SAS data analytic development dimensions of software quality Troy Martin Hughes |
| title_short | SAS data analytic development |
| title_sort | sas data analytic development dimensions of software quality |
| title_sub | dimensions of software quality |
| topic | SAS (Computer file) COMPUTERS / Programming / General bisacsh Datenverarbeitung Quantitative research / Data processing |
| topic_facet | SAS (Computer file) COMPUTERS / Programming / General Datenverarbeitung Quantitative research / Data processing |
| url | https://onlinelibrary.wiley.com/doi/book/10.1002/9781119255680 |
| work_keys_str_mv | AT hughestroymartin sasdataanalyticdevelopmentdimensionsofsoftwarequality |