系统分析与设计导论(英文版) [平装] 9787111352785,711135

《系统分析与设计导论(英文版)》是经典教材《系统分析与设计方法》的简明版本，既保留了经典教材内容全面的特色，又对高级主题进行了适当的精减，更强调系统概念，使之更加适用于导论课教学要求。 全书详细阐述面向对象系统分析和设计技术。作者通过融入基于UML的面向对象分析和设计技术。对现代概念、工具、技术以及应用等各方面内容进行了很好的平衡。《系统分析与设计导论(英文版)》提供了市场上可用的、丰富的系统分析和设计的实例。 《系统分析与设计导论》是经典原版书库。 作者：（美国）惠滕（Whitten.J.L.） （美国）本特利（Bentley.L.D.） 惠滕，美国普度大学计算机技术系主任兼教授，曾两次荣获James G．Dwyer最佳教师奖。自1984年任教授后，他开始编著《系统分析与设计方法》一书，目前已经出版到第7版。该书长期位于同类书销售排行榜第1名，被700多所学校采纳作为教材。Whitlen教授是多个学术组织的活跃成员，其中包括：信息技术专业学会(ATP)、信息系统学会(AIS)、计算机学会(ACM)、信息管理协会(SIM)等。 本特利，美国普度大学计算机技术系教授，主要教学和研究领域包括：系统分析和设计、企业应用系统、业务过程重构、计算机辅助软件工程(CASE)、快速应用开发(RAD)和图形用户界面设计。 Preface iv PART ONE The Context of Systems Development Projects 3 1 THE CONTEXT OF SYSTEMS ANALYSIS AND DESIGN METHODS 4 Introduction 5 The Product——Information System 5 The People——System StakehoMers 7 Systems Owners 7 Systems Users 7 Systems Designers 9 Systems Builders 9 Systems Analysts 10 External Service Providers 10 The Project Manager 10 Business Drivers forToday's Information Systems 11 Globalization of the Economy 11 Electronic Commerce and Business 11 Security and Privacy 14 Collaboration and Partnership 14 Knowledge Asset Management 15 Continuous Improvement and Total Quality Management 15 Business Process Redesign 16 Technology Drivers for Toclay's Information Systems 16 Netwrks and the Internet 16 Mobile and Wireless Technologies 18 Object Technologies 18 Collaborative Technologies 19 Enterprtse Applications 19 The Process-System Development Process 23 System Initiation 25 System Analysis 25 System Design 26 System Implementation 26 System Support and Continuous Improvement 27 2 INFORMATION SYSTEMS DEVELOPMENT 00 Introduction 35 The Process of Systems Development 35 The Capability Maturity Model 35 Life Cycle versua Methodology 3 7 Underlying Principles for Systems Development 38 A Systems Development Process 41 Where Do Systems Development Projects Come From? 41 The Systems Development Phases 43 Cross Life-Cycle Activities 52 Sequential versus Iterative Development 54 Alternative Routes and Strategies 54 The Model-Driven Development Strategy 57 The Rapid Application Development Strategy 60 The Commercial Application Package Implementation Strategy 62 Hybrid Strategiss 65 System Maintenance 65 AntomatedTools andTechnology 68 Computer Asststed systems Engineering 68 Application Environments 71 Process and Project Managers 71 3 PROJECT MANAGEMENT 78 Introduction 79 What Is Project Management? 79 The Causes of Failed Projects 80 The Project Management Body of Knowledge 83 The Project Management Life Cycle 87 Activity l——Negotiate Scope 89 Activity 2——1dentify Tasks 89 Activity 3——Estimate Tusk Durations 91 Activity 4——Specify Intertask Dependencies 93 …… 4 Systems Analysis 5 Fact-Finding Techniques for Requirements Discovery 6 Modeling System Requirements with Use Cases 7 Data Modeling and Analysis 8 Process Modeling 9 Object-Oriented Analysis and Modeling Using the UML 10 Feasibility Analysis and the System Proposal Part Three Systems Design Methods 11 Systems Design 12 Application Architecture and Modeling 13 Database Design 14 Output Design and Prototyping 15 Input Design and Prototyping 16 User Interface Design 17 Object-Oriented Design and Modeling Using the UML Part Four Beyond Systems Analysis and Design 18 Systems Construction and Implementation 版权页： 插图： Let's walk through the sequence diagram shown in Figure 17-11.The Member makeshis or her selections using the on-screen tools provided in the ORDER WINDOW （which isnoted to be an interface class）.The ORDER WINDOW then passes those selections with anitem and quantity specification for each to the Controller class. The CONTROLLER100pSthrough each of the items.The use case says that for each ordered item, the system mustverify product availability.To do that the CONTROLLER sends a message to PRODUCT, callingits calculateQtyInStock method.We may have already identified calculateQtyln Stock asa behavior of PRODUCT and so we can read it right off the class diagram and plug it inhere. If it isn't a behavior already, then we can determine a need for its existence from this sequence diagram and then add it to the class diagram. Why would this behaviorbe assigned to PRODUCT~ We see from Figure 17-11 that PRODUCT has a quantityIn Stock at-tribute, so it is the natural source of this information. PRODUCT returns quantityInStock tothe CONTROLLER.The use case includes verbiage to handle items not in stock, hut we arenot following that scenario.This sequence diagram assumes all items are in stock. Each in-stock item must be added to the order. Should that be a responsibility of MEMBER ORDER or MEMBER ORDERED PRODUCT？We see from Figure 17-12 that MEMBER ORDERhas a composition relationship to MEMBER ORDERED PRODUCT, making MEMBER ORDER responsible for the creation and deletion of instances. So we will have the CONTROLLER pass this message to MEMBER ORDER.As it adds an item, MEMBER ORDER needs to recalculate itstotal. So it calls one of its own methods （calcTotal）.To do this calculation, it needs the extended price （quantity times price） of the new item, so it calls calc ExtPrice of MEMBERORDERED PRODUCT. That calculation needs price information, which is held by PRODUCT.So MEMBER ORDERED PRODUCT Creates an instance of PRODUCT to look up the price.The ex-tended price can then be passed back to MEMBER ORDER, which passes the entire order to the CONTAOLLER. Finally, the CONTROLLER passes the order to the ORDER WINDOW for display. From this we can determine what behaviors should be assigned to what classes and the parameters they will accept and return. Once the behaviors have been identiffed, documented, and associated to specific classes, then the class diagram Can beupdated to include those behaviors in the appropriate classes.

ISBN	9787111352785,711135
出版社	机械工业出版社
作者	惠滕(Whitten.J.L.)
尺寸	16