06-09-2021

INTRODUCTION Need ???

Information systems
the
structure for meeting the support
Billions of dollars spent yearly on acquisition,
company's design, development, implementation, and
strategies and goals maintenance of IT systems
New systems Companies depend on information more than
are created ever
-employees requestit Leads to the need of systematic and
---
to obtain a
competitive advantage strategic approach for development of new
systems

SYSTEMS DEVELOPMENT LIFE CYCLE

(SDLC) SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC)
Systems development life cycle (SDLC) - a The SDLC has 6
structured step-by-step approach for phases:
1. Recognition of need
developing information systems
Typical activities include: 2. Feasibility study and planning
3. Analysis
Determining budgets
Gathering business requirements 4. Design
Designing models 4.1 Development (coding)
Writing user documentation
4.2 Testing
5. Implementation
6. Maintenance

SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC) SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC)
SDLC
**

ACTIVITIES SDLC PHASE ACTIVITIES

PHASE Design Design the technical architecturegeneral design
specifications (general solution)
Recognition ofPreliminary survey/ initial investigation -Design system models
need statement of scope and objectives Detailed design specifications output, input, files,
procedures, interface, testing technique and criteria,
Feasibility -Evaluation of existing system and procedures documentation, user training
study Analysis of alternative candidate systems 4.1 Program Build technical architecture
Development and Build databases and programs
| Cost estimates
Testing Write test conditions
Analysis Data collection-- Gather business Perform testing
Unit testing8
Tequirements
Combined module testing
Detailed evaluation of present system User acceptance testing
 DEVELOPMENT LIFE CYCLE (SDLC
SYSTEMS
DEVELOPMENT LIFE CYCLE (SDLC)
SYSTEMS
1. PLANNING
ACTIVITIES
SDLC PHASE
2. ANALYSIS
7. MAINTENANCE
documentation
Write
|5. Implementation |
user

SDLC
| -Provide training
3.DESIGN
File/system conversion 6. IMPLEMENTATION

6. Post- Build a help desk

implementation Evaluation 5. TESTING 4. DEVELOPMENT
& Maintenance Maintenance

| Enhancement---Support system changes

Phase 1: Planning/initial investigation Phase 1: Planning

Planning phase- 2. Set the project scope

- What is the problem or opportunity Project scope clearly defines the high-level system
requirements
involves determining a solid plan for Scope creep - occurs when the scope of the project
developing your information system increases
occurs when developers add extra
primary planning activities: Featurecreep
Three features that were not part of the initial requirements
1. Define the system to be developed Project scope document -

a written definition of the

Critical success factor (CSF) - a factor simply project scope an is usually no longer than a

critical to your organization's success paragraph

Phase 1: Planning 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 12wwss

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 1se
penea

Project milestones- represent key dates for which you

need a certain group of activities performed
 06-09-2021
Phase 2:
What are the Feasibility Study
Is the user's
problem worthdemonstrable needs? Phase 3: Analysis
problem solving?
How can the
be Analysis phase
Results-Technical/behavioral feasibility, cost
benefit analysis,
redefined?
statement of
scope and Objectives new
specialists workinginvolves end users and IT
-

together to gather,
understand, and document
system requirements
-What must be
for the
the business
proposed
done to system
solve the
-What are the facts problem

Phase 3: Analysis
Two primary
1. analysis activities: Phase 3: Analysis
Gather the business
Business requirements 2. Prioritize the
requirements-
worker requests that the detailed set of Requirementsrequirements
the system must meet knowledge definition
requirements anddocument-prioritizes the
be successful in order business
to
Joint
applicotion comprehensive document places them in a formal
workers and IT development (JAD)- knowledge
-

Results- logical model of

days, to define specialists
or review
meet, sometimes for several dictionary, data flow diagram,system e.g. data
the business
the system
requirements
for data). databases (pertinent

Phase 3: Analysis
$2.000
Phase 4: Design
S1,800
$1,600 Design phase -

builda
technical
work blueprint of how
$1,400 the proposed system will
S1,200 In general, what is the solution?
$1,000 format) (output and its
S800
600 Specifically, what is the solution (input and files
S400
specifications, databases)
$200 Processing/ flow of system
SO Does the user approve the
Pianning Anpys system
Desg DevelopmenM Testing mplementatian Maintenanee How well individual
Are programs ready for
programs/modules test out
acceptance test
 Phase 4: Design
Phase 4: Design
models
of how the 2. Design system
Design phase build a technical blueprint
-

proposed system will work,

Modeling the activity of drawing a graphical
representation of a design
- alternative solutions design,
the interface to
Graphical user interface (GUI) an
-

cost/benefit analysis,
hardware, cost, implementation schedule and specifications,
information system
test plans, formal system test, user approval of system,
security audit and operating procedures

Two primary design activities:

1. Design the technical architecture
Technical architecture defines the hardware, software, and
telecommunications equipment required to run the system

Phase 4.1: Development Phase 4.2: Testing

Development phase - take all of your detailed
design documents from the design phase and Testing phase- verifies that the system works
and meets all of the business requirements
transform them into an actual system defined in the analysis phase
Two primary development activities: Jwo primary testing activities:
1. Build the technical architecture
1. Write the test conditions
2. Build the database and programs Test conditions -the detailed steps the system must
Both of these activities are mostly perform along with the expected results of each step
performed byIT
specialists

Phase 4.2: Testing

Phase 5: Implementation
2. Perform the testing of the system
Unit testing -tests individual units of code Implementation phase distribute the
System testing-verifies that the system to all of the
correctly when integrated
units of code function knowledge workers and
Integration testing-verifies that separate systems
they begin using the system to perform their
work together everyday jobs
User acceptance testing (UAT)- determines if the Actual operation?, user manuals
system satisfies the business
requirements delays? ready?, any
 06-09-2021

Phase 5: implementation
Two Phase 5: Implementation
primary implementation activities
1. Write detailed user Choose the right
User
documentation implementation method
documentation highlights how to use the
-
-

Parallel implementation use -

both the old and

2. Provide training for the system new system simultaneously
system users
Online training runs over the Internet
-

Plunge implementation discard the old system

or off a CD-ROM completely and use the new
Workshop training- is held in a classroom environment
and lead by Pilot Implementation - start with small groups of
an instructor
people on the new system and gradually add more
users
Phased Implementation- implement the new
system in phases

Phase 6: Maintenance
Project termination
Maintenance phase monitor and support
-
Changing objectives or requirements of the user
cannot be met by existing project
the new system to ensure it continues to - Requirements are not clearly defined o r understood

meet the business goals - Non- involvement of users

system running ---

- Inexperienced analysts/programmers
well?, require modification? -

Feasibility study is poor

Two primary maintenance activities: -

User training is poor

1. Build a help desk to support the system users -

Hardware is not properly planned

H e l p desk - a group of people who responds to
-

New system has drastic change

knowledge workers' questions
-

New system was not user-friendly

2. Provide Benefits realized are not justified

an environment to support system
Sudden change in user's budget as compared to
changes estimated budget
Project has cost as well as time creep

sYSTEMS DEVELOPMENT
METHODOLOGIES
Waterfall Methodology
Developers have different development Waterfall methodology-a sequential,
methodologies: activity-based process in which each phase in
- Waterfall methodologBy
the SDLC is performed sequentially from
- prototyping
planning through implementation
 Waterfall M o d e l - Advantages
Waterfall Model - Application
understand and use
Simple and easy to
Requirements are very well documented, clear to the rigidity of the model. Each
Easy to manage due deliverables and a review process.
and fixed. phase has specific
deadlines for each stage of
A schedule can be set with
Product definition is stable. development and a product can proceed through the
model phases one by one
development process
Technology is understood and is not dynamic. where requirements
well for smaller projects
are
Works
There are no ambiguous requirements. very well understood.

Clearly defined stages.

Ample resources with required expertise are Well understood milestones.
available to support the product. Easy to arrange tasks.
Process andresults are well documented.
The project is short.

Waterfall Model- Disadvantages PROTOTYPING

Nocycle.working software is produced until late during the lfe Prototyping - the process of building a model
High amounts of risk and uncertainty.
Not a good model for complex and object-oriented projects. that demonstrates the features ofa proposed
Poor model for long and ongoing projects. product, service, or system
Not suitable for the projects where requirements are at a - Proof-of-concept prototype - used to prove the
moderate to high risk of changing. So, risk and uncertainty is
high with this process model. technical feasibility of a proposed system
I t is difficult to measure progress within stages. - Selling prototype - used to convince people of the
Cannot accommodate changing requirements. worth of a proposed system
Adjusting scope during the life cycle can end a project.
Integration is done as a "big-bang". At the very end, which
doesn't allow identifying any technological or business
bottleneck or challenges early.

The Prototyping Process The Prototyping Process

STEP
The prototyping process involves four steps: edy
rseata

1. Identify basic requirements

$TRP2
. Develop initial prototype
Frootvpe
3. User review
4. Revise and enhance the prototype wpeWorkas

STEP

Konpnue theso >

06-09
06-09-202

Advantages of Prototyping
Disadvantages of Prototyping
Encourages -Active User Participation
Helps-Resolve Discrepancies Among Users Leads-People to Believe the Final System Will
Follow
Gives-Users a Feel for the Final System Gives--No Indication of Performance under
.Helps--Determine Technical Feasibility Operational Conditions
.Helps--Sell the ldea of a Proposed System Leads--the Project Team to Forgo Proper
Testing and Documentation