1

Systems, Roles, and

Development
Methodologies
Systems Analysis and Design, 8e
Kendall & Kendall

Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall

 Learning Objectives

• Recall the basic types of computer-based 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
system analyst are.
• Comprehend the fundamentals of three development
methodologies: SDLC, the agile approach, and
object-oriented systems analysis and design .
• Understand what CASE tools are and how they help
a systems analyst.

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-2
 Information—A Key Resource

• Fuels business and can be the critical

factor in determining the success or
failure of a business
• Needs to be managed correctly
• Managing computer-generated
information differs from handling
manually produced data

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-3
 Major Topics

• Fundamentals of different kinds of

information systems
• Roles of systems analysts
• Phases in the systems development life cycle as
they relate to Human-Computer Interaction
(HCI) factors
• Computer-Aided Software Engineering
(CASE) tools
Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-4
 Systems Analysts Recommend, Design, and
Maintain Many Types of Systems for Users

• Transaction Processing Systems (TPS)

• Office Automation Systems (OAS)
• Knowledge Work Systems (KWS)
• Management Information Systems (MIS)
• Decision Support Systems (DSS)
• Expert Systems (ES)
• Executive Support Systems (ESS)
• Group Decision Support Systems (GDSS)
• Computer-Supported Collaborative Work Systems
(CSCWS)

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-5
 A systems analyst
m ay be involved in
Strategic any or all of these
Level
systems at each
organization level.
Higher
Level

Knowledge
Level

Operational
Level

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-6
 Operational Level

• Transaction Processing System (TPS)

• Process large amounts of data for routine
business transactions
• Boundary-spanning
• Support the day-to-day operations of the company
• Examples: Payroll Processing, Inventory
Management

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-7
 Knowledge Level

• Office Automation System (OAS)

• Supports data workers who share information, but do not
usually create new knowledge
• Examples: word processing, spreadsheets, desktop
publishing, electronic scheduling, communication through
voice mail, email, teleconferencing
• Knowledge Work System (KWS)
• Supports professional workers such as scientists, engineers,
and doctors
• Examples: computer-aided design systems, virtual reality
systems, investment workstations

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-8
 Higher Level

• Management Information System (MIS)

• Supports a broad spectrum of organizational tasks including
decision analysis and decision making
• Examples: profit margin by sales region, expenses vs. budgets
• Decision Support System (DSS)
• Aids decision makers in the making of decisions
• Examples: financial planning with what-if analysis,
budgeting with modeling
• Expert System (ES) and Artificial Intelligence
• Captures and uses the knowledge of an expert for solving a particular
problem which leads to a conclusion or recommendation
• Researching understanding natural language and the ability to reason
through a problem to its logical conclusion

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-9
 Strategic Level

• Executive Support System (ESS)

• H elps executives to make unstructured strategic
decisions in an informed way
• Examples: drill-down analysis, status access
• Group Decision Support System (GDSS)
• Permit group members to interact with electronic support.
• Examples: email, Lotus Notes
• Computer-Supported Collaborative Work System
(CSCWS)
• CSCWS is a more general term of GDSS.
• May include software support
called groupware for team
• collaboration via network
computers
Example: video conferencing, Web survey system
Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-10
 Integrating New Technologies into
Traditional Systems
• Ecommerce and Web Systems
• Enterprise Resource Planning Systems
• Wireless and Mobile Systems
• Open Source Software
• Need for Systems Analysis and Design

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-11
 Systems Analysts Need to Be Aware that
Integrating Technologies Affects all Types of
System (Figure 1.2)
s

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-12
 Ecommerce and Web
Systems
• Benefits
• Increasing user awareness of the availability of a
service, product, industry, person, or group
• The possibility of 24-hour access for users
• Improving the usefulness and usability of interface
design
• 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

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-13
 Enterprise Resource Planning
Systems (ERP)
• Performs integration of many
information systems existing on
different management levels and within
different functions.

• Example: SAP, Oracle

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-14
 Wireless and Mobile Systems

• A system analyst may be asked to design

standard or wireless and mobile
communication networks that
integrate voice, video, and email
into organizational intranets or
industry extranets
•
A system analyst may also be asked to
develop intelligent agents.
•
Example: iPhone, iPod, BlackBerry
• Wireless communication is referred to
as m-commerce (mobile commerce)
Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-15
 Open Source
Software
• An alternative of traditional software
development where proprietary code is
hidden from the users
• Open source software is free to distribute,
share, and modify.
• Characterized as a philosophy rather than simply
the process of creating new software
• Example: Linux Operating System, Apache
Web Server, Mozilla Firefox Web Browser

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-16
 Need for Systems Analysis and
Design
• Installing a system without proper planning
leads to great user dissatisfaction and
frequently causes the system to fall into
disuse.
• Lends structure to the analysis and design of
information systems
• A series of processes systematically
undertaken to improve a business through the
use of computerized information systems

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-17
 with computers.

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-18
 Roles of the Systems Analyst

• The analyst must be able to work with

people of all descriptions and be
experienced in working with computers.
• Three primary roles:
• Consultant
• Supporting expert
• Agent of change

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-18
 Qualities of the Systems Analyst

• Problem solver
• Communicator
• Strong personal and professional ethics
• Self-disciplined and self-motivated

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-19
 Systems Development Life Cycle
(SDLC)
• The systems development life cycle is a
phased approach to solving business
problems.
• Developed through the use of a specific
cycle of analyst and user activities
• Each phase has unique user activities.

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-20
 The Seven Phases of the Systems
Development Life Cycle (Figure 1.3)

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-21
The SDLC in Four Steps

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-21
SDLC Output per phase

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-21
 Incorporating Human-Computer
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 human-centered approach at the outset of a
project.

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-22
 1. Identifying Problems,
Opportunities, and Objectives
• Activity
• Interviewing user management
• Summarizing the knowledge obtained
• Estimating the scope of the project
• Documenting the results
• Output:
• Feasibility report containing problem definition and
objective summaries from which management can
make a decision on whether to proceed with the
proposed project

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-23
 2. Determining Human Information
Requirements
• Activity:
• Interviewing
• Sampling and investing hard data
• Questionnaires
• O bserve th e decisio n m aker’s behavio rand environm ent.
• Prototyping
• Learn the who, what, where, when, how, and why of the
current system.
• Output:
• The analyst understands how users accomplish their work
when interacting with a computer; and begin to know how to
make the new system more useful and usable. The analyst
should also know the business functions and have complete
information on the people, goals, data, and procedure
involved.
Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-24
 3. Analyzing System Needs

• Activity:
• Create data flow, activity, or sequence
diagrams.
• Complete the data dictionary.
• Analyze the structured decisions made.
• Prepare and present the system proposal.
• Output:
• Recommendation on what, if anything,
should be done

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-25
 4. Designing the Recommended
System
• Activity:
• Design procedures for data entry.
• Design the human-computer interface.
• Design system controls.
• Design database and/or files.
• Design backup procedures.
• Output
• Model of the actual system

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-26
 5. Developing and Documenting
Software
• Activity:
• System analyst works with programmers to develop
any original software.
• Works with users to develop effective documentation.
• Programmers design, code, and remove syntactical
errors from computer programs.
• Document software with help files, procedure manuals,
and Web sites with Frequently Asked Questions.
• Output:
• Computer programs
• System documentation

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-27
 6. Testing and Maintaining the
System
• Activity
• Test the information system.
• System maintenance.
• Maintenance documentation.
• Output:
• Problems, if any
• Updated programs
• Documentation

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-28
 7. Implementing and Evaluating
the System

• Activity:
• Train users.
• Analyst plans smooth conversion from old
system to new system.
• Review and evaluate system.
• Output:
• Trained personnel
• Installed system

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-29
 Some Researchers Estimate that the Amount of Time Spent
on Systems Maintenance May Be as Much as 60 Percent of
the Total Time Spent on Systems Projects (Figure 1.4)

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-30
 The Impact of Maintenance

• Maintenance is performed for two

reasons:
• Removing software errors
• 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.

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-31
 Resource Consumption over the
System Life (Figure 1.5)

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-32
 Approaches to Structured Analysis and Design
and to the Systems Development Life Cycle

• Traditional systems development

life cycle
• C A S E system s develop m e n t
life cycle
• Object-oriented systems analysis
and design

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-33
 Case Tools

• CASE tools are productivity tools for systems

analysts that have been created explicitly to
improve their routine work through the use of
automated support.

• Reasons for using CASE tools

• Increasing analyst productivity
• Improving analyst-user communication
• Integrating life cycle activities

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-34
 Case Tool Classifications

• Upper CASE tools perform analysis

and design.
• Lower CASE tools generate
programs from C A S E design.

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-35
 Upper C A S E Tools

• Create and modify the system

design.
• Help in modeling organizational
requirements and defining system
boundaries.

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-36
 Lower C A S E Tools

• Lower CASE tools generate

computer source code from the
CASE design.
• S ource code is usually generated in
several languages
• Decreases maintenance time
• Generates error-free code

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-37
My additions!
•  Real CASE tools are categorized into 3 levels:
–  Upper CASE
–  Lower CASE
–  Integrated CASE
 The Agile Approach

• Based on:
• Values
• Principles
• Core practices

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-38
 The figure represents the
repository concept.

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-42
 Agile Values

• Communication
• S im p li c ity
• F e e d b a ck
• C o urage

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-39
 Four Agile Resources

• Resources are adjusted to ensure

successful project completion.
• Time
• Cost
• Quality
• Scope

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-40
 Five Stages of Agile Development

• Exploration
• Planning
• Iterations to the first release
• Productionizing
• Maintenance

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-41
 Agile Project Development
Process (Figure 1.7)

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-42
 Object-Oriented (O-O) Systems
Analysis and Design
•  Alternate approach to the structure approach of the
SDLC that is intended to facilitate the development
of systems that change rapidly in response to
dynamic business environments
•  Analysis is performed on a small part of the system
followed by design and implementation.
•  The cycle repeats with analysis, design, and
implementation of the next part and this repeats until
the project is complete.
•  Examines the objectives of a system

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-43
 Unified Modeling Language
(UML) Phases
• Define the use case model:
• Use case diagram
• Use case scenarios
• Create UML diagrams.
• Develop class diagrams.
• Draw statechart diagrams.
• Modify the UML diagrams.
• Develop and document the system.

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-44
Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-45
 Choosing a Method

• Choose either:
• SDLC
• Agile
• Object-oriented methodologies

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-45
 When to Use the SDLC

• Systems have been developed and

documented using SLDC.
• It is important to document each step.
• Upper level management feels more
comfortable or safe using SDLC.
• There is an adequate resources and time to
complete the full SDLC
• Communication of how new systems work is
important.

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-46
 When to Use the Agile

• There is a project champion of agile methods in the

organization.
• Applications need to be developed quickly in
response to a dynamic environment.
• A rescue takes places (the system failed and there is no
time to figure out what went wrong.
• The customer is satisfied with incremental
improvements.
• Executives and analysts agree with
the principles of agile methodologies

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-47
 W h e n t o U s e t h e Object-
Oriented
• The problems modeled lend themselves to
classes.
• An organization supports the UML learning.
• Systems can be added gradually, one
subsystem at a time.
•Reuse of previously written
software is a possibility
•  I t i s a c c e p t a b l e t o t a c k l e
the difficult problems first.

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-48
 Summary

•  I n f o r m a t i o n i s a k e y r e s o u r c e .
•  Systems analysts deal with many types of information
s y s t e m s
•  Integration of traditional systems with new
t e c h n o l o g i e s
•  Roles and qualities of the systems analysts
•  T h e s y s t e m s d e v e l o p m e n t l i f e c y c l e
•  C A S E t o o l s
•  A g i l e s y s t e m s d e v e l o p m e n t
•  O b j e c t - o r i e n t e d s y s t e m s d e v e l o p m e n t

Kendall & Kendall Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1-49
All rights reserved. No part of this publication may be reproduced, stored in a
retrieval system, or transmitted, in any form or by any means, electronic,
mechanical, photocopying, recording, or otherwise, without the prior written
permission of the publisher. Printed in the United States of America.
Copyright © 2011 Pearson Education, Inc.
Publishing as Prentice Hall

1-50
Mini Exercises
1.  Look in the classified section of your local newspaper. What kinds of job
opportunities are available for people who want analyst positions?
Compare and contrast the skills that the ads solicit with the skills that
were presented in this chapter.
2.  Think about your ideal analyst position. Write a newspaper ad to hire
someone for that position. What requirements would the job have?
What skills and experience would be required? How would applicants
demonstrate that they have the appropriate skills and experience?
3.  Locate a news article in an IT trade magazine (e.g., Computerworld,
ABS-CBN) about an organization that is implementing a new computer
system. Describe the tangible and intangible values that the organization
likely will realize from the new system.
4.  Car dealers have realized how profitable it can be to sell automobiles by
using the Web. Pretend that you work for a local car dealership that is
part of a large chain such as CarMax. Create a system request that you
might use to develop a Web-based sales system. Remember to list
special issues that are relevant to the project.