Muutke küpsiste eelistusi

E-raamat: Software Engineering Reviews and Audits

4.00/5 (2 hinnangut Goodreads-ist)
  • Formaat: 260 pages
  • Ilmumisaeg: 07-Jan-2011
  • Kirjastus: Taylor & Francis Inc
  • Keel: eng
  • ISBN-13: 9781439851463
Teised raamatud teemal:
  • Formaat - PDF+DRM
  • Hind: 75,40 €*
  • * 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 Engineering Reviews and AuditsSuurem pilt
  • Formaat: 260 pages
  • Ilmumisaeg: 07-Jan-2011
  • Kirjastus: Taylor & Francis Inc
  • Keel: eng
  • ISBN-13: 9781439851463
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. 

Accurate software engineering reviews and audits have become essential to the success of software companies and military and aerospace programs. These reviews and audits define the framework and specific requirements for verifying software development efforts.

Authored by an industry professional with three decades of experience, Software Engineering Reviews and Audits offers authoritative guidance for conducting and performing software first article inspections, and functional and physical configuration software audits. It prepares readers to answer common questions for conducting and performing software reviews and audits, such as: What is required, who needs to participate, and how do we ensure success in all specified requirements in test and released configuration baselines?

Complete with resource-rich appendices, this concise guide will help you:



























Conduct effective and efficient software reviews and audits





Understand how to structure the software development life cycle





Review software designs and testing plans properly





Access best methods for reviews and audits





Achieve compliance with mandatory and contractual software requirements





The author includes checklists, sample forms, and a glossary of industry terms and acronyms to help ensure formal audits are successful the first time around. The contents of the text will help you maintain a professional setting where software is developed for profit, increase service quality, generate cost reductions, and improve individual and team efforts.
List of Figures
xiii
List of Tables
xv
Preface xvii
Acknowledgments xix
Chapter 1 Introduction
1(6)
1.1 Senior Management
2(1)
1.2 Process and Quality
3(1)
1.3 Software Lifecycle
4(3)
1.3.1 Requirements Phase
4(1)
1.3.2 Design Phase
4(1)
1.3.3 Implementation Phase
5(1)
1.3.4 Test Phase
5(1)
1.3.5 Installation and Checkout Phase
5(1)
1.3.6 Operation and Maintenance Phase
6(1)
1.3.7 Conclusion
6(1)
Further Reading
6(1)
Chapter 2 Process Model
7(10)
2.1 Process Model
7(1)
2.2 CMMI Understanding
8(1)
2.3 Process Areas
9(3)
2.4 Staged Maturity Levels
12(1)
2.5 Common Features
12(5)
2.5.1 Software Engineering Process Group
13(1)
2.5.2 Process Change Management
14(1)
Further Reading
15(2)
Chapter 3 Quality Management Systems
17(4)
3.1 Quality Management Systems
17(1)
3.2 Quality Management Systems Understanding
18(1)
3.3 AS9100 Program Audit
19(1)
3.4 Future Quality Management Systems Objectives
19(1)
3.5 Quantitative Management Process
20(1)
Further Reading
20(1)
Chapter 4 Policy
21(4)
4.1 Policy Understanding
21(2)
4.1.1 Organization-Level Policy
22(1)
4.2 Planning Process
23(1)
4.3 Planning Procedures
23(1)
4.4 Control Procedures
24(1)
Further Reading
24(1)
Chapter 5 Systems Engineering
25(4)
5.1 Systems Engineering Method
25(1)
5.2 Systems Analysis of Requirements
26(1)
5.2.1 Requirements Analysis
26(1)
5.2.2 Functional Analysis of Requirements
26(1)
5.2.3 Systems Integration of Requirements
27(1)
5.2.4 Systems Verification and Validation of Requirements
27(1)
5.3 Systems Engineering Management Plan
27(2)
Further Reading
28(1)
Chapter 6 Software Design
29(26)
6.1 Software Design Method
29(1)
6.2 Software Development Process
30(1)
6.3 Software Design Decisions
31(2)
6.3.1 Evaluate Requirements and Architecture
31(1)
6.3.2 Analyze Requirements and Architecture
31(2)
6.4 Computer Application Methods
33(2)
6.4.1 Waterfall Software Method
33(1)
6.4.2 Spiral Software Method
33(2)
6.5 Definition of Agile
35(1)
6.5.1 Agile Software Development Method
35(1)
6.6 Definition of Lean
36(1)
6.7 Definition of Firmware
36(1)
6.7.1 Software Components of Firmware
37(1)
6.7.2 Hardware Components of Firmware
37(1)
6.8 Identify Software Components
37(2)
6.8.1 Define Relationships
38(1)
6.8.2 Interfaces and Data
38(1)
6.9 Detailed Design
39(1)
6.9.1 Components into Software Units
39(1)
6.9.2 Configuration Item Details
39(1)
6.9.3 Interface and Data Design
39(1)
6.10 Evaluate the Software Design
40(1)
6.11 Software Coding and Unit Test
41(1)
6.12 Peer Review Method
41(1)
6.13 Peer Review Participants
41(4)
6.13.1 Peer Review Steps
43(1)
6.13.2 Establish Peer Review Plan
44(1)
6.14 Prepare the Products for the Peer Review
45(4)
6.14.1 Prepare the Peer Review Package
45(1)
6.14.2 Distribute the Peer Review Package
46(1)
6.14.3 Conduct the Peer Review
46(1)
6.14.4 Categorize the Comments and Disposition
47(1)
6.14.5 Complete the Peer Review
48(1)
6.14.6 Complete the Peer Review Records
48(1)
6.15 Design Traceability
49(1)
6.16 Design Definition
49(1)
6.17 Measurement Data
49(1)
6.18 Configuration Control
50(1)
6.19 Software Inspections
50(1)
6.20 Software Integration and Testing
50(2)
6.21 Software Formal Testing
52(1)
6.22 Software User Documentation
52(1)
6.23 Maintain Software Development
52(3)
Further Reading
52(3)
Chapter 7 Software Quality
55(12)
7.1 SQA and SQE/EQA Terminology
55(1)
7.2 Software Quality Methods
56(1)
7.3 Software Quality Organization
57(1)
7.4 Functional Software Quality Tasks
57(1)
7.5 Software Quality Program Planning
58(1)
7.6 Process Audit
58(1)
7.7 Support Verification and Validation
59(1)
7.8 Support Software Configuration Management
60(1)
7.9 Support Milestone Reviews
60(1)
7.10 Monitor Supplier Quality
60(1)
7.11 Software Noncompliance Handling
61(1)
7.12 Perform Software Product Evaluations
61(1)
7.13 SQA Role in Agile Software Development
62(1)
7.14 Software Quality Assurance Plan
63(1)
7.15 Summary
64(3)
Further Reading
65(2)
Chapter 8 Software Configuration Management
67(14)
8.1 Software Configuration Management Methods
67(1)
8.2 Organization
68(5)
8.2.1 Software Build Engineer
69(1)
8.2.2 Software Change Request
69(1)
8.2.3 Software Release
69(1)
8.2.4 Engineering Review Board
70(1)
8.2.5 Configuration Management Plan
70(1)
8.2.6 Software Development Plan
70(1)
8.2.7 Operating Procedures
71(1)
8.2.8 Computer Program Library
71(1)
8.2.9 Computer Program Library Contents
72(1)
8.2.10 Configuration Control
72(1)
8.2.11 Developmental Configuration
72(1)
8.3 Configuration Identification
73(2)
8.3.1 Computer Software Component Identification
74(1)
8.3.2 Computer Software Unit Identification
74(1)
8.3.3 Nondeliverable Software Identification
74(1)
8.3.4 Nondeliverable Software Control
74(1)
8.3.5 Part Number Identification
74(1)
8.4 Change Control
75(1)
8.4.1 Lower-Level Changes
75(1)
8.4.2 Middle-Level Changes
75(1)
8.4.3 High-Level Changes
75(1)
8.5 Configuration Status Accounting
76(1)
8.5.1 Software Records
76(1)
8.5.2 Archive Software Records
77(1)
8.5.3 Reports
77(1)
8.5.4 Test Configuration
77(1)
8.6 Software Configuration Audit Checklist
77(4)
Further Reading
79(2)
Chapter 9 Software Supplier Audit
81(10)
9.1 Starting Point for Software Supplier Audits
81(1)
9.2 Key Requirements for Software Supplier Audits
82(1)
9.3 Gate Review for Software Supplier Audits
82(1)
9.4 Software Technical Subcontract Management
83(1)
9.5 Subcontractor Software Configuration Management Audits
84(1)
9.5.1 Subcontractor Configuration Identification
84(1)
9.5.2 Subcontractor Computer Program Library
85(1)
9.6 Monitor Supplier Software Quality
85(6)
9.6.1 Monitor Supplier Quality Method
85(1)
9.6.2 Supplier Selection Activities
86(1)
9.6.3 Provide Quality Plan
86(1)
9.6.4 Quality Management Survey
86(1)
9.6.5 Project-Specific Supplier Audits
87(1)
9.6.6 Review Supplier-Delivered Products
87(1)
9.6.7 Participate in Formal Milestone Reviews
87(1)
9.6.8 Support Supplier Qualification Test
87(1)
9.6.9 Acceptance of Software Supplier Reviews
87(3)
Further Reading
90(1)
Chapter 10 Software Engineering Reviews
91(12)
10.1 Resources
91(1)
10.2 Software Engineering Review Steps
92(1)
10.3 Purpose
92(1)
10.3.1 Software Quality Assurance
93(1)
10.3.2 Integrated Product Teams
93(1)
10.4 Planning
93(3)
10.4.1 Software Development Plan
94(1)
10.4.2 Review Plans
95(1)
10.5 Performing
96(1)
10.6 Document Control Provisions
96(1)
10.7 Recording
97(3)
10.8 Reporting
100(1)
10.8.1 Reporting and Coordination
100(1)
10.8.2 Corrective Action/Process Improvement
100(1)
10.9 Summary
100(3)
Further Reading
101(2)
Chapter 11 Software Engineering Audits
103(12)
11.1 Audit Overview
103(1)
11.2 Audit Scope
104(1)
11.3 Audit Preparation
104(1)
11.4 Audit Schedule
105(1)
11.5 Audit Plan
105(1)
11.6 Audit Communication
106(1)
11.7 Audit Entry Criteria
106(1)
11.7.1 Collect Data Package
106(1)
11.8 Conduct and Perform Audit
107(2)
11.8.1 Audit Action Items
109(1)
11.9 Audit Report
109(1)
11.10 Audit Exit Criteria
110(1)
11.11 Audit Record Retention
110(1)
11.12 Summary
111(4)
Further Reading
113(2)
Chapter 12 Formal Reviews and Audits
115(22)
12.1 System Requirements Review
116(1)
12.2 System Design Review
116(1)
12.3 Software Specification Review
116(1)
12.4 Preliminary Design Review
116(1)
12.5 Critical Design Review
117(1)
12.6 Joint Technical Reviews
117(1)
12.7 Interim and Final Design Reviews
118(1)
12.7.1 Final Design Review Objectives
118(1)
12.9 Required Software Documentation
119(2)
12.9.1 Software Documentation Status
119(1)
12.9.2 Software Requirements Specification
119(1)
12.9.3 Interface Design Description
120(1)
12.9.4 System/Subsystem Design Description
120(1)
12.9.5 Database Design Description
120(1)
12.9.6 Software Design Description
121(1)
12.10 Test Readiness Reviews
121(2)
12.10.1 Software Test Plan
123(1)
12.10.2 Software Test Report
123(1)
12.10.3 Version Description Document
123(1)
12.11 Software Compliance Status
123(2)
12.11.1 Software Development Files
123(1)
12.11.2 Software Verification and Validation
124(1)
12.12 First Article Inspection
125(1)
12.13 Process Steps
125(2)
12.13.1 Determine Levels
125(1)
12.13.2 Create Records
126(1)
12.13.3 Plan and Schedule
126(1)
12.13.4 Release Information
126(1)
12.13.5 Provide Details
126(1)
12.13.6 Perform Quality Inspection and Record Results
126(1)
12.13.7 Software Documentation
127(1)
12.13.8 Audit Exit Criteria
127(1)
12.14 FCA/PCA Audits
127(1)
12.15 Functional Configuration Audit
127(2)
12.16 Physical Configuration Audit
129(1)
12.17 Preliminary Meetings
130(1)
12.18 Audit Preparation
130(2)
12.18.1 Collect Engineering Data Package
131(1)
12.19 Perform Audit Pre-Brief
132(1)
12.20 Audit Plan
132(1)
12.21 Audit Metrics
133(1)
12.22 Audit Execution
134(1)
12.23 Audit Final Meeting
134(1)
12.24 Audit Method for Software
135(1)
12.25 Final Summary
136(1)
Further Reading
136(1)
Appendix A Acronyms and Glossary 137(8)
Appendix B Software Development Plan 145(36)
Appendix C Software Quality Assurance Plan 181(20)
Appendix D Software Configuration Management Plan 201(18)
Appendix E FCA Checklist 219(4)
Appendix F PCA Checklist 223(6)
Acronyms 229(6)
Index 235
Boyd Summers received a Bachelor of Science (BS) in Business Management from Weber State University in 1985. He has since received awards such as the Outstanding Support Award from NSA Aerospace Data Facility Y2K (2000), Outstanding recognition for successful CDR for Next Generation Trainer (2007), and an Accomplishment for Integrated Defense Systems final Design Review (2009).
Lisainfo e-raamatute kohta Lisainfo e-raamatute kohta
Püsilink: https://www.kriso.ee/db/97814398514632e.html
Märksõnad: