Systems Development Life Cycle

From Wikipedia, the free encyclopedia

Jump to: navigation, search
For other uses, see SDLC (disambiguation).

Model of the Systems Development Life Cycle with the Maintenance bubble highlighted.
The Systems Development Life Cycle (SDLC), or Software Development Life Cycle in systems
engineering, information systems and software engineering, is the process of creating or altering
systems, and the models and methodologies that people use to develop these systems. The
concept generally refers to computer or information systems.
In software engineering the SDLC concept underpins many kinds of software development
methodologies. These methodologies form the framework for planning and controlling the
creation of an information system[1]: the software development process.
Contents
 1 Overview
 2 History
 3 Systems development phases
o 3.1 Requirements gathering and analysis
o 3.2 Design
o 3.3 Build or coding
o 3.4 Testing
o 3.5 Operations and maintenance
 4 Systems development life cycle topics
o 4.1 Management and control
o 4.2 Work breakdown structured organization
o 4.3 Baselines in the SDLC
o 4.4 Complementary to SDLC
 5 Strengths and weaknesses
 6 See also
 7 References
 8 Further reading
  9 External links

[edit] Overview
Systems and Development Life Cycle (SDLC) is a process used by a systems analyst to
develop an information system, including requirements, validation, training, and user
(stakeholder) ownership. Any SDLC should result in a high quality system that meets or exceeds
customer expectations, reaches completion within time and cost estimates, works effectively and
efficiently in the current and planned Information Technology infrastructure, and is inexpensive
to maintain and cost-effective to enhance.[2]
Computer systems are complex and often (especially with the recent rise of Service-Oriented
Architecture) link multiple traditional systems potentially supplied by different software vendors.
To manage this level of complexity, a number of SDLC models have been created: "waterfall";
"fountain"; "spiral"; "build and fix"; "rapid prototyping"; "incremental"; and "synchronize and
stabilize".[citation needed]
SDLC models can be described along a spectrum of agile to iterative to sequential. Agile
methodologies, such as XP and Scrum, focus on light-weight processes which allow for rapid
changes along the development cycle. Iterative methodologies, such as Rational Unified Process
and Dynamic Systems Development Method, focus on limited project scopes and expanding or
improving products by multiple iterations. Sequential or big-design-upfront (BDUF) models,
such as Waterfall, focus on complete and correct planning to guide large projects and risks to
successful and predictable results[citation needed]. Other models, such as Anamorphic Development,
tend to focus on a form of development that is guided by project scope and adaptive iterations of
feature development.
In project management a project can be defined both with a project life cycle (PLC) and an
SDLC, during which slightly different activities occur. According to Taylor (2004) "the project
life cycle encompasses all the activities of the project, while the systems development life cycle
focuses on realizing the product requirements".[3]
[edit] History
The systems development life cycle (SDLC) is a type of methodology used to describe the
process for building information systems, intended to develop information systems in a very
deliberate, structured and methodical way, reiterating each stage of the life cycle. The systems
development life cycle, according to Elliott & Strachan & Radford (2004), "originated in the
1960s to develop large scale functional business systems in an age of large scale business
conglomerates. Information systems activities revolved around heavy data processing and
number crunching routines".[4]
Several systems development frameworks have been partly based on SDLC, such as the
Structured Systems Analysis and Design Method (SSADM) produced for the UK government
Office of Government Commerce in the 1980s. Ever since, according to Elliott (2004), "the
traditional life cycle approaches to systems development have been increasingly replaced with
alternative approaches and frameworks, which attempted to overcome some of the inherent
deficiencies of the traditional SDLC".[4]
[edit] Systems development phases
 This section relies largely or entirely upon a single source. Please help improve this
article by introducing appropriate citations of additional sources. (September 2010)
The System Development Life Cycle framework provides system designers and developers to
follow a sequence of activities. It consists of a set of steps or phases in which each phase of the
SDLC uses the results of the previous one.
A Systems Development Life Cycle (SDLC) adheres to important phases that are essential for
developers, such as planning, analysis, design, and implementation, and are explained in the
section below. Several Systems Development Life Cycle Models exist, the oldest of which —
originally regarded as "the Systems Development Life Cycle" — is the waterfall model: a
sequence of stages in which the output of each stage becomes the input for the next. These stages
generally follow the same basic steps, but many different waterfall methodologies give the steps
different names and the number of steps seems to vary between four and seven. There is no one
correct Systems Development Life Cycle model.

The SDLC can be divided into ten phases during which defined IT work products are created or
modified. The tenth phase occurs when the system is disposed of and the task performed is either
eliminated or transferred to other systems. The tasks and work products for each phase are
described in subsequent chapters. Not every project will require that the phases be sequentially
executed. However, the phases are interdependent. Depending upon the size and complexity of
the project, phases may be combined or may overlap.[5]
[edit] Requirements gathering and analysis
The goal of system analysis is to determine where the problem is in an attempt to fix the system.
This step involves breaking down the system in different pieces to analyze the situation,
analyzing project goals, breaking down what needs to be created and attempting to engage users
so that definite requirements can be defined. Requirements analysis sometimes requires
individuals/teams from client as well as service provider sides to get detailed and accurate
requirements....often there has to be a lot of communication to and from to understand these
requirements. Requirement gathering is the most crucial aspect as many times communication
gaps arise in this phase and this leads to validation errors and bugs in the software program.
[edit] Design
In systems, design functions and operations are described in detail, including screen layouts,
business rules, process diagrams and other documentation. The output of this stage will describe
the new system as a collection of modules or subsystems.
The design stage takes as its initial input the requirements identified in the approved
requirements document. For each requirement, a set of one or more design elements will be
produced as a result of interviews, workshops, and/or prototype efforts. Design elements
describe the desired software features in detail, and generally include functional hierarchy
diagrams, screen layout diagrams, tables of business rules, business process diagrams,
pseudocode, and a complete entity-relationship diagram with a full data dictionary. These design
elements are intended to describe the software in sufficient detail that skilled programmers may
develop the software with minimal additional input design.
[edit] Build or coding
Modular and subsystem programming code will be accomplished during this stage. Unit testing
and module testing are done in this stage by the developers. This stage is intermingled with the
next in that individual modules will need testing before integration to the main project.
[edit] Testing
The code is tested at various levels in software testing. Unit, system and user acceptance testings
are often performed. This is a grey area as many different opinions exist as to what the stages of
testing are and how much if any iteration occurs. Iteration is not generally part of the waterfall
model, but usually some occur at this stage.
Below are the following types of testing:
 Data set testing.
 Unit testing
 System testing
 Integration testing
 Black box testing
 White box testing
 Regression testing
 Automation testing
 User acceptance testing
 Performance testing
 Production process that ensures that the program performs the intended task.
[edit] Operations and maintenance
The deployment of the system includes changes and enhancements before the decommissioning
or sunset of the system. Maintaining the system is an important aspect of SDLC. As key
personnel change positions in the organization, new changes will be implemented, which will
require system updates.
[edit] Systems development life cycle topics
[edit] Management and control

SDLC Phases Related to Management Controls.[6]

The Systems Development Life Cycle (SDLC) phases serve as a programmatic guide to project
activity and provide a flexible but consistent way to conduct projects to a depth matching the
scope of the project. Each of the SDLC phase objectives are described in this section with key
deliverables, a description of recommended tasks, and a summary of related control objectives
for effective management. It is critical for the project manager to establish and monitor control
objectives during each SDLC phase while executing projects. Control objectives help to provide
a clear statement of the desired result or purpose and should be used throughout the entire SDLC
process. Control objectives can be grouped into major categories (Domains), and relate to the
SDLC phases as shown in the figure.[6]
To manage and control any SDLC initiative, each project will be required to establish some
degree of a Work Breakdown Structure (WBS) to capture and schedule the work necessary to
complete the project. The WBS and all programmatic material should be kept in the “Project
Description” section of the project notebook. The WBS format is mostly left to the project
manager to establish in a way that best describes the project work. There are some key areas that
must be defined in the WBS as part of the SDLC policy. The following diagram describes three
key areas that will be addressed in the WBS in a manner established by the project manager.[6]
[edit] Work breakdown structured organization
Work Breakdown Structure.[6]
The upper section of the Work Breakdown Structure (WBS) should identify the major phases
and milestones of the project in a summary fashion. In addition, the upper section should provide
an overview of the full scope and timeline of the project and will be part of the initial project
description effort leading to project approval. The middle section of the WBS is based on the
seven Systems Development Life Cycle (SDLC) phases as a guide for WBS task development.
The WBS elements should consist of milestones and “tasks” as opposed to “activities” and have
a definitive period (usually two weeks or more). Each task must have a measurable output (e.g.
document, decision, or analysis). A WBS task may rely on one or more activities (e.g. software
engineering, systems engineering) and may require close coordination with other tasks, either
internal or external to the project. Any part of the project needing support from contractors
should have a Statement of work (SOW) written to include the appropriate tasks from the SDLC
phases. The development of a SOW does not occur during a specific phase of SDLC but is
developed to include the work from the SDLC process that may be conducted by external
resources such as contractors and struct.[6]
[edit] Baselines in the SDLC
Baselines are an important part of the Systems Development Life Cycle (SDLC). These baselines
are established after four of the five phases of the SDLC and are critical to the iterative nature of
the model .[7] Each baseline is considered as a milestone in the SDLC.
 Functional Baseline: established after the conceptual design phase.
 Allocated Baseline: established after the preliminary design phase.
 Product Baseline: established after the detail design and development phase.
 Updated Product Baseline: established after the production construction phase.
[edit] Complementary to SDLC
Complementary Software development methods to Systems Development Life Cycle (SDLC)
are:
 Software Prototyping
 Joint Applications Design (JAD)
 Rapid Application Development (RAD)
 Extreme Programming (XP); extension of earlier work in Prototyping and RAD.
 Open Source Development
 End-user development
 Object Oriented Programming
Comparison of Methodology Approaches (Post, & Anderson 2006)[8]
 Open
SDLC RAD Objects JAD Prototyping End User
Source
Control Formal MIS Weak Standards Joint User User
Time Frame Long Short Medium Any Medium Short Short
Users Many Few Few Varies Few One or Two One
MIS staff Many Few Hundreds Split Few One or Two None
Transaction/DSS Transaction Both Both Both DSS DSS DSS
Interface Minimal Minimal Weak Windows Crucial Crucial Crucial
Documentation
Vital Limited Internal In Objects Limited Weak None
and training
Integrity and
Vital Vital Unknown In Objects Limited Weak Weak
security
Reusability Limited Some Maybe Vital Limited Weak None
[edit] Strengths and weaknesses
Few people in the modern computing world would use a strict waterfall model for their Systems
Development Life Cycle (SDLC) as many modern methodologies have superseded this thinking.
Some will argue that the SDLC no longer applies to models like Agile computing, but it is still a
term widely in use in Technology circles. The SDLC practice has advantages in traditional
models of software development, that lends itself more to a structured environment. The
disadvantages to using the SDLC methodology is when there is need for iterative development or
(i.e. web development or e-commerce) where stakeholders need to review on a regular basis the
software being designed. Instead of viewing SDLC from a strength or weakness perspective, it is
far more important to take the best practices from the SDLC model and apply it to whatever may
be most appropriate for the software being designed.
A comparison of the strengths and weaknesses of SDLC:
Strength and Weaknesses of SDLC [8]
Strengths Weaknesses
Control. Increased development time.
Monitor Large projects. Increased development cost.
Detailed steps. Systems must be defined up front.
Evaluate costs and completion targets. Rigidity.
Documentation. Hard to estimate costs, project overruns.
Well defined user input. User input is sometimes limited.
Ease of maintenance.
Development and design standards.
Tolerates changes in MIS staffing.
An alternative to the SDLC is Rapid Application Development, which combines prototyping,
Joint Application Development and implementation of CASE tools. The advantages of RAD are
speed, reduced development cost, and active user involvement in the development process.
It should not be assumed that just because the waterfall model is the oldest original SDLC model
that it is the most efficient system. At one time the model was beneficial mostly to the world of
automating activities that were assigned to clerks and accountants. However, the world of
technological evolution is demanding[citation needed] that systems have a greater functionality that
would assist help desk technicians/administrators or information technology specialists/analysts.
[edit] See also
 Application Lifecycle Management
[edit] References
1. ^ SELECTING A DEVELOPMENT APPROACH. Retrieved 27 October 2008.
2. ^ "Systems Development Life Cycle". In: Foldoc(2000-12-24)
3. ^ James Taylor (2004). Managing Information Technology Projects. p.39..
4. ^ a b Geoffrey Elliott & Josh Strachan (2004) Global Business Information Technology. p.87.
5. ^ US Department of Justice (2003). INFORMATION RESOURCES MANAGEMENT Chapter
1. Introduction.
6. ^ a b c d e U.S. House of Representatives (1999). Systems Development Life-Cycle Policy. p.13.
7. ^ Blanchard, B. S., & Fabrycky, W. J.(2006) Systems engineering and analysis (4th ed.) New
Jersey: Prentice Hall. p.31
8. ^ a b Post, G., & Anderson, D., (2006). Management information systems: Solving business
problems with information technology. (4th ed.). New York: McGraw-Hill Irwin.
Further reading
 Blanchard, B. S., & Fabrycky, W. J.(2006) Systems engineering and analysis (4th ed.)
New Jersey: Prentice Hall.
 Cummings, Haag (2006). Management Information Systems for the Information Age.
Toronto, McGraw-Hill Ryerson
 Beynon-Davies P. (2009). Business Information Systems. Palgrave, Basingstoke. ISBN
978-0-230-20368-6
 Computer World, 2002, Retrieved on June 22, 2006 from the World Wide Web:
 Management Information Systems, 2005, Retrieved on June 22, 2006 from the World
Wide Web:
 This article was originally based on material from the Free On-line Dictionary of
Computing, which is licensed under the GFDL.
[edit] External links
Wikimedia Commons has media related to: Systems Development Life Cycle

 US Department of Education - Lifecycle Management Document

 System Development Lifecycle (SDLC) Review Document G23 from the Information
Systems Audit and Control Association (ISACA)
 The Agile System Development Lifecycle
 Software as a Service Application Service Provider Systems Development Lifecycle
 Pension Benefit Guaranty Corporation - Information Technology Solutions Lifecycle
Methodology
 SDLC Industry Interest Group
 State of Maryland SDLC
 HHS Enterprise Performance Life Cycle Framework
 CMS Integrated IT Investment & System Life Cycle Framework
 Collection of All SDLC Models in One Place With External Good Resources
  OpenSDLC.org
v • d • e
Software Engineering
Requirements analysis • Systems analysis • Software design • Computer
Fields programming • Formal methods • Software testing • Software deployment •
Software maintenance
Data modeling • Enterprise architecture • Functional specification •
Modeling language • Programming paradigm • Software • Software
Concepts architecture • Software development methodology • Software development
process • Software quality • Software quality assurance • Software
archaeology • Structured analysis
Agile • Aspect-oriented • Object orientation • Ontology • Service orientation
Orientations
• SDLC
Development Agile • Iterative model • RUP • Scrum • Spiral
models model • Waterfall model • XP • V-Model
Automotive SPICE • CMMI • Data model •
Models Function model • Information model •
Other models
Metamodeling • Object model • Systems model •
View model
Modeling languages IDEF • UML
Kent Beck • Grady Booch • Fred Brooks • Barry Boehm • Ward Cunningham
• Ole-Johan Dahl • Tom DeMarco • Martin Fowler • C. A. R. Hoare • Watts
Software Humphrey • Michael A. Jackson • Ivar Jacobson • Craig Larman • James
engineers Martin • Bertrand Meyer • David Parnas • Winston W. Royce • Colette
Rolland • James Rumbaugh • Niklaus Wirth • Edward Yourdon • Victor
Basili
Computer science • Computer engineering • Enterprise engineering • History
Related
• Management • Mathematics • Project management • Quality management •
fields
Software ergonomics • Systems engineering
v • d • e
Systems Engineering
Biological systems engineering • Configuration management • Earth
systems engineering and management • Enterprise systems engineering
Fields
• Performance engineering • Reliability engineering • Safety engineering
• Space Systems Engineering
Requirements analysis • Functional specification • System integration •
Processes
Verification and validation • Design review
Business process • System • Systems engineering process • System
Concepts
lifecycle • Systems Development Life Cycle
Languages Systems Modeling Language • IDEF
Decision making • Functional modelling • Optimization • Planning •
Tools Reliable analysis • Statistical analysis • Systems analysis • System
dynamics • Systems modeling • V-Model • Work breakdown structure
 Wernher von Braun • Harold Chestnut • Arthur David Hall III • Derek
Systems
Hitchins • Robert E. Machol • Simon Ramo • Joseph Francis Shea •
engineers
John N. Warfield
Control engineering • Computer engineering • Industrial engineering •
Related fields Operations research • Project management • Quality management •
Software engineering
Retrieved from "http://en.wikipedia.org/wiki/Systems_Development_Life_Cycle"
Categories: Systems engineering | Computing terminology | Software development process |
Software systems | Software engineering
Hidden categories: All articles with unsourced statements | Articles with unsourced statements
from December 2009 | Articles needing additional references from September 2010 | All articles
needing additional references | Articles with unsourced statements from August 2010 | Wikipedia
articles incorporating text from FOLDOC

http://en.wikipedia.org/w/index.php?
title=Special:Book&bookcmd=download&collection_id=885a3d0f80bc9716&writer=rl&return_
to=Systems+Development+Life+Cycle