SlideShare a Scribd company logo
1 of 37
Chapter 1 
Assuming the Role of the 
Systems Analyst 
Systems Analysis and Design 
Kendall and Kendall 
Fifth Edition
Major Topics 
Information systems 
Phases of analysis and design 
System maintenance 
CASE tools 
Alternate methodologies 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-2
Information 
Information is an organizational 
resource which must be managed as 
carefully as other resources 
Costs are associated with information 
processing 
Information processing must be 
managed to take full advantage of its 
potential 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-3
Categories 
Information systems fall into one of the 
following eight categories: 
Transaction processing systems (TPS) 
Office automation systems (OAS) 
Knowledge work systems (KWS) 
Management information systems (MIS) 
Decision support systems (DSS) 
Expert systems (ES) 
Group decision support systems (GDSS) 
 Executive support systems (EES) 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-4
New Technologies 
New technologies are being integrated 
into traditional systems 
Ecommerce uses the Web to perform business 
activities 
Enterprise Resource Planning (ERP) has the 
goal of integrating many different information 
systems within the corporation 
Wireless and handheld devices, including 
mobile commerce (mcommerce) 
Open source software 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-5
Advantages of Using the Web 
Increasing awareness of the availability 
of the service, product, industry, 
person, or group 
24-hour access for users 
Standard interface design 
Creating a global system 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-6
Nature of Analysis and Design 
Systems analysis and design is a 
systematic approach to identifying 
problems, opportunities, and objectives; 
analyzing the information flows in 
organizations; and designing 
computerized information systems to 
solve a problem 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-7
Systems Analyst 
Systems analysts act as 
Outside consultants to businesses 
Supporting experts within a business 
As change agents 
Analysts are problem solvers, and 
require communication skills 
Analysts must be ethical with users and 
customers 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-8
Systems Development Life 
Cycle 
The systems development life cycle is a 
systematic approach to solving business 
problems 
It is divided into seven phases 
Each phase has unique activities 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-9
Phase 1 
 Identifying 
Problems 
Opportunities 
Objectives 
Personnel involved 
Analyst 
User management 
Systems management 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-10
Phase 2 
Determining information requirements 
Interview management, operations 
personnel 
Gather systems/operating documents 
Use questionnaires 
Observe the system and personnel involved 
Learn the who, what, where, when, and 
how, and the why for each of these 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-11
Phase 2 
Personnel involved 
Analyst 
User management 
User operations workers 
Systems management 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-12
Phase 3 
Analyzing system needs 
Create data flow diagrams 
Document procedural logic for data flow 
diagram processes 
Complete the data dictionary 
Make semistructured decisions 
Prepare and present the system proposal 
Recommend the optimal solution to 
management 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-13
Phase 3 
Personnel involved 
Analyst 
User management 
Systems management 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-14
Phase 4 
Designing the recommended system 
Design the user interface 
Design output 
Design input 
Design system controls 
Design files and/or database 
Produce program specifications 
Produce decision trees or tables 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-15
Phase 4 
Personnel involved 
Analyst 
System designer 
User management 
User operations workers 
Systems management 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-16
Phase 5 
Developing and documenting software 
Design computer programs using structure 
charts, Nassi-Schneiderman charts, and 
pseudocode 
Walkthrough program design 
Write computer programs 
Document software with help files, 
procedure manuals, and Web sites with 
Frequently Asked Questions 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-17
Phase 5 
Personnel involved 
Analyst 
System designer 
Programmers 
Systems management 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-18
Phase 6 
Testing and maintaining the system 
Test and debug computer programs 
Test the computer system 
Enhance system 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-19
Phase 6 
Personnel involved 
Analyst 
System designer 
Programmers 
Systems management 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-20
Phase 7 
Implementing and evaluating the 
system 
Plan conversion 
Train users 
Purchase and install new equipment 
Convert files 
Install system 
Review and evaluate system 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-21
Phase 7 
Personnel involved 
Analyst 
System designer 
Programmers 
User management 
User operations workers 
Systems management 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-22
Rapid Application Development 
Rapid Application development (RAD) is 
an object-oriented approach to systems 
development 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-23
System Maintenance 
System maintenance is 
Removing undetected errors, and 
Enhancing existing software 
Time spent on maintenance typically 
ranges from 48-60 percent of total time 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-24
System Enhancements 
Systems are enhanced for the following 
reasons: 
Adding additional features to the system 
Business and governmental requirements 
change over time 
Technology, hardware, and software are 
rapidly changing 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-25
CASE Tools 
CASE tools are automated, microcomputer-based 
software packages for systems 
analysis and design 
Four reasons for using CASE tools are: 
To increase analyst productivity 
Facilitate communication among analysts and 
users 
Providing continuity between life cycle phases 
To assess the impact of maintenance 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-26
CASE Tool Categories 
CASE tools may be divided into several 
categories 
Upper CASE (also called front-end CASE) 
tools, used to perform analysis and design 
Lower CASE (also called back-end CASE). 
These tools generate computer language 
source code from CASE design 
Integrated CASE, performing both upper 
and lower CASE functions 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-27
Upper CASE 
Upper CASE tools 
Create and modify the system design 
Store data in a project repository 
The repository is a collection of records, 
elements, diagrams, screens, reports, and 
other project information 
These CASE tools model organizational 
requirements and define system 
boundaries 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-28
Lower CASE 
Lower CASE tools generate computer 
source code from the CASE design 
Source code may usually be generated 
in several languages 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-29
Advantages of Generating 
Code 
Time to develop new systems decreases 
The time to maintain generated code is 
less than to maintain traditional systems 
Computer programs may be generated in 
more than one language 
CASE design may be purchased from third-party 
vendors and tailored to 
organizational needs 
Generated code is free from program 
coding errors 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-30
Reverse Engineering 
Reverse engineering is generating the 
CASE design from computer program 
code 
Source code is examined, analyzed, and 
converted into repository entities 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-31
Reverse Engineering Produces 
Reverse engineering produces 
(depending on the tool set used) 
Data structures and elements, describing 
the files, records, and field 
Screen designs, if the program is online 
Report layouts for batch programs 
A structure chart showing the hierarchy of 
the modules in the program 
Database design and relationships 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-32
Advantages of Reverse 
Engineering 
It has the following advantages: 
Reduced system maintenance time 
Program documentation is produced for 
loosely documented programs 
Structured programs may be generated 
from unstructured, older programs 
Future system maintenance is easier to 
implement 
Unused portions of programs may be 
eliminated 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-33
Object-Oriented Analysis and 
Design 
Object-oriented (O-O) analysis and 
design is used to build object-oriented 
programs 
This includes not only data but the 
instructions about operations that 
manipulate the data 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-34
Types of Object-Oriented 
Analysis and Design 
There are three types of object-oriented 
analysis and design: 
Object-oriented analysis (OOA) 
Object-oriented design (OOD) 
The Unified Modeling Language (UML), a 
standardized object-oriented modeling 
language 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-35
Nature of Analysis and Design 
Structured analysis and design provides 
a systematic approach to developing 
systems and is cyclic in nature 
Analysis and design errors detected in 
the later phases of the systems 
development life cycle cost more to fix 
than if detected in earlier phases 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-36
Alternate Methodologies 
Alternate methodologies are available 
for analyzing systems 
These include 
Prototyping 
ETHICS 
Project champions 
Soft Systems Methodology 
Multi-view 
Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-37

More Related Content

What's hot (20)

Chap22
Chap22Chap22
Chap22
 
Chap02
Chap02Chap02
Chap02
 
Chap11
Chap11Chap11
Chap11
 
Chap09
Chap09Chap09
Chap09
 
Chap04
Chap04Chap04
Chap04
 
Kendall sad8e ch03
Kendall sad8e ch03Kendall sad8e ch03
Kendall sad8e ch03
 
Chap15
Chap15Chap15
Chap15
 
Chap13
Chap13Chap13
Chap13
 
Chap17
Chap17Chap17
Chap17
 
Chap16
Chap16Chap16
Chap16
 
Chap10
Chap10Chap10
Chap10
 
Chap01
Chap01Chap01
Chap01
 
Kendall sad8e ch01
Kendall sad8e ch01Kendall sad8e ch01
Kendall sad8e ch01
 
Chap19
Chap19Chap19
Chap19
 
Kendall7e ch05
Kendall7e ch05Kendall7e ch05
Kendall7e ch05
 
Kendall7e ch02
Kendall7e ch02Kendall7e ch02
Kendall7e ch02
 
Projman
ProjmanProjman
Projman
 
Ch07-Moving into Design
Ch07-Moving into DesignCh07-Moving into Design
Ch07-Moving into Design
 
Ch10-Program Design
Ch10-Program DesignCh10-Program Design
Ch10-Program Design
 
Useanalysis
UseanalysisUseanalysis
Useanalysis
 

Similar to Chap01

chapter01 The Systems Development Environment.ppt
chapter01 The Systems Development Environment.pptchapter01 The Systems Development Environment.ppt
chapter01 The Systems Development Environment.pptTupulupus Asin
 
System analysis and design
System analysis and designSystem analysis and design
System analysis and designRobinsonObura
 
Kendall7e ch01
Kendall7e ch01Kendall7e ch01
Kendall7e ch01sayAAhmad
 
Analisis dan Perancangan Sistem - 1 - Kendall7e ch01
Analisis dan Perancangan Sistem - 1 - Kendall7e ch01Analisis dan Perancangan Sistem - 1 - Kendall7e ch01
Analisis dan Perancangan Sistem - 1 - Kendall7e ch01Ullum Pratiwi
 
Chap12 Developing Business It Solutions[1]
Chap12 Developing Business It Solutions[1]Chap12 Developing Business It Solutions[1]
Chap12 Developing Business It Solutions[1]sihamy
 
8.2 system analysis and design
8.2 system analysis and design8.2 system analysis and design
8.2 system analysis and designKhan Yousafzai
 
Project initiation
Project initiationProject initiation
Project initiationukrulz4u
 
Different Approaches To Sys Bldg
Different Approaches To Sys BldgDifferent Approaches To Sys Bldg
Different Approaches To Sys BldgUSeP
 

Similar to Chap01 (20)

chapter01 The Systems Development Environment.ppt
chapter01 The Systems Development Environment.pptchapter01 The Systems Development Environment.ppt
chapter01 The Systems Development Environment.ppt
 
Role of System Analysis & Design
Role of System Analysis & DesignRole of System Analysis & Design
Role of System Analysis & Design
 
PPT01
PPT01PPT01
PPT01
 
James hall ch 14
James hall ch 14James hall ch 14
James hall ch 14
 
System analysis and design
System analysis and designSystem analysis and design
System analysis and design
 
Kendall7e ch01
Kendall7e ch01Kendall7e ch01
Kendall7e ch01
 
Analisis dan Perancangan Sistem - 1 - Kendall7e ch01
Analisis dan Perancangan Sistem - 1 - Kendall7e ch01Analisis dan Perancangan Sistem - 1 - Kendall7e ch01
Analisis dan Perancangan Sistem - 1 - Kendall7e ch01
 
Chap12 Developing Business It Solutions[1]
Chap12 Developing Business It Solutions[1]Chap12 Developing Business It Solutions[1]
Chap12 Developing Business It Solutions[1]
 
8.2 system analysis and design
8.2 system analysis and design8.2 system analysis and design
8.2 system analysis and design
 
Ppt 21 ge
Ppt 21 gePpt 21 ge
Ppt 21 ge
 
Project initiation
Project initiationProject initiation
Project initiation
 
Ch07
Ch07Ch07
Ch07
 
Plm rev5 innovation 2012
Plm rev5 innovation 2012Plm rev5 innovation 2012
Plm rev5 innovation 2012
 
architectures of erp systems
architectures of erp systemsarchitectures of erp systems
architectures of erp systems
 
Information systems
Information systemsInformation systems
Information systems
 
BIS Ch 4.ppt
BIS Ch 4.pptBIS Ch 4.ppt
BIS Ch 4.ppt
 
Intro_toDB.ppt
Intro_toDB.pptIntro_toDB.ppt
Intro_toDB.ppt
 
Chapter01
Chapter01Chapter01
Chapter01
 
lecture_29.pptx
lecture_29.pptxlecture_29.pptx
lecture_29.pptx
 
Different Approaches To Sys Bldg
Different Approaches To Sys BldgDifferent Approaches To Sys Bldg
Different Approaches To Sys Bldg
 

Chap01

  • 1. Chapter 1 Assuming the Role of the Systems Analyst Systems Analysis and Design Kendall and Kendall Fifth Edition
  • 2. Major Topics Information systems Phases of analysis and design System maintenance CASE tools Alternate methodologies Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-2
  • 3. Information Information is an organizational resource which must be managed as carefully as other resources Costs are associated with information processing Information processing must be managed to take full advantage of its potential Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-3
  • 4. Categories Information systems fall into one of the following eight categories: Transaction processing systems (TPS) Office automation systems (OAS) Knowledge work systems (KWS) Management information systems (MIS) Decision support systems (DSS) Expert systems (ES) Group decision support systems (GDSS)  Executive support systems (EES) Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-4
  • 5. New Technologies New technologies are being integrated into traditional systems Ecommerce uses the Web to perform business activities Enterprise Resource Planning (ERP) has the goal of integrating many different information systems within the corporation Wireless and handheld devices, including mobile commerce (mcommerce) Open source software Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-5
  • 6. Advantages of Using the Web Increasing awareness of the availability of the service, product, industry, person, or group 24-hour access for users Standard interface design Creating a global system Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-6
  • 7. Nature of Analysis and Design Systems analysis and design is a systematic approach to identifying problems, opportunities, and objectives; analyzing the information flows in organizations; and designing computerized information systems to solve a problem Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-7
  • 8. Systems Analyst Systems analysts act as Outside consultants to businesses Supporting experts within a business As change agents Analysts are problem solvers, and require communication skills Analysts must be ethical with users and customers Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-8
  • 9. Systems Development Life Cycle The systems development life cycle is a systematic approach to solving business problems It is divided into seven phases Each phase has unique activities Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-9
  • 10. Phase 1  Identifying Problems Opportunities Objectives Personnel involved Analyst User management Systems management Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-10
  • 11. Phase 2 Determining information requirements Interview management, operations personnel Gather systems/operating documents Use questionnaires Observe the system and personnel involved Learn the who, what, where, when, and how, and the why for each of these Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-11
  • 12. Phase 2 Personnel involved Analyst User management User operations workers Systems management Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-12
  • 13. Phase 3 Analyzing system needs Create data flow diagrams Document procedural logic for data flow diagram processes Complete the data dictionary Make semistructured decisions Prepare and present the system proposal Recommend the optimal solution to management Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-13
  • 14. Phase 3 Personnel involved Analyst User management Systems management Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-14
  • 15. Phase 4 Designing the recommended system Design the user interface Design output Design input Design system controls Design files and/or database Produce program specifications Produce decision trees or tables Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-15
  • 16. Phase 4 Personnel involved Analyst System designer User management User operations workers Systems management Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-16
  • 17. Phase 5 Developing and documenting software Design computer programs using structure charts, Nassi-Schneiderman charts, and pseudocode Walkthrough program design Write computer programs Document software with help files, procedure manuals, and Web sites with Frequently Asked Questions Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-17
  • 18. Phase 5 Personnel involved Analyst System designer Programmers Systems management Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-18
  • 19. Phase 6 Testing and maintaining the system Test and debug computer programs Test the computer system Enhance system Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-19
  • 20. Phase 6 Personnel involved Analyst System designer Programmers Systems management Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-20
  • 21. Phase 7 Implementing and evaluating the system Plan conversion Train users Purchase and install new equipment Convert files Install system Review and evaluate system Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-21
  • 22. Phase 7 Personnel involved Analyst System designer Programmers User management User operations workers Systems management Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-22
  • 23. Rapid Application Development Rapid Application development (RAD) is an object-oriented approach to systems development Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-23
  • 24. System Maintenance System maintenance is Removing undetected errors, and Enhancing existing software Time spent on maintenance typically ranges from 48-60 percent of total time Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-24
  • 25. System Enhancements Systems are enhanced for the following reasons: Adding additional features to the system Business and governmental requirements change over time Technology, hardware, and software are rapidly changing Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-25
  • 26. CASE Tools CASE tools are automated, microcomputer-based software packages for systems analysis and design Four reasons for using CASE tools are: To increase analyst productivity Facilitate communication among analysts and users Providing continuity between life cycle phases To assess the impact of maintenance Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-26
  • 27. CASE Tool Categories CASE tools may be divided into several categories Upper CASE (also called front-end CASE) tools, used to perform analysis and design Lower CASE (also called back-end CASE). These tools generate computer language source code from CASE design Integrated CASE, performing both upper and lower CASE functions Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-27
  • 28. Upper CASE Upper CASE tools Create and modify the system design Store data in a project repository The repository is a collection of records, elements, diagrams, screens, reports, and other project information These CASE tools model organizational requirements and define system boundaries Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-28
  • 29. Lower CASE Lower CASE tools generate computer source code from the CASE design Source code may usually be generated in several languages Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-29
  • 30. Advantages of Generating Code Time to develop new systems decreases The time to maintain generated code is less than to maintain traditional systems Computer programs may be generated in more than one language CASE design may be purchased from third-party vendors and tailored to organizational needs Generated code is free from program coding errors Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-30
  • 31. Reverse Engineering Reverse engineering is generating the CASE design from computer program code Source code is examined, analyzed, and converted into repository entities Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-31
  • 32. Reverse Engineering Produces Reverse engineering produces (depending on the tool set used) Data structures and elements, describing the files, records, and field Screen designs, if the program is online Report layouts for batch programs A structure chart showing the hierarchy of the modules in the program Database design and relationships Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-32
  • 33. Advantages of Reverse Engineering It has the following advantages: Reduced system maintenance time Program documentation is produced for loosely documented programs Structured programs may be generated from unstructured, older programs Future system maintenance is easier to implement Unused portions of programs may be eliminated Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-33
  • 34. Object-Oriented Analysis and Design Object-oriented (O-O) analysis and design is used to build object-oriented programs This includes not only data but the instructions about operations that manipulate the data Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-34
  • 35. Types of Object-Oriented Analysis and Design There are three types of object-oriented analysis and design: Object-oriented analysis (OOA) Object-oriented design (OOD) The Unified Modeling Language (UML), a standardized object-oriented modeling language Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-35
  • 36. Nature of Analysis and Design Structured analysis and design provides a systematic approach to developing systems and is cyclic in nature Analysis and design errors detected in the later phases of the systems development life cycle cost more to fix than if detected in earlier phases Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-36
  • 37. Alternate Methodologies Alternate methodologies are available for analyzing systems These include Prototyping ETHICS Project champions Soft Systems Methodology Multi-view Kendall & Kendall Copyright © 2002 by Prentice Hall, Inc. 1-37