Scribd
Upload
8 views33 pages

Lecture 1.pptx

The document outlines key concepts in Information Systems, emphasizing the importance of understanding organizational needs to avoid project failures, which historically occur in about 85% of cases. It details the Systems Development Life Cycle (SDLC), which includes planning, analysis, design, and implementation phases, along with the roles of various team members involved in the process. Additionally, it highlights common pitfalls in software development, such as unrealistic expectations and the 'gold plating' of features.

Uploaded by

stevenhashiru
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
8 views33 pages

Lecture 1.pptx

The document outlines key concepts in Information Systems, emphasizing the importance of understanding organizational needs to avoid project failures, which historically occur in about 85% of cases. It details the Systems Development Life Cycle (SDLC), which includes planning, analysis, design, and implementation phases, along with the roles of various team members involved in the process. Additionally, it highlights common pitfalls in software development, such as unrealistic expectations and the 'gold plating' of features.

Uploaded by

stevenhashiru
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 33

INFORMATION SYSTEMS

Key Ideas

Many failed systems were abandoned because analysts


tried to build wonderful systems without understanding
the organization.

The primarily goal is to create value for the organization.

Quality is satisfaction of requirements, not ‘goodness’


Key Ideas

The systems analyst is a key person analyzing the


business, identifying opportunities for improvement, and
designing information systems to implement these ideas.

It is important to understand and develop through


practice the skills needed to successfully design and
implement new information systems.
The hardest single part of building a software system is deciding precisely
what to build. No other part of the conceptual work is a difficult as
establishing the detailed technical requirements, including all the interfaces
to people, to machines, and to other software systems. No other work so
cripples the resulting system if done wrong. No other part is more difficult to
rectify later.

Fred Brooks
IS Development Project Track Record

Over budget,
canceled
late, or without
before
needed features
completion
Source: The Standish Group International, Inc., “Chaos: A Recipe for Success”
IS Development Project Track Record
IS Development Project Track Record

Source: The Standish Group International, Inc., The 2009 Chaos Report
Historically, ~ 85% of projects "fail."
Why?

- management sets unrealistic expectations; developers don't


correct them

- overestimating the positive impact of shiny new tools and


hardware

- hired developers based on availability despite warning signs


personality conflicts between developers

- changes in rate structure requirements in middle of work

- one delay causes another (dev delay leads to test delay, etc.)
Historically, ~ 85% of projects "fail."
Why?

- developers end up working "death marches" (6-day, 10-hour weeks)


- overestimating how nearly done you are ("I'm 90% there!")
- developer time taken away by other tasks
- tons of bugs come out in testing
- developers don't listen to testers; ignore severity of bugs reported
- management breaking promises (bonuses, time off, etc.)
Making software is hard - Pitfalls to avoid

Slide 10
Making software is hard - Pitfalls to avoid

Slide 11
Making software is hard - Pitfalls to avoid

The 'gold plating' means the addition of any feature not considered in the
original scope plan or product description at any point of the project.
Making software is hard - Pitfalls to avoid

The Silver bullet syndrome occurs whenever managers or developers expect any single
new tool, resource, procedure or methodology to solve all its productivity problems.
THE SYSTEMS DEVELOPMENT LIFE CYCLE
(SDLC)
System Development Life Cycle

Planning
Analysis
Design
Implementation
Testing
Deployment
Support
End of Life Cycle
Major Attributes of the Lifecycle

The project

Moves systematically through phases where each phase


has a standard set of outputs

Produces project deliverables

Uses deliverables in implementation

Results in actual information system

Uses gradual refinement


4 Main Project Phases

Planning
Why build the system?
Analysis
What, when, where will the system be?
Design
How will the system work?
Implementation
System construction & delivery
Planning

Identifying business value (is it worth doing?)


Analyze feasibility (is it possible?)
Develop work plan (when?)
Staff the project (who?)
Control and direct project
Analysis

Analysis (what do we want? Who will use the


system?)
Information gathering
Process modelling (what happens?)
Data modelling (… and to what?)
Design

Design strategy
Architectural design
Interface design (HCI)
Database and file design
Program design (what will the programs do?)
Implementation

Construction (Programming, testing, validation


etc)
Installation (including migration, change
management)
Processes and Deliverables
Processes and Deliverables
Processes and Deliverables
Processes and Deliverables

Process Product

Planning Project Plan

Analysis System Proposal

Design System
Specification

Implementation New System and


Maintenance Plan
Project Team Roles and Skills
Project Team Roles

Business analyst (business value)


Systems analyst (IS issues)
Infrastructure analyst (technical issues – how the system will
interact with the organization’s hardware, software,
networks, databases)
Change management analyst (people and management
issues)
Project manager (budget, time, planning, managing)
The Term
Project
• You make product proposals

• You’re divided into project teams of 4-5 students


- Larger teams, larger projects, like industry
• You develop your deliverable in stages

• I will act as your customer


- Ultimately, a project will be successful only if it
satisfies its customer
Project Topic in class
Car rental system

The case study used throughout is a rental and reservation


system called Coot, developed for a fictitious company called
Nowhere Cars.
Suggested Project Topics

Front-office management for a Large Luxury Hotel

Luxury hotels offer several types of rooms and a wide range of


services to its guests - including routine room service and laundry
services as well as specialized services such as a travel desk,
business centre, rental of a laptop/mobile phone, etc.

This system must allow the front-office to handle all these


operations and must provide all necessary support to serve the
guest, from the time he makes a reservation to the time he/she
checks out.
Suggested Project Topics

Airline Reservation

This system will cater to passenger services only and will exclude
cargo handling, hangar administration, etc.

However, the services themselves differ to some extent.


This system must also allow check-in of passengers and their
baggage. Depending on the number of participants, the group can
also develop a system meant to be deployed at the various travel
agencies' terminals.
Summary

The Systems Development Life Cycle (SDLC)


consists of four stages:

Planning

Analysis

Design

Implementation
Summary
There are five major team roles:

business analyst

systems analyst

infrastructure analyst

change management analyst

project manager.

You might also like