How do you get started on developing an information system?

1. ISINFORMATION SYSTEMS
BY: JAN WONG
HELLO AND
WELCOME TO
Chapter Two:
DEVELOPMENT OF
INFORMATION SYSTEMS
“How to get started?”

2. ISHow do you start designing an
information system?

3. IS
It starts with a problem.
Consumers Business
P R O C E S S
“Network of activities or a series of activities,
repositories, roles, resources, and data flows that
interact to accomplish a business function.”

4. Then with an objective.
Consumers Business
To correct
a problem
To improve
Competition
External
demand
To initiate a project request.

5. And assemble a team.
Users
The people whom
which the system
is being
developed for.
Steering Committee
The decision making body
Systems Analyst
The Project Leader
manages, schedules
and controls the team.
Programmer
Converts the design
into a working product.
Vendor
External party that
supplies necessary
support to the team.
Tester
Breaks things… I mean,
make sure the product
is working as intended.
Specialist
An expert in a
specific field e.g.
mobile, database,
UX, etc.
Systems Architect
Ensures all specs are catered to with the right support.

6. And assemble a team.
To commence
SDLC.

7. ISIntroducing, the System
Development Lifecycle (SDLC)

8. 5 steps of SDLC.
1. Planning
4. Implementation
5. Operation,
Support & Security
3. Design
2. Analysis

9. SDLC
Let’s talk about
PLANNING
Phase one:
5 steps in making sure the
system is successful
• Begins when the steering committee
(stakeholders) receives the request.
• Includes:
• Review & approval of requests.
• Prioritise requests.
• Allocation of resources.
• Find the right team members.
I call the shots
here.

10. SDLC
Let’s talk about
ANALYSIS
Phase two:
5 steps in making sure the
system is successful
• Conducts two things:
• To create a:
Feasibility Study
(Or preliminary investigation)
• To determine if the project
is really worth doing.
• Using data gathering
techniques:
• Documentation Review
• Observation
• Questionnaire / Interview
• Joint-Application Design
(JAD)
• Research
Detailed Analysis
(Or logical design)
• To determine what the
project should have by:
• Studying how the current
system works
• Find out users’
requirements and needs
• Recommend a solution
+
System Proposal
• Contains the results from Feasibility Study
• Recommends solution based on detailed analysis
• Presented to Steering Committee for decision making

11. SDLC
Let’s talk about
DESIGN
Phase three:
5 steps in making sure the
system is successful
• Does two things to ensure all
components of the system is present:
• The outcome: Deliverables that will
help periodic inspection to make sure
errors are identified and fixed.
Acquire Required
Hardware & Software
• To identify relevant
technical specifications
• Solicit vendor proposals
• Test & evaluate proposals
• Make a decision
Develop All Details of
The Required System
(Detailed / Physical design)
• Detailed specifications for
all required system
components:
1.
2.
3.
Database Design
Input & Output Design
Program Design

12. DESIGN
Phase three:
Database Design Input & Output Design Program Design
Goal of Detailed /
Physical Design:
To remove ambiguity among the programming team
during the implementation phase.
List down what data &
records are needed.
A table of expected inputs &
outputs from the system.
A mockup containing sample
data and information.

13. SDLC
Let’s talk about
IMPLEMENTATION
Phase four:
5 steps in making sure the
system is successful
• To construct new or modified system
to be deployed for the users.
• Four (4) phases:
Develop
Test
Train
Convert
Programmers write code.
For quality assurance.
Show users how to use.
Replace old system.

14. IMPLEMENTATION
Phase four:
Develop Test Train Convert
Step 1:
Analyze
Requirements
Step 2:
Design
Solution
Step 3:
Validate
Design
Step 4:
Implement
Design
Step 5:
Test
Solution
Step 6:
Document
Solution
Making sure
Detailed / Physical
design is clear.
Starts preparing
coding framework
and pseudocode.
Checks if framework
is suitable for the
system.
Starts developing the
required features.
Quality checks to
ensure features are
working as intended.
Produces both technical
& user manuals for
future reference.

15. IMPLEMENTATION
Phase four:
Develop Test Train Convert
Quality checks to
ensure features are
working as intended.
Step 5:
Test
Solution
Unit
Testing
Verifies each
module /
feature works
by itself.
Systems
Testing
Verifies all
modules / features
work together.
Integration
Testing
Verifies overall
system works with
other systems.
Acceptance
Testing
Verifies new systems
works with actual data.

16. IMPLEMENTATION
Phase four:
Develop Test Train Convert
• Sessions / workshops with the
users to guide them in using the
new system.
• Users are usually grouped based
on their departments or user
access level.
• User manuals are given out as a
guide.

17. IMPLEMENTATION
Phase four:
Develop Test Train Convert
4 Types of Conversion Strategies
Direct Old System New System
Parallel Old System
New System
Phased
Old System New System
Pilot Old Old New New
New Old Old New
Old New Old New

18. SDLC
Let’s talk about
OPERATION,
SUPPORT &
SECURITY
Phase five:
5 steps in making sure the
system is successful
• To provide on-going assistance after
system is implemented:
• Post-Implementation Review: meeting
ensure system is performing to expectations.
• Perform Maintenance Activities: Keeping
the system in a good state for repair /
upgrades / transfers.
• Monitor System Performance: Periodic
checks to ensure system is running optimally
(speed, accuracy, reliability, etc).
• Assess System Security: To have a
computer security plan to explain all the
safeguards in place and considered.
Identify all
system assets
List all potential
security risks
List safeguards
for each risk

19. 5 steps of SDLC.
1. Planning
4. Implementation
5. Operation,
Support & Security
3. Design
2. Analysis

20. ISHow do you think companies / project
teams can cope with everything in SDLC?

21. Computer-aided
software engineering
(CASE) to support the
activities.
Companies use what we call
In short, softwares to help manage SDLC.

22. Prototyping (UX)
Creates wireframe / models to help
users visualise the system better.
Project Management
Keeps tracks of tasks, backlogs and
timeline for timely system delivery.
Code Repository
Central codes storage for coding
teams and to minimise overlaps.
Quality Assurance
Analyzes deliverables to ensure
input/output is accurate & expected.
Housekeeping
User access management, security
processes, backup & recovery.
Graphics
Enables drawing of project diagrams,
flow charts or user interface.

23. QUESTIONS?
jan.wong@apu.edu.my
slideshare.net/janwong
iamjanwongjanwongmy janwongmy