Professional Documents
Culture Documents
CIS 145 Kendall7e - ch01
CIS 145 Kendall7e - ch01
Assuming the Role of Learning Objectives
the Systems Analyst 1
• Recall the basic types of computerbased systems
that a systems analyst needs to address
• Understand how users working in context with new
technologies change the dynamics of a system
• Realize what the many roles of the systems analyst
are
• Know the steps of the SDLC as they relate to HCI and
how to apply them to a real system
Systems Analysis and Design, 7e • Understand what CASE tools are and how they help a
systems analyst
Kendall & Kendall • Explore other methodologies such as objectoriented
systems design and prototyping
©2008 Pearson Prentice Hall
Kendall & Kendall 12
Information – A Key Resource Major Topics
• Fuels business and can be the critical • Fundamentals of different kinds of
factor in determining the success or information systems
failure of a business • Roles of systems analysts
• Needs to be managed correctly • Phases in the systems development life
• Managing computergenerated cycle as they relate to Human
information differs from handling Computer Interaction (HCI) factors
manually produced data • ComputerAided Software Engineering
(CASE) tools
Kendall & Kendall 13 Kendall & Kendall 14
Systems Analysts Recommend, Design, and A systems analyst
may be involved with
Maintain Many Types of Systems for Users Strategic
any or all of these
Level
systems at each
organization level
• Transaction Processing Systems (TPS)
Higher
• Office Automation Systems (OAS) Level
• Knowledge Work Systems (KWS)
• Management Information Systems (MIS) Knowledge
Level
• Decision Support Systems (DSS)
• Expert Systems (ES) Operational
• Executive Support Systems (ESS) Level
• Group Decision Support Systems (GDSS)
• ComputerSupported Collaborative Work Systems
(CSCWS)
1
1/28/2008
Operational Level Knowledge Level
• Transaction Processing System (TPS) • Office Automation System (OAS)
• Process large amounts of data for routine business • Supports data workers who share information, but do not
usually create new knowledge
transactions
• Examples: Word processing, Spreadsheets, Desktop
• Boundaryspanning publishing, Electronic scheduling, Communication through
• Support the daytoday operations of the company voice mail, Email, Video conferencing
• Examples: Payroll Processing, Inventory • Knowledge Work System (KWS)
Management • Supports professional workers such as scientists, engineers,
and doctors
• Examples: computeraided design systems, virtual reality
systems, investment workstations
Higher Level Strategic Level
• Management Information System (MIS) • Executive Support System (ESS)
• Support a broad spectrum of organizational tasks including • Helps executives to make unstructured strategic decisions in
decision analysis and decision making an informed way
• Examples: profit margin by sales region, expenses vs. • Examples: drilldown analysis, status access
budgets
• Group Decision Support System (GDSS)
• Decision Support System (DSS) • Permit group members to interact with electronic support
• Aids decision makers in the making of decisions • Examples: email, Lotus Notes
• Examples: financial planning with whatif analysis, budgeting
with modeling • ComputerSupported Collaborative Work System
• Expert System (ES) (CSCWS)
• CDCWS is a more general term of GDSS
• Captures and uses the knowledge of an expert for solving a
particular problem which leads to a conclusion or • May include software support called “groupware” for team
recommendation collaboration via network computers
• Examples: MYCIN, XCON • Example: video conferencing, Web survey system
Integrating New Technologies Figure 1.2 Systems analysts need to be aware
that integrating technologies affects all types of
into Traditional Systems systems
• Ecommerce and Web Systems
• Enterprise Resource Planning Systems
• Wireless Systems
• Open Source Software
• Need for Systems Analysis and Design
2
1/28/2008
Ecommerce and Web Systems Enterprise Resource Planning
Systems (ERP)
• Benefits • Performs integration of many
• Increasing user awareness of the availability of a information systems existing on
service, product, industry, person, or group
different management levels and within
• The possibility of 24hour access for users
• Improving the usefulness and usability of interface
different functions
design • Example: SAP, Oracle
• Creating a system that can extend globally rather
than remain local, thus reaching people in remote
locations without worry of the time zone in which
they are located
Wireless Systems Open Source Software
• System analyst may be asked to design • An alternative of traditional software
standard or wireless communication networks development where proprietary code is
that integrate voice, video and email into hidden from the users
organizational intranets or industry extranets • Open source software is free to distribute,
• System analyst may also be asked to develop share and modify
intelligent agents • Characterized as a philosophy rather than
• Example: Microsoft's new software based on simply the process of creating new software
Bayesian statistics • Example: Linux Operating System, Apache
• Wireless communication is referred as m Web Server, Mozilla Firefox Web browser
commerce (mobile commerce)
Kendall & Kendall 115 Kendall & Kendall 116
Need for Systems Analysis and Roles of the Systems Analyst
Design
• Installing a system without proper planning • The analyst must be able to work with
leads to great user dissatisfaction and people of all descriptions and be
frequently causes the system to fall into experienced in working with computers
disuse
• Lends structure to the analysis and design of
• Three primary roles:
information systems • Consultant
• A series of processes systematically • Supporting Expert
undertaken to improve a business through • Agent of change
the use of computerized information systems
Kendall & Kendall 117 Kendall & Kendall 118
3
1/28/2008
Qualities of the Systems Analyst Systems Development Life Cycle
(SDLC)
• Problem solver • The systems development life cycle is a
• Communicator phased approach to solving business
• Strong personal and professional ethics problems
• Selfdisciplined and selfmotivated • Developed through the use of a specific
cycle of analyst and user activities
• Each phase has unique user activities
Figure 1.3 The seven phases of the Incorporating HumanComputer
systems development life cycle Interaction (HCI) Considerations
• The demand for analysts who are
capable of incorporating HCI into the
systems development process keeps
increasing, as companies begin to
realize that the quality of systems and
the quality of work life can be improved
by taking a humancentered approach
at the outset of a project
Identifying Problems, Determining Human Information
Opportunities, and Objectives Requirements
• Activity: • Activity:
• Interviewing
• Interviewing user management • Sampling and investing hard data
• Summarizing the knowledge obtained • Questionnaires
• Estimating the scope of the project • Observe the decision maker’s behavior and environment
• Prototyping
• Documenting the results • Learn the who, what, where, when, how, and why of the
• Output: current system
• Feasibility report containing problem definition and • Output:
• Analyst understands how users accomplish their work when
objective summaries from which management can interacting with a computer; and begin to know how to
make a decision on whether to proceed with the make the new system more useful and usable. The analyst
proposed project should also know the business functions and have complete
information on the people, goals, data and procedure
involved
4
1/28/2008
Analyzing System Needs Designing the Recommended
System
• Activity: • Activity:
• Create data flow diagrams • Design procedures for data entry
• Complete the data dictionary • Design the humancomputer interface
• Analyze the structured decisions made • Design system controls
• Prepare and present the system proposal • Design files and/or database
• Design backup procedures
• Output:
• Recommendation on what, if anything, • Output
should be done • Model of the actual system
Developing and Documenting Testing and Maintaining the
Software System
• Activity: • Activity:
• System analyst works with programmers to develop any
original software • Test the information system
• Works with users to develop effective documentation • System maintenance
• Programmers design, code, and remove syntactical errors
from computer programs
• Maintenance documentation
• Document software with help files, procedure manuals,
and Web sites with Frequently Asked Questions
• Output:
• Output: • Problems, if any
• Computer programs • Updated programs
• System documentation • Documentation
Figure 1.4 Some researchers estimate that the amount of
Implementing and Evaluating the time spent on systems maintenance may be as much as 60
System percent of the total time spent on systems projects
• Activity:
• Train users
• Analyst plans smooth conversion from old
system to new system
• Review and evaluate system
• Output:
• Trained personnel
• Installed system
5
1/28/2008
The Impact of Maintenance Figure 1.5 Resource consumption
over the system life
• Maintenance is performed for two
reasons
• Removing software errors, and
• Enhancing existing software
• Over time the cost of continued
maintenance will be greater than that of
creating an entirely new system. At that
point it becomes more feasible to
perform a new systems study
Approaches to Structured Analysis and Design
and to the Systems Development Life Cycle
Case Tools
• Traditional systems development • CASE tools are productivity tools for
systems analysts that have been created
life cycle explicitly to improve their routine work
• CASE systems development life through the use of automated support
cycle • Reasons for using CASE tools
• Increasing Analyst Productivity
• ObjectOriented Systems Analysis • Improving AnalystUser Communication
and Design • Integrating Life Cycle Activities
• Accurately Assessing Maintenance Changes
Case Tool Classifications Upper CASE Tools
• Upper CASE tools perform analysis • Create and modify the system
and design design
• Lower CASE tools generate • Help in modeling organizational
programs from CASE design requirements and defining system
• Integrated CASE tools perform both boundaries
upper and lower CASE functions • Can also support prototyping of
screen and report designs
Kendall & Kendall 135 Kendall & Kendall 136
6
1/28/2008
Lower CASE Tools Figure 1.7 Traditional versus CASE
systems development life cycle
• Lower CASE tools generate
computer source code from the
CASE design
• Source code is usually generated in
several languages
ObjectOriented Systems Analysis Alternate Approaches to Structured Analysis
and Design and to the Systems Development
and Design Life Cycle
• Alternate approach to the structured approach of • Agile approach
the SDLC that is intended to facilitate the
development of systems that must change • Prototyping
rapidly in response to dynamic business
environments • ETHICS
• Analysis is performed on a small part of the
system followed by design and implementation. • Project champion
The cycle repeats with analysis, design and • Soft Systems Methodology
implementation of the next part and this repeats
until the project is complete • Multiview
Summary
• Information is a key resource
• Systems analysts deal with many types of
information systems
• Integration of traditional systems with new
technologies
• Roles and qualities of the systems analyst
• The systems Development Life Cycle
• CASE tools
• Alternatives to structured analysis and design
and to the SDLC
Kendall & Kendall 141
7