《Systems Analysis and Design_Alan Dennis著》pdf电子书免费下载
下载方式一：
百度网盘下载地址：https://pan.baidu.com/s/1Km4JijJKgG2An_wrJMTVIw
百度网盘密码：1111
下载方式二：
http://ziliaoshare.cn/Download/af_124287_pd_SystemsAnalysisandDesign_AlanDennisZ.zip
|
|
作者：empty 页数：574 出版社：empty |
《Systems Analysis and Design_Alan Dennis著》介绍
This book was set in 105/12TimesNewRomanbyAptarat， Inc.and printedand bu und by RRD/Von HofmannThe cover was printed by RRD Von Hoffmann.Ths book is pre duma caH free paper@Copyright@2009JuhnWiley&Sons， Inc.All rights reserved No part of this publication maybereproduced.slur edina retrieval system.or transmit ied in any form or by any means.electronic，mechanicaL photocopying.recording.scanning， ur otherwise， except as permitted under Section107or108ofthe1976Lnited States Copy ngh tAct， wthout ether the prior wi ten permission ofthe Pa bls her or authorization through payment of the appropriate per copy fee to the CopyrightClearance Center.Inc， 222 Rosewood Drive.Danvers， MA 01923，www.copyrightcom.Requeststothe Publisher for permission should be addressed to the Permissions Department.John Wiley&Sons， Inc.Ml Rier Street Hoboken， NJ 07030-5774.(201) 7486011.fax(2017486008，hp：/wwwwileycomgo permissions.
PREFACEPURPOSE OF THIS BOOKSystems Analysis and Design(SAD) is an exciting， active field in which analystscontinually learn new techniques and approaches to develop systems more effec-tively and efficiently.However， there is a core set of skills that all analysts need toknow no matter what approach or methodology is used.All information systemsprojects move through the four phases of planning， analysis， design， and imple-mentation， all projects require analysts to gather requirements， model the businessneeds， and create blueprints for how the system should be built， and all proje etsrequire an understanding of organizational behavior concepts like change manage-ment and teambuildingfocused on doing SAD while presenting the core set of skills that we feel every sys-tems analyst needs to know today and in the future， This book builds on our pro-fessional experience as systems analysts and on our experience in teaching SAD inthe classroom.major project as part of their course.Each chapter descr ihes one part of the process，provides clear explanations on howto do it， gives a detailed example， and then hasexercises for the students to practice.In this way， students can leave the course withexperience that will form a rich foundation for further work as a systems analyst.Second and more obvious to students， we include a final chapter on the majorThis book captures the dynamic aspects of the field by keeping studentsThis book will be of particular interest to instructors who have students do aOUTSTANDING FEATURES
A Focus on Doing SADThe goal of this book is to enable students to do SAD—not just read about it， butunderstand the issues so that they can actually analyze and design systems.Thebook introduces each major technique， explains what it is， explains howto do it，presents an example， and provides opportunities for students to practice before theydo it in a real-world project After reading each chapter， the student will be able toperform that step in the system development lifecycle(SDLC) process.Rich Examples of Sue cess and FailureThe book includes a running case about a fictitious company called Tunc SourceEach chapter show show thc concepts arc applied in situations atTune SourceUnlike running cases in other books， this text focuses examples on planning， man-aging， and executing the activities descr bed in the chapter， rather than on detaileddialog uc between fictitious actors.In this way， the running case serves as a templatethat students can apply to their own work.Each chapter also includes numerousConcepts in Action boxes that de seri be how real companies succeeded—andfailed—in performing the activities in the chapter.Many of these examples aredrawn from our own experiences as systems analysts.Incorporation of Obj eet-Oriented Concepts and TechniquesThe field is moving toward object-oriented concepts and techniqu cs， both throughUML 2.0， the new standard for object-oriented analysts and design， as well as bygradually incorporating object-oriented concepts into traditional techniques.Wehave taken two approaches to incorporating object-oriented analysis and design intothe book.First， we have in tcg rated several objc ct-oriented concepts into our dis-cussion of traditional techniques， a though this may not be noticed by the studentsbecause few concepts arc explicitly labeled as object-oriented concepts.For cx am-ple， we include the development of use cases as thc first step in process modeling(i.c.， dataflow diagramming) in Chapter 4， and the use(and reuse y of standardinterface templates and use scenarios for interface design in Chapter 9.clements of UML 2.0 that can be used as an introduction to object o rented analystsand dc sign.This chapter can be used at the end of a cours c—while students are busyworking on projects or can be introduced after or instead of Chapters 5 and 6.Real-World Focus
The skills that students learn in a systems analysis and design course should mirrorthe work that they ultimately will do in real organizations.We have tried to makethis hook as“real as possible by building extensively on our experience as profes-sional systems analysts for organizations such as IBM， the U.S.Department ofDefense， and the Australian Army， We have also worked with diverse industry advi-sory hoards of IS professionals and consultants in developing the book and haveincorporated their stories， feedback， and advice throughout.Many students who usethis hook will eventually apply the skills on the job in a business environment， andwe he lieve that they will have a competitive edge by understanding what suce ess-ful practitioners feel is relevant in the real worldProject ApproachWe have presented the topics in this book in the SDLC order in which an analystencounters them in atypical project.Although the presentation necessarily is linear(becaus c students have to learn concepts in the way in which they build on cachother) ，wecmphasizetheiterativc.complex nature of SAD as the book unfolds.Thepresentation of the material should align well with courses that encourag c studentsto work on projects， because it presents topics as students need to apply them.
Graphic OrganizationThe underlying metaphor for the book is doing SAD through a project.We hav ctr icdto c mph a size this graphically throughout the book so that students canbet tcr under-stand how the major clements in the SDLC arc related to cach other.First， at the startof every major phase of the system dev c lopment lifecycle， wc prc sent a graphicillustration showing the major deliverables that will be developed and added to the“project binder”during that phase.Second， at the start of each chapter， we present achecklist of key tasks or activities that will be performed to produc c the deliverablesassociated with this chapter.These graphic clements thc binder of deliverables tiedto each phase and the task checklist tied to cach chapter—can help students betterunderstand how the tasks.dc liver ables， and phases are related to and fi ow from oneto another.
by marking box cs and illustrations with a pushpin.These topics arc particularlyimportant in the practical day-to-day life of systems analysts and arc the kind oftopics that junior analysts should pullout of thc book and post on the bull ct in boardin their office to help them avoid costly mistakesPart 1 covers the first phase of the SDLC， the planning phase.Chapter 1 intro-Part 2 presents techniques needed during the analysis phase.In Chapter 3，tha be sgn Phase is covered in Part 3ofthetexbookInChaptr 7， su.The implementation phase is presented in Chapters 12 and 13.ChapterChapter 14 provides a background of objector ie nation and explains severalFinally， wc have highlighted important practical aspects throughout the bop kWHAT'S NEW IN THE FOURTH EDITIONThe fourth edition contains several important enhancements， including a new run-ning case.new examples， many new Concepts in Action， and so mcrc organizedmaterial.are introduced to pro jeet in itation immedi at cly in the first chapter.The Tune Sourcerunning case is launched in Chapter Iso that students can be involved in a projectcontext from the outset of the book.The topic of project selection has beencn hanced with a discussion of project portfolio man agc ment.The discussion ofSDLC methodologies has been updated and shifted to Chapter 2.In this way， thereview of alte mative methodologies is placed within the context of planning a pro-ject and sc lecting the hest methodology for it.Finally.some of the more technicalconcepts associated with economic feasibility financial calculations， function pointanalysis， and project management techniques have been moved to chapter appen-dices.This kc eps the material available forth osc instructors who choose to includeit.but streamlines the main chapter content for those instructors who exclude thesetopics due to time constraintscles， is introduced to provide additional illustrations of concepts.tc ch niques，and deliverables.The topic of requirements determination is cn hanced by asam plc intervi cw transcript that provides the basis for new requirements in theHoliday Travel Vc hicles case.The discussion of data model normalization hasbeen moved to a chapter appendix.Completed use cases， process mod cls， anddata models are included for both the Tune Source case and the Holiday TravelVehicle cases， providing morc extensive c xamples and illustrations for studentsand instructors.
and the use of offshore outsourcing.Then-tiered client-server architectur cis explainedthrough anc-commerc c illustration.The role of exte mal security requirements andstandards is introduced as welL Userinterface examples and illustrations all havebeen updated to use Web-based fom ms or(VisualBasic) Windows-based foms to bet-terrell ect thc environment with which students will be involved.tially revised and replaced with current examples and illustrations.Chapter ref-erences to outside sour ees have heen updated to current resources whereverpossible.Part 1， Planning.has been substantially reorganized and streamlined.StudentsIn Part 2， Analysis， a new additional example case.Holday Travel V chi-Part 3， Design.includes some updated material on the usc of packaged softwareThroughout the book， the Concepts in Action material has been substan-ORGANIZATION OF THIS BOOKThis book is organized by the phases of the systems development lifecycle(SDLC) .Each chapter has been written to teach students specific tasks that analystsneed to accomplish over the course of a project， and the deliverables that will beproduced from the tasks.As students complete the book.tasks will be“checkedoff and deliverables will be completed and filed in a project binder.Along the way，students will be reminded of their progress by roadmaps that indicate where theircurrent task fits into the larger context of SADduces the SDLC， the roles and skills needed for a project team， project initiation，the systems request， and feasibility analysis.Chapter 2 discusses project selection，the selection of an SDLC methodology for the project， and project management，with emphasis on the workplan， staf ing plan， project charter， risk assessment， andtools used to help manage and control the project.students are introduced to requirements determination and arc taught a variety ofanalysis techniques to help with business process automation， business processimprovement， and business process reengineering.Chapter 4 focuses on usecases， Chapter 5 covers process models.and Chapter 6 explains data models andnormalization.dents create an alternative matrix that compares custom， packaged， and out sourc-ing alternatives， Chapter 8 focuses on designing the system architecture， whichincludes the architecture design.hardware/software specification， and securityplan.Chapter 9 focuses on the userinterface and presents interface design； in thischapter， students leam howto create use scenarios， the interface structure dia-gram， interface standards， and interface prototypes.Finally， data storage designand program design are discussed in Chapters 10 and 11.which contain informa-tion regarding the data storage design， the program structure chart， and programspecifications.12 focuses on system construction， and students learn howto build and test thesystem.It includes information about the test plan and user documentation，Conversion is covered in Chapter 13， where students learn about the conver-sion plan， the change management plan， the support plan， and the projectassessment.key object concepts supported by the standard set of object-modeling techniquesused by systems analysts and developers.Then， we explain howto draw four of themost effective models in UML：the use case diagram， the sequence diagram， theclass diagram.and the behavioral state machine diagram.
《Systems Analysis and Design_Alan Dennis著》目录
Stephen L.Shih
Uln ke Schultze
Tny Sci me
ArnldS chrn
Jhn B.Schwartz
Ken Shumate
AnneMarie Smith
Ted Strickland
James Suleiman
Rn Thmpsn
Jnathan Trwer
Duan cP.True xIII
William J.Va chula
David Vance
Bruce White
Rsann Webb Cllins
Vincent Yen
University f Kansas
University f Arkansas
University f Virginia
University f Virginia
Saint Luis University
East Carlina University
S.Jhns University-St.Vincents Cllege
SUNY Binghamtn
DeVry Institute f Technlgy， Clumbus， hi
The University f Memphis
Del ry Institute f Technlg u.Decatur， Gergia
University f Nrth Texas
University f Tled
Nrth era Illinis University
Lyla University.Chicag
Bellevue University
Suthern Illinis University
Suthern Methdist University
State University f NewYrk.Cllege at Brckprt
Buru ch Cllege
University f Mu ryland， Baltimre Cunty
Chapman University Cllege
LaSalle University
University f Luisville
University f Clrad.Clrad Springs
Wake Frest University
Baylr Universi ry
Gergia State University
University f Pena sylvania
Suthern Illinis University
Quinnipiac University
University f Suth Flrid u
Wri ghr State University
We wuld like t thank the many practiners frm private practice， public rgani-
zatins， and cnsulting firms fr helping us add a real-wrld cmpnent t this pr-
jec LA special remembrance ges t Matt Andersn frm Ace en ture， wh was a
rle mdel fr all wh knew him wh demnstrated excellen cc in systems analy-
sis and design and in life ingen cr al.Thanks als t Bruce White f Quinnipiac Uni-
versity fr his cntributin in updating the Cncepts in Actin material.
Thanks als t ur fami ies and friends fr their patience and supprt alng the way，
especially t Christpher， Haley， and Hannah Wixm； Alec Dennis， and Richard Jnes.
Preface
PART NEPLANNING PHASE3
CHAPTER 1THE SYSTEMS ANALYST AND INFRMATIN SYSTEMS DEVELPMENTS
CHAPTER 2PRJECT SELECTIN AND MANAGEMENT41
PART TWANALYSIS PHASE95
CHAPTER 3REQUIREMENTS DETERMINATIN97
CHAPTER 4USE CASE ANALYSIS143
CHAPTERSPRCESS MDE UING171
CHAPTER 6DATA MDELING209
PART THREEDESIGN PHASE245
CHAPTER 7MVING INT DESIGN247
CHAPTER 8ARCHITECTURE DESIGN269
CHAPTER 9USERINTERFACE DESIGN301
CHAPTER 10PRGRAM DESIGN353
CHAPTER 11DATA STRAGE DESIGN393
PART FURIMPLEMENTATIN PHASE431
CHAPTER 12MVING INT IMPLEMENTATIN433
CHAPTER 13TRANSITIN T THE NEW SYSTEM459
CHAPTER 14THE MVEMENT T BJECTS491
Alan Tennis
ardennis@indiana.edu
Rbby Rll
Rberta.Rth@uni.cdu
BRIEF
B r bWi xem
bwixm@mindspring.cm
CHAPTER 1
Intrductin 6
The Systems Analyst 8
Systems Anu lyst Skills 8
Systems Analyst Specializatin 9
The Systems Develpment LifeCycle 10
Planning??
Analysis 72
Design 13
Imple n entatin 14
Prject Identificatin and Initiatin14
System Request 16
Applying the Cncepts atTune Surce 16
Feasibility Analysis 21
Technical Feasibility
Ecnmic Feasibility
rganizatinal Feasibility27
Applying the Cncepts atTune Surce 30
Summary 32
PLANNING PHASE
THE SYSTEMS ANALYST AND INFRMATIN
SYSTEMS DEVELPMENT
Appendix1A：FinancialCnceptsfrCst-BeneitAnalysis37
Appendix IB：Detailed Ecnmic Feasibility
Analysis frTune Surce 37
CHAPTER 2 PRJECT SELECTIN AND MANAGEMENT
Intrductin 42
Prject Selectin43
Applying the Cncepts at Tunc Surce 44
Creating the Prject Plan 47
Prject Methdlgy ptins 47
Selecting the Apprpriate Develpmen r Methdlgy 54
Estimating the Prject TimeFrame 57
Develping the WrkPlan 58
Staffing the Prject 60
Staffing Plan 60
Crdinating Prject Activities 66
Managing and Cntrlling the Prject 69
Refining Estimates 70
Managing Scpe7I
Time bxing 73
Managing Risk 74
Applying the Cncepts atTune Surce 76
Staffing the Prject 77
Crdinating Prject Activities 77
Summary 80
Appendix2A：TheFunctinPintApprach85
Appendix2B：PrjectManagementTls：TheGanttChart
and PERT Chart 90
Gantt Chart 90
PERT Chart 90
PART TWANALYSIS PHASE
CHAPTER 3 REQUIREMENTS DETERMINATIN
Intrductin 98
Requirements Determinatin 99
What Is a Requirement ? 99
Requirements Definitin 102
Determining Requirements 103
Creating the Requirements Def nitin 104
Requirements Analysis Techniques 105
Business Prcess Autmatin 106
Business Prcess Imprvement 107
Business Prcess Reengineering 110
Cmparing Analysis Techniques 12
Requirements-Gathering Techniques113
Requirements-Gathering in Practice 113
Interviews 114
Jint Applicatin Develpment(JAD) 121
Questinnaires 125
Dcument An a hys is 127
h servatin 128
Selecting the Apprpriate Techniques I 30
Applying the Cncepts atTune Surce 132
Requirements Analysis Techniques 132
Requirements-Gathering Techniques 132
Requirements Definitin I 33
Sj stem Prpsal 133
Summary 135
CHAPTER 4USE CASE ANALYSIS
Intrductin 144
Use Cases 145
Elements f a Use Case 145
Building Use Cases 148
Applying the Cncepts atTune Surce 158
Identifying the Majr Use Cases 158
Prcesses 177
Identifying the Majr Steps fr Each Use Case 162
Identifying the Elements With an Steps 162
Cnfirming the Use Case 164
Summary 166
CHAPTERS PRCESS MDELING
Intrductin 172
DataFlw Diagrams 172
Reading DataFlw Dia grans 172
Elements f DataFlw Diagrams 175
Using DataFlw Diagrams t Define Business
Prcess Descriptins 180
Creating DataFlw Diagrams 181
Creating the Cntext Diagram 182
Creating Duta Flw Diagram Frug ments 183
Creating the Level DataFlw Dia gran 185
Creating Level l DataFlw Diagrams(and Belw) 188
Wah dating the DataFlw Diagrams 191
Applying the Cncepts atTune Surce 195
Creating the Cntext Dia gran 195
Creating DataFlw Diagram Fragments 195
Creating the Level DataFlw Diagram 197
Creating Level l DataFlw Diagrams(and Belw j 198
lali dating the DataFlw Diagrams 201
Summary 202
Appendix5A：SupplementalDFDsFrHliday
Travel Vehicles 205
CHAPTER 6 DATA MDELING
Intrductin 210
The Entity Relatinship Diagram 210
Reading an Entity Relatinship Di gram t 211
Elements f an Entity Relatinship Diagram 212
The Duta Dictinary and Metadata 216
Creating an Entity Relatinship Diagram 219
Building Entity Relatinship Diagrams 219
Advanced Svn tux 223
Applying the Cncepts atTune Surce 224
Validating a nERD228
Design Guidelines 228
Nrmalizatin 231
xvi{r rnt
Balancing Entity Relatinship Dia grans with DataFlw Diagrams 231
Summary 233
Appendix6A：NrmalizingtheDataMdel238
PART THREEDESIGN PHASE245
CHAPTER 7 MVING INT DESIGN247
Intrductin 248
Transitin frm Requirements t Design 248
System Acquisitin Strategies 251
Custm Develpment 251
Packaged Sftware 252
utsurcing 254
Influences n the Acquisitin Strategy 256
Business Need 256
In-Huse Experience 257
Prject Skills 258
Prject Management 258
TimeFrame 259
Selecting an Acquisitin Strategy 259
Alterna rive Matrix 260
Applying the Cncep is atTune Surce 262
Summary 264
CHAPTER 8 ARCHITECTURE DESIGN269
Intrductin 270
Elements f an Architecture Design e 270
Architectural Cmpnents270
Server-Based Archif ec tures271
Client-Based Architectures
Client-Server Architectures强
Client-Server Tiers 274
Cmparing Architecture ptins 275
Creating an Architecture Design 277
peratinal Requirements 278
Perfrman ee Requirements279
Security Requirements 281
Cultural and Plitical Requirements 286
Designing the Architecture 289
Hardware and Sftware Specificatin 291
Applying the Cncepts atTune Surce 293
Creating an Architecture Design 293
Hardware and Sftware Specif catin 295
Summary 295
CHAPTER 9 USERINTERFACE DESIGN
Intrductin302
Principles fr UserInterface Design 302
Layut 303
Cntent Awareness 305
Aesthetics 307
User Experience 309
Cnsistency 310
Minimize User Effrt 310
UserInterface Design Prcess
Use Scenari Develpment
Interface Structure Design
Interface Standards Design
Interface Design Prttyping 317
Interface Evalutin 320
Navigatin Design 322
Basic Principles 322
Types f Navigatin Cntrls 323
Messages 326
Input Design 328
Bus ic Principles329
Tpes f Inputs331
Input Fali datin 333
utput Design 335
Bus ic Principles335
Types f utputs 336
Media 337
Applying the Cncepts atTune Surce 339
Use Scenari Develpment339
Interface Structure Design339
Interface Standards Design34l
Interface Template Design341
Design Prttyping 342
Interface Evaluatin 343
Summary 345
CHAPTER 10 PRGRAM DESIGN
Intrductin 354
Mving frm Lgical t Physical Prcess Mdels 354
The Physical DataFlw Diagram 354
Applying the Cncepts atTune Surce 357
Designing Prgrams359
Structure Chart 362
Syntax 362
Building the Structure Chart 365
Applying the Cncepts atTune Surce 368
Design Guidelines 372
Prgram Specificatin 379
Syntax 379
Applying the Cncepts atTune Surce 382
Summary 385
CHAPTER 11 DATA STRAGE DESIGN
Intrductin 394
Data Strage Frmats 394
Files 395
Databases397
Selecting aS t ruge Frmat 403
Applying the Cncepts atTune Surce 405
Mving frm Lgical t Physical Data Mdels406
The Physical Entity Relatinship Diagram 406
Revisiting the CRUD Matrix 410
Apply ng the Cncepts atTune Surce 410
ptimizing Data Strage 413
ptimizing Strage Eff ciency 414
ptimizing Access Speed 416
Estimating S t ruge Size 421
Appl vng the Cncepts atTune Surce 424
Summary 425
PART FURIMPLEMENTATIN PHASE
CHAPTER 12 MVING INT IMPLEMENTATIN
Intrductin 434
Managing the Prgramming Prcess434
Assigning Prgram mig Tasks 434
Crdinating