7. What did we learn so far?
Why many new system implementations fail ?
What can be done ?
8. IS/ IT
• Planning
• Justification
IS/ IT system
development
methodologies
and options
• Team effort
• Several approaches
• Start with
investigation and
analysis, design,
maintenance and
review
Emphasis
• How to deliver
• Right information to
the right person at the
right time!
9. Workshop III Review
Why Most New Information Systems Fail?
Nature of Software Development
IS/ IT Planning & Justification
IS/ IT System Development Methodologies
IS/ IT Funding & Costs
Summary
Your activities for coming week
10. Basic system development
framework
IS development – intangible,
eventually visible
Process of design
to delivery is
repeatable
Software
engineering –
shifts from
waterfall paradigm
Analogies –
limited and
not complete
Iterative, agile
development
12. IS/ IT Mgmt.
Policies
IS Strategy IT Strategy
Future
Application
Portfolio
Framework for IS/ IT Planning continued
13. Development of Information Systems, Business Manager’s Point ofView
Strategic High Potential
Key Operational Support
Business Development Projects IT Development Projects
Business Infrastructure Projects IT Infrastructure Projects
14. IS Planning Process
Align organization’s mission and Business assessment
Arrive at Organization’s strategic plan
Consider current technology architecture
IS strategic plan
New InformationTechnology architecture
IS Operational Plan
IS development plans
16. Workshop III Review
Why Most New Information Systems Fail?
Nature of Software Development
IS/ IT Planning & Justification
IS/ IT System Development Methodologies
IS/ IT Funding & Costs
Summary
Your activities for coming week
Topics
18. SupportingTools of SDLC during various stages
Prototyping
Joint
Application
Design
Upper case
tools
Lower case tools
Examples?
19. What are the benefits of planning for Information
Systems? What obstacles teams might have to overcome to
have their plans heard in an organization? Discuss
20. Problem Recognition and Definition
User
mentions a
problem
Is it a
problem or
symptom
Establish
the need
Define the problem
21. Technical feasibility
(Proof of concept)
Economic feasibility
(costs vs Benefits)
Legal Feasibility (laws
and regulations)
Operational feasibility
(historical acceptance
of IT systems,
Personnel re-training)
Schedule feasibility
(balancing time and
resource)
Feasibility Study
28. What
• IS/ IT planning
• justification of investments
Did we learn
• System development methodologies
• Options
So far?
• How to deliver the right information
to the right person at the right time?
30. Workshop III Review
Why Most New Information Systems Fail?
Nature of Software Development
IS/ IT Planning & Justification
IS/ IT System Development Methodologies
IS/ IT Funding & Costs
Summary
Your activities for coming week
Topics
34. Your activities for coming week
Prepare and submit assignments as per syllabus.
Remember to include all references and use proper
citations.The final exam is during week four – week five.
Follow Materials Link.
Read:
Selected Readings specified in Materials tab
Refer to your syllabus for details on activities during the
workshop
35. The chapters recommended from the electronic texts in
Materials were used.
Some of the figures used in the slides were taken from the
chapters in texts.
Source for slides on Information Architecture and
Information Management are from Principles of
Information Systems Management by John Ward
Source of slides on Information Systems failures is from
Phil Simon’s Why New Systems Fail theory and practice
collide.