INTRODUCTION TO

INFORMATION SYSTEMS

Safia Bal-Bourai
s_bourai@esi.dz

2CP 2024-2025

11
Chapter 4:

Fundamental IS
development process

2
 Objectives
• Explain the importance of a structured
approach to information system
development.
• Describe the key phases of the SDLC
(Systems development life cycle).
• Identify the risks of skipping or rushing
through any phase of the SDLC.
• Apply best practices in SDLC.

Content
• Introduction to SDLC
• Overview of SDLC phases
• Success factors and risks
3
What is the systems
development process?

Systems development process is the activity of

creating new systems or modifying existing
systems. It refers to all aspects of the process
from identifying problems to solve or
opportunities to exploit to implementing and
refining the chosen solution.

4
Why initiate a Development
Project?
When an organization needs to accomplish a new
task or change a work process, how does it do so?

It develops a new system or modifies an existing

one.

5
Initiating Systems Development

Organizations embark on systems development

in response to various factors, such as
technological advancements, changes in
business processes, increased competition,
the need to improve efficiency,… These
causes play a crucial role in shaping the
direction and scope of any new system
project.

6
Initiating Systems Development

Figure 1: Typical Reasons to Initiate a

Systems Development Project 7
System development Life
cycle (SDLC)
The systems development process is also called a
systems development life cycle (SDLC) because the
activities associated with it are ongoing. As each
system is built, the project has timelines and
deadlines, until at last the system is installed and
accepted.
The life of the system continues as it is maintained and
reviewed. If the system needs significant
improvement beyond the scope of maintenance, if it
needs to be replaced because of a new generation of
technology, or if the IS needs of the organization
change significantly, a new project will be initiated
and the cycle will start over.

8
System Development Life
Cycle (SDLC)
❏ The systems are best developed through the
use of a systematic development approach.
❏ The systems development life cycle (SDLC) is
a conceptual model used in project
management. It describes the stages
involved in an information system
development project, from an initial
feasibility study (investigation) through
maintenance of the completed application.

9
System Development Life Cycle
(SDLC)

10
Participants in Systems
Development

11
IS Planning

The translation of strategic

and organizational goals
into system
development initiatives.

Designing new systems or modifying Figure 2: IS planning

existing ones should always be

aimed at helping an organization
achieve its goals.
12
Importance of IS Planning
- The IS plan should guide
development of the IS
infrastructure over time.
- The IS planning is that it
ensures better use of IS
resources including funds,
personnel and time for
scheduling specific projects.
- The steps of IS planning are
shown in Figure 3.
Figure 3: IS planning’s steps

13
SDLC Approaches

Several common systems development life cycles exist:

- Traditional
- Prototyping
- Application development (RAD) and Joint Application
Development (JAD)
- End-user systems development
- Use of CASE tools
- Object-Oriented Systems Development
In addition, companies can outsource the systems
development process. 14
The Traditional Systems
Development Life Cycle

Figure 4: The Traditional Systems

Development Life Cycle

Sometimes, information learned in

a particular phase requires cycling
back to a previous phase.
15
The traditional Systems
Development Life Cycle
▪ Systems investigation: problems and
opportunities are identified and considered in
light of the goals of the business.
▪ Systems analysis: study of existing systems
and work processes to identify strengths,
weaknesses, and opportunities for
improvement.
▪ Systems design: defines how the
information system will do what it must do to
obtain the problem’s solution
16
The traditional Systems
Development Life Cycle
▪ Systems implementation: the creation or
acquiring of various system components
detailed in the systems design, assembling
them, and placing the new or modified
system into operation.
▪ Systems maintenance and review: ensures
that the system operates, and modifies the
system so that it continues to meet changing
business needs.

17
Prototyping
Prototyping is a system development method that
is carried out in successive steps (iterative
approach).
In each iteration, the following actions are taken:
● User needs and possible solutions to the
problem are identified and analyzed.
● New ideas are designed to improve the system.
● A part of the system is implemented, meaning a
prototype (a test model) is created.
Then, users test this prototype and provide their
feedback. 18
Prototyping

Figure 6: Refining
During Prototyping
Each generation of prototype
is a refinement of the
Figure 5: Prototyping previous generation based on
user feedback.
19
Rapid Application Development (RAD)
and Joint Application Development
(JAD)
▪ Rapid application development (RAD): a
systems development approach that employs
tools, techniques and methodologies designed
to speed application development.
▪ Joint application development (JAD): a process
for data collection and requirements analysis in
which users, stakeholders and IS professionals
work together to analyze existing systems,
propose possible solutions and define the
requirements of a new or modified system.
20
The End-User Systems
Development Life Cycle
Any systems development project in which the
primary effort is undertaken by a combination
of business managers and users End-user-
developed systems can be structured as
complementary to, rather than in conflict with,
existing and emerging information systems

21
Use of Computer-Aided Software
Engineering (CASE) Tools
▪ Tools that automate many of the tasks
required in a systems development effort and
enforce adherence to the SDLC.
▪ These tools enable users to :
- Save time

- Reduce errors

- Ensure better organization

- Support SDLC steps

22
Use of Computer-Aided Software
Engineering (CASE) Tools

Examples:
- Microsoft Visio
- StarUML, Lucidchart
- Enterprise Architect
- Visual Paradigm
- PowerDesigner (SAP)

23
Object-Oriented Systems
Development
▪ OOSD is the approach that combines the logic of
the systems development life cycle with the
power of object-oriented modeling and
programming.
▪ OOSD typically involves:
- Identifying potential problems and opportunities
within the organization that would be appropriate
for the OO approach
- Defining the kind of system users require
- Designing the system
- Programming or modifying modules
- Evaluation by users
- Periodic review and modification 24
 1. Systems investigation

▪ Systems investigation: is the exercise of

understanding the problem to be solved
or opportunity to be addressed.

1- Systems Request form:

- Identifies problems or opportunities
- States objectives of systems
investigation
- Presents an overview of the proposed
system
- Projects expected costs and benefits of
the proposed system

25
1. Systems investigation
2. Feasibility analysis
Legal
feasibility

Operational
feasibility
Measure of the
feasibility of the
Feasibility
system
tests:
development for
Schedule
the company feasibility

Economic
feasibility
(also called Technical
cost/benefit feasibility
feasibility)
26
 1. Systems investigation
3. Feasibility Analysis
Systems investigation report

A summary of the results of the

systems investigation and the
process of feasibility analysis
and recommendations of a
course of action.

27
 2. Systems analysis

Systems analysis: includes

gathering all the specific details
required for a new system as well
as determining the first ideas for
prototypes.

28
 2. Systems analysis
The activities in this stage:
1. Assembling the participants for systems analysis

2. Collecting appropriate data and requirements

3. Analyzing the data and requirements

4. Preparing a report on the existing system, new system requirements

and project priorities

29
3.Systems design
Systems design: how the new system will
work to meet the business needs
defined during systems analysis.
The purpose of systems design is to
answer the question “How will the
information system solve a problem?”.
The systems design details system
outputs, inputs, and user interfaces;
specifies hardware, software,
telecommunications, personnel and
procedures and shows how these
components are related.

30
4. Systems implementation
▪ Systems implementation: creating or
acquiring the various system
components defined in the design
step, assembling them, and putting
the new system into operation.
▪ It involves:
- Hardware and software acquisitions
- Software development
- Testing of programs and procedures
- User training
- Development of technical
documentation
- Various installation activities

31
5. Systems maintenance and review

▪ Systems maintenance
and review: check and
modify the system so
that it continues to meet
changing business needs.

32
Systems maintenance

Reasons for the need of Maintenance:

▪ Bugs or errors in the program

▪ New requests from users and stakeholders
▪ Technical and hardware problems
▪ Change in operating system or hardware
▪ Changes in business processes
▪ Corporate mergers and acquisitions
▪ Government regulations

33
Systems review

▪ Process of analyzing systems to make sure that

they are operating as intended: Often compares
the performance and benefits of the system as it
was designed with the actual performance and
benefits of the system in operation.
▪ Event-driven review: review triggered by a
problem or opportunity, such as an error, a
corporate merger or a new market for products.
▪ Time-driven review: review performed after a
specified amount of time.
34
Success Factors and Risks in
IS development process
Key Success Factors
▪ Clear Requirements Definition: Well-defined user needs and
business objectives.
▪ Project Management: Timeline control, resource allocation,
risk mitigation, Flexibility to adapt to changes,...
▪ Stakeholder Involvement: Regular feedback and
collaboration.
▪ Skilled Team Members: Competent developers, analysts,…
▪ Effective Communication among team members and
stakeholders.
▪ Technology Fit: Appropriate tools and platforms for the
system.

35
Success Factors and Risks in
IS development process
Common Risks
▪ Scope Creep: Uncontrolled changes leading to delays and
budget overruns
▪ Poor Requirement Analysis: Leads to product misalignment
with user needs.
▪ Inadequate Testing : Increases chances of post-deployment
failures.
▪ Resource Constraints: Budget, time or personnel shortages.
▪ Lack of User Involvement: Results in resistance or poor system
adoption.
▪ Unrealistic Timelines: Leads to rushed development and lower
quality.
▪ Technological Challenges: Incompatibilities or lack of technical
expertise.
36
 To Remember…
▪ The SDLC provides a structured approach to building high-
quality information systems.
▪ Each phase (Investigation, Analysis, Design, Implementation
and Maintenance ) is essential to project success.
▪ Skipping or rushing a phase may lead to errors, increased costs
or failure.
Best Practices
▪ Take time for detailed requirement analysis and planning.
▪ Ensure clear communication among all users.
▪ Use Agile principles when flexibility and quick feedback are
needed.
▪ Regularly monitor risks, scope and quality.
▪ Provide strong user training and support during deployment and
maintenance.
37
References

▪ Chalal R.(2021), Système d’information. Boite à outils

d’analyse, Pages Bleues Internationales.
▪ Morley C. (2016), Management d’un projet Systèmes
d’information, 8ème édition, DUNOD.
▪ Stair, R., & Reynolds, G. (2018), Fundamentals of
Information Systems (9th ed.), Cengage Learning.

38