System Development Process

1
System Development Process

• Dont Forget
• Goal of IS is solution to a specific business
  challenges
• IS is result of a series of activities known as
  the systems development process
• or more accurately, the system development life
  cycle
• Stages are
• Systems Analysis and Specification
• System Design (High and Low Level)
• Programming
• Testing
• Deployment
• Production, maintenance and enhancement

Will never be perfect first time
2
Building an Information System
3
Building an Information System
4
Building an Information System
5
Building an Information System
6
Building an Information System
7
Building an Information System
User Requirement
8
Building an Information System
User Requirement
Feasibility Study
9
Building an Information System
Design Specification
User Requirement
Feasibility Study
10
Building an Information System
Design Specification
Test Plan
User Requirement
Feasibility Study
11
Building an Information System
Design Specification
Test Plan
User Requirement
Feasibility Study
Deployment Approaches
12
Building an Information System
13
Building an Information System
14
Building an Information System
Design Specification
Test Plan
User Requirement
Feasibility Study
In-Service Management
Deployment Approaches
15
Alternative Project Approach
16
Alternative Project Approach
17
Golden Rule One
Never implement before designing
18
Project Components
CLEAR SCOPE
START
PERFORMANCE
BUDGET RESOURCES
FINISH
19
Project Components
(OBJECTIVES)
CLEAR SCOPE
START
PERFORMANCE
(RISK MANAGEMENT)
(QUALITY)
BUDGET RESOURCES
FINISH
(CONTROL (Progress Costs))
20
Project Variables
Resource
Quality
When you squeeze in one place, it bulges out in
another
Cost factors
Product factors
Function
Schedule
21
Definition of a Project

• A project is a one time multitask job that has
• a specific scope of work,
• a specified level of performance to be achieved,
• clearly defined start and finish,
• a budget and resource allocation

22
Project Considerations

• Because information systems have enormous
  strategic value to the organization commissioning
  them, the wrong information system or a poor
  implementation can be absolutely disastrous.
  Often this is because the system was developed,
  procured or implemented in a vacuum. Active
  involvement from the organizations management
  and the users was missing, so that the final
  system pursues the wrong objectives. The benefits
  were not delivered and the system ends up as
  another overhead to be set against the company
  profits.
• Therefore, projects should be structured so as to
  allow
• The setting of clearly defined objectives (Clear
  project scope). Involvement of management and
  users in defining the objectives
• Clear definition of expectations as to the level
  of performance to be achieved.
• Accurate assessment of the projects
  economics/costs/resource requirements required to
  complete each stage of the project.
• A finite and defined life (Start and Finish).
• Systems development has to be part of business
  strategy and must serve the business goals, be
  consistent with the business plan and match any
  planned organizational change.

23
A Successful IS Project
24
Building an Information System

• Systems development has to be part of business
  strategy
• Must serve the business goals
• Be consistent with the business plan
• And match any planned organizational change
• TQM and Enterprise Analysis
• Look at processes and organization wide goals
• Focus on managers rather than general users
• System development has to consider all its users
• Erics view
• Big Bang developments usually fail
• Managers need to minimize number of sources of
  risk