Please enable JavaScript.
Coggle requires JavaScript to display documents.
Ch 20 : Introduction to systems development and systems analysis (HOW TO…
Ch 20 : Introduction to systems development and systems analysis
SDLC
1. System Analysis
do system survey
do feasibility study
determine info needs and system requirement
deliver system requirement
do initial investigation
2. Conceptual Design
develop design specifications
deliver conceptual design requirements
identify and evaluate design alternatives
3. Physical Design
develop procedures
develop programs
design input
design controls
design database
deliver developed system
design output
4. Implementation and Conversion
Train personnel
Test the system
install hardware and software
Complete documentation
develop an implementation and conversion plan
Convert from old to new system
deliver operational system
5. Operations and Maintenance
do ongoing maintenance
modify system
operate system
deliver improved system
Fine-tune and do post implementation review
WHO IS INVOLVED IN SDLC?
programmers
write and test programs according to analysts spec
system analysts
determine info needs, prepare spec for programmers
project development team
conduct meeting, plan and monitor project progress
management
provide support, align project accordingly, establish goals
info system steering committee
executive level, plans and oversees IS, facilitate
users
communicate need to system developers
SYSTEM DEVELOPMENT PLANNING
project development plan
specific to a project and authored by project team identifies people, hardware, software
master plan
long-range and authored by steering committee outlining prioritized projects and timetables
planning techniques
program evaluation and review technique(PERT)
Gantt chart
BUSINESS CASE(FEASIBILITY ANALYSIS)
legal
scheduling
technical
operational
economic
CAPITAL BUDGETING
net present value(NPV)
Internal rate of return(IRR)
payback period
WHY BEHAVIOURAL PROBLEMS OCCUR?
fear
lack of top mgmt support
bad prior experiences
poor communication
disruption
personal characteristic and background
biases and emotions
manner change is introduced
HOW TO PREVENT BEHAVIORAL PROBLEMS?
satisfy user needs
mgmt support
involve users
reduce fears
avoid emotionalism
provide training
performance evaluation
keep open communication
test the system prior to implementation
keep system simple
control uses's expectations
HOW PEOPLE RESIST CHANGES?
avoidance
projection
agression