This groundbreaking text presents a balanced focus on concepts and techniques from both the traditional,structured approach and the newer object-oriented approach to system development,providing the most complete and up-to-date coverage of systems analysis and design available.The authors emphasize fundamentals of lasting value,while acknowledging the diverse development environments available in the real world today.Project management,system modeling,object technology with UML,client-server architecture,the Internet,and packages/ERPare all addressed within the context of the system development lifecycle Instructors may use this text to emphasize the traditional approach,the object-oriented approach,or both approaches,while referring to appropriate examples ftom one integrated case study.Finally,there is an alternative available for analysis and design courses that can prepare students for today and for tomorrow.

It is not easy to develop information Systems in today's rapidly changing environment, but the satisfaction and rewards for a job well done are substantial. This text is designed for students and practitioners of analysis and design who are up to the challengc of trying to do it right
　　Systems analysis and design is a practical field that relies on a core set of concepts and principles. as well as what sometimes seems an eclectic collection of rapidly evolving tools and techniques. Learning analysis and design today therefore requires an appreciation of the tried-and-true techniques widely embraced by experienced analysts plus the mastery of new and emerging tools and techniques that new graduates are increasingly expected to apply on the job. This text was developed for use in undergraduate and graduate courses in systems analysis and design where instructors and students do not want to ignore the past or hide from the future.
　　
Objectives and Vision
　　This text was dereloped by a team who shared a commitment to produce an analysis and design text that was different--a text that is flexible and streamlined, yet comprehensive and deep. We were guided by the belief that the text must be flexible enough to appeal to instructors emphasizing more traditional approaches to systems analysis and design as well as those emphasizing the latest object-oriented techniquca We did not went to oversimplify the problem of system development yet we felt that it was time to reevaluate whether many of the topics and features in duded in competing analysis and design texts were still essential. At the same time many new developments are affecting systems analysis and design, and we wanted to include key trends--package solutions,enterprise resource planning (ERP), components the Internet and so on.
　　We also wanted the text to teach the key concepts and techniques not just describe them. Therefore we focus on fundamentals of lasting value and then show how these fundamentals apply to alI approaches to development Then we explore traditional'structured analysis and design and object-oriented analysis and design in depth. Flexible and streamlined Comprehensive and deep We think you will agree these objectives have been achieved with this text.
　　
Innovation.
　　This text is unique in its integration of Key systems modeling concepts that apply to both the traditional structured approach and the newer object-oriented approach-events that　trigger system activities and objects/entities that are part of the system's problem domain. We devote one chapter to event partitioning and modeling key Objects/entities. After completing that chapter ,instructors can emphasize structured analysis and design or object-oriented analysis and design,or both,The object-oriented approach is not added as an afterthought-it is assumed from the beginning that everyone should understand the key object-oriented concepts. The traditional approach is not discarded--it is assumed from the beginning that everyone should understand the key structured concepts.
　　The traditional approach presented in this text is based on modem structured analysis and design as refined by McMenamin and Palmer Ed Yourdon, and Meilir Page-Jones. Modem structured analysis is an integrated,model-driven approach that includes event partitioning data modeling with entity-relationship diagrams (ERD),and process modeling with data How diagrams (DFDs). Modem structured　design is also based on event partitioning and uses the structure chart for software design.Database design using a reational database management implementation is featured. Instructors who emphasize the structured approach to development will be satisfied by the presentation and depth of coverage in this the.
　　The object-oriented approach　in this text is based on the Unified Modeling Language (UML) from the Object Management Group as originated by Booch,Rumbaugh,and Jacobson.Amodel-driven approach to analysis starts with use cases and scenarios　and then defines classes of objects and object interactions We include require ments modeling with use case diagrams,class diagrams, sequence diagrams, collaboration diagrams, and statechart diagrams.Design models are also discussed in detail,with particular attention to design class diagrams and statechart diagrams that are used to design methods.Our database design chapter covers two approaches to object persistence-a hybrid approach using relational database management and a pure approach using　Object-oriented database management systems (OODBMS). Instructors who emphasize the object-oriented approach will not be disappointed by the presentation and depth of coverage in this text.
　　Additional concepts and techniques are included in response to the realities of System development today First rapid application development and component based development are covered in depth. Second, package solutions and enterprise resource planning (ERP) are described as alternatives to custom development.
　　
Features and Pedagogy
　　The text uses　an integrated case study of moderate complexity-Rocky Mountain Outfitters--to illustrate key concepts and techniques on a specific system project .An overview of the strategic system splan for Rocky Mountain Outfitters (RMO) is presented　in Chapter1 to place the system project in context It is a Planned project of strategic importance to RMO and the need to integrate the new system with legacy systems and other planned systems is emphasized from the beginning. The planned system architecture provides　for rich examples-a　client-server Windows-based component as weIl as an e-commerce component with direct customer interaction via the lnternet. Details about the case are integrated directly into each chapter to make a point or to illustrate a concept-just-in-time examples-rather than isolating the case study in sep arate sections of the chapters. The same system project is used to illustrate　traditional and object-oriented models and solutions so both approaches can　be understood　and directly compared.
　　Short stand-alone opening case studies describe a real-world situation relevant to the material in each chapter .A variety of companies and situations are includend to provide the reader with a broad view of the Problems and opportunities found in the real world.
　　Each chapter includes extensive figures and illustrations designed to clarify and summarize key points and to provide examples of models and to provide　of models and other delivderables pro duced by an analyst .Margin definitions　of key terms are Placed in the Atext when the term is first used. End-of-chapter material includes a detailed summary,an indered list of key terms, and a list of additional resources and references. Each chapter also icludes ample review questions, Problems and exercisesr to get the student thinking critically, a collection of experiential exercises　involving additional research or problem solving and end-of-chapter case studies that invite students to Practice competing analysis and design tasks appropriate to the chapter Some cases extend from chapter to chapter to build on earlier concepts and techniques.
　　
Organlzation and Use
　　The text inxludes fifteen chapters Organized into four parts--far fewer chapters than competing texts Additionally, many chapters are modular-sections can be skipped without loss of continuity based on the objectives for the course Some chapters are entirely optional. The Instructor's Manual includes a discussion of different approaches to using the text in analysis and design　courses,including suggested course outlines for instructors emphasizing the traditional Structured approach or the Object-oriented approach and for instructors teaching graduate courses on analysis and design,
　　Part 1: The Modern Systems Analyst
　　Chapter 1 discusses　the work of a modern systems analyst including a streamlineddis cussion of Systems and the role of the systems analyst as a problem solver in a modem business organization. Chapter 2 moves right to the heart of the course-a systems development project--introduced while describing　the system development liff cycle (SDLC), project planning feasibility --assessment and project management. Students are drawn quickly into the RMO project so that the material has a meaningful context.Chapter3 then asks Now that we have a project What do we have to do to get this sys tem built That is　what are the methodologies models,tools and techniques that can be used to develop systems We make it clear that for are a variety of approaches to system development and that today's analysts need to be familiar with all of them. Even if students specialize in one approach in their course or later in their job they should be able to distinguish among the structured approaches information engineer ing and the object-oriented approach in a meaningful way.
　　Part 2: Systems Analysis Tasks
　　Part 2 moves ahead with systems analysis techniques Chapter 4 covers investigating sys tem requirements including gathering information and interviewing system owners and users. Chapter 5 covers modeling system requirements-using our approach which includes event partitioning and modeling objects/entities as described earier Chapter 6 continues requirements modeling using the traditional　approach including data flow diagrams (DFDS), data flow definitions process descriptions and so on. A few additional models that an analyst might encounter are also presented. Chaptr 7 continues the discussion　from Chapter 5 using the Object-oriented approach to require ments Instructors　can simply choose to emphasize Chapter 6 or Chapter 7 to focus the course on either the traditional or the object approach or both. Chapter 8 Pre sents an overiew of technical environments that affect the generation of altermative sts tem solutions. Then, a comprehensive guide to generating and evaluating alternatives is presented, including the rality that a package solution is always a viable option.
　　Part 3: System Design Tasks
　　Chapter 9 covers system design,including both traditional structured design models and object-oriented models.The instructor can includeeither or both sections Chapter l0 covers database design-relational,hybrid and object oriented databases Again the instsructor can emphasize any or all approaches Chaptr　11 discuses sys tem　inputs and　outputs with particular attention to system controls Capter l2 cov ers human-computer interaction and we include general principles and concepts of dialog design　in addition　to using UML diagrams to model the dialog
　　Part 4: Implemen tation and Support
　　System implementation is increasingly technology specific and because　of the biverse development environments in the real world we decided to streamline the discussion Of implementation. However we did include two chapters on important alternative approaches to implementation Although the text　emphasizes iteration and prototyp ing throughout we include　a comprehensive　discussion of rapid　application, develop ment and component-based development in Chapter l3. Similarly,although package solutions are discussed as viable alternatives throughout we include a detailed　dis cussion　of packages　and enterprise resource　planning (ERP)in　Chapter l4.including specific examples from SAP Chapter l5 provides　an overview Of implementation　and support　that addresses traditional technology　and object technology
　　
Available Support
　　The text includes　a package　of proven supplements　for instructors and students. The Instructor's Resource Kit includes Course Presenter, Course Test Manager, Electronic Instructor's Manual and Figure Files.
　　Course Presenter includes a PowerPoint lecture presentation in outline form with figures for each chapter Coures Test Manager can be used to create paper or LAN-based
tests with multiple-choice fill-in-the-blank, and/or essay questions.The Electronic Instructor's Manual includes suggestions and strategies　for using　the text, test bank ques tions answers to review questions and suggested solutions to chapter exercises and cases. Figure Files allow instructors to create their own presentations using figures from the text.
　　Many instructors like to include software for students to use for exercises　and courseprojects,and this text offers many bundling possibilities. A ppular option to usee for　drawing diagrams is visio Professional 5.0. Some instructors like to emphasize CASE tools and Course Technology can bundle several popular CASE tools with the text,including Oracle Designer,Visible Analyst Student Edition and others Contact Course Technology for the latest information.
　　
Credits and Acknowledgments
　　This project was launched following some initial brainstorming between publisher Kristen Duerr of Course Technology and author John Satzinger.We agreed that an analysis and design text required a major commitment from the publisher and from a team of authors to be competitive. It was agreed that no one person or even pairof authors could complete a text that met the objectives-flexible and streamlined,yet comprehensive and deep. Therefore,Course Technology took an active role in assem bling a team of authors who shared the vision.The senior editor brought in to man age the project　was Jennifer Normandin,who had a major role in bringing　the authors together　and shaping the direction and final form of the text .This text truly could not have been completed without the commitment of Kristen Duerr and the leadership and energy of Jennifer Normandin. We thank them for everything.
　　Another essential member of the team is developmental editor Karen Hill of Elm Street Publishing Services.She collected and digested the comments and reactions of reviewers,provided guidance and design for the features and chapter pedagogy, suggested improvements and refinements to the organization and content, read each draft of each chapter from the perspective of the student to help us be consistent and (to the extent it is humanly possible) edited the chapters to provide a consistent style
　　We also want to thank some other key people for their specific contributions Richard　A Johason of Southwest Missouri State University for writing Chapter 14 on packages and ERP William Baker for contributing material on presentation tech niques and Mario Busjra for designing the RMO Logo and Web site Many other colleagues and friends at SMSU, BYU the University of New Mexico and elsewhere contributed to and supported our work in one way or another. Special thanks also to Lavette Teague,Lorne Olfman and Paul Gray for guidance and inspiration.
　　Many other people were involved in the production of this text.Amanda Young of Course was always available and helpful.Debbie Masi,the production editor came through for us to help sort out the subtleties of diagrams that probably appeared　rather primitive to the artists. the production team went the extra mile to be true to the　diagramming conventions and standards to the extent that we could define them.
　　Last, but certainly not least, we want to thank the reviewers who worked so hard for us beginning with an initial Proposal and continuing all the Way through to the completion of the text It is not easy to review a work in progress, and we were lucky enough to have reviewers with broad perspectives, in-depth knowledge and diverse Preferences. We listened very carefully and the text is much better as a result of their input. The reviewers included:
　　Robert Beatty University of Wisconsin,Milwaukee
　　Paul H. Cheney,University of Central Florida
　　Jon D. Clark Colorado State University
　　David Little High Point University
　　Ellen D. Hoadley Loyola　College in Maryland
　　Robert Keim, Arizona State University
　　Rebecca Koop,Wright State University
　　James E. La University of Wisconsin--Eau Claire
　　George M. Marakas Indiana University
　　Roger McHaney,Kansas State University
　　Bruce Neubauer,Pittsburgh State University
　　Mary Prescott University of South Florida
　　Robert Saldarini, Bergen Community College
　　AII of us involved in the development of this text wish you all the best as you take on the challenge of analysis and design in a changing world.
　　
John Satzinger
Bob Jackson
Steve Burd

PART 1 I The Modern Systems Analyst
CHAPTER l The World of the Modern Systems Analyst
A Systems Analyst　at Rutherford　Manufacturing
The Analyst as a Business Problem Solver
Systems That Solve Business Problems
Required Skills of the Systems Analyst
The Environment Surrounding the Analyst
The Analyst's Role in Strategic Planning
Strategic Systems Plan for Rocky Mountain Outfitters
The Analyst as a System Derelope (The Heart of the Course)
Summary
KeyTerms
Review Questions
Thinking Critically
Experiential Exercises
Case Study
Further Resources
CHAPTER 2 The Analyst as a Project Manager
Blue Sky Family of Mutual Funds: Managing the IRA Project
Systems Development Projects and the SDLC
Project Management
Project Initiation
The Project Planning Phase
Summary
Key Terms
Review Questions
Thinking Critically
Experiential Exercises
Case Study
Further Resources
CHAPTER 3 Approaches to System Development
Development Approaches at Ajax Corporation,Consoiidated Concepts,and Pinnacle
Manufacturing
Methodologies,Models,Tools,and Techniques
Three Approaches to System Development
System Development Life Cycle Variations
Computer-Aided System Engineering (CASE)Tools
Analysis and Design Phases in More Detail
Summary
Key Terms
Review Questions
Thinking Critically
Experiential Exercises
Case Study
Further Resources
CHAPTER 4 Investigating System Requirements
Providing Customer Service-and Gasoline-at Convenience America
Functional and Technical Requirements
Stakeholders--the Source of System Requirements
Identifying System Requirements
Structured　Walkthroughs
Business Process Reengineering
Summary
Key Terms
Review Questions
Thinking Critically
Experiential Exercises
Case Study
Further Resources
CHAPTER 5 Modeling System Requirements:Events and Things
Waiters on Wheels: Computerized Delivery Tracking
Models and Modeling
Events and System Requirements
Things and System Requirements
Data Entities and Objects
The Entity-Relationship Diagram
Where You Are Headed
Summary
Key Terms
Review Questions
Thinking Critically
Experiential Exercises
Case Studies
Further Resources
CHAPER 6 The Traditional Approach to Requirements
Performance Auto Electric: Following the Data Flow
Traditional and Object-Oriented Views of Activities
Data Flow Diagrams
Documenting DFD Components
Information Engineering Models
Considering Locations and Communication through Networks
Work flnow Modeling
Summary
Key Terms
Review Questions
Thinking Critically
Experiential Exercises
Case Studies
Further Resources
CHAPTER 7 The Object-Oriented Approach to Requirements
Northwoods Kayaks:Identifying the Methods within the Objects
The Unified Modeling Language and the Object Management Group
Object-Oriented Requirements
The Class Diagram
The System Activities: An Object-Oriented Use Case/Scenario View
Object Interactions: Collaboration and SequenceDiagrams
Object Behavioc States, State Transitions, and Statechart Diagrams
Summary
KeyTerms
Review Questions
Thinking Critically
Experiential Exercises
Case Studies
Further Resources
CHAPTER 8 Environments Alternatives, and Decisions
Tropic Fish Tales: Netting the Right System
Assessing the Target Processing Environment
Deciding on Scope and Level of Automation
Generating Alternatives for Implementation
Choosing an Alternative for Implementation
Considering Outsourced Solutions.
Presenting the Results and Making the Decisions
Summary
Key Terms
Review Questions
Thinking Critically
Experiential Exercises
Case Study
Further Resources
CHAPTER 9 Moving to Design
New Capital Band:Object-Oriented Denelopment of a Peyroll System
Understanding the Elements of Design
Designing the Application Architecture: The StructuredApproach
Designing the Application Architecture: The Object-Oriented Approach
Coordinating the Project
Summary
KeyTerms
Review Questions
Thinking Critically
Experiential Exercises
Case Studies
FurtherResources
CHAPTER 10 Designing Databases
Nationwide Books: Designing a New Database
Databases and Database Management Systems
Relational Databases
Object-Oriented Datatbase
Hybrid Object-Relational Database Design
Data Types
Distributed Databases
Summary
KeyTerms
Review Questions
Thinking Critically
Experiential Exercises
Case Studies
Further Resources
CHAPTER 11 Designing Inputs Outputs and Coutrols
Customized Cars Clearinghouse:Moving into ElectronicCommerce
Integrity Controls
Design of System Inputs
Design of System Outputs
Summary
Key Terms
Review Questions
Thinking Critically
Experiential Exercises
Case Study
Further Resources
CHAPTER 12 Humau-Computer Interaction
Interface Design at Aviation Electronics
The User Interface
lnterface Design Guidelines
Documenting Dialog Designs
Cuidelines for Designing Windows Forms
Dialog Design for Rocky Mountain Outfitters
Dialog Design for Web Sites
Summary
KeyTerms
Review Questions
Thinking Critically
Experiential　Exercises
Case Studies
Further Resources
PART 4 I Implomontation and Support
CHAPTER l3 Rapid Application Development and Component
Based Development
CDs Direct 2U: Speeding Development of Customer Support System
Rapid Application Devvelopment
Rapid Development Approaches
Rapid Development Techniques
Objed Frameworks
Components
Summary
KeyTerms
Review Questions
Thinking Critically
Experiential Exercises
Case Study
Further Resources
CHAPTER 14 Packaged Software and Enterprise ResourcePlanning
Pizza Amore:Revamping　Systems to Manage More Information
Packaged Software
Enterprise Resource Planning
A Closer Look at One ERP Package: SAP R/3
Summary
KeyTerms
Review Questions
Thinking Critically
Experiential Exercises
Case Study
Further Resources
CHAPTER l5 Making the System Operational (Implementation,
Conversion and Support)
Tri-State Heating Oil: Juggling Priorities to Begin Operation
Program Derelopment
Quality Assurance
Installation
Documentation
Training and User Support
Maintenance
Summary
KeyTerms
Review Questions
Thinking Critically
Faperiential Exercises
Case Studies
Further Resources
APPENDICES
APPENDIX A The Responsibilities of a Project Manager
Providing Leadership and Vision
Planning and Organizing the Project
Organizing and Managing the Projed Team
Estimating Costs and Developing the Project Budget
Monitoring and Controlling the Project Schedule
Ensuring the Quality of the Final Result
KeyTerms
Review Questions
Application Questions
APPENDIX B Calculating Net Present Value, Payback Period,
and Return on Investment
Net Present Value Calculations
Payback Period Calculations
Return on Investment
key Terms
Review Questions
Thinking Critically
APPENDIX C Developing a Project Schedule with PERT/CPM Charts
Building PERT/CPM Charts
Creating the RMO Project Schedule with Microsoft Project
Key Terms
Review Questions
Thinking Critically
APPENDlX D Presenting the Results to Management
Preparing the Prerentation
Giving the Presentation
Use of Visual Aids
Questions and Answers
INDEX