Managing Systems Development
Managing Systems Development
Managing Systems Development
Systems Development
Managing
Systems Development
I. Systems Development
III. IT Projects
Learning Objectives
Phase1: Planning
Analysis
developed
Testing
Phase2: Analysis
Analysis
Phase3: Design
Analysis
Development
Design the files and database
structure
Testing Design output (on-screen or
printed) with users
Implementation
Design controls and backup
procedures
Maintenance
Planning
Phase4: Development
Analysis
Phase5: Testing
Analysis
Phase6: Implementation
Analysis
User training
Testing Data Conversion
User documentation
Implementation
Bring new system into production
Maintenance
Phase6: Implementation
Implementation methods
Pilot implementation start with
small groups of people on the new
system and gradually add more users
Phased implementation implement
the new system in phases
Parallel implementation use both
the old and new system
simultaneously
Plunge implementation discard the
old system completely and use the
new
Planning
Phase7: Maintenance
Analysis
errors or bugs
Testing
Maintenance
Pros and Cons of SDLC
Advantages
Systematic and enforces quality
High probability of not missing
anything in the requirement analysis
Disadvantages
Users have trouble describing
requirements for the system
Excessive documentations
Takes too long
Simplifying the Phases
of Systems Development
Design
Planning
Development Implementation Maintenance
Analysis
Testing
Operations
Initiation Development Implementation and
Maintenance
System Design Error Graph
Alternative
System
Development
Methods
Three choices for building
a system includes
Staffing the IS Project
Insourcing the development and support of
IT systems by the organzations IT
department
Prototype
Process Evaluate
prototype
Decide on
Abandon project next step Further revision
Prototyping
completed successfully
Switch to
Decide how to Complete the system
traditional
complete project from prototype
system life cycle
Prototype
Advantages
Tangible system to work with
Encourages user participation
Immediate feedbacks
Disadvantages
Leads user to believe the final system
will follow shortly
Leads the project team to forgo
proper testing and documentation
Succession of rapid changes
Application Package
commercially available software
reduces the development phase
usually avoids delays in developing
systems, limits risk due to business
and technical uncertainties, reduces
the resources needed to solve the
problem
use this process to solve a resource
and timing problem by using
commercially available software
Application Package Process
Evaluate software
Purchase software
Customize software
Data conversion
Testing
Implementation
Vendor provides supports and
updates
Application Package
Advantages
Focus on unique core competencies
Exploit the intellect of another
organization
Software exists already and has been
tested by others
Acquire leading-edge technology
Reduce delays for analysis, design
and programming
Has good documentation
Application Package
Disadvantages
Increases dependency on other
organizations
May be difficult to get updates
Lack of knowledge about how and
why the system works that way
Reduces technical know-how for
future innovation
Reduces degree of control
End-User Development
Source of tension
Users: It is too slow and they dont
know our business process
IT: Users produce poor systems and
leave us with maintenance
How should IT respond to this?
Ignore
Override
Offer assistance and consultation
End-User Development
development of information systems
by end-users instead of programmers
end users use spreadsheets,
database packages, report
generators, analytical packages, and
other tools that can be used by
nonprogrammers
use this process to solve a
responsiveness problem involving the
inability of the information system
groups to keep up with the
individual's changing information
needs
Common Issues in
End-User Development
Issue Common Approach
Hardware selection and IS Staff selects type of hardware than can be purchased
maintenance and maintains the hardware
Data availability End users control their own data and share it using LAN
Data security Users can access only the data they need
Systems analysis IS staff helps end user with system analysis and design
when necessary. They also provide other types of
support.
End-User Development
Advantages
Users have good knowledge of
business needs
Bypass the IS department and
avoid delays
User controls the application
and can change it as needed
Increases speed of systems
development
End-User Development
Disadvantages
Inadequate user expertise leads to
inadequately developed systems
Many systems require consulting and
maintenance assistance from the IS
department
More prone to bugs
Lack of documentation and external
support leads to short-lived systems
Comparison
Life Cycle Approach Issues Addressed Summary of Method
System development life Control Proceed through a fixed sequence
cycle of steps with signoffs after each
steps and careful documentation
EXAMPLE:
United Parcel Service (UPS)- is in the package delivery service.
Jobholder- delivery driver
Skill- understanding city street numbering and park layout
Problem- driver leave UPS
Improving maintenance job
Five core job dimension
1. Skill variety- person need to use a number of different
skills and talents
2. Task identity- refer to identifiable piece of work
3. Task significant- impact to the life or work of other people
4. Autonomy- freedom in accomplishing the job
5. Feedback- reward
How can legacy system be
improved?
Replace or Not to replace?
Replace
3 factors to consider
1. Cost and benefit
2. How specialized the new system
3. Staff skill
Improving Legacy System
Project Management
is simply the management of a project.
Management
is the act or process of managing.
Project
is a collection of related tasks and activities
undertaken to achieve a specific goal.
All Projects should:
RISK
An uncertain event or set of
circumstances which, should it
occur, will have an effect on
achievement of objectives.
High Project
Overrun
Business Unnecessary
Customization
IT Resource
Redundancy
Incorrect
Business
Benefits
Improper
Application
Redundant
Infrastructure
Opportunity
Costs
Prioritization Requirement
Critical Path
Are most project failures caused by technical
problems, people problems or business
problems?
It is caused by People problems.
OPERATIONAL ROLE
Discipline, Planning,
Documentation and
Management.
Proper Planning
User Involvement
Work as a Team
Proper Monitoring and
Controlling
Prototyping
Proper Project Closure
Project Management DOs &
DONTs #1
2. Nothing is FREE.