軟件工程

內(nèi)容概要

　　《軟件工程面向?qū)ο蠛蛡鹘y(tǒng)的方法(英文版.第8版)》對軟件工程的基礎(chǔ)知識(包括面向?qū)ο蠛蛡鹘y(tǒng)方法)進(jìn)行了嚴(yán)謹(jǐn)和全面的介紹，是軟件工程領(lǐng)域的經(jīng)典著作。
　　《軟件工程面向?qū)ο蠛蛡鹘y(tǒng)的方法(英文版.第8版)》共分兩大部分：第一部分介紹基本的軟件工程理論；第二部分講述更實用的軟件生命周期。作者采用這種獨特的、極具可讀性的組織方式，幫助學(xué)生和廣大讀者理解軟件工程中的一些復(fù)雜概念。
　　最新版第8版對《軟件工程面向?qū)ο蠛蛡鹘y(tǒng)的方法(英文版.第8版)》進(jìn)了整體更新，新增兩章內(nèi)容，分別概括介紹軟件工程的關(guān)鍵知識點和近年涌現(xiàn)的新技術(shù)。

作者簡介

　　Stephen R.
Schach　1972年獲魏茲曼科學(xué)院物理學(xué)理科碩士學(xué)位，1973年獲開普敦大學(xué)應(yīng)用數(shù)學(xué)博士學(xué)位，目前是美國范德比爾特大學(xué)計算機科學(xué)和計算機工程名譽教授。他的研究興趣主要集中在軟件工程領(lǐng)域，特別是對軟件維護(hù)與開源軟件的實驗分析有深入研究。他著有多部軟件工程、面向?qū)ο笙到y(tǒng)分析與設(shè)計方面的教材。

書籍目錄

preface iv
chapter　1 the scope of software engineering
　learning objectives
　　1.1 historical aspects
　　1.2 economic aspects
　　1.3 maintenance aspects
　　　1.3.1 classical and modern views of maintenance
　　　1.3.2 the importance of postdelivery maintenance
　　1.4 requirements, analysis, and design aspects
　　1.5 team development aspects
　　1.6 why there is no planning phase
　　1.7 why there is no testing phase
　　1.8 why there is no documentation phase
　　1.9 the object-oriented paradigm
　　1.10 the object-oriented paradigm in perspective
　　1.11 terminology
　　1.12 ethical issues
　　chapter review
　　for further reading
　　key terms
　　problems
　　references
part a 　software engineering concepts
chapter 2　software life-cycle models
　learning objectives
　　2.1 software development in theory
　　2.2 winburg mini case study
　　2.3 lessons of the winburg mini case study
　　2.4 teal tractors mini case study
　　2.5 iteration and incrementation
　　2.6 winburg mini case study revisited
　　2.7 risks and other aspects of iteration and incrementation
　　2.8 managing iteration and incrementation
　　2.9 other life-cycle models
　　　2.9.1 code-and-fix life-cycle model
　　　2.9.2 waterfall life-cycle model
　　　2.9.3 rapid-prototyping life-cycle model
　　　2.9.4 open-source life-cycle model
　　　2.9.5 agile processes
　　　2.9.6 synchronize-and-stabilize life-cycle model
　　　2.9.7 spiral life-cycle model
　　2.10 comparison of life-cycle models
　　chapter review
　　for further reading
　　key terms
　　problems
　　references
chapter 3　the software process
chapter 4　teams
chapter 5　the tools of the trade
chapter 6　testing
chapter 7　from modules to objects
chapter 8　reusability and portability
chapter 9　planning and estimating
chapter 10　key material from part a
chapter 11　requirements
chapter 12　classical analysis
chapter 13　object-oriented analysis
chapter 14　design
chapter 15　implementation
chapter 16　postdelivery maintenance
chapter 17　more on uml
chapter 18　emerging technologies
bibliography
appendix
author index
subject index
　
　　

章節(jié)摘錄

版權(quán)頁：插圖：A word used on almost every page of this book is software. Software consists of not just code in machine-readable form but also all the documentation that is an intrinsic com- ponent of every project. Software includes the specification document, the design docu- ment, legal and accounting documents of all kinds, the software project management plan, and other management documents as well as all types of manuals. Since the 1970s, the difference between a program and a system has become blurred. In the "good old days;' the distinction was clear. A program was an autonomous piece of code, generally in the form of a deck of punched cards that could be executed. A system was a related collection of programs. A system might consist of programs P, Q, R, and S. Magnetic tape Twas mounted, and then program Pwas run. It caused a deck of data cards to be read in and produced as output tapes T2 and Ta. Tape T2 then was rewound, and pro- gram Q was run, producing tape T4 as output. Program R now merged tapes Ta and T4 into tape Ts; Ts served as input for program S, which printed a series of reports.Compare that situation with a product, running on a machine with a front-end com- munications processor and a back-end database manager, that performs real-time control of a steel mill. The single piece of software contro！ling the steel mill does far more than the old-fashioned system, but in terms of the classic definitions of program and system, this software undoubtedly is a program. To add to the confusion, the term system now is also used to denote the hardware-software combination. For example, the flight control system in an aircraft consists of both the in-flight computers and the software running on them. Depending on who is using the term, the flight control system also may include the controls, such as the joystick, that send commands to the computer and the parts of the aircraft, such as the wing flaps, controlled by the computer. Furthermore, within the context of traditional software development, the term systems analysis refers to the first two phases （requirements and analysis phases） and systems design refers to the third phase （design phase）.To minimize confusion, this book uses the term product to denote a nontrivial piece of software. There are two reasons' for this convention. The first is simply to obviate the pro- gram versus system confusion by using a third term. The second reason is more important. This book deals with the process of software production, that is, the way we produce soft- ware, and the end result of a process is termed a product. Finally, the term system is used in its modem sense, that is, the combined hardware and software, or as part of universally accepted phrases, such as operating system and management information system.Two words widely used within the context of software engineering are methodology  and paradigm. In the 1970s, the word methodology began to be used in the sense of "a way of developing a software product"; the word actually means the "science of meth- ods."

編輯推薦

《軟件工程:面向?qū)ο蠛蛡鹘y(tǒng)的方法(英文版)(第8版)》是經(jīng)典原版書庫之一。本版新增內(nèi)容：新增兩章內(nèi)容：第10章總結(jié)第一部分涉及的關(guān)鍵知識點，便于學(xué)生在做團(tuán)隊項目時參考使用；第18章概括介紹面向方面的技術(shù)、模型驅(qū)動技術(shù)、基于組件的技術(shù)、面向服務(wù)的技術(shù)、社交計算、Web工程、云技術(shù)、Web 3.0和模型檢測等新技術(shù)。?擴展設(shè)計模式的相關(guān)材料，新增一個小的案例?新增兩個理論工具，即分而治之和關(guān)注點分離?新增100多道習(xí)題，并更新了大量參考文獻(xiàn)。

圖書封面

圖書標(biāo)簽Tags

無

評論、評分、閱讀與下載

---

    軟件工程 PDF格式下載

---