CSD 012_01
CSD 012_01
CSD 012
An information system is a
collection of interrelated
components that collect, process
and store, and provide as output
the information needed to
complete a business task.
4
Examples of Information
Systems
• Course registration system
• Online order system
• Online banking system
5
Systems
Can Be Composed of Subsystems
System
8
System Analysis vs.
System Design
• System Analysis:
– Investigation of the problem and requirement
rather than solution.
• System Design:
– A conceptual solution that fulfills the
requirements, rather than implementation.
9
System Analyst
• A business professional who uses analysis
and design techniques to solve business
problems using information technology.
10
The Role of a System
Analyst
• Business knowledge.
• Business problem solver.
• Help translate business requirements into IT
projects.
11
Traditional System Development
Life Cycle (SDLC)
12
Traditional System Development
life Cycle (SDLC)
• Project planning – initiate, ensure feasibility, plan
schedule, obtain approval for project
• Analysis – understand business needs and
processing requirements
• Design – define solution system based on
requirements and analysis decisions
• Implementation – construct, test, train users, and
install new system
• Support – keep system running and improve it
13
• Each of the phases include a set of steps, which
rely on techniques that produce specific
deliverables that provide understanding about
the project.
1 - 14
• To Understand the SDLC:
– Each phase consists of steps that lead to specific deliverables
– The system evolves through gradual refinement
1 - 15
Planning
• This phase is the fundamental
process of understanding why an
information system should be built.
• The Planning phase will also
determine how the project team
will go about building the
information system.
• The Planning phase is composed
of two planning steps.
1 - 16
Planning
1. During project initiation, the system’s
business value to the organization is identified
(How will it lower costs or increase revenues?)
as well as the feasibility of the project from
different point of views
1 - 18
Analysis
1. Analysis strategy: This is developed to guide
the projects team’s efforts. This includes an
analysis of the current system.
2. Requirements gathering: The analysis of this
information leads to the development of a
concept for a new system. This concept is used
to build a set of analysis models.
3. System proposal: The proposal is presented
to the project sponsor and other key individuals
who decide whether the project should
continue to move forward.
1 - 19
Analysis
• The system proposal is the initial
deliverable that describes what
business requirements the new
system should meet.
• The deliverable from this phase
is both an analysis and a high-
level initial design for the new
system. 1 - 20
Design
• In this phases it is decided how the
system will operate, in terms of the
hardware, software, and network
infrastructure; the user interface,
forms, and reports that will be used;
and the specific programs,
databases, and files that will be
needed.
1 - 21
Design
1. Design Strategy: This clarifies whether the
system will be developed by the company
or outside the company.
2. Architecture Design: This describes the
hardware, software, and network
infrastructure that will be used.
3. Database and File Specifications: These
documents define what and where the data
will be stored.
4. Program Design: Defines what programs
need to be written and what they will do.
UI Design
1 - 22
Implementation
• During this phase, the system is
either developed or purchased
(in the case of packaged
software).
• This phase is usually the
longest and most expensive
part of the process.
• The phase has three steps.
1 - 23
Implementation
• System Construction: The
system is built and tested to make
sure it performs as designed.
• Installation: Prepare to support
the installed system.
• Support Plan: Includes a post-
implementation review.
1 - 24