Scribd
Upload
73 views

Life Cycle Development Model

Uploaded by

api-256677991
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
73 views

Life Cycle Development Model

Uploaded by

api-256677991
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 26

Systems Analysis and Design, 7e

Kendall & Kendall


2
Know the steps of the SDLC as they relate to HCI and how to
apply them to a real system
Understand what CASE tools are and how they help a
systems analyst
Explore other methodologies such as object-oriented
systems design and prototyping
Kendall & Kendall 1-2
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 1-3
Phases in the systems development life cycle
as they relate to Human-Computer
Interaction (HCI) factors
Computer-Aided Software Engineering
(CASE) tools
Kendall & Kendall 1-4
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 1-5
Kendall & Kendall 1-6
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 1-7
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 1-8
Activity:
Interviewing
Sampling and investing hard data
Questionnaires
Observe the decision makers behavior and environment
Prototyping
Learn the who, what, where, when, how, and why of the current
system
Output:
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 1-9
Activity:
Create data flow 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 1-10
Activity:
Design procedures for data entry
Design the human-computer interface
Design system controls
Design files and/or database
Design backup procedures
Output
Model of the actual system
Kendall & Kendall 1-11
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 1-12
Activity:
Test the information system
System maintenance
Maintenance documentation
Output:
Problems, if any
Updated programs
Documentation
Kendall & Kendall 1-13
Activity:
Train users
Analyst plans smooth conversion from old system
to new system
Review and evaluate system
Output:
Trained personnel
Installed system
Kendall & Kendall 1-14
Kendall & Kendall 1-15
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
Kendall & Kendall 1-16
Kendall & Kendall 1-17
Traditional systems development life
cycle
CASE systems development life cycle
Object-Oriented Systems Analysis and
Design
Kendall & Kendall 1-18
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
Accurately Assessing Maintenance Changes
Kendall & Kendall 1-19
Upper CASE tools perform analysis and
design
Lower CASE tools generate programs
from CASE design
Integrated CASE tools perform both
upper and lower CASE functions
Kendall & Kendall 1-20
Create and modify the system design
Help in modeling organizational
requirements and defining system
boundaries
Can also support prototyping of screen
and report designs
Kendall & Kendall 1-21
Lower CASE tools generate computer
source code from the CASE design
Source code is usually generated in
several languages
Kendall & Kendall 1-22
Kendall & Kendall 1-23
Alternate approach to the structured approach of the
SDLC that is intended to facilitate the development of
systems that must 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
Kendall & Kendall 1-24
Agile approach
Prototyping
ETHICS
Project champion
Soft Systems Methodology
Multiview
Kendall & Kendall 1-25
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 1-26

You might also like