Systems Development: Oktalia Juwita, S.Kom., M.MT

Dasar-dasar Sistem Informasi IKU1102
SYSTEMS DEVELOPMENT
Oktalia Juwita, S.Kom., M.MT.
INTRODUCTION
Why do businesses build information systems ?
How does a business know when it is time to replace
the old information system with a new one ?
TYPICALLY: Knowledge workers will request new
systems to help them perform their work.
TYPICAL REASONS TO INITIATE A SYSTEMS

DEVELOPMENT PROJECT
Problems with existing systems
Desire to exploit new opportunities
Increasing competition
Desire to make more
effective use of information
Organizational growth
Merger or acquisition
Change in market or
external environment
Perception of potential
benefit by individual
capable of initiating
change
Systems development
process initiated
Developing of an information system may fail.

There are many factors that must be considered
and come together in order to develop a
successful information system.
The SDLC = Systems Development Life Cycle is
one approach to reduce the risk of failure.
Systems development life

cycle (SDLC) - a structured
step-by-step approach for
developing information
systems.
When developing a new system, you have 3 who

choices
1. Insourcing IT specialists inside your
organization
2. Selfsourcing do-it-yourself approach many end
users take with little or no help from IT specialists
3. Outsourcing a third-party organization (i.e., let
someone do the work and pay them for it)
PHASE 1: PLANNING
Planning phase - create a solid plan for developing your

information system
Three primary planning activities:
1. Define the system to be developed
You cant build every system, so you make choices
based on your organizations priorities, which may be
expressed as critical success factors
Critical success factor (CSF) - a factor simply critical
to your organizations success
6-8
PHASE 1: PLANNING
2. Set the project scope
Project scope - clearly defines the high-level system
requirements
Scope creep - occurs when the scope of the project
increases
Feature creep - occurs when developers add extra
features that were not part of the initial requirements
Project scope document - a written definition of the
project scope and is usually no longer than a paragraph
6-9
PHASE 1: PLANNING
3. Develop the project plan including tasks, resources, and
timeframes
Project plan - defines the what, when, and who
questions of system development
Project manager - an individual who is an expert in
project planning and management, defines and
develops the project plan and tracks the plan to ensure
all key project milestones are completed on time
Project milestones - represent key dates for which
you need a certain group of activities performed
6-10
PHASE 1: PLANNING
Sample Project Plan
6-11
PHASE 2: ANALYSIS
Analysis phase - involves end users and IT
specialists working together to gather, understand,
and document the business requirements for the
proposed system
6-12
PHASE 2: ANALYSIS
Two primary analysis activities:

1. Gather the business requirements
Business requirements - the detailed set of knowledge
worker requests that the system must meet in order to be
successful
Business requirements address the why and what of your
development activities
Joint application development (JAD) - knowledge workers
and IT specialists meet, sometimes for several days, to
define or review the business requirements for the system
6-13
PHASE 2: ANALYSIS
2. Prioritize the requirements
Requirements definition document prioritizes the
business requirements and places them in a formal
comprehensive document
Again, you probably cant do everything, so prioritizing
is important
Users sign off on this document which clearly sets the
scope for the project
6-14
PHASE 2: ANALYSIS
Take time during analysis to get the business requirements correct. If

you find errors, fix them immediately. The cost to fix an error in the
early stages of the SDLC is relatively small. In later stages, the cost is
huge.
6-15
PHASE 3: DESIGN
Design phase - build a technical blueprint of how the

proposed system will work
Two primary design activities:
1. Design the technical architecture
Technical architecture - defines the hardware,
software, and telecommunications equipment required
to run the system
6-16
PHASE 3: DESIGN
6-17
PHASE 3: DESIGN
2. Design system models
This includes GUI screens that users will interface with,
database designs (see XLM/C), report formats,
software steps, etc
Starting with design, you take on less of an active participation

role and act more as a quality control function, ensuring that
the IT people are designing a system to meet your needs
6-18
PHASE 4: DEVELOPMENT
Development phase - take all of your detailed design

documents from the design phase and transform them into an
actual system
Two primary development activities:
1. Build the technical architecture
2. Build the database and programs
Both of these activities are mostly performed by IT
specialists
6-19
PHASE 5: TESTING
Testing phase - verifies that the system works and meets all
of the business requirements defined in the analysis phase
Two primary testing activities:
1. Write the test conditions
Test conditions - the detailed steps the system must
perform along with the expected results of each step
6-20
PHASE 5: TESTING
2. Perform the testing of the system
Unit testing tests individual units of code
System testing verifies that the units of code
function correctly when integrated
Integration testing verifies that separate systems
work together
User acceptance testing (UAT) determines if the
system satisfies the business requirements
6-21
PHASE 6: IMPLEMENTATION
Implementation phase - distribute the system to all of the

knowledge workers and they begin using the system to
perform their everyday jobs
Two primary implementation activities
1. Write detailed user documentation
User documentation - highlights how to use the
system
6-22
2. Provide training for the system users
Online training - runs over the Internet or off a CDROM
Workshop training - is held in a classroom
environment and lead by an instructor
6-23
Choose the right implementation method
Parallel implementation use both the old and new
system simultaneously
Plunge implementation discard the old system
completely and use the new
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
6-24
PHASE 7: MAINTENANCE
Maintenance phase - monitor and support the new system

to ensure it continues to meet the business goals
Two primary maintenance activities:
1. Build a help desk to support the system users
Help desk - a group of people who responds to
knowledge workers questions
2. Provide an environment to support system changes
6-25
CONTINUED TO NEXT SESSION

-THANK YOU-

Systems Development: Oktalia Juwita, S.Kom., M.MT

Uploaded by

Copyright:

Available Formats

Systems Development: Oktalia Juwita, S.Kom., M.MT

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Systems Development: Oktalia Juwita, S.Kom., M.MT

Uploaded by

Copyright:

Available Formats

Dasar-dasar Sistem Informasi IKU1102

TYPICAL REASONS TO INITIATE A SYSTEMS

Developing of an information system may fail.

Systems development life

When developing a new system, you have 3 who

Planning phase - create a solid plan for developing your

Sample Project Plan

Two primary analysis activities:

Take time during analysis to get the business requirements correct. If

Design phase - build a technical blueprint of how the

Starting with design, you take on less of an active participation

Development phase - take all of your detailed design

Implementation phase - distribute the system to all of the

Maintenance phase - monitor and support the new system

CONTINUED TO NEXT SESSION

You might also like