Muutke küpsiste eelistusi

E-raamat: Software Reading Techniques: Twenty Techniques for More Effective Software Review and Inspection

3.50/5 (11 hinnangut Goodreads-ist)
  • Formaat: PDF+DRM
  • Ilmumisaeg: 17-Nov-2016
  • Kirjastus: APress
  • Keel: eng
  • ISBN-13: 9781484223468
Teised raamatud teemal:
  • Formaat - PDF+DRM
  • Hind: 34,57 €*
  • * hind on lõplik, st. muud allahindlused enam ei rakendu
  • Lisa ostukorvi
  • Lisa soovinimekirja
  • See e-raamat on mõeldud ainult isiklikuks kasutamiseks. E-raamatuid ei saa tagastada.
Software Reading Techniques: Twenty Techniques for More Effective Software Review and InspectionSuurem pilt
  • Formaat: PDF+DRM
  • Ilmumisaeg: 17-Nov-2016
  • Kirjastus: APress
  • Keel: eng
  • ISBN-13: 9781484223468
Teised raamatud teemal:

DRM piirangud

  • Kopeerimine (copy/paste):

    ei ole lubatud

  • Printimine:

    ei ole lubatud

  • Kasutamine:

    Digitaalõiguste kaitse (DRM)
    Kirjastus on väljastanud selle e-raamatu krüpteeritud kujul, mis tähendab, et selle lugemiseks peate installeerima spetsiaalse tarkvara. Samuti peate looma endale  Adobe ID Rohkem infot siin. E-raamatut saab lugeda 1 kasutaja ning alla laadida kuni 6'de seadmesse (kõik autoriseeritud sama Adobe ID-ga).

    Vajalik tarkvara
    Mobiilsetes seadmetes (telefon või tahvelarvuti) lugemiseks peate installeerima selle tasuta rakenduse: PocketBook Reader (iOS / Android)

    PC või Mac seadmes lugemiseks peate installima Adobe Digital Editionsi (Seeon tasuta rakendus spetsiaalselt e-raamatute lugemiseks. Seda ei tohi segamini ajada Adober Reader'iga, mis tõenäoliselt on juba teie arvutisse installeeritud )

    Seda e-raamatut ei saa lugeda Amazon Kindle's. 

This concise book teaches software professionals and software engineering students the full set of twenty software reading techniques to enhance their effectiveness in reviewing and inspecting software artifacts such as requirements specifications, designs, code files, and usability. 
Software review and inspection is the best practice in software development whose purpose is to detect and fix problems early. Software professionals are trained to write software but not read and analyze software written by peers. As a result, individual reading skills vary widely. Because the effectiveness of software review and inspection is highly dependent on individual reading skills, differential outcomes among software readers vary by a factor of ten. Software Reading Techniques is designed to close that gap.
Dr Yang-Ming Zhu’s depth of experience as a software architect, team leader, and scientist make him singularly well-equipped to bring software readers up to speed on all the techniques and tips for optimizing the effectiveness and efficiency of their software review and inspection skills.

What You'll Learn
  • Software review and inspection procedures and reading skills
  • Traditional and modern advanced reading techniques applicable to almost all software artifacts
  • Specific reading techniques for software requirements specification, software design, and code

Who This Book Is For
Software Reading Techniques is for all software professionals and software engineering students and researchers.

Arvustused

Eight chapters cover generic software reading techniques that apply to any artifact and specific techniques that apply only to requirements, designs, or code. The books primary audience is software engineering practitioners. As a practicing software developer who has been doing reviews and inspections on all sorts of material for many years, I highly recommend it to anyone interested in software reviews. It would also be an excellent source for software engineering researchers interested in quality assurance or software reviews. (Computing Reviews, September, 2017) 

About the Author xiii
About the Technical Reviewer xv
Acknowledgments xvii
Introduction xix
Chapter 1 Introduction 1(6)
1.1 Software Quality, Software Reviews and Inspections
1(3)
1.2 About This Book
4(1)
1.2.1 Organization of This Book
4(1)
1.2.2 Intended Audience and How to Use This Book
5(1)
1.3 References
5(2)
Chapter 2 Software Review Procedures 7(14)
2.1 A Generic Software Review Procedure
7(1)
2.2 Fagan Inspection and Extensions
8(5)
2.2.1 Fagan Inspection
8(3)
2.2.2 Extensions to Fagan Inspection
11(2)
2.3 Active Design Review and Extensions
13(2)
2.3.1 Active Design Review
13(2)
2.3.2 Extensions to the Active Design Review
15(1)
2.4 Other Types of Reviews
15(1)
2.5 Factors Impacting Software Reviews
16(2)
2.6 Summary
18(1)
2.7 References
19(2)
Chapter 3 Basic Software Reading Techniques 21(14)
3.1 Introduction to Software Reading
21(2)
3.1.1 Definition of Software Reading
22(1)
3.1.2 Purposes of Software Reading
22(1)
3.1.3 Taxonomy of Software Reading Techniques
23(1)
3.2 Ad hoc Reading
23(1)
3.3 Checklist-Based Reading
24(5)
3.3.1 Checklist Definition, Types, and Examples
24(2)
3.3.2 Checklists with Guidance
26(2)
3.3.3 Best Practices of Checklists
28(1)
3.3.4 Empirical Experiences
28(1)
3.4 Differential Reading
29(3)
3.5 Summary
32(1)
3.6 References
33(2)
Chapter 4 Scenario-Based Reading Techniques 35(34)
4.1 Principles of Scenario-Based Reading
35(2)
4.2 Defect-Based Reading
37(5)
4.2.1 Taxonomy of Defects in Requirements Specifications
38(1)
4.2.2 Defect-Based Reading Techniques
39(2)
4.2.3 Empirical Experiences
41(1)
4.3 Perspective-Based Reading
42(22)
4.3.1 A Generic Perspective-Based Reading
42(3)
4.3.2 Perspective-Based Requirements Reading
45(3)
4.3.3 Perspective-Based Design Reading
48(4)
4.3.4 Perspective-Based Code Reading
52(2)
4.3.5 Perspective-Based Usability Reading
54(4)
4.3.6 Why Does Perspective-Based Reading Work?
58(6)
4.4 Alternative Partitioning of Reading Responsibilities
64(2)
4.4.1 Ad hoc Partition
64(1)
4.4.2 Function Point-Based Partition
65(1)
4.5 Summary
66(1)
4.6 References
66(3)
Chapter 5 Requirements Reading Techniques 69(8)
5.1 Critical Roles of Requirements in Software Development
69(1)
5.2 A Combined Reading Technique for Requirements
70(2)
5.2.1 Motivations for a Combined Reading
70(1)
5.2.2 The Combined-Reading Technique
70(2)
5.2.3 Empirical Experiences
72(1)
5.3 Test-Case Driven Reading for Requirements
72(2)
5.3.1 Test-Case-Driven Reading Technique
72(2)
5.3.2 Empirical Experiences
74(1)
5.4 Individual Factors Impacting Requirements Reading Efficiency
74(1)
5.5 Summary
75(1)
5.6 References
76(1)
Chapter 6 Design Reading Techniques 77(26)
6.1 Introduction
77(1)
6.2 Usage-Based Reading
77(4)
6.2.1 Usage-Based Reading Technique
78(2)
6.2.2 Variations of Usage-Based Reading
80(1)
6.2.3 Empirical Experiences
80(1)
6.3 Traceability-Based Reading
81(12)
6.3.1 Types of Design Defects
82(1)
6.3.2 High-Level OO Designs Using UML Diagrams
82(1)
6.3.3 Traceability-Based Reading Techniques
83(9)
6.3.4 Empirical Experiences
92(1)
6.4 Architecture Reading
93(4)
6.4.1 What Is Software Architecture?
93(1)
6.4.2 Traceability-Based Architecture Reading
94(1)
6.4.3 Empirical Experiences
95(1)
6.4.4 Other Architecture Reading Techniques
96(1)
6.5 Scope-Based Reading
97(3)
6.5.1 What Is an Application Framework?
97(1)
6.5.2 Scope-Based Reading Techniques
97(2)
6.5.3 Empirical Experiences
99(1)
6.6 Summary
100(1)
6.7 References
100(3)
Chapter 7 Code Reading Techniques 103(16)
7.1 Code Reading As a Professional Skill
103(2)
7.1.1 Importance of Code Reading
103(1)
7.1.2 How Do People Read Code?
104(1)
7.2 Reading by Stepwise Abstraction
105(2)
7.3 Object-Oriented Code Reading
107(4)
7.3.1 Challenges of Object-Oriented Code Reading
107(1)
7.3.2 Abstraction-Driven Reading
108(1)
7.3.3 Use-Case-Driven Reading
109(1)
7.3.4 Empirical Experiences
110(1)
7.4 Object-Oriented Framework Code Reading
111(3)
7.4.1 Why Yet Another Object-Oriented Code Reading Technique?
111(1)
7.4.2 Functionality-Based Approach to Framework Understanding
112(1)
7.4.3 Functionality-Based Reading
113(1)
7.4.4 Empirical Experiences
114(1)
7.5 Task-Directed Inspection
114(1)
7.6 Code Readability Factors
115(1)
7.7 Summary
116(1)
7.8 References
117(2)
Chapter 8 Conclusion 119(4)
Index 123
YangMing Zhu is Principal Scientist at Philips Healthcare, currently serving as the software architect for the Recon and Imaging Physics team for Advanced Molecular Imaging. He practices and researches image processing and software engineering with a focus on software architecture, requirements engineering, best practices, software quality, and processes. He is a senior member of IEEE and has published more than 80 book chapters and papers in such journals as IEEE Software, IEEE IT Professional, IEEE Trans Medical Imaging, IEEE Trans Image Processing, Journal of Nuclear Medicine, Physical Review Letters, Physical Review E, and Applied Physical Letters. He holds nine US patents (additional seven are pending approval), numerous professional awards, the Software Architecture Professional Certificate from the Software Engineering Institute at Carnegie Mellon University, and advanced degrees in computer science (MS from Kent State University), biomedical engineering (MS/BS from Shanghai Jiaotong University), and physics (PhD from Southeast University).
Lisainfo e-raamatute kohta Lisainfo e-raamatute kohta
Püsilink: https://www.kriso.ee/db/97814842234682e.html
Märksõnad: