



















Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
An overview of the Systems Development Life Cycle (SDLC), focusing on the four fundamental phases: planning, analysis, design, and implementation. Each phase consists of various steps and techniques that produce deliverables. The document also introduces risk management in the context of SDLC.
Typology: Assignments
1 / 27
This page cannot be seen from the preview
Don't miss anything!




















THE SYSTEMS DEVELOPMENT LIFE CYCLE
Introduction to SDLC
o Planning phrase
o Analysis phrase
o Design phrase
o Implementation phrase
Introduction to risk management
The planning phase is the fundamental process of understanding why an
information system should be built and determining how the project
team will go about building it
Focus: Why build this system?
How to structure project?
Primary outputs
o System Request with feasibility study
o Project plan
Identify opportunity
o Example: how will it lower costs or increase revenues?
Analyze feasibility
o Examines key aspects of the proposed project
Develop work plan
Staff project
Control and direct project
System request
o A system request presents a brief summary of a business need, and it explains how a system
that supports the need will create business value
Feasibility study
Project plan
o How the project team will go about developing the system
In the analysis phase, the systems analyst works extensively with the
business users of the new system to understand their needs from the
new system.
Focus: Who, what where, and when for this system?
Primary output: System proposal
System proposal
o Requirements definition
o Use cases
o Process models
o Data model
Business process: automation, improvement, reengineering
Interview, JAD, Questionnaire, Document analysis..
Use case analysis
Data flow diagramming
Entity relationship modeling
Normalization
Design architecture
o Describes the system’s hardware, software, and network environment.
o The architecture design flows primarily from the nonfunctional requirements, such as operational,
performance, security, cultural, and political requirements
Design interface
o It includes the screen displays that provide navigation through the system, the screens and forms that
capture data, and the reports that the system produces
Design programs
o Examples: Physical DFD, Structure chart, Psedocode, cohesion, coupling, event driven…
Design databases
o Examples: data storage format, Physical ERD, Optimizing data storage
Alternative matrix
o Can be used to organize the pros and cons of the design alternatives so that the best solution will
be chosen in the end
System specification
o Architecture report
o Hardware & software specification
o Interface design
o Physical process model
o Program design
o Database & file specification
o Physical data model
Programmers will carry out the time-consuming and costly task of
writing programs, while the systems analyst prepares plans for a variety
of tests that will verify that the system performs as expected
Focus: delivery and support of completed system
Primary output: Installed system