具体描述
软件工程实践者的研究方法（英文第4版），ISBN：9787111067115，作者：（美）普莱斯曼著
《软件工程》 内容简介： 这是一本关于软件开发方法论、过程模型、项目管理、需求工程、系统设计、测试策略以及软件维护的深度探讨。本书旨在为读者构建一个全面的软件工程知识体系，涵盖从项目启动到最终交付的全生命周期管理。 核心内容聚焦： 软件开发过程模型： 详细解析瀑布模型、迭代模型（如螺旋模型、增量模型）、敏捷开发模型（如Scrum、XP）、DevOps等多种主流软件开发过程模型。通过对比分析，揭示不同模型的适用场景、优缺点以及在实际项目中的演进。重点强调如何根据项目特点选择和定制最适合的开发流程。 项目管理与组织： 深入讲解软件项目管理的各项职能，包括项目启动、规划（范围、时间、成本、资源、质量、风险）、执行、监控和收尾。介绍不同的组织结构（如职能型、项目型、矩阵型）及其对项目管理的影响。提供项目风险识别、评估、应对和监控的实用技巧，以及如何有效地管理项目团队和沟通。 需求工程： 详述需求获取、分析、规格说明、验证和管理的全过程。介绍多种需求获取技术，如访谈、问卷、观察、原型法、焦点小组等。讲解需求分析的技术，如用例建模、数据流图、实体关系图等，并强调如何撰写清晰、完整、一致、可验证的软件需求规格说明书（SRS）。探讨需求变更管理的重要性及方法。 系统设计： 涵盖软件架构设计、详细设计和用户界面设计。深入探讨不同的软件架构风格（如客户端-服务器、分层架构、微服务架构、面向服务架构），以及如何选择和应用合适的架构。讲解模块化设计、接口设计、数据结构和算法设计等详细设计原则。提供用户体验（UX）和用户界面（UI）设计的最佳实践，强调可用性、可访问性和交互性。 软件测试与质量保证： 全面介绍软件测试的各个层次和类型，包括单元测试、集成测试、系统测试、验收测试。探讨不同的测试方法，如黑盒测试、白盒测试、灰盒测试。讲解测试计划、测试用例设计、测试执行和缺陷管理。强调质量保证（QA）在整个开发生命周期中的作用，以及如何建立有效的质量度量体系。 软件维护与演进： 阐述软件维护的挑战和策略，包括修正性维护、适应性维护、完善性维护和预防性维护。介绍软件重构、代码审查和配置管理的重要性，以及如何有效管理软件的版本和变更。探讨遗留系统的演进和现代化改造。 新兴技术与实践： 关注软件工程领域的新发展，如DevOps的实践、容器化技术（如Docker）、自动化部署、持续集成/持续交付（CI/CD）、微服务架构下的开发与运维挑战，以及基于人工智能的软件开发辅助工具。 本书特色： 本书结构清晰，逻辑严谨，理论与实践相结合。通过丰富的案例分析和项目实践指导，帮助读者将抽象的理论知识转化为解决实际问题的能力。语言通俗易懂，适合不同层次的读者阅读，包括计算机科学与技术、软件工程专业的学生，以及希望提升软件开发能力的从业人员。本书不仅是学习软件工程理论的优秀教材，更是指导软件项目成功实施的实用指南。 读者受益： 阅读本书后，您将能够： 深刻理解软件开发的全生命周期。 掌握多种软件开发过程模型，并能根据项目选择最合适的方法。 熟练运用项目管理技术，有效规划、执行和控制软件项目。 掌握需求工程的关键技术，确保软件满足用户需求。 理解软件架构和详细设计的原则，设计出高质量的软件系统。 掌握全面的软件测试策略，确保软件的质量和可靠性。 了解软件维护的挑战，并能有效管理软件的生命周期后期。 熟悉当前软件工程领域的前沿技术和发展趋势。 本书将为您在快速变化的软件开发领域提供坚实的理论基础和实践指导，助力您成为一名优秀的软件工程师。
作者简介
Roger S. Pressman is an intemationally recognized consultant and author
in software engineering. He received a B.S.E. (cum laude) from the
University of Connecticut, an M.S. firom the University of Bridgeport and a
Ph-D. in engineering from the University ofConnecticut, and has over 25 years
of industry experience, holding both technical and management positions with
responsibility for the development ofsoftware for engineered products and sys-
tems.
As an industry practitioner and manager, Dr. Pressman worked on the de-
velopment of CAD/CAM systems for advanced engineering and manufacturing
in aerospace applications. He has also held positions with responsibility for sci-
entific and systems programming.
In addition to his industry experience, Dr. Pressman was Bullard Associate
Professor ofComputer Engineering at the University ofBridgeport and Director
of the University's Computer-Aided Design and Manufacturing Center.
Dr. Pressman is President of R.S. Pressman & Associates, Inc., a consult-
ing fim specializing in software engineering methods and training. He serves
as principal consultant, specializing in helping companies establish effective
software engineering practices. He developed the RSP&A software engineering
assessment method, a unique blend of quantitative and qualitative analysis
that helps clients assess their current state of software engineering practice.
In addition to consulting services rendered to many Fortune 500 clients,
R-S. Pressman & Associates, Inc. markets a wide variety of software engineer-
ing training products and process improvement services. The company has de-
veloped a state-of-the-art video curriculum, Essential Software Engineering,
which is among the industry's most comprehensive treatments of the subject.
Another product, Process Advisor, is a self-directed system for software process
unprovement.
Dr. Pressman is author of many technical papers, is a regular contributor
to industry periodicals, and is author of six books. In addition to Software
Engineering: A Practitioner's Approach, he has written Making Software
Engineering Happen (Prentice Hall), the first book to address the critical man-
agement problems associated with software engineering process improvement,
Software Shock (Dorset House), a treatment of software and its impact on busi-
ness and sodety, and A Manager's Guide to Software Engineering (McGraw-
Hill), a book that uses a unique Q&A format to present management guidelines
for instituting and understanding the technology. Dr. Pressman is on the edi-
torial boards ofAmerican Programmer and IEEE Software, and is editor of the
"Manager" column in IEEE Software. He is a member of the ACM, IEEE, and
Tau Beta Pi, Phi Kappa Phi, Eta Kappa Nu, and Pi Tau Sigma.
目录信息
CONTENTS AT A GLANCE
PREFACE
PART ONE THE PRODUCT AND THI PROCESS
CHAPTER 1 THE PRODUCT
CHAPTER 2 THE PROCESS
PART TWO MANAOINO SOFTWARE PROJECTS
CHAPTER 3 PROJECT MANAGEMENT CONCEPTS
CHAPTER 4 SOFTWARE PROCESS AND PROJECT METRICS
CHAPTER 5 SOFTWARE PROJECT PIANNING
CHAPTER 6 RISK MANAGEMENT
CHAPTER 7 PROJECT SCHEDULING AND TRACKING
CHAFTER 8 SOFTWARE QUALITY ASSURANCE
CHAPTER 9 SOFTWARE CONFIGURATION MANAGEMENT
PART THREE CONVENTIONAL METHODS FOR SOFTWARE ENGINEEMNG
CHAPTER 10 SYSTEM ENGINEERING
CHAPTER 11 ANALYSIS CONCEPTS AND PRINCIPLES
CHAPTER12 ANALYSIS MODELING
CHAPTER 13 DESIGN CONCEPTS AND PRINCIPLES
CHAPTER 14 DESlGN METHODS
CHAPTER 15 DESlGN FOR REAL-TlME SYSTEMS
CHAPTER 16 SOFTWARE TESTlNG TECHNlQUES
CHAPTER 17 SOFTWARE TESTlNG STRATEGlES
CHAPTER l 8 TECHNlCAL METRlCS FOR SOFTWARE
PART FOUR OBJECT-ORlENTED SOFTWARE ENOlNEERlNG
CHAPTER l 9 OBJECT-ORlENTED CONCEPTS AND PRlNClPLES
CHAPTER 20 OBjECTORlENTED ANALYSlS
CHAPTER 21 OBJECT-ORlENTED DESlGN
CHAPTER 22 OBJECT-ORlENTED TESTlNG
CHAPTER 23 TECHNlCAL METRlCS FOR OBJECTORlENTED SYSTEMS
PART FlVE ADVANCED TOPICS IN SOFTWARE ENGlNEERlNG
CHAPTER 24 FORMAL METHODS
CHAPTER 25 CLEANROOM SOFTWARE ENGlNEERlNG
CHAPTER 26 SOFTWARE REUSE
CHAPTER 27 REENGlNEERlNG
CHAPTER 28 CLlENT/SERVER SOFTWARE ENGlNEERlNG
CHAPTER 29 COMPUTER-AlDED SOFTWARE ENGlNEERlNG
CHAPTER 30 THE ROAD AHEAD
TABLE OF CONTENTS
PREFACE
PART ONE THE PRODUCT AND THE PROCESS
CHAPTER 1 THE PRODUCT
1.1 THE EVOLVING ROLE OF SOFTWARE
1.1.1 An Industry Perspective
1.1.2 An Aging Software Plant
1.1.3 Soflware Competitiveness
1.2 SOFTWARE
1.2.1 Software Characteristics
1.2.2 Soflware Components
1.2.3 Software Applications
1.3 SOFTWARE: A CRISIS ON THE HORIZON
1.4 SOFTWARE MYTHS
1.5 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND INFORMATION SOURCES
CHAPTER 2 THE PROCESS
2.1 SOFTWARE ENGINEERING-A lAYERED TECHNOLOGY
2.1.1 Process, Methods, and Tools
2.1.2 A Generic View of Software Engineering
2.2 THE SOFTWARE PROCESS
2.3 SOFTWARE PROCESS MODELS
2.4 THE LINEAR SEQUENTIAL MODEL
2.5 THE PROTOTYPING MODEL
2.6 THERADMODEL
2.7 EVOLUTIONARY SOFTWARE PROCESS MODELS
2.7.1 The Incremental Model
2.7.2 The Spiral Model
2.7.3 The Component Assembly Model
2.7.4 The Concurrent Development Model
2.8 THE FORMAl METHODS MODEL
2.9 FOURTH GENERATION TECHNIQUES
2.10 PROCESS TECHNOLOGY
2.11 PRODUCT AND PROCESS
2.12SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
PART TWO MANAGING SOFTWARE PROJECTS
CHAPTER 3 PROJECT MANAGEMENT CONCEPTS
3.1 THE MANAGEMENT SPECTRUM
3.1.1 People
3.1.2 TheProblem
3.1.3 TheProcess
3.2 PEOPLE
3.2.1 ThePlayers
3.2.2 Team leaders
3.2.3 The Software Team
3.2.4 Coordination and Communication Issues
3.3 THEPROBLEM
3.3.1 Soflware Scope
3.3.2 Problem Decomposition
3.4 THEPROCESS
3.4.1 Melding the Problem and the Process
3.4.2 Process Decomposition
3.5 THEPRQIECT
3.6 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 4 SOFTWARE PROCESS AND PROJECT METRICS
4.1 MEASURES, METRICS, AND INDICATORS
4.2 METRICS IN THE PROCESS AND PROJECT DOMAINS
4.2.1 Process Metrics and Software Process Improvement
4.2.2 Proiect Metrics
4.3 SOFTWARE MEASUREMENT
4.3.1 SizeOriented Metrics
4.3.2 Function-Oriented Metrics
4.3.3 Extended Function Point Metrics
4.4 RECONCILING DIFFERENT METRICS APPROACHES
4.5 METRICS FOR SOFTWARE QUALITY
4.5.1 An Overview of Factors That Affect Quality
4.5.2 Measuring Quality
4.5.3 Defect Removal Efficiency
4.6 INTEGRATING METRICS WITHIN THE SOFTWARE PROCESS
4.7 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 5 SOFTWARE PROJECT PIANNING
5.1 OBSERVATIONS ON ESTIMATING
5.2 PROJECT PIANNING OBJECTIVES
5.3 SOFTWARE SCOPE
5.3.1 Obtaining Information Necessary for Scope
5.3.2 A Scoping Example
5.4 RESOURCES
5.4.1 Human Resources
5.4.2 Reusable Software Resources
5.4.3 Environmental Resources
5.5 SOFTWARE PROJECT ESTIMATION
5.6 DECOMPOSITION TECHNIQUES
5.6.1 Soflware Sizing
5.6.2 Problem-Based Estimation
5.6.3 An Example of LOC-Based Esftmation
5.6.4 An Example of FP-Based Estimation
5.6.5 Process-Based Estimation
5.6.6 An Example of Process-Based Estimation
5.7 EMPIRICAL ESTIMATION MODELS
5.7.1 The Structure of Estimation Models
5.7.2 The COCOMO Model
5.7.3 The Soflware Equation
5.8 THE MAKE-BUY DECISION
5.8.1 Creating a Decision Tree
5.8.2 Outsourcing
5.9 AUTOMATED ESTIMATION TOOLS
5.10SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINQS AND OTHER INFORMATION SOURCES
CHAPTER 6 RISK MANAGEMENT
6.1 REACTIVE VS. PROACTIVE RISK STRATEGIES
6.2 SOFTWARE RISKS
6.3 RISK IDENTIFICATION
6.3.1 Product Size Risks
6.3.2 Business Impoct Risks
6.3.3 Customer-Related Risks
6.3.4 Process Risks
6.3.5 Technology Risk
6.3.6 Development Environment Risks
6.3.7 Risks Associated with Staff Size and Experience
6.3.8 Risk Components and Drivers
6.4 RISK PROJECTION
6.4.1 Developing a Risk Table
6.4.2 Assessing Risk Impact
6.4.3 Risk Assessment
6.5 RISK MITIGATION, MONITORING, AND MANAGEMENT
6.6 SAFETY RISKS AND HAZARDS
6.7 THERMMMPIAN
6.8 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 7 PROJECT SCHEDULING AND TRACKING
7.1 BASIC CONCEPTS
7.1.1 Comments on "Lateness'
7.1.2 Basic Principles
7.2 THE REIATIONSHIP BETWEEN PEOPLE AND EFFORT
7.2.1 An Example
7.2.2 An Empirical Relationship
7.2.3 Effort Distribufion
7.3 DEFINING A TASK SET FOR THE SOFTWARE PROJECT
7.3.1 OegreeofRigor
7.3.2 Defining Adaptation Criteria
7.3.3 Computing a Task Set Selector Value
7.3.4 Interpreting the TSS Value and Selecting the Task Set
7.4 SELECTING SOFTWARE ENGINEERING TASKS
7.5 REFINEMENT OF MAJOR TASKS
7.6 DEFINING A TASK NETWORK
7.7 SCHEDULING
7.7.1 Timeline Charts
7.7.2 Tracking the Schedule
7.8 THE PROJECT PIAN
7.9 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 8 SOFTWARE QUALrTY ASSURANCE
8.1 QUAUTY CONCEPTS
8.1.1 Qualily
8.1.2 Qualily Control
8.1.3 Qualily Assurance
8.1.4 Cost of Quality
8.2 THE QUALITY MOVEMENT
8.3 SOFTWARE QUAUTY ASSURANCE
8.3.1 Background Issues
8.3.2 SQAActivities
8.4 SOFTWARE REVIEWS
8.4.1 Cost Impact of Software Defects
8.4.2 Defect Amplification and Removal
8.5 FORMAL TECHNICAL REVIEWS
8.5.1 The Review Meeting
8.5.2 Review Reporting and Record Keeping
8.5.3 Review Guidelines
8.6 FORMAL APPROACHES TO SQA
8.7 STATISTICAL QUALITY ASSURANCE
8.8 SOFTWARE REUABILITY
8.8.1 Measures of Reliabilily and Availabilify
8.8.2 Soflware Safely and Hazard Analysis
8.9 THESQAPlAN
8.10 THE ISO 9000 QUALITY STANDARDS
8.10.1 The ISO Approach to Qualily Assurance Systems
8.10.2 The ISO 9001 Standard
8.11 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 9 SOFTWARE CONFIGURATION MANAGEMENT
9.1 . SOFTWARE CONFIGURATION MANAGEMENT
9.1.1 Baselines
9.1.2 Software Configuration Items
9.2 THE SCM PROCESS
9.3 IDENTIFICATION OF OBJECTS IN THE SOFTWARE CONFIGURATION
9.4 VERSION CONTROL
9.5 CHANGE CONTROL
9.6 CONFIGURATION AUDIT
9.7 STATUS REPORTING
9.8 SCMSTANDARDS
9.9 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
PART THREE CONVINTiONAL METHOOS FOR SOnWARE JNOINHRINO
CHAPTER 10 SYSTEM ENGNEERING
10.1 COMPUTER-BASED SYSTEMS
10.2 THE SYSTEM ENGINEERING HIERARCHY
10.2.1 System Modeling
10.2.2 Information Engineering: An Overview
10.2.3 Product Engineering: An Overview
10.3 INFORMATION ENGINEERING
10.4 INFORMATION STRATEGY PIANNING
10.4.1 Enterprise Modeling
10.4.2 Business-level Dala Modeling
10.5 BUSINESS AREA ANALYSIS
10.5.1 Process Modeling
10.5.2 Information Flow Modeling
10.6 PRODUCT ENGINEERING
10.6.1 System Analysis
10.6.2 Identification of Need
10.6.3 Feasibility Study
10.6.4 EconomicAnalysis
10.6.5 Technical Analysis
10.7 MODELNNG THE SYSTEM ARCHITECTURE
10.8 SYSTEM MODEUNG AND SIMUIATION
10.9 SYSTEM SPECIFICATION
10.10SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 11 ANALYSIS CONCEPTS AND PRINCIPLES
11.1 REQUIREMENTS ANALYSIS
11.2 COMMUNICATION TECHNIQUES
11.2.1 Initiating the Process
11.2.2 Facilitaled Application Specification Techniques
11.2.3 Qualily Function Deployment
11.3 ANALYSIS PRINCIPLES
11.3.1 The Information Domain
11.3.2 Modeling
11.3.3 Partitioning
11.3.4 Essential and Implementation Views
11.4 SOFTWARE PROTOTYPING
11.4.1 Selecting the Protolyping Approach
11.4.2 Protolyping Methods and Tools
11.5 SPECIFICATION
11.5.1 Specification Principles
11.5.2 Representation
11.5.3 The Software Requirements Specification
11.6 SPECIFICATION REVIEW
11.7 SUMMARY
REFERENCES
PROBIEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 12 ANALYSIS MODELING
12.1 A BRIEF HISTORY
12.2 THE ELEMENTS OF THE ANALYSIS MODEL
12.3 DATAMODELING
12.3.1 Data Objects, Altributes, and Relationships
12.3.2 Cardinalityand Modality
12.3.3 Entily-RelalionshipDiagrams
12.4 FUNCTIONAl MODELING AND INFORMATION FLOW
12.4.1 Data Flow Diagrams
12.4.2 Extensions for Real-Time Syslems
12.4.3 Ward and Mellor Extensions
12.4.4 Hatley and Pirbhai Extensions
12.5 BEHAVIORAL MODEUNG
12.6 THE MECHANICS OF STRUCTURED ANAIYSIS
12.6.1 Creating an Entily-RelationshipDiagram
12.6.2 Creating a Data Flow Model
12.6.3 Creating a Control Flow Model
12.6.4 The Control Specification
12.6.5 The Process Specification
12.7 THE DATA DICTIONARY
12.8 AN OVERVIEW OF OTHER CIASSICAL ANALYSIS METHODS
12.8.1 Data Structured Systems Development
12.8.2 Jackson System Development
12.8.3 SADT
12.9 SUMMARY
REFERENCES
PROBIEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 13 DESIGN CONCEPTS AND PRINCIPLES
13.1 SOFTWARE DESIGN AND SOFTWARE ENGINEERING
13.2 THE DESIGN PROCESS
13.2.1 Design dnd Software Qualily
13.2.2 The Evolution of Soflware Design
13.3 DESIGN PRINCIPLES
13.4 DESIGN CONCEPTS
13.4.1 Abstraction
13.4.2 Refinement
13.4.3 Modularily
13.4.4 Soflware Architectre
13.4.5 Control Hierarchy
13.4.6 Structural Partitioning
13.4.7 Data Structure
13.4.8 Software Procedure
13.4.9 Information Hiding
13.5 EFFECTIVE MODUIAR DESIGN
13.5.1 Functional Independence
13.5.2 Cohesion
13.5.3 Coupling
13.6 DESIGN HEURISTICS FOR EFFECTIVE MODULARITY
13.7 THE DESIGN MODEL
13.8 DESIGN DOCUMENTATION
13.9 SUMMARY
REFERENCES
PROBtEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 14 DESIGN METHODS
14.1 DATADESIGN
14.2 ARCHITECTURAL DESIGN
14.2.1 Contributors
14.2.2 Areas of Application
14.3 THE ARCHITECTURAL DESIGN PROCESS
14.3.1 Transform Flow
14.3.2 Transaction Flow
14.4 TRANSFORM MAPPING
14.4.1 An Example
14.4.2 Design Steps
14.5 TRANSACTION MAPPING
14.5.1 An Example
14.5.2 DesignSteps
14.6 DESIGN POSTPROCESSING
14.7 ARCHITECTURAL DESIGN OPTIMIZATION
14.8 INTERFACE DESIGN
14.8.1 Intemal and External Interface Design
14.8.2 User Interface Design
14.9 HUMAN-COMPUTER INTERFACE DESIGN
14.9.1 Interface Design Models
14.9.2 Task Analysis and Modeling
14.9.3 Design Issues
14.9.4 Implementation Tools
14.9.5 Design Evaluation
14.10 INTERFACE DESIGN GUIDELINES
14.10.1 General Interaction
14.10.2 Information Display
14.10.3 Datalnput
14.11 PROCEDURAL DESIGN
14.11.1 Structured Programming
14.11.2 Graphical Design Notation
14.11.3 Tabular Design Notation
14.11.4 Program Design Language
14.11.5 APDLExample
14.12 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 15 DESIGN FOR REAl-TIME SYSTEMS
15.1 SYSTEM CONSIDERATIONS
15.2 REAL-TIME SYSTEMS
15.2.1 Integration and Performance Issues
15.2.2 Interrupt Handling
15.2.3 Real-Time Data Bases
15.2.4. Real-Time Operating Systems
15.2.5 Real-Time Languages
15.2.6 Task Synchromzation and Communication
15.3 ANALYSIS AND SIMUIATION OF REAL-TIME SYSTEMS
15.3.1 Mathematical Tools for Real-Time System Analysis
15.3.2 Simulation and Modeling Techniques
15.4 REAL-TIME DESIGN
15.5 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 16 SOFTWARE TESTING METHODS
16.1 SOFTWARE TESTING FUNDAMENTALS
16.1.1 Testing Obiectives
16.1.2 Testing Principles
16.1.3 Testability
16.2 TEST CASE DESIGN
16.3 WHITE BOX TESTING
16.4 BASIS PATH TESTING
16.4.1 Flow Graph Notation
16.4.2 Cyclomatic Complexity
16.4.3 Deriving Test Cases
16.4.4 Graph Matrices
16.5 CONTROL STRUCTURE TESTING
16.5.1 Condition Testing
16.5.2 Data Flow Testing
16.5.3 Loop Testing
16.6 BIACK-BOX TESTING
16.6.1 Graph-Based Testing Methods
16.6.2 Equivalence Partitioning
16.6.3 Boundary Value Analysis
16.6.4 Comparison Testing
16.7 TESTING FOR SPECIALIZED ENVIRONMENTS
16.7.1 TestingGUls
16.7.2 Testing of Client/Server Architectures
16.7.3 Testing Documentation and Help Facilities
16.7.4 Testing fof Real-Time Systems
16.8 SUMMARY
REFERENCES .
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 17 SOFTWARE TESTING STRATEGIES
17.1 A STRATEGIC APPROACH -TO SOFTWARE TESTING
17.1.1 Verification and Validation
17.1.2 Organizing for Software Testing
17.1.3 A Soflware Testing Strategy
17.1.4 Criteria for Completion or Testing
17.2 STRATEGIC ISSUES
17.3 UNITTESTING
17.3.1 Unit Test Considerations
17.3.2 Unit Test Procedures
17.4 INTEGRATLON TESTING
17.4.1 Top-Down Integration
17.4.2 Bottom-Up Integration
17.4.3 Regression Testing
17.4.4 Comments on Integration Testing
17.4.5 Integration Test Documentation
17.5 VALIDATION TESTING
17.5.1 Validation Test Criteria
17.5.2 Configuration Review
17.5.3 Alpha and Beta Testing
17.6 SYSTEM TESTING
17.6.1 Recovery Testing
17.6.2 Securily Testing
17.6.3 StressTesting
17.6.4 Performance Testing
17.7 THE ARTOF DEBUGGING
17.7.1 The Debugging Process
17.7.2 Psychological Considerations
17.7.3 Debugging Approaches
17.8 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 18 TECHNICAL METRICS FOR SOFTWARE
18.1 SOFTWARE QUAUTY
18.1.1 McCall's Qualily Factors
18.1.2 FURPS
18.1.3 The Transition to a Quantitative View
18.2 A FRAMEWORK FOR TECHNICAL SOFTWARE METRICS
18.2.1 The Challenge of Technical Metrics
18.2.2 Measurement Principles
18.2.3 The Attributes of Effective Software Metrics
18.3 METRICS FOR THE ANALYSIS MODEl
18.3.1 Function-Based Metrics
18.3.2 The Bang Metric
18.3.3 Metrics for Specification Quality
18.4 METRICS FOR THE DESIGN MODEL
18.4.1 Highlevel Design Metrics
18.4.2 Component level Design Metrics
18.4.3 Interface Design Metrics
18.5 METRICS FOR SOURCE CODE
18.6 METRICS FOR TESTING
18.7 METRICS FOR MAINTENANCE
18.8 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
PART POUR OBJECT-ORIENTED SOFTWARE ENOINEERINO
CHAPTER 19 OBJECT-ORIENTED CONCEPTS AND PRINCIPLES
19.1 THE OBJECTORIENTED PARADIGM
19.2 OBJECTORIENTED CONCEPTS
19.2.1 Classes and Objects
19.2.2 Attributes
19.2.3 Operations, Methods and Services
19.2.4 Messages
19.2.5 Encapsuhtion, Inheritance, and Polymorphism
19.3 IDENTIFYING THE ELEMENTS OF AN OBJECT MODEL
19.3.1 Identifying Classes and Objects
19.3.2 Specifying Attributes
19.3.3 Defining Operations
19.3.4 Finalizing the ObIect Definition
19.4 MANAGEMENT OF OBJECT-ORIENTED SOFTWARE PROJECTS
19.4.1 The Common Process Framework for 00
19.4.2 ObjeclOriented Project Metrics and Estimation
19.4.3 An 00 Estimoting and Scheduling Approach
19.4.4 Progress for an ObjectOriented Proiect
19.5 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 20 OBJECT-ORIENTED ANALYSIS
20.1 OBIECTORIENTED ANALYSIS
20.1.1 Conventional vs. 00 Approaches
20.1.2 The OOA Landscape
20.2 DOMAIN ANALYSIS
20.2.1 Reuse and Domain Analysis
20.2.2 The Domain Analysis Process
20.3 GENERIC COMPONENTS OF THE 00 ANALYSIS MODEL
20.4 THE OOA PROCESS
20.4.1 UseCases
20.4.2 Class-Responsibility-CollaboratorModeling
20.4.3 Defining Structures and Hierarchies
20.4.4 Defining Subjects and Subsystems
20.5 THE OBJECT-REIATIONSHIP MODEL
20.6 THE OBJECT-BEHAVIOR MODEL
20.6.1 Event Identification with Use Cases
20.6.2 State Representations
20.7 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 21 OBJECT-ORIENTEDDESIGN
21.1 DESIGN FOR OBJECT-ORIENTED SYSTEMS
21.1.1 Conventional vs. 00 Approoches
21.1.2 Design Issues
21.1.3 The OOD Landscape
21.2 THE GENERIC COMPONENTS OF THE 00 DESIGN MODEL
21.3 THE SYSTEM DESIGN PROCESS
21.3.1 Partitioning the Analysis Model
21.3.2 Concurrency and Subsystem Allocation
21.3.3 The Task Management Component
21.3.4 The Data Management Component
21.3.5 The Resource Management Component
21.3.6 The Human-Computer Interface Component
21.3.7 Inter-Subsystem Communication
21.4 THE OBJECT DESIGN PROCESS
21.4.1 ObjectDescriptions
21.4.2 Designing Algorithms and Data Structures
21.4.3 Program Components and Interfaces
21.5 DESIGN PATTERNS
21.5.1 Describing a Design Pattern
21.5.2 Using Patterns in Design
21.6 OBJECt-ORIENTEDPROGRAMMING
21.7 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 22 OBJECT-ORIENTED TESTING
22.1 BROADENING THE VIEW OF TESTING
22.2 TESTING OOA AND OOD MODELS
22.2.1 Correctness of OOA and OOD Models
22.2.2 Consistency of OOA and OOD Models
22.3 OBJECTORIENTED TESTING STRATEGIES
22.3.1 Unit Testing in the 00 Context
22.3.2 Infegration Testing in the 00 Context
22.3.3 Validation Testing in an 00 Context
22.4 TEST CASE DESIGN FOR 00 SOFTWARE
22.4.1 The Test Case Design Implications of 00 Concepts
22.4.2 Applicability of Conventional Test Case Design Methods
22.4.3 Fault-Based Testing
22.4.4 The Impact of 00 Programming on Testing
22.4.5 Test Cases and the Class Hierarchy
22.4.6 Scenario-Based Test Design
22.4.7 Testing Surface Structure and Deep Structure
22.5 TESTING METHODS APPLICABLE AT THE CIASS LEVEL
22.5.1 Random Testing for 00 Classes
22.5.2 Partition Testing at the Class Level
22.6 INTERCIASS TEST CASE DESIGN
22.6.1 Multiple Class Testing
22.6.2 Tests Derived from Behavior Models
22.7 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 23 TECHNICAL METRICS FOR OBJECT-ORIENTED SYSTEMS
23.1 THE INTENT OF OBJECTORIENTED METRICS
23.2 THE DISTINGUISHING CHARACTERISTICS
23.2.1 Localization
23.2.2 Encapsulation
23.2.3 Information hiding
23.2.4 Inheritance
23.2.5 Abstraction
23.3 METRICS FOR THE 00 DESIGN MODEL
23.4 CLASS-ORIENTED METRICS
23.4.1 The CK Metrics Suite
23.4.2 Metrics Proposed by Lorenz and Kidd
23.5 OPERATION-ORIENTED METRICS
23.6 METRICS FOR OBJECT-ORIENTED TESTING
23.7 METRICS FOR OBJECTORIENTED PROJECTS
23.8 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 24 FORMAL METHODS
24.1 BASIC CONCEPTS
24.1.1 Deficiencies of Less Formal Approaches
24.1.2 Mathematics in Soflware Development
24.1.3 Formal Methods Concepts
24.2 MATHEMATICAl PRELIMINARIES
24.2.1 Sets and Constructive Specification
24.2.2 Set.Operators
24.2.3 Logic Operators
24.3 APPLYING MATHEMATICAl NOTATION FOR FORMAL SPECIFICATION
24.4 FORMAL SPECIFICATION LANGUAGES
24.5 USING Z TO REPRESENT AN EXAMPLE SOFTWARE COMPONENT
24.6 THE TEN COMMANDMENTS OF FORMAL METHODS
24.7 FORMAL METHODS-THE ROAD AHEAD
24.8 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 25 CLEANROOM SOFTWARE ENGINEERING
25.1 THE CLEANROOM APPROACH
25.1.1 The Cleanroom Strategy
25.1.2 What Makes Cleanroom Different?
25.2 FUNCTIONAL SPECIFICATION
25.2.1 Black-Box Specification
25.2.2 State-Box Specification
25.2.3 Clear-Box Specification
25.3 DESIGN REFINEMENT AND VERIFICATION
25.3.1 Design Refinement and Verification
25.3.2 Advantages of Design Verification
25.4 CLEANROOM TESTING
25.4.1 Statistical Use Testing
25.4.2 Gertificotion
25.5 SUMMARY .
REFERENCES
PROBIEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 26 SOFTWARE REUSE
26.1 MANAGEMENT ISSUES
26.1.1 Roadblocks to Reuse
26.1.2 A Hardware Analogy
26.1.3 Some Suggestions for Establishing an Approach to Reuse
26.2 THE REUSE PROCESS
26.2.1 Reusable Artifacts
26.2.2 A Process Model
26.3 DOMAIN ENGINEERING
26.3.1 The Domain Analysis Process
26.3.2 Characterization Functions
26.3.3 Structural Modeling and Structure Points
26.4 BUILDING REUSABLE COMPONENTS
26.4.1 Analysis and Design for Reuse
26.4.2 Construction Methods
26.4.3 Component-Based Development
26.5 CIASSIFYING AND RETRIEVING COMPONENTS
26.5.1 Describing Reusable Components
26.5.2 The Reuse Environment
26.6 ECONOMICS OF SOFTWARE REUSE
26.6.1 Impact on Quality, Productivity and Cost
26.6.2 Cost Analysis Using Structure Points
26.6.3 Reuse Metrics
26.7 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 27 REENGINEERING
27.1 BUSINESS PROCESS REENGINEERING
27.1.1 Business Processes
27.1.2 Principles of Business Process Reengineering
27.1.3 ABPRModel
27.1.4 Words of Warning
27.2 SOFTWARE REENGINEERING
27.2.1 Software Maintenance
27.2.2 A SoftwareReengineering Process Model
27.3 REVERSE ENGINEERING
27.3.1 Reverse Engineering to Understand Processing
27.3.2 Reverse Engineering to Understand Data
27.3.3 Reverse Engineering User Interfaces
27.4 RESTRUCTURING
27.4.1 Code Restructuring
27.4.2 Data Restructuring
27.5 FORWARD ENGINEERING
27.5.1 Forward Engineering for Client/Server Architectures
27.5.2 Forward Engineering for Object-Oriented Architectures
27.5.3 Forward Engineering User Interfaces
27.6 THE ECONOMICS OF REENGINEERING
27.7 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 28 CLlENT/SERVER SOFTWARE ENGlNEERlNG
28.l THE STRUCTURE OF CLlENT/SERVER SYSTEMS
28.l.l Soflware Components for C/S Systems
28.l.2 The Distribution of Software Components
28.l.3 Guidelines for Distributing Application Components
28.l.4 linking C/S Software Components
28.l.5 Middfeware and Obiect Request Broker
28.2 SOFTWARE ENGlNEERlNG FOR C/S SYSTEMS
28.3 ANALYSlS MODEUNG iSSUES
28.4 DESlGN FOR C/S SYSTEMS
28.4. l Conventional Design Approaches
28.4.2 Databose Design
28.4.3 An Overview of a Design Approach
28.4.4 Process Design iteration
28.5 TESTlNG iSSUES
28.5.1 Overall C/S Testing Strategy
28.5.2 C/S Testing Tactics
28.6 SUMMARY
REFERENCES
PROBLEMS AND POlNTS TO PONDER
FURTHER READlNGS AND OTHER INFORMATlON SOURCES
CHAPTER 29 COMPUTER-AlDED SOFTWARE ENGlNEERlNG
29.1 WHATlSCASE?
29.2 BUlLDlNG BLOCKS FOR CASE
29.3 A TAXONOMY OF CASE TOOLS
29.4 INTEGRATED CASE ENVlRONMENTS
29.5 THE INTEGRATlON ARCHlTECTURE
29.6 THE CASE REPOSlTORY
29.6.l The Roe of the Repository in l-CASE
29.6.2 Features and Content
29.7 SUMMARY
REFERENCES
PROBlEMS AND POlNTS TO PONDER
FURTHER READlNGS AND OTHER INFORMATlON SOURCES
CHAPTER 30 THE ROAD AHEAD
30.1 THE IMPORTANCE OF SOFTWARE-REVlSlTED
30.2 THE SCOPE OF CHANGE
30.3 PEOPLE AND THE WAY THEY BUlLD SYSTEMS
30.4 THE "NEW" SOFTWARE PROCESS
30.5 NEW MODES FOR REPRESENTlNG INFORMATlON
30.6 TECHNOLOGY AS A DRlVER
30.7 A CONCLUDlNG COMMENT
REFERENCES
PROBLEMS AND POlNTS TO PONDER
FURTHER READlNGS AND OTHER INFORMATlON SOURCES
· · · · · · (收起)
PREFACE
PART ONE THE PRODUCT AND THI PROCESS
CHAPTER 1 THE PRODUCT
CHAPTER 2 THE PROCESS
PART TWO MANAOINO SOFTWARE PROJECTS
CHAPTER 3 PROJECT MANAGEMENT CONCEPTS
CHAPTER 4 SOFTWARE PROCESS AND PROJECT METRICS
CHAPTER 5 SOFTWARE PROJECT PIANNING
CHAPTER 6 RISK MANAGEMENT
CHAPTER 7 PROJECT SCHEDULING AND TRACKING
CHAFTER 8 SOFTWARE QUALITY ASSURANCE
CHAPTER 9 SOFTWARE CONFIGURATION MANAGEMENT
PART THREE CONVENTIONAL METHODS FOR SOFTWARE ENGINEEMNG
CHAPTER 10 SYSTEM ENGINEERING
CHAPTER 11 ANALYSIS CONCEPTS AND PRINCIPLES
CHAPTER12 ANALYSIS MODELING
CHAPTER 13 DESIGN CONCEPTS AND PRINCIPLES
CHAPTER 14 DESlGN METHODS
CHAPTER 15 DESlGN FOR REAL-TlME SYSTEMS
CHAPTER 16 SOFTWARE TESTlNG TECHNlQUES
CHAPTER 17 SOFTWARE TESTlNG STRATEGlES
CHAPTER l 8 TECHNlCAL METRlCS FOR SOFTWARE
PART FOUR OBJECT-ORlENTED SOFTWARE ENOlNEERlNG
CHAPTER l 9 OBJECT-ORlENTED CONCEPTS AND PRlNClPLES
CHAPTER 20 OBjECTORlENTED ANALYSlS
CHAPTER 21 OBJECT-ORlENTED DESlGN
CHAPTER 22 OBJECT-ORlENTED TESTlNG
CHAPTER 23 TECHNlCAL METRlCS FOR OBJECTORlENTED SYSTEMS
PART FlVE ADVANCED TOPICS IN SOFTWARE ENGlNEERlNG
CHAPTER 24 FORMAL METHODS
CHAPTER 25 CLEANROOM SOFTWARE ENGlNEERlNG
CHAPTER 26 SOFTWARE REUSE
CHAPTER 27 REENGlNEERlNG
CHAPTER 28 CLlENT/SERVER SOFTWARE ENGlNEERlNG
CHAPTER 29 COMPUTER-AlDED SOFTWARE ENGlNEERlNG
CHAPTER 30 THE ROAD AHEAD
TABLE OF CONTENTS
PREFACE
PART ONE THE PRODUCT AND THE PROCESS
CHAPTER 1 THE PRODUCT
1.1 THE EVOLVING ROLE OF SOFTWARE
1.1.1 An Industry Perspective
1.1.2 An Aging Software Plant
1.1.3 Soflware Competitiveness
1.2 SOFTWARE
1.2.1 Software Characteristics
1.2.2 Soflware Components
1.2.3 Software Applications
1.3 SOFTWARE: A CRISIS ON THE HORIZON
1.4 SOFTWARE MYTHS
1.5 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND INFORMATION SOURCES
CHAPTER 2 THE PROCESS
2.1 SOFTWARE ENGINEERING-A lAYERED TECHNOLOGY
2.1.1 Process, Methods, and Tools
2.1.2 A Generic View of Software Engineering
2.2 THE SOFTWARE PROCESS
2.3 SOFTWARE PROCESS MODELS
2.4 THE LINEAR SEQUENTIAL MODEL
2.5 THE PROTOTYPING MODEL
2.6 THERADMODEL
2.7 EVOLUTIONARY SOFTWARE PROCESS MODELS
2.7.1 The Incremental Model
2.7.2 The Spiral Model
2.7.3 The Component Assembly Model
2.7.4 The Concurrent Development Model
2.8 THE FORMAl METHODS MODEL
2.9 FOURTH GENERATION TECHNIQUES
2.10 PROCESS TECHNOLOGY
2.11 PRODUCT AND PROCESS
2.12SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
PART TWO MANAGING SOFTWARE PROJECTS
CHAPTER 3 PROJECT MANAGEMENT CONCEPTS
3.1 THE MANAGEMENT SPECTRUM
3.1.1 People
3.1.2 TheProblem
3.1.3 TheProcess
3.2 PEOPLE
3.2.1 ThePlayers
3.2.2 Team leaders
3.2.3 The Software Team
3.2.4 Coordination and Communication Issues
3.3 THEPROBLEM
3.3.1 Soflware Scope
3.3.2 Problem Decomposition
3.4 THEPROCESS
3.4.1 Melding the Problem and the Process
3.4.2 Process Decomposition
3.5 THEPRQIECT
3.6 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 4 SOFTWARE PROCESS AND PROJECT METRICS
4.1 MEASURES, METRICS, AND INDICATORS
4.2 METRICS IN THE PROCESS AND PROJECT DOMAINS
4.2.1 Process Metrics and Software Process Improvement
4.2.2 Proiect Metrics
4.3 SOFTWARE MEASUREMENT
4.3.1 SizeOriented Metrics
4.3.2 Function-Oriented Metrics
4.3.3 Extended Function Point Metrics
4.4 RECONCILING DIFFERENT METRICS APPROACHES
4.5 METRICS FOR SOFTWARE QUALITY
4.5.1 An Overview of Factors That Affect Quality
4.5.2 Measuring Quality
4.5.3 Defect Removal Efficiency
4.6 INTEGRATING METRICS WITHIN THE SOFTWARE PROCESS
4.7 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 5 SOFTWARE PROJECT PIANNING
5.1 OBSERVATIONS ON ESTIMATING
5.2 PROJECT PIANNING OBJECTIVES
5.3 SOFTWARE SCOPE
5.3.1 Obtaining Information Necessary for Scope
5.3.2 A Scoping Example
5.4 RESOURCES
5.4.1 Human Resources
5.4.2 Reusable Software Resources
5.4.3 Environmental Resources
5.5 SOFTWARE PROJECT ESTIMATION
5.6 DECOMPOSITION TECHNIQUES
5.6.1 Soflware Sizing
5.6.2 Problem-Based Estimation
5.6.3 An Example of LOC-Based Esftmation
5.6.4 An Example of FP-Based Estimation
5.6.5 Process-Based Estimation
5.6.6 An Example of Process-Based Estimation
5.7 EMPIRICAL ESTIMATION MODELS
5.7.1 The Structure of Estimation Models
5.7.2 The COCOMO Model
5.7.3 The Soflware Equation
5.8 THE MAKE-BUY DECISION
5.8.1 Creating a Decision Tree
5.8.2 Outsourcing
5.9 AUTOMATED ESTIMATION TOOLS
5.10SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINQS AND OTHER INFORMATION SOURCES
CHAPTER 6 RISK MANAGEMENT
6.1 REACTIVE VS. PROACTIVE RISK STRATEGIES
6.2 SOFTWARE RISKS
6.3 RISK IDENTIFICATION
6.3.1 Product Size Risks
6.3.2 Business Impoct Risks
6.3.3 Customer-Related Risks
6.3.4 Process Risks
6.3.5 Technology Risk
6.3.6 Development Environment Risks
6.3.7 Risks Associated with Staff Size and Experience
6.3.8 Risk Components and Drivers
6.4 RISK PROJECTION
6.4.1 Developing a Risk Table
6.4.2 Assessing Risk Impact
6.4.3 Risk Assessment
6.5 RISK MITIGATION, MONITORING, AND MANAGEMENT
6.6 SAFETY RISKS AND HAZARDS
6.7 THERMMMPIAN
6.8 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 7 PROJECT SCHEDULING AND TRACKING
7.1 BASIC CONCEPTS
7.1.1 Comments on "Lateness'
7.1.2 Basic Principles
7.2 THE REIATIONSHIP BETWEEN PEOPLE AND EFFORT
7.2.1 An Example
7.2.2 An Empirical Relationship
7.2.3 Effort Distribufion
7.3 DEFINING A TASK SET FOR THE SOFTWARE PROJECT
7.3.1 OegreeofRigor
7.3.2 Defining Adaptation Criteria
7.3.3 Computing a Task Set Selector Value
7.3.4 Interpreting the TSS Value and Selecting the Task Set
7.4 SELECTING SOFTWARE ENGINEERING TASKS
7.5 REFINEMENT OF MAJOR TASKS
7.6 DEFINING A TASK NETWORK
7.7 SCHEDULING
7.7.1 Timeline Charts
7.7.2 Tracking the Schedule
7.8 THE PROJECT PIAN
7.9 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 8 SOFTWARE QUALrTY ASSURANCE
8.1 QUAUTY CONCEPTS
8.1.1 Qualily
8.1.2 Qualily Control
8.1.3 Qualily Assurance
8.1.4 Cost of Quality
8.2 THE QUALITY MOVEMENT
8.3 SOFTWARE QUAUTY ASSURANCE
8.3.1 Background Issues
8.3.2 SQAActivities
8.4 SOFTWARE REVIEWS
8.4.1 Cost Impact of Software Defects
8.4.2 Defect Amplification and Removal
8.5 FORMAL TECHNICAL REVIEWS
8.5.1 The Review Meeting
8.5.2 Review Reporting and Record Keeping
8.5.3 Review Guidelines
8.6 FORMAL APPROACHES TO SQA
8.7 STATISTICAL QUALITY ASSURANCE
8.8 SOFTWARE REUABILITY
8.8.1 Measures of Reliabilily and Availabilify
8.8.2 Soflware Safely and Hazard Analysis
8.9 THESQAPlAN
8.10 THE ISO 9000 QUALITY STANDARDS
8.10.1 The ISO Approach to Qualily Assurance Systems
8.10.2 The ISO 9001 Standard
8.11 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 9 SOFTWARE CONFIGURATION MANAGEMENT
9.1 . SOFTWARE CONFIGURATION MANAGEMENT
9.1.1 Baselines
9.1.2 Software Configuration Items
9.2 THE SCM PROCESS
9.3 IDENTIFICATION OF OBJECTS IN THE SOFTWARE CONFIGURATION
9.4 VERSION CONTROL
9.5 CHANGE CONTROL
9.6 CONFIGURATION AUDIT
9.7 STATUS REPORTING
9.8 SCMSTANDARDS
9.9 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
PART THREE CONVINTiONAL METHOOS FOR SOnWARE JNOINHRINO
CHAPTER 10 SYSTEM ENGNEERING
10.1 COMPUTER-BASED SYSTEMS
10.2 THE SYSTEM ENGINEERING HIERARCHY
10.2.1 System Modeling
10.2.2 Information Engineering: An Overview
10.2.3 Product Engineering: An Overview
10.3 INFORMATION ENGINEERING
10.4 INFORMATION STRATEGY PIANNING
10.4.1 Enterprise Modeling
10.4.2 Business-level Dala Modeling
10.5 BUSINESS AREA ANALYSIS
10.5.1 Process Modeling
10.5.2 Information Flow Modeling
10.6 PRODUCT ENGINEERING
10.6.1 System Analysis
10.6.2 Identification of Need
10.6.3 Feasibility Study
10.6.4 EconomicAnalysis
10.6.5 Technical Analysis
10.7 MODELNNG THE SYSTEM ARCHITECTURE
10.8 SYSTEM MODEUNG AND SIMUIATION
10.9 SYSTEM SPECIFICATION
10.10SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 11 ANALYSIS CONCEPTS AND PRINCIPLES
11.1 REQUIREMENTS ANALYSIS
11.2 COMMUNICATION TECHNIQUES
11.2.1 Initiating the Process
11.2.2 Facilitaled Application Specification Techniques
11.2.3 Qualily Function Deployment
11.3 ANALYSIS PRINCIPLES
11.3.1 The Information Domain
11.3.2 Modeling
11.3.3 Partitioning
11.3.4 Essential and Implementation Views
11.4 SOFTWARE PROTOTYPING
11.4.1 Selecting the Protolyping Approach
11.4.2 Protolyping Methods and Tools
11.5 SPECIFICATION
11.5.1 Specification Principles
11.5.2 Representation
11.5.3 The Software Requirements Specification
11.6 SPECIFICATION REVIEW
11.7 SUMMARY
REFERENCES
PROBIEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 12 ANALYSIS MODELING
12.1 A BRIEF HISTORY
12.2 THE ELEMENTS OF THE ANALYSIS MODEL
12.3 DATAMODELING
12.3.1 Data Objects, Altributes, and Relationships
12.3.2 Cardinalityand Modality
12.3.3 Entily-RelalionshipDiagrams
12.4 FUNCTIONAl MODELING AND INFORMATION FLOW
12.4.1 Data Flow Diagrams
12.4.2 Extensions for Real-Time Syslems
12.4.3 Ward and Mellor Extensions
12.4.4 Hatley and Pirbhai Extensions
12.5 BEHAVIORAL MODEUNG
12.6 THE MECHANICS OF STRUCTURED ANAIYSIS
12.6.1 Creating an Entily-RelationshipDiagram
12.6.2 Creating a Data Flow Model
12.6.3 Creating a Control Flow Model
12.6.4 The Control Specification
12.6.5 The Process Specification
12.7 THE DATA DICTIONARY
12.8 AN OVERVIEW OF OTHER CIASSICAL ANALYSIS METHODS
12.8.1 Data Structured Systems Development
12.8.2 Jackson System Development
12.8.3 SADT
12.9 SUMMARY
REFERENCES
PROBIEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 13 DESIGN CONCEPTS AND PRINCIPLES
13.1 SOFTWARE DESIGN AND SOFTWARE ENGINEERING
13.2 THE DESIGN PROCESS
13.2.1 Design dnd Software Qualily
13.2.2 The Evolution of Soflware Design
13.3 DESIGN PRINCIPLES
13.4 DESIGN CONCEPTS
13.4.1 Abstraction
13.4.2 Refinement
13.4.3 Modularily
13.4.4 Soflware Architectre
13.4.5 Control Hierarchy
13.4.6 Structural Partitioning
13.4.7 Data Structure
13.4.8 Software Procedure
13.4.9 Information Hiding
13.5 EFFECTIVE MODUIAR DESIGN
13.5.1 Functional Independence
13.5.2 Cohesion
13.5.3 Coupling
13.6 DESIGN HEURISTICS FOR EFFECTIVE MODULARITY
13.7 THE DESIGN MODEL
13.8 DESIGN DOCUMENTATION
13.9 SUMMARY
REFERENCES
PROBtEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 14 DESIGN METHODS
14.1 DATADESIGN
14.2 ARCHITECTURAL DESIGN
14.2.1 Contributors
14.2.2 Areas of Application
14.3 THE ARCHITECTURAL DESIGN PROCESS
14.3.1 Transform Flow
14.3.2 Transaction Flow
14.4 TRANSFORM MAPPING
14.4.1 An Example
14.4.2 Design Steps
14.5 TRANSACTION MAPPING
14.5.1 An Example
14.5.2 DesignSteps
14.6 DESIGN POSTPROCESSING
14.7 ARCHITECTURAL DESIGN OPTIMIZATION
14.8 INTERFACE DESIGN
14.8.1 Intemal and External Interface Design
14.8.2 User Interface Design
14.9 HUMAN-COMPUTER INTERFACE DESIGN
14.9.1 Interface Design Models
14.9.2 Task Analysis and Modeling
14.9.3 Design Issues
14.9.4 Implementation Tools
14.9.5 Design Evaluation
14.10 INTERFACE DESIGN GUIDELINES
14.10.1 General Interaction
14.10.2 Information Display
14.10.3 Datalnput
14.11 PROCEDURAL DESIGN
14.11.1 Structured Programming
14.11.2 Graphical Design Notation
14.11.3 Tabular Design Notation
14.11.4 Program Design Language
14.11.5 APDLExample
14.12 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 15 DESIGN FOR REAl-TIME SYSTEMS
15.1 SYSTEM CONSIDERATIONS
15.2 REAL-TIME SYSTEMS
15.2.1 Integration and Performance Issues
15.2.2 Interrupt Handling
15.2.3 Real-Time Data Bases
15.2.4. Real-Time Operating Systems
15.2.5 Real-Time Languages
15.2.6 Task Synchromzation and Communication
15.3 ANALYSIS AND SIMUIATION OF REAL-TIME SYSTEMS
15.3.1 Mathematical Tools for Real-Time System Analysis
15.3.2 Simulation and Modeling Techniques
15.4 REAL-TIME DESIGN
15.5 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 16 SOFTWARE TESTING METHODS
16.1 SOFTWARE TESTING FUNDAMENTALS
16.1.1 Testing Obiectives
16.1.2 Testing Principles
16.1.3 Testability
16.2 TEST CASE DESIGN
16.3 WHITE BOX TESTING
16.4 BASIS PATH TESTING
16.4.1 Flow Graph Notation
16.4.2 Cyclomatic Complexity
16.4.3 Deriving Test Cases
16.4.4 Graph Matrices
16.5 CONTROL STRUCTURE TESTING
16.5.1 Condition Testing
16.5.2 Data Flow Testing
16.5.3 Loop Testing
16.6 BIACK-BOX TESTING
16.6.1 Graph-Based Testing Methods
16.6.2 Equivalence Partitioning
16.6.3 Boundary Value Analysis
16.6.4 Comparison Testing
16.7 TESTING FOR SPECIALIZED ENVIRONMENTS
16.7.1 TestingGUls
16.7.2 Testing of Client/Server Architectures
16.7.3 Testing Documentation and Help Facilities
16.7.4 Testing fof Real-Time Systems
16.8 SUMMARY
REFERENCES .
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 17 SOFTWARE TESTING STRATEGIES
17.1 A STRATEGIC APPROACH -TO SOFTWARE TESTING
17.1.1 Verification and Validation
17.1.2 Organizing for Software Testing
17.1.3 A Soflware Testing Strategy
17.1.4 Criteria for Completion or Testing
17.2 STRATEGIC ISSUES
17.3 UNITTESTING
17.3.1 Unit Test Considerations
17.3.2 Unit Test Procedures
17.4 INTEGRATLON TESTING
17.4.1 Top-Down Integration
17.4.2 Bottom-Up Integration
17.4.3 Regression Testing
17.4.4 Comments on Integration Testing
17.4.5 Integration Test Documentation
17.5 VALIDATION TESTING
17.5.1 Validation Test Criteria
17.5.2 Configuration Review
17.5.3 Alpha and Beta Testing
17.6 SYSTEM TESTING
17.6.1 Recovery Testing
17.6.2 Securily Testing
17.6.3 StressTesting
17.6.4 Performance Testing
17.7 THE ARTOF DEBUGGING
17.7.1 The Debugging Process
17.7.2 Psychological Considerations
17.7.3 Debugging Approaches
17.8 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 18 TECHNICAL METRICS FOR SOFTWARE
18.1 SOFTWARE QUAUTY
18.1.1 McCall's Qualily Factors
18.1.2 FURPS
18.1.3 The Transition to a Quantitative View
18.2 A FRAMEWORK FOR TECHNICAL SOFTWARE METRICS
18.2.1 The Challenge of Technical Metrics
18.2.2 Measurement Principles
18.2.3 The Attributes of Effective Software Metrics
18.3 METRICS FOR THE ANALYSIS MODEl
18.3.1 Function-Based Metrics
18.3.2 The Bang Metric
18.3.3 Metrics for Specification Quality
18.4 METRICS FOR THE DESIGN MODEL
18.4.1 Highlevel Design Metrics
18.4.2 Component level Design Metrics
18.4.3 Interface Design Metrics
18.5 METRICS FOR SOURCE CODE
18.6 METRICS FOR TESTING
18.7 METRICS FOR MAINTENANCE
18.8 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
PART POUR OBJECT-ORIENTED SOFTWARE ENOINEERINO
CHAPTER 19 OBJECT-ORIENTED CONCEPTS AND PRINCIPLES
19.1 THE OBJECTORIENTED PARADIGM
19.2 OBJECTORIENTED CONCEPTS
19.2.1 Classes and Objects
19.2.2 Attributes
19.2.3 Operations, Methods and Services
19.2.4 Messages
19.2.5 Encapsuhtion, Inheritance, and Polymorphism
19.3 IDENTIFYING THE ELEMENTS OF AN OBJECT MODEL
19.3.1 Identifying Classes and Objects
19.3.2 Specifying Attributes
19.3.3 Defining Operations
19.3.4 Finalizing the ObIect Definition
19.4 MANAGEMENT OF OBJECT-ORIENTED SOFTWARE PROJECTS
19.4.1 The Common Process Framework for 00
19.4.2 ObjeclOriented Project Metrics and Estimation
19.4.3 An 00 Estimoting and Scheduling Approach
19.4.4 Progress for an ObjectOriented Proiect
19.5 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 20 OBJECT-ORIENTED ANALYSIS
20.1 OBIECTORIENTED ANALYSIS
20.1.1 Conventional vs. 00 Approaches
20.1.2 The OOA Landscape
20.2 DOMAIN ANALYSIS
20.2.1 Reuse and Domain Analysis
20.2.2 The Domain Analysis Process
20.3 GENERIC COMPONENTS OF THE 00 ANALYSIS MODEL
20.4 THE OOA PROCESS
20.4.1 UseCases
20.4.2 Class-Responsibility-CollaboratorModeling
20.4.3 Defining Structures and Hierarchies
20.4.4 Defining Subjects and Subsystems
20.5 THE OBJECT-REIATIONSHIP MODEL
20.6 THE OBJECT-BEHAVIOR MODEL
20.6.1 Event Identification with Use Cases
20.6.2 State Representations
20.7 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 21 OBJECT-ORIENTEDDESIGN
21.1 DESIGN FOR OBJECT-ORIENTED SYSTEMS
21.1.1 Conventional vs. 00 Approoches
21.1.2 Design Issues
21.1.3 The OOD Landscape
21.2 THE GENERIC COMPONENTS OF THE 00 DESIGN MODEL
21.3 THE SYSTEM DESIGN PROCESS
21.3.1 Partitioning the Analysis Model
21.3.2 Concurrency and Subsystem Allocation
21.3.3 The Task Management Component
21.3.4 The Data Management Component
21.3.5 The Resource Management Component
21.3.6 The Human-Computer Interface Component
21.3.7 Inter-Subsystem Communication
21.4 THE OBJECT DESIGN PROCESS
21.4.1 ObjectDescriptions
21.4.2 Designing Algorithms and Data Structures
21.4.3 Program Components and Interfaces
21.5 DESIGN PATTERNS
21.5.1 Describing a Design Pattern
21.5.2 Using Patterns in Design
21.6 OBJECt-ORIENTEDPROGRAMMING
21.7 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 22 OBJECT-ORIENTED TESTING
22.1 BROADENING THE VIEW OF TESTING
22.2 TESTING OOA AND OOD MODELS
22.2.1 Correctness of OOA and OOD Models
22.2.2 Consistency of OOA and OOD Models
22.3 OBJECTORIENTED TESTING STRATEGIES
22.3.1 Unit Testing in the 00 Context
22.3.2 Infegration Testing in the 00 Context
22.3.3 Validation Testing in an 00 Context
22.4 TEST CASE DESIGN FOR 00 SOFTWARE
22.4.1 The Test Case Design Implications of 00 Concepts
22.4.2 Applicability of Conventional Test Case Design Methods
22.4.3 Fault-Based Testing
22.4.4 The Impact of 00 Programming on Testing
22.4.5 Test Cases and the Class Hierarchy
22.4.6 Scenario-Based Test Design
22.4.7 Testing Surface Structure and Deep Structure
22.5 TESTING METHODS APPLICABLE AT THE CIASS LEVEL
22.5.1 Random Testing for 00 Classes
22.5.2 Partition Testing at the Class Level
22.6 INTERCIASS TEST CASE DESIGN
22.6.1 Multiple Class Testing
22.6.2 Tests Derived from Behavior Models
22.7 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 23 TECHNICAL METRICS FOR OBJECT-ORIENTED SYSTEMS
23.1 THE INTENT OF OBJECTORIENTED METRICS
23.2 THE DISTINGUISHING CHARACTERISTICS
23.2.1 Localization
23.2.2 Encapsulation
23.2.3 Information hiding
23.2.4 Inheritance
23.2.5 Abstraction
23.3 METRICS FOR THE 00 DESIGN MODEL
23.4 CLASS-ORIENTED METRICS
23.4.1 The CK Metrics Suite
23.4.2 Metrics Proposed by Lorenz and Kidd
23.5 OPERATION-ORIENTED METRICS
23.6 METRICS FOR OBJECT-ORIENTED TESTING
23.7 METRICS FOR OBJECTORIENTED PROJECTS
23.8 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 24 FORMAL METHODS
24.1 BASIC CONCEPTS
24.1.1 Deficiencies of Less Formal Approaches
24.1.2 Mathematics in Soflware Development
24.1.3 Formal Methods Concepts
24.2 MATHEMATICAl PRELIMINARIES
24.2.1 Sets and Constructive Specification
24.2.2 Set.Operators
24.2.3 Logic Operators
24.3 APPLYING MATHEMATICAl NOTATION FOR FORMAL SPECIFICATION
24.4 FORMAL SPECIFICATION LANGUAGES
24.5 USING Z TO REPRESENT AN EXAMPLE SOFTWARE COMPONENT
24.6 THE TEN COMMANDMENTS OF FORMAL METHODS
24.7 FORMAL METHODS-THE ROAD AHEAD
24.8 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 25 CLEANROOM SOFTWARE ENGINEERING
25.1 THE CLEANROOM APPROACH
25.1.1 The Cleanroom Strategy
25.1.2 What Makes Cleanroom Different?
25.2 FUNCTIONAL SPECIFICATION
25.2.1 Black-Box Specification
25.2.2 State-Box Specification
25.2.3 Clear-Box Specification
25.3 DESIGN REFINEMENT AND VERIFICATION
25.3.1 Design Refinement and Verification
25.3.2 Advantages of Design Verification
25.4 CLEANROOM TESTING
25.4.1 Statistical Use Testing
25.4.2 Gertificotion
25.5 SUMMARY .
REFERENCES
PROBIEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 26 SOFTWARE REUSE
26.1 MANAGEMENT ISSUES
26.1.1 Roadblocks to Reuse
26.1.2 A Hardware Analogy
26.1.3 Some Suggestions for Establishing an Approach to Reuse
26.2 THE REUSE PROCESS
26.2.1 Reusable Artifacts
26.2.2 A Process Model
26.3 DOMAIN ENGINEERING
26.3.1 The Domain Analysis Process
26.3.2 Characterization Functions
26.3.3 Structural Modeling and Structure Points
26.4 BUILDING REUSABLE COMPONENTS
26.4.1 Analysis and Design for Reuse
26.4.2 Construction Methods
26.4.3 Component-Based Development
26.5 CIASSIFYING AND RETRIEVING COMPONENTS
26.5.1 Describing Reusable Components
26.5.2 The Reuse Environment
26.6 ECONOMICS OF SOFTWARE REUSE
26.6.1 Impact on Quality, Productivity and Cost
26.6.2 Cost Analysis Using Structure Points
26.6.3 Reuse Metrics
26.7 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 27 REENGINEERING
27.1 BUSINESS PROCESS REENGINEERING
27.1.1 Business Processes
27.1.2 Principles of Business Process Reengineering
27.1.3 ABPRModel
27.1.4 Words of Warning
27.2 SOFTWARE REENGINEERING
27.2.1 Software Maintenance
27.2.2 A SoftwareReengineering Process Model
27.3 REVERSE ENGINEERING
27.3.1 Reverse Engineering to Understand Processing
27.3.2 Reverse Engineering to Understand Data
27.3.3 Reverse Engineering User Interfaces
27.4 RESTRUCTURING
27.4.1 Code Restructuring
27.4.2 Data Restructuring
27.5 FORWARD ENGINEERING
27.5.1 Forward Engineering for Client/Server Architectures
27.5.2 Forward Engineering for Object-Oriented Architectures
27.5.3 Forward Engineering User Interfaces
27.6 THE ECONOMICS OF REENGINEERING
27.7 SUMMARY
REFERENCES
PROBLEMS AND POINTS TO PONDER
FURTHER READINGS AND OTHER INFORMATION SOURCES
CHAPTER 28 CLlENT/SERVER SOFTWARE ENGlNEERlNG
28.l THE STRUCTURE OF CLlENT/SERVER SYSTEMS
28.l.l Soflware Components for C/S Systems
28.l.2 The Distribution of Software Components
28.l.3 Guidelines for Distributing Application Components
28.l.4 linking C/S Software Components
28.l.5 Middfeware and Obiect Request Broker
28.2 SOFTWARE ENGlNEERlNG FOR C/S SYSTEMS
28.3 ANALYSlS MODEUNG iSSUES
28.4 DESlGN FOR C/S SYSTEMS
28.4. l Conventional Design Approaches
28.4.2 Databose Design
28.4.3 An Overview of a Design Approach
28.4.4 Process Design iteration
28.5 TESTlNG iSSUES
28.5.1 Overall C/S Testing Strategy
28.5.2 C/S Testing Tactics
28.6 SUMMARY
REFERENCES
PROBLEMS AND POlNTS TO PONDER
FURTHER READlNGS AND OTHER INFORMATlON SOURCES
CHAPTER 29 COMPUTER-AlDED SOFTWARE ENGlNEERlNG
29.1 WHATlSCASE?
29.2 BUlLDlNG BLOCKS FOR CASE
29.3 A TAXONOMY OF CASE TOOLS
29.4 INTEGRATED CASE ENVlRONMENTS
29.5 THE INTEGRATlON ARCHlTECTURE
29.6 THE CASE REPOSlTORY
29.6.l The Roe of the Repository in l-CASE
29.6.2 Features and Content
29.7 SUMMARY
REFERENCES
PROBlEMS AND POlNTS TO PONDER
FURTHER READlNGS AND OTHER INFORMATlON SOURCES
CHAPTER 30 THE ROAD AHEAD
30.1 THE IMPORTANCE OF SOFTWARE-REVlSlTED
30.2 THE SCOPE OF CHANGE
30.3 PEOPLE AND THE WAY THEY BUlLD SYSTEMS
30.4 THE "NEW" SOFTWARE PROCESS
30.5 NEW MODES FOR REPRESENTlNG INFORMATlON
30.6 TECHNOLOGY AS A DRlVER
30.7 A CONCLUDlNG COMMENT
REFERENCES
PROBLEMS AND POlNTS TO PONDER
FURTHER READlNGS AND OTHER INFORMATlON SOURCES
· · · · · · (收起)
读后感
评分
评分
评分
评分
评分
用户评价
评分
总而言之，这本书为我提供了一个系统化的学习路径，帮助我从一个“码农”逐渐成长为一名真正懂得“工程”思维的软件开发者。它不仅仅传授了技术知识，更重要的是塑造了我的思维方式，让我能够以更宏观、更专业的视角去看待软件开发这门艺术。我感谢作者能够将如此丰富和实用的知识，以如此清晰和易懂的方式呈现出来。这本书的价值，绝对超出了它的价格，它将是我未来软件开发生涯中不可或缺的宝贵财富，我也会强烈推荐给所有正在或者即将踏入软件开发领域的朋友们，它会让你少走很多弯路，并且更早地掌握成功的关键。
评分这本书带来的最直观的改变，是我对“质量”的理解发生了翻天覆地的变化。过去，我可能更关注功能的实现，而对代码的可读性、可测试性、可维护性等“软性”指标有所忽视。然而，这本书让我明白，这些“软性”指标才是决定一个软件能否长期健康发展的关键。作者在“软件测试”章节的讲解，让我看到了测试的真正意义，它不仅仅是找出bug，更是对软件设计和实现的系统性验证。他对不同测试方法（单元测试、集成测试、系统测试等）的详细介绍，以及如何构建有效的测试用例，都让我受益匪浅。我开始将测试视为开发过程中不可或缺的一部分，并且意识到，越早发现问题，修复成本就越低。这种“质量前置”的理念，正在潜移默化地改变我的开发习惯。
评分阅读这本书的过程，更像是在进行一场思想的深度对话。作者的笔触并非冰冷的学术论述，而是饱含着对软件行业发展的深刻洞察和对开发者实践经验的提炼。他不仅仅是在介绍“是什么”，更是在探讨“为什么”以及“如何做”。我尤其欣赏他在介绍软件开发生命周期各个阶段时，那种循序渐进的逻辑，从需求分析的精细到设计的高屋建瓴，再到编码的严谨以及测试的周全，每一个环节都仿佛被剥茧抽丝般地展现在我面前，让我看到一个完整的、有血有肉的软件诞生过程。书中对于“模块化”和“抽象”的讲解，更是让我醍醐灌顶。我以前常常陷入代码堆砌的泥潭，缺乏整体的架构思维，导致项目后期维护困难重重。而这本书通过生动的案例，清晰地阐释了如何通过良好的设计来降低复杂性，提高代码的可读性和可复用性。这种“思想的力量”让我意识到，软件工程不仅仅是关于写代码，更是关于如何思考、如何组织、如何协作，如何构建一个可持续发展的系统。
评分我在阅读过程中，有一个强烈的感受，那就是这本书帮助我构建了一个全新的“系统思维”框架。过去，我更多地是从一个“点”出发，关注代码的实现、功能的开发。但这本书让我看到，软件工程的本质是“系统”，它是由无数个相互关联的组件构成的有机整体。作者在阐述“架构设计”时，对于不同架构模式的分析，让我对如何构建可扩展、可维护的系统有了更深刻的理解。他并非简单罗列名词，而是深入剖析了每种架构模式的优缺点，以及适用的场景。这种“辨证”的视角，让我能够根据项目的具体需求，做出更明智的技术选型。书中的“设计模式”部分，更是如同一本武功秘籍，为我提供了解决常见设计问题的经典方案。我开始能够在代码中看到那些“模式”的影子，并且尝试去运用它们，这极大地提升了我编写高质量代码的能力。
评分书中关于“版本控制”和“持续集成/持续部署（CI/CD）”的章节，对我来说是极具价值的。我过去常常一个人埋头苦干，或者与少数几个人进行零散的代码合并，这导致了巨大的协作成本和潜在的冲突。这本书详细介绍了Git等版本控制工具的使用方法，以及如何利用CI/CD流程来自动化构建、测试和部署，这极大地提高了团队的开发效率和代码质量。它让我看到了现代软件开发流程的“智能化”和“自动化”的魅力。我开始尝试将这些实践应用到我的个人项目中，并且深刻体会到了它们带来的效率提升和风险降低。这种对自动化和流程优化的追求，正是这本书所传递的核心精神之一。
评分这本书的封面设计就足够吸引人，一种沉静而有力量的蓝色，配上简洁但充满现代感的字体，让我对即将翻开的“软件工程”之旅充满了期待。我并非科班出身，接触软件开发更多是源于对科技的好奇和解决实际问题的热情。所以，当我看到这本书时，内心涌起的是一种希望能够系统梳理我现有零散知识的渴望，并且能从中窥探到专业领域更深层次的智慧。拿到手沉甸甸的，感觉内容一定非常充实。翻开第一页，不是枯燥的代码或者理论公式，而是作者对于软件工程价值的开篇论述，他用了一种非常平易近人的方式，将软件工程比作建造一座宏伟的建筑，需要精密的蓝图、严谨的施工、可靠的维护，这让我立刻产生了共鸣。我一直觉得，很多时候我们做的事情，虽然结果看起来是“软件”，但背后支撑的逻辑和原则，与任何一个领域的精益求精都是相通的。这本书似乎正是要揭示这些普遍存在的、能够提升工作效率和质量的“工程”思维。我对书中如何将那些看似抽象的“过程”、“方法论”变得具体，如何让我在实际开发中能够切实运用这些原则，感到非常好奇。毕竟，理论再好，如果不能落地，那终究是纸上谈兵。
评分这本书的影响，已经开始在我实际的开发工作中显现出来。我发现自己能够更清晰地思考问题的本质，而不是仅仅停留在表面。在需求分析阶段，我能够更好地与产品经理沟通，准确把握用户的真实需求，避免了许多不必要的返工。在设计阶段，我能够运用书中介绍的各种设计原则和模式，构建出更加健壮和灵活的系统。在编码阶段，我更加注重代码的可读性和可维护性，并且开始自觉地编写单元测试。这本书就像是为我打开了一扇新的大门，让我看到了软件开发更广阔的天地。它不仅仅是一本技术书籍，更是一本关于如何成为一名优秀软件工程师的“方法论”。
评分这本书所带来的启发，远远超出了我对“软件工程”这个词汇的固有认知。我原本以为它会充斥着各种技术细节和复杂的算法，但事实证明，它更像是一本关于“智慧”的指南。作者对于“项目管理”和“团队协作”的章节，尤其让我印象深刻。我曾在项目中经历过无数次的沟通不畅、需求变更带来的混乱，以及由于缺乏有效的管理而导致的项目延期。这本书提供了一套系统化的方法，从如何清晰地定义项目目标，到如何有效地分配任务，再到如何进行风险预估和控制，都给出了非常实操性的建议。它强调了“沟通”在软件开发中的核心地位，并且提供了各种促进有效沟通的工具和技巧。我开始意识到，一个成功的软件项目，离不开所有参与者的紧密协作和高效沟通。书中的“敏捷开发”理念，更是让我看到了在快速变化的市场环境中，如何保持灵活性和响应速度的答案，这对我来说是革命性的。
评分这本书的阅读体验，让我感觉像是在和一位经验丰富的导师进行一对一的交流。作者的语言风格清晰、流畅，即使是对于一些复杂的概念，也能用通俗易懂的语言进行解释。书中穿插的各种案例分析，更是让理论变得生动形象，我仿佛置身于那些真实的开发场景之中，思考着如何运用书中的知识去解决问题。我尤其喜欢他对于“重构”的论述。我常常在开发一段时间后，发现自己的代码变得越来越难以理解和修改。这本书提供的系统性的重构策略，让我看到了摆脱“技术债务”的希望。它教会我如何识别“坏味道”，如何安全地进行代码改进，这对于保持代码的健康度和可维护性至关重要。
评分我特别欣赏这本书在论述“软件维护”时所展现出的长远眼光。很多人往往只关注软件的开发过程，而忽略了软件交付后的维护工作。然而，这本书却将维护视为软件生命周期中至关重要的一环，并提供了许多关于如何降低维护成本、提高维护效率的方法。它强调了良好的文档、清晰的代码结构以及完善的测试对于简化维护的重要性。我意识到，一个真正优秀的软件，不仅要能够按时按质交付，更要能够经受住时间的考验，易于修改和升级。书中关于“技术债务”的讨论，更是让我警醒，要时刻关注代码的质量，避免因为短期的效率而牺牲长期的可维护性。
评分目前图书馆少数能找到的关于软件工程的书
评分目前图书馆少数能找到的关于软件工程的书
评分目前图书馆少数能找到的关于软件工程的书
评分目前图书馆少数能找到的关于软件工程的书
评分目前图书馆少数能找到的关于软件工程的书
相关图书
本站所有内容均为互联网搜索引擎提供的公开搜索信息，本站不存储任何数据与内容，任何内容与数据均与本站无关，如有需要请联系相关搜索引擎包括但不限于百度，google,bing,sogou 等
© 2026 book.quotespace.org All Rights Reserved. 小美书屋 版权所有