The System Development Life Cycle (SDLC) outlines six main phases for developing hardware and software systems: planning, analysis, design, implementation, support, and review. During planning, project requests are prioritized and resources allocated. Analysis involves investigating current systems and user requirements. Design develops system details and programs. Implementation builds the new system, trains users, and tests. Support provides ongoing assistance after deployment. Review assesses system performance after implementation. The SDLC aims to develop systems that meet user needs through documentation, testing, and stakeholder involvement at each phase.

2. System Development Life Cycle (SDLC)
by
ANEESH.S

3. System Development Life Cycle (SDLC)
1. System Development Life Cycle (SDLC) is a series
of six main phases to create a hardware system
only, a software system only or a combination of
both to meet or exceed customer’s expectations.

4. The System Development Life Cycle
What is an information system (IS)?
Hardware, software, data,
people, and procedures that
work together to produce
quality information
Hardware, software, data,
people, and procedures that
work together to produce
quality information
System—Set of components
that interact to achieve
common goal
System—Set of components
that interact to achieve
common goal
Businesses use many types of
systems
Businesses use many types of
systems

5. The System Development Life Cycle
What are the phases of the system development cycle?
Phase 1. Planning
Phase 2. Analysis
Phase 3. Design
Phase 4. ImplementationPhase 5. Support
 Review project requests
 Prioritize project
requests
 Allocate resources
 Identify project
development team
 Conduct preliminary investigation
 Perform detailed analysis activities:
Study current system
Determine user requirements
Recommend solution
 Acquire hardware
and software, if
necessary
 Develop details of
system
 Develop programs, if necessary
 Install and test new system
 Train users
 Convert to new system
 Conduct post-implementation
system review
 Identify errors and enhancements
 Monitor system performance

6. Arrange tasks into phases
(groups of activities)
The System Development Life Cycle
What are guidelines for system development?
Involve users (anyone for whom
system is being built)
Develop clearly defined standards (procedures
company expects employees to follow)

7. The System Development Life Cycle
Who participates
in the system
development life
cycle?

8. The System Development Life Cycle
What is a systems analyst?
Responsible for designingResponsible for designing
and developingand developing
information systeminformation system
Liaison between usersLiaison between users
and IT professionalsand IT professionals

9. The System Development Life Cycle
What is the project team?
Consists of users, systems analyst, and other IT professionals
Formed to work on project from beginning to end
Project leader—one member of the team who
manages and controls project budget and schedule

10. The System Development Life Cycle
What is feasibility?
Measure of
how suitable
system
development
will be to the
company
Operational
feasibility
Schedule
feasibility
Four feasibility
tests:
Technical
feasibility
Economic
feasibility
(also called
cost/benefit
feasibility)

11. The System Development Life Cycle
What is documentation?
Includes reports, diagrams,
programs, and other deliverables
Collection and summarization
of data and information

12. The System Development Life Cycle
What are six data and information gathering techniques?
 Review documentation
 Observe
 Questionnaire
 Interview
 Joint-application
design (JAD) session
 Research

13. The System Development Life Cycle
What are some reasons to create or modify an
information system?
Competition can
lead to change
To improve
existing system
Outside group may
mandate change
To correct problem
in existing system

14. The System Development Life Cycle
What is a request for system services?
 Formal request for
new or modified
information system
 Also called
project request

15. The System Development Life Cycle
What is the planning phase?
Begins when steering committee receives project request
SteeringSteering
committeecommittee——
decision-makingdecision-making
body for thebody for the
companycompany
Function of committee:
Review andReview and
approve projectapprove project
requestsrequests
AllocateAllocate
resourcesresources
Form projectForm project
developmentdevelopment
team for eachteam for each
approvedapproved
projectproject
PrioritizePrioritize
project requestsproject requests

16. The System Development Life Cycle
What is the analysis phase?
Conduct preliminaryConduct preliminary
investigation, alsoinvestigation, also
called feasibilitycalled feasibility
studystudy
Perform detailedPerform detailed
analysisanalysis

17. The System Development Life Cycle
What is the preliminary investigation?
 Determine exact nature of problem or improvement
and whether it is worth pursuing
 Findings are presented in feasibility report, also known as a feasibility study

18. The System Development Life Cycle
What is detailed analysis?
Sometimes called logical design
2. Determine user’s wants, needs,
and requirements
3. Recommend solution
1. Study how current system
works

19. Presented toPresented to
steeringsteering
committee,committee,
which decideswhich decides
how system willhow system will
be developedbe developed
The System Development Life Cycle
What is the
system proposal? AssessesAssesses
feasibilityfeasibility
of eachof each
alternativealternative
solutionsolution
RecommendsRecommends
the mostthe most
feasiblefeasible
solution forsolution for
the projectthe project

20. The System Development Life Cycle
What are possible solutions?
Buy packaged software—prewritten
software available for purchase
Buy packaged software—prewritten
software available for purchase
Outsource—have outside source
develop software
Outsource—have outside source
develop software
Write own custom software—software
developed at user’s request
Write own custom software—software
developed at user’s request
Vertical market
software—designed
for particular industry
Vertical market
software—designed
for particular industry
Horizontal market
software—meets
needs of many
companies
Horizontal market
software—meets
needs of many
companies

21. The System Development Life Cycle
What is the design phase?
Acquire hardware and softwareAcquire hardware and software
Develop all details of new or
modified information system
Develop all details of new or
modified information system

22. Visit vendors’ storesVisit vendors’ storesVisit vendors’ storesVisit vendors’ stores
The System Development Life Cycle
What is needed to acquire new hardware and software?
 Identify all hardware and software requirements of new or
modified system
Surf WebSurf WebSurf WebSurf Web
Read print andRead print and
online trade journals,online trade journals,
newspapers, andnewspapers, and
magazinesmagazines
Read print andRead print and
online trade journals,online trade journals,
newspapers, andnewspapers, and
magazinesmagazines
Talk with otherTalk with other
systems analystssystems analysts
Talk with otherTalk with other
systems analystssystems analysts

23. The System Development Life Cycle
What are three basic documents used to summarize
technical specifications?
Less formal method
that uses standard
form to request
information about
product or service
Vendor quotes
price(s) for
listed
product(s)
Vendor selects
product(s) that
meet(s) your
requirements and
then quotes price(s)
Identifies
product(s)
you want
Request for information (RFI)Request for information (RFI)
Request for proposal (RFP)Request for proposal (RFP)
Request for quotation (RFQ)Request for quotation (RFQ)

24. The System Development Life Cycle
How do systems analysts test software products?
 References from vendor
 Talk to current users of product
 Product demonstrations
 Trial version of software
 Benchmark test measures performance

25. The System Development Life Cycle
What is a detailed design?
Includes several activities
Database
design
Database
design
Input and
output design
Input and
output design
Program
design
Program
design
Detailed design specifications for components in proposed solution

26. The System Development Life Cycle
What is a mockup?
 Sample of input or output that contains actual data

27. The System Development Life Cycle
What is a prototype?
Working model of
proposed system
Working model of
proposed system
Beginning a prototype
too early may lead to
problems
Beginning a prototype
too early may lead to
problems

28. The System Development Life Cycle
What is computer-aided software engineering (CASE)?
 Software tools designed to support activities of system
development cycle

29. Convert to new systemConvert to new system
The System Development Life Cycle
What is the implementation phase?
 Purpose is to construct, or build, new or modified
system and then deliver it to users
Train usersTrain users
Install and test new systemInstall and test new system
Develop programsDevelop programs

30. The System Development Life Cycle
What are the three types of tests performed by system
developers?
Verifies application
works with other
applications
Systems test
Integration Test
Unit Test
Verifies each
individual program
works by itself
Verifies all programs
in application work
together

31. The System Development Life Cycle
What is training?
 Showing users exactly
how they will use new
hardware and software
in system

32. The System Development Life Cycle
What is the support phase?
Conduct post-implementation system review—meeting to find out if
information system is performing according to expectations
Identify errors
Identify enhancements
Monitor system performance
 Provides ongoing assistance after system is implemented

33. Advantages
1. Formal review is created at the end of each stage
allowing maximum management control.
2. This approach creates considerable system
documentation.
3. This documentation ensures that system
requirements can be traced back to stated business
requirements.
4. It produces many intermediate products that can be
reviewed to see whether they meet the user’s needs
and conform to standards. These can be further
worked on if they require tweaks to be made,
ensuring that the business gets exactly what it
needs.

34. Disadvantages
1. What may be seen as a major problem for some, end-user
does not see the solution until the system is almost
complete.
2. Users get a system that meets the need as understood by the
developers; this may not be what was really needed for
them. There may be a loss in translation.
3. Documentation is expensive and time-consuming to create.
It is also difficult to keep current. What may be current
this month may not be the same this time next year!
4. Users cannot easily review intermediate products and
evaluate whether a particular product (e.g., data flow
diagram) meets their business requirements.