INFORMATION SYSTEMS

DEVELOPMENT
Objectives
• Define System development and list the system
development phases
• Identify the guidelines for system development
• Describe the persons who initiates System
Development
• Describe the information systems planning process
• Discuss the concept of System Development Life
Cycle (SDLC)
• Discuss the phases of SDLC
• Discuss the alternative methods for Systems
Development
Case study

A government agency needed a project

management system: not Microsoft Project, but a
business information system to manage their functional
projects. The overall scope included projects, staff,
deliverables, assignments, status reports, travel and
expenses, client organizations and their staff, and the
like. So the agency hired a contractor to come in and do
a requirements analysis and build a business
information system.
Case study

A government agency needed a project

management system: not Microsoft Project, but a
business information system to manage their functional
projects. The overall scope included projects, staff,
deliverables, assignments, status reports, travel and
expenses, client organizations and their staff, and the
like. So the agency hired a contractor to come in and do
a requirements analysis and build a business
information system.
Case study

The requirements analysis was standard fare:

meet with management, meet with functional experts,
and meet with technical staff. Everybody was
interviewed and the requirements document filled
several volumes. Everyone was happy.
The contractor took the requirements document
away and implemented the business information
system. After about a year of detailed design, coding,
unit testing, and system testing, the business
information system was delivered to the government
agency.
Case study

The government agency shrieked in horror. What

had the contractor done? That is not what the agency
had said. Not what they had wanted. How could this
happen? The contractor was promptly fired.
Since this clearly had to be an aberration, a new
contractor was hired. The new contractor met with
management, met with functional experts, and met
with technical staff. Everybody was interviewed and the
requirements document filled several volumes.
Everyone was happy.
Case study

The contractor took the requirements document

away and implemented the business information
system. After about a year of detailed design, coding,
unit testing, and system testing, the business
information system was delivered to the government
agency. The government agency shrieked in horror.
What had the contractor done? That is not what the
agency had said. Not what they had wanted.
How could this happen? The contractor was
promptly fired.
Case study

Since this clearly had to be an aberration, a new

contractor was hired. The new contractor met with
management . . . .
Case study

 Initiative

 Means/resources

 Man power

x Proper system
development process
 When someone has an idea for a new function to
be performed by a computer, how does that idea
become reality?
If a company wants to implement a new business
process and needs new hardware or software to
support it, how do they go about making it happen?
 A system is a set of components that interact
System to achieve a common goal
Development
is a set of
activities used
An information system (IS) is a collection of
to build an hardware, software, data, people, and
information procedures that work together to produce
system quality information
solution to
business
problem or System development activities are grouped
opportunity into phases, and is called the system
development life cycle (SDLC)
 Who initiates a System Development Project?

• A user may request a new or modified system

• Organizations may want to improve hardware,
software, or other technology
• Situations beyond an organization’s control might
require a change
• Management might mandate a change.
A system should follow three general guidelines:

Group activities or task into phases

Involve users

Define standards
Information Systems Planning
Organization Mission Business Assessment

Organizational Current Information

Strategic Plan Technology Architecture

IS Strategic Plan

New Information
Technology Architecture

IS Operational Plan

IS Development
Projects
 IS Strategic Plan

A set of long-range goals that describe the IT

architecture and major IS initiatives needed to
achieve the goals of an organization

Efficiency Effectiveness Competitiveness

 IS Operational Plan
A clear set of projects that will be executed by the
IS department and by functional area managers in
support of the IS strategic plan

Mission
IS Environment
Objectives of the IS Function
Constraints on the IS Function
Long-term system needs
Short-range plan
Development teams usually includes:

• Users
• System analyst
• Programmers
• Technical Specialist
• System stakeholders
System Development Life Cycle (SDLC)
 Traditional System Development
Life Cycle (SDLC)

- a structured framework that consists of sequential

processes by which information systems are
developed.
Systems investigation

System analysis

Systems design

Programming

Testing

Implementation

Operation

Maintenance

Go back to a previous stage or stop

1. SYSTEMS INVESTIGATION

• begins with the business problem.

• determines and defines the exact nature of the
problem

Feasibility Studies - determines the probability of

success of the proposed systems development
project
Technical
determines if the hardware, software, and
communications components can be developed
and/or acquired to solve the business problem.
Economic
determines if the project is an acceptable financial
risk and if the organization can afford the expense
and time needed to complete the project.
Behavioral
addresses the human issues of the project. All
systems development projects introduce change
into the organization, and people generally fear
change.
 2. SYSTEMS ANALYSIS

the examination of the business problem that the

organization plans to solve with an information
system.

1. Defines the problem

2. Identifies its cause
3. Specify the solution
4. Identifies the information requirements that the
solution must satisfy
The system analysis identifies the following:

• Strengths and weaknesses of the existing system

• Functions that the new system must have to
solve the business problem
• User information requirements for the new
system
 3. SYSTEMS DESIGN

Systems analysis describes what a system must do to

solve the business problem, and systems design
describes how the system will accomplish this task.

Logical System design Physical System Design

 4. PROGRAMMING

involves the translation of the design specifications

into computer code.

For example, a flowchart for a simple payroll

application might look like the one shown in the
figure.
 Read employee
record.

Empl
oyee NO Gross pay =
hourl Salary/52
y?
YES

Hours NO Gross pay = #

worke of hours x hour
d>40? rate

YES

Gross pay = (40 x hr. rate) + (# hours –

40) x (hr. rate x 1.5)
YES

Last
record
?

YES

Stop
5. TESTING

designed to detect errors (“bugs”) in the

computer code.

Syntax errors (e.g., Logic errors permit

a misspelled word the program to run,
or a misplaced but result in
comma) are easier incorrect output
to find and will not
permit the
program to run.
 6. IMPLEMENTATION

is the process of converting from the old system to

the new system.

• parallel conversion - the old system and the new

system operate simultaneously for a period of
time.
• direct conversion- the old system is cut off and
the new system is turned on at a certain point in
time.
• pilot conversion - introduces the new system in
one part of the organization, such as in one
plant or in one functional area.
• phased conversion - introduces components of
the new system, such as individual modules, in
stages
 7-8. OPERATION AND MAINTENANCE

audits are performed during operation to assess the

system’s capabilities and determine if it is being used
correctly.

System needs several types of maintenance:

1. Debugging the program
2. Updating the system
3. Addition of new functionality
Alternative Method for Systems Development

1. Prototyping - systems developers first obtain

only a general idea of user requirements. That
is, the developers do not try to obtain a
complete set of user specifications for the
system and do not plan to develop the system
all at once.
2. Joint Application Design (JAD)- is a group-
based method for collecting user
requirements and creating system designs.
JAD is most often used within the systems
analysis and systems design stages of the
SDLC.
3. Rapid Application Development (RAD)- is a
systems development method that can
combine JAD, prototyping, and integrated
CASE tools (described below) to rapidly
produce a high-quality system.
4. Integrated Computer-Assisted Software
Engineering (ICASE) Tools - tools automate
many of the tasks in the SDLC. The tools
used to automate the early stages of the
SDLC (systems investi- gation, analysis, and
design) are called upper CASE tools. The
tools used to automate later stages in the
SDLC (programming, testing, operation and
maintenance) are called lower CASE tools.
5. Object-Oriented Development - based on a
fundamentally different view of computer
systems than that found in traditional SDLC
development approaches. It begins not with
the task to be performed, but with the
aspects of the real world that must be
modeled to perform that task.
• Make Effective Presentations
• Using Awesome Backgrounds
• Engage your Audience
• Capture Audience Attention
 Slide Title

Product A Product B
• Feature 1 • Feature 1
• Feature 2 • Feature 2
• Feature 3 • Feature 3