软件工程 pdf epub mobi txt 电子书下载 2026

简体网页||繁体网页

☆☆☆☆☆

出版者:高等教育

作者:(美)弗莱格//阿特利

出品人:

页数:756

译者:

出版时间:2009-12

价格:53.00元

装帧:

isbn号码:9787040279474

丛书系列:

图书标签:

计算机
软件工程
软件开发
编程
计算机科学
系统设计
需求分析
测试
项目管理
软件质量
软件架构

下载链接在页面底部

facebook linkedin mastodon messenger pinterest reddit telegram twitter viber vkontakte whatsapp 复制链接

想要找书就要到图书目录大全

book.wenda123.org

立刻按 ctrl+D收藏本页

你会得到大惊喜!!

具体描述

《国外优秀信息科学与技术系列教学用书·软件工程:理论与实践(第4版·影印版)》主要内容：This introduction to software engineering and practice addresses both procedural and object-oriented development. The book applies concepts consistently to two common examples —— a typical information system and a real-time system. It combines theory with real, practical applications by providing an abundance of case studies and examples from the current literature. This revision has been thoroughly updated to reflect significant changes in software engineering, including modeling and agile methods.

《软件工程》这本书，顾名思义，其核心在于系统地阐述软件开发这一复杂过程的科学与艺术。然而，若要深入探究其精髓，首先需要明确它所不包含的内容，这样才能更清晰地勾勒出这本书所聚焦的独特价值与边界。首先，这本书不是一本关于具体编程语言的“速成手册”。它不会手把手教你如何编写 C++ 的类，如何使用 Python 的装饰器，或是如何掌握 Java 的多线程。它不会提供大量代码示例，让你通过模仿来学习。相反，它关注的是更宏观、更具普适性的原则和方法。你可以将这本书理解为软件开发的“操作系统”层面的知识，而具体的编程语言则是运行在这个操作系统上的“应用程序”。掌握了这些底层原理，无论你选择哪种编程语言，都能更有效地进行开发。这本书的重点在于“工程”二字，强调的是体系化、规范化、可控化的开发流程，而非孤立的语法技巧。其次，《软件工程》不涉及“创业指南”或“市场营销策略”。它不会告诉你如何找到你的第一个客户，如何撰写一份吸引投资人的商业计划书，或者如何进行产品推广。虽然优秀的软件产品离不开成功的商业运作，但本书的视角 strictly 聚焦于软件本身的构建过程。它关心的是如何从一个需求出发，将其转化为高质量、可维护、可扩展的软件系统。它探讨的是如何管理项目、如何设计架构、如何进行测试，但它不会教你如何“卖”你的软件。这本书是一门关于“造好软件”的学问，而非“卖好软件”的策略。再者，这本书不是一本“个人效率提升”的工具集。它不会提供让你立刻成为“时间管理大师”的秘诀，或者告诉你如何在家高效工作。尽管软件工程中的许多原则，如模块化、抽象、关注点分离等，都能在一定程度上提升个人工作效率，但这并非本书的直接目标。它所关注的效率，更多的是体现在团队协作、项目进度控制、资源优化以及最终软件产品的质量和交付周期上。它旨在通过系统性的方法来提高整个软件开发过程的效率和有效性，而不是仅仅关注个人层面的时间管理技巧。此外，《软件工程》不会深入探讨“计算机硬件原理”或“底层操作系统细节”。虽然了解一些基础的硬件知识对于理解软件性能至关重要，但本书不会花费篇幅去讲解 CPU 的工作原理、内存管理的具体实现，或者文件系统的底层结构。它假设读者已经具备一定的计算机科学基础，并着重于在软件层面进行讨论。它关心的是如何设计出在现有硬件和操作系统之上运行良好的软件，而不是如何设计硬件或操作系统本身。同时，这本书不会深入研究“人工智能的算法细节”或“机器学习的数学模型”。虽然人工智能和机器学习是软件工程的重要应用领域，并且很多现代软件都集成了这些技术，但《软件工程》这本书的范畴更为广泛，它涵盖了所有类型的软件开发，无论是否涉及 AI。它关注的是如何将 AI 模型集成到软件系统中，如何管理 AI 项目的生命周期，但它不会详细讲解深度学习的反向传播算法，或者如何构建一个决策树。这本书是对整个软件开发领域，包括 AI 驱动的软件开发，提供一个通用的框架和指导。另外，《软件工程》不会包含“游戏开发的独特技巧”或“嵌入式系统的实时性要求”。虽然游戏开发和嵌入式系统开发都是软件工程的重要分支，并且有其独特的挑战和技术栈，但本书的目的是提供一套通用的软件工程原理，适用于各种类型的软件项目。它不会针对特定领域的开发进行深入的探讨。例如，对于游戏开发中的图形渲染技术，或者嵌入式系统中对实时性的严苛要求，这本书不会提供具体的解决方案，但它会提供管理这些复杂项目的方法论。最后，需要强调的是，《软件工程》不是一本“经验分享”或“案例分析”的集合。虽然书中可能会引用一些经典的软件项目作为例子来说明某个概念，但它不会提供大量详细的、来自一线开发者的“亲身经历”。它所传递的是经过提炼和总结的、具有理论指导意义的知识体系，而非零散的个人经验。经验固然宝贵，但软件工程更需要的是一套经过时间检验、能够被广泛应用的科学方法和工程实践。那么，《软件工程》这本书究竟是关于什么的呢？它是一门关于如何系统地、有组织地、高效地开发软件的学科。它关注软件生命周期的各个阶段，从最初的需求分析，到设计、实现、测试、部署，再到维护。它提供了一套概念、原则、方法、工具和技术，帮助开发者和项目管理者更好地应对软件开发过程中出现的各种挑战。在需求分析阶段，这本书会探讨如何准确地理解用户的需求，如何将模糊的语言转化为清晰、可执行的规格说明。它会介绍各种需求获取技术，如访谈、问卷、原型法等，以及如何对需求进行建模和分析，以确保项目方向的正确性。在设计阶段，它会深入讲解软件设计的艺术和科学。这包括如何进行高层次的系统架构设计，如何将系统分解为可管理的模块，以及如何进行详细的模块设计。它会介绍诸如面向对象设计（OOD）、面向服务架构（SOA）、微服务架构等设计范式，并强调模块化、抽象、封装、继承、多态等面向对象设计的核心原则。同时，它也会讨论如何进行接口设计、数据设计，以及如何确保设计的可扩展性和可维护性。在实现阶段，虽然不直接教授编程语言，但它会强调编写清晰、可读、可维护的代码的重要性。它会讨论代码规范、编码风格，以及如何利用版本控制系统（如 Git）来管理代码的变更。它还会涉及软件构建和集成的过程，以及如何自动化这些流程。在测试阶段，这本书会详细阐述软件测试的各种方法和策略。从单元测试、集成测试，到系统测试和验收测试，它会解释每种测试的目的和方法。它还会介绍测试用例的设计原则，以及如何进行回归测试和性能测试。它会强调测试在保证软件质量方面不可或缺的作用。在部署和维护阶段，它会讨论如何将软件成功地交付给用户，以及如何在软件上线后进行持续的监控和维护。它会涉及配置管理、版本发布、故障排除、以及如何对软件进行更新和迭代，以适应不断变化的需求和环境。此外，《软件工程》还将聚焦于软件项目管理。它会探讨如何进行项目规划，如何估算项目的时间和成本，如何分配资源，以及如何识别和管理项目风险。它会介绍敏捷开发方法（如 Scrum、Kanban）和传统瀑布模型等不同的项目管理方法论，并帮助读者理解在不同场景下如何选择合适的方法。质量保证（QA）也是本书的一个重要组成部分。它不仅仅局限于测试，而是贯穿于软件开发的全过程。它会讨论如何建立和维护质量文化，如何进行代码审查，如何进行度量和分析，以持续地提升软件的整体质量。最后，本书还会触及软件工程的伦理和法律方面。例如，数据隐私、知识产权、软件许可协议等，这些都是现代软件开发不可忽视的考量因素。总而言之，《软件工程》这本书，旨在构建一个扎实的、系统的、具有高度实践指导意义的软件开发知识体系。它通过对软件开发全过程的系统性梳理和方法论的讲解，帮助读者建立起科学的工程思维，掌握有效的设计与管理技巧，从而能够更自信、更高效地构建出高质量的软件产品。它是一份通往“造好软件”之路的蓝图，而非某个具体技术细节的说明书。

作者简介

Shaft Lawrence Pfleeger (Ph.D., Information Technology and Engineering, George Mason University; M.S., Planning, Pennsylvania State University; M.A., Mathematics, Pennsylvania State University; B.A., Mathematics, Harpur College) is a senior information scientist at the RAND Corporation. Her current research focuses on policy and decision-making issues that help organizations and government agencies understand whether and how information technology supports their missions and goals. Her work at RAND has involved assisting clients in creating software measurement programs, supporting government agencies in defining information assurance policies, and supporting decisions about cyber security and homeland security.

Joanne M.Atlee (Ph.D. and M.S., Computer Science, University of Maryland; B.S., Computer Science and Physics, College of William and Mary; P.Eng.) is an Associate Professor in the School of Computer Science at the University of Waterloo. Her research focuses on software modeling, documentation, and analysis. She is best known for her world on model checking software requirements specifications. Other research interests include model-based software engineering, modular software development, feature interactions, and cost-benefit analysis of formal software development techniques. Atlee serves on the editorial boards for IEEE Transactions on Software Engineering, Software and Systems Modeling, and the Requirements Engineering Journal and is Vice Chair of the International Federation for Information Processing (IFIP) Working Group 2.9, an international group of researchers working on advances in software requirements engineering. She is Program Co-Chair for the 31st International Conference on Software Engineering (ICSE'09).

目录信息

PrefaceAbout the Authors1 Why Software Engineering? 1.1 What Is Software Engineering? 1.2 How Successful Have We Been? 1.3 What Is Good Software? 1.4 Who Does Software Engineering? 1.5 A Systems Approach 1.6 An Engineering Approach 1.7 Members of the Development Team 1.8 How Has Software Engineering Changed? 1.9 Information Systems Example 1.10 Real-Tune Example 1.11 What This Chapter Means for You 1.12 What This Chapter Means for Your Development Team 1.13 What This Chapter Means for Researchers 1.14 Term Project 1.15 Key References 1.16 Exercises2 Modeling the Process and Life Cycle 2.1 The Meaning of Process 2.2 Software Process Models 2.3 Tools and Techniques for Process Modeling 2.4 Practical Process Modeling 2.5 Information Systems Example 2.6 Real-Time Example 2.7 What This Chapter Means for You 2.8 What This Chapter Means for Your Development Team 2.9 What This Chapter Means for Researchers 2.10 Term Project 2.11 Key References 2.12 Exercises3 Planning and Managing the Project 3.1 Tracking Progress 3.2 Project Personnel 3.3 Effort Estimation 3.4 Risk Management 3.5 The Project Plan 3.6 Process Models and Project Management 3.7 Information Systems Example 3.8 Real-Time Example 3.9 What This Chapter Means for You 3.10 What This Chapter Means for Your Development Team 3.11 What This Chapter Means for Researchers 3.12 Term Project 3.13 Key References 3.14 Exercises4 Capturing the Requirements 4.1 The Requirements Process 4.2 Requirements Elicitation 4.3 Types of Requirements 4.4 Characteristics of Requirements 4.5 Modeling Notations 4.6 Requirements and Specification Languages 4.7 Prototyping Requirements 4.8 Requirements Documentation 4.9 Validation and Verification 4.10 Measuring Requirements 4.11 Choosing a Specification Technique 4.12 Information Systems Example 4.13 Real-Time Example 4.14 What This Chapter Means for You 4.15 What This Chapter Means for Your Development Team 4.16 What This Chapter Means for Researchers 4.17 Term Project 4.18 Key References 4.19 Exercises5 Designing the Architecture 5.1 The Design Process 5.2 Modeling Architectures 5.3 Decomposition and Views 5.4 Architectural Styles and Strategies 5.5 Achieving Quality Attributes 5.6 Collaborative Design 5.7 Architecture Evaluation and Refinement 5.8 Documenting Software Architectures 5.9 Architecture Design Review 5.10 Software Product Lines 5.11 Information Systems Example 5.12 Real-Time Example 5.13 What This Chapter Means for You 5.14 What This Chapter Means for Your Development Team 5.15 What This Chapter Means for Researchers 5.16 Term Project 5.17 Key References 5.18 Exercises6 Designing the Modules 6.1 Design Methodology 6.2 Design Principles 6.3 OO Design 6.4 Representing OO Designs in the UML 6.5 OO Design Patterns 6.6 Other Design Considerations 6.7 OO Measurement 6.8 Design Documentation 6.9 Information Systems Example 6.10 Real-Time Example 6.11 What This Chapter Means for You 6.12 What This Chapter Means for Your Development Team 6.13 What This Chapter Means for Researchers 6.14 Term Project 6.15 Key References 6.16 Exercises7 Writing the Programs 7.1 Programming Standards and Procedures 7.2 Programming Guidelines 7.3 Documentation 7.4 The Programming Process 7.5 Information Systems Example 7.6 Real-Time Example 7.7 What This Chapter Means for You 7.8 What This Chapter Means for Your Development Team 7.9 What This Chapter Means for Researchers 7.10 Term Project 7.11 Key References 7.12 Exercises8 Testing the Programs 8.1 Software Faults and Failures 8.2 Testing Issues 8.3 Unit Testing 8.4 Integration Testing 8.5 Testing Object-Oriented Systems 8.6 Test Planning 8.7 Automated Testing Tools 8.8 When to Stop Testing 8.9 Information Systems Example 8.10 Real-Time Example 8.11 What This Chapter Means for You 8.12 What This Chapter Means for Your Development Team 8.13 What This Chapter Means for Researchers 8.14 Term Project 8.15 Key References 8.16 Exercises9 Testing the System 9.1 Principles of System Testing 9.2 Function Testing 9.3 Performance Testing 9.4 Reliability, Availability, and Maintainability 9.5 Acceptance Testing 9.6 Installation Testing 9.7 Automated System Testing 9.8 Test Documentation 9.9 Testing Safety-Critical Systems 9.10 Information Systems Example 9.11 Real-Time Example 9.12 What This Chapter Means for You 9.13 What This Chapter Means for Your Development Team 9.14 What This Chapter Means for Researchers 9.15 Term Project 9.16 Key References 9.17 Exercises10 Delivering the System 10.1 Training 10.2 Documentation 10.3 Information Systems Example 10.4 Real-Time Example 10.5 What This Chapter Means for You 10.6 What This Chapter Means for Your Development Team 10.7 What This Chapter Means for Researchers 10.8 Term Project 10.9 Key References 10.10 Exercises11 Maintaining the System 11.1 The Changing System 11.2 The Nature of Maintenance 11.3 Maintenance Problems 11.4 Measuring Maintenance Characteristics 11.5 Maintenance Techniques and Tools 11.6 Software Rejuvenation 11.7 Information Systems Example 11.8 Real-Time Example 11.9 What This Chapter Means for You 11.10 What This Chapter Means for Your Development Team 11.11 What This Chapter Means for Researchers 11.12 Term Project 11.13 Key References 11.14 Exercises12 Evaluating Products, Processes, and Resources 12.1 Approaches to Evaluation 12.2 Selecting an Evaluation Technique 12.3 Assessment vs. Prediction 12.4 Evaluating Products 12.5 Evaluating Processes 12.6 Evaluating Resources 12.7 Information Systems Example 12.8 Real-Time Example 12.9 What This Chapter Means for You 12.10 What This Chapter Means for Your Development Team 12.11 What This Chapter Means for Researchers 12.12 Term Project 12.13 Key References 12.14 Exercises13 Improving Predictions, Products, Processes, and Resources 13.1 Improving Predictions 13.2 Improving Products 13.3 Improving Processes 13.4 Improving Resources 13.5 General Improvement Guidelines 13.6 Information Systems Example 13.7 Real-Time Example 13.8 What This Chapter Means for You 13.9 What This Chapter Means for Your Development Team 13.10 What This Chapter Means for Researchers 13.11 Term Project 13.12 Key References 13.13 Exercises14 The Future of Software Engineering 14.1 How Have We Done? 14.2 Technology Transfer 14.3 Decision-Making in Software Engineering 14.4 The Professionalization of Software Engineering: Licensing, Certification, and Ethics 14.5 Term Project 14.6 Key References 14.7 ExercisesAnnotated BibliographyIndex
· · · · · · (收起)