Professional Documents
Culture Documents
System Analysis Design Chapter 1
System Analysis Design Chapter 1
1-1
Intended Learning
Outcomes
Understand the need for systems
analysis and design in organizations.
Realize what the many roles of the
systems analyst are.
Comprehend the fundamentals of three
development methodologies:
SDLC
The agile approach
Object-oriented systems analysis and design
Kendall & Kendall
Hall
1-3
Assessment Tasks
Case Study
Recitation
1-4
Topics
Fundamentals of different kinds of
information systems
Roles of systems analysts
Phases in the systems development
life cycle as they relate to HumanComputer Interaction (HCI) factors
CASE tools
Open Source Software
1-5
1-6
1-8
1-10
Identifying Problems,
Opportunities, and Objectives
Activity:
Interviewing user management
Summarizing the knowledge obtained
Estimating the scope of the project
Documenting the results
1-12
Identifying Problems,
Opportunities, and Objectives
Output:
Feasibility report containing problem
definition and objective summaries
from which management can make a
decision on whether to proceed with
the proposed project
1-13
Determining Human
Information Requirements
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
1-14
Determining Human
Information Requirements
Output:
The analyst understands how users
accomplish their work when interacting with
a computer
Begin to know how to make the new system
more useful and usable
Know the business functions
Have complete information on the:
People
Goals
Data
Procedure involved
1-15
Output
Model of the actual system
1-17
1-19
Output:
Problems, if any
Updated programs
Documentation
1-20
Output:
Trained personnel
Installed system
1-21
1-22
1-24
Traditional systems
development life cycle
CASE systems development
life cycle
Object-oriented systems
analysis and design
1-25
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
1-26
1-27
1-28
1-29
Agile Values
Communication
Simplicity
Feedback
Courage
1-30
1-31
1-32
1-33
1-35
1-37
Choosing a Method
Choose either:
SDLC
Agile
Object-oriented methodologies
1-38
1-40
1-41
Ad hoc
Standardized
Organized
Commercial
1-43
General structure
Environment
Goals
Methods
User community
Licensing
1-44
1-46
1-47
Collective Design
Through a process of collective
design the IT artifact is imbued
with
Community and organizational
structures
Knowledge
Practices
1-49
Summary
Information is a key resource
Integration of traditional systems with new
technologies
Roles and qualities of the systems analyst
The systems development life cycle
CASE tools
Agile systems development
Object-oriented systems development
Open source systems
1-50
1-51