text:
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, highlighting the maintenance phase
The systems development life cycle (SDLC), also referred to as the application development life-cycle, is a term used in systems engineering, information systems and software engineering to describe a process for planning, creating, testing, and deploying an information system.[1] The systems development lifecycle concept applies to a range of hardware and software configurations, as a system can be composed of hardware only, software only, or a combination of both.[2]
Contents
[hide]
1 Overview
2 History and details
3 Phases
3.1 System investigation
3.2 System analysis
3.3 Design
3.4 Environments
3.5 Testing
3.6 Training and transition
3.7 Operations and maintenance
3.8 Evaluation
4 Systems analysis and design
5 Object-oriented analysis
6 Life cycle
6.1 Management and control
6.2 Work breakdown structured organization
6.3 Baselines
6.4 Complementary methodologies
7 Strengths and weaknesses
8 See also
9 References
10 Further reading
11 External links
Overview[edit]
A systems development life cycle is composed of a number of clearly defined and distinct work phases which are used by systems engineers and systems developers to plan for, design, build, test, and deliver information systems. Like anything that is manufactured on an assembly line, an SDLC aims to produce high-quality systems that meet or exceed customer expectations, based on customer requirements, by delivering systems which move through each clearly defined phase, within scheduled time frames and cost estimates.[3] 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 or methodologies have been created, such as waterfall, spiral, Agile software development, rapid prototyping, incremental, and synchronize and stabilize.[4]
SDLC can be described along a spectrum of agile to iterative to sequential methodologies. Agile methodologies, such as XP and Scrum, focus on lightweight processes which allow for rapid changes (without necessarily following the pattern of SDLC approach) along the development cycle. Iterative methodologies, such as Rational Unified Process and dynamic systems development method, focus on limited project scope and expanding or improving products by multiple iterations. Sequential or big-design-up-front (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".[5]
SDLC is used during the development of an IT project, it describes the different stages involved in the project from the drawing board, through the completion of the project.
The SDLC is not a methodology per se, but rather a description of the phases in the life cycle of a software application. These phases (broadly speaking) are, investigation, analysis, design, build, test, implement, and maintenance and support. All software development methodologies (such as the more commonly known waterfall and scrum methodologies) follow the SDLC phases but the method of doing that varies vastly between methodologies. In the Scrum methodology, for example, one could say a single user story goes through all the phases of the SDLC within a single two-week sprint. Contrast this to the waterfall methodology, as another example, where every business requirement (recorded in the analysis phase of the SDLC in a document called the Business Requirements Specification) is translated into feature/functional descriptions (recorded in the design phase in a document called the Functional Specification) which are then all built in one go as a collection of solution features typically over a period of three to nine months, or more. These methodologies are obviously quite different approaches yet, they both contain the SDLC phases in which a requirement is born, then travels through the life cycle phases ending in the final phase of maintenance and support, after-which (typically) the whole life cycle starts again for a subsequent version of the software application.
History and details[edit]
The product life cycle describes the process for building information systems in a very deliberate, structured and methodical way, reiterating each stage of the product's life. 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".[6]
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".[6]
Phases[edit]
This article may require cleanup to meet Wikipedia's quality standards. The specific problem is: parts of this section appear to be unfinished and half-written/typed Please help improve this article if you can. (July 2015) (Learn how and when to remove this template message)
This section needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. (September 2010) (Learn how and when to remove this template message)
The system development life cycle framework provides a sequence of activities for system designers and developers to follow. It consists of a set of steps or phases in which each phase of the SDLC uses the results of the previous one.
The SDLC adheres to important phases that are essential for developers, such as planning, analysis, design, and implementation, and are explained in the section below. It includes evaluation of present system, information gathering, feasibility study and request approval. A number of SDLC models have been created: waterfall, fountain, spiral, build and fix, rapid prototyping, incremental, synchronize and stabilize. The oldest of these, and the best known, is the waterfall model: a sequence of stages in which the output of each stage becomes the input for the next. These stages can be characterized and divided up in different ways, including the following:[7]
Preliminary analysis: The objective of phase 1 is to conduct a preliminary analysis, propose alternative solutions, describe costs and benefits and submit a preliminary plan with recommendations.
Conduct the preliminary analysis: in this step, you need to find out the organization's objectives and the nature and scope of the problem under study. Even if a problem refers only to a small segment of the organization itself, you need to find out what the objectives of the organization itself are. Then you need to see how the problem being studied fits in with them.
Propose alternative solutions: In digging into the organization's objectives and specific problems, you may have already covered some solutions. Alternate proposals may come from interviewing employees, clients, suppliers, and/or consultants. You can also study what competitors are doing. With this data, you will have three choices: leave the system as is, improve it, or develop a new system.
Describe the costs and benefits.
Systems analysis, requirements definition: Defines project goals into defined functions and operation of the intended application. It is the process of gathering and interpreting facts, diagnosing problems and recommending improvements to the system. Analyzes end-user information needs and also removes any inconsistencies and incompleteness in these requirements.
A series of steps followed by the developer are:[8]
Collection of Facts: End user requirements are obtained through documentation, client interviews, observation and questionnaires,
Scrutiny of the existing system: Identify pros and cons of the current system in-place, so as to carry forward the pros and avoid the cons in the new system.
Analyzing the proposed system: Solutions to the shortcomings in step two are found and any specific user proposals are used to prepare the specifications.
Systems design: Describes desired features and operations in detail, including screen layouts, business rules, process diagrams, pseudocode and other documentation.
Development: The real code is written here.
Integration and testing: Brings all the pieces together into a special testing environment, then checks for errors, bugs and interoperability.
Acceptance, installation, deployment: The final stage of initial development, where the software is put into production and runs actual business.
Maintenance: During the maintenance stage of the SDLC, the system is assessed to ensure it does not become obsolete. This is also where changes are made to initial software. It involves continuous evaluation of the system in terms of its performance.
Evaluation: Some companies do not view this as an official stage of the SDLC, while others consider it to be an extension of the maintenance stage, and may be referred to in some circles as post-implementation review. This is where the system that was developed, as well as the entire process, is evaluated. Some of the questions that need to be answered include: does the newly implemented system meet the initial business requirements and objectives? Is the system reliable and fault-tolerant? Does the system function according to the approved functional requirements? In addition to evaluating the software that was released, it is important to assess the effectiveness of the development process. If there are any aspects of the entire process, or certain stages, that management is not satisfied with, this is the time to improve. Evaluation and assessment is a difficult issue. However, the company must reflect on the process and address weaknesses.
Disposal: In this phase, plans are developed for discarding system information, hardware and software in making the transition to a new system. The purpose here is to properly move, archive, discard or destroy information, hardware and software that is being replaced, in a manner that prevents any possibility of unauthorized disclosure of sensitive data. The disposal activities ensure proper migration to a new system. Particular emphasis is given to proper preservation and archival of data processed by the previous system. All of this should be done in accordance with the organization's security requirements.[9]
In the following diagram, these stages of the systems development life cycle are divided in ten steps from definition to creation and modification of IT work products:
A ten-phase version of the systems development life cycle[10]
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.[10]
System investigation[edit]
The system investigates the IT proposal. During this step, we must consider all current priorities that would be affected and how they should be handled. Before any system planning is done, a feasibility study should be conducted to determine if creating a new or improved system is a viable solution. This will help to determine the costs, benefits, resource requirements, and specific user needs required for completion. The development process can only continue once management approves of the recommendations from the feasibility study.[11]
Following are different components of the feasibility study:
Operational feasibility
Economic feasibility
Technical feasibility
Human factors feasibility
Legal/Political feasibility
System analysis[edit]
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.
Design[edit]
In systems design, the 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 system features in detail, and generally include functional hierarchy diagrams, screen layout diagrams, tables of business rules, business process diagrams, pseudo-code, and a complete entity-relationship diagram with a full data dictionary. These design elements are intended to describe the system in sufficient detail, such that skilled developers and engineers may develop and deliver the system with minimal additional input design.
Environments[edit]
Environments are controlled areas where systems developers can build, distribute, install, configure, test, and execute systems that move through the SDLC. Each environment is aligned with different areas of the SDLC and is intended to have specific purposes. Examples of such environments include the:
Development environment, where developers can work independently of each other before trying to merge their work with the work of others,
Common build environment, where merged work can be built, together, as a combined system,
Systems integration testing environment, where basic testing of a system's integration points to other upstream or downstream systems can be tested,
User acceptance testing environment, where business stakeholders can test against their original business requirements,
Production environment, where systems finally get deployed to, for final use by their intended end users.
Testing[edit]
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 the means to rectify defects and validate fixes prior to deployment is incorporated into this phase.
The following are types of testing that may be relevant, depending on the type of system under development:
Defect testing the failed scenarios, including defect tracking
Path testing
Data set testing
Unit testing
System testing
Integration testing
Black-box testing
White-box testing
Regression testing
Automation testing
User acceptance testing
Software performance testing
Training and transition[edit]
Once a system has been stabilized through adequate testing, the SDLC ensures that proper training on the system is performed or documented before transitioning the system to its support staff and end users.
Training usually covers operational training for those people who will be responsible for supporting the system as well as training for those end users who will be using the system after its delivery to a production operating environment.
After training has been successfully completed, systems engineers and developers transition the system to its final production environment, where it is intended to be used by its end users and supported by its support and operations staff.
Operations and maintenance[edit]
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. There are two approaches to system development; there is the traditional approach (structured) and object oriented. Information Engineering includes the traditional system approach, which is also called the structured analysis and design technique. The object oriented approach views the information system as a collection of objects that are integrated with each other to make a full and complete information system.
Evaluation[edit]
The final phase of the SDLC is to measure the effectiveness of the system and evaluate potential enhancements.
Systems analysis and design[edit]
The systems analysis and design (SAD) is the process of developing information systems (IS) that effectively use hardware, software, data, processes, and people to support the company's businesses objectives. System analysis and design can be considered the meta-development activity, which serves to set the stage and bound the problem. SAD can be leveraged to set the correct balance among competing high-level requirements in the functional and non-functional analysis domains. System analysis and design interacts strongly with distributed enterprise architecture, enterprise I.T. Architecture, and business architecture, and relies heavily on concepts such as partitioning, interfaces, personae and roles, and deployment/operational modeling to arrive at a high-level system description. This high level description is then further broken down into the components and modules which can be analyzed, designed, and constructed separately and integrated to accomplish the business goal. SDLC and SAD are cornerstones of full life cycle product and system planning.
Object-oriented analysis[edit]
Object-oriented analysis (OOA) is the process of analyzing a task (also known as a problem domain), to develop a conceptual model that can then be used to complete the task. A typical OOA model would describe computer software that could be used to satisfy a set of customer-defined requirements. During the analysis phase of problem-solving, a programmer might consider a written requirements statement, a formal vision document, or interviews with stakeholders or other interested parties. The task to be addressed might be divided into several subtasks (or domains), each representing a different business, technological, or other areas of interest. Each subtask would be analyzed separately. Implementation constraints, (e.g., concurrency, distribution, persistence, or how the system is to be built) are not considered during the analysis phase; rather, they are addressed during object-oriented design (OOD).
The conceptual model that results from OOA will typically consist of a set of use cases, one or more UML class diagrams, and a number of interaction diagrams. It may also include some kind of user interface mock-up.
The input for object-oriented design is provided by the output of object-oriented analysis. Realize that an output artifact does not need to be completely developed to serve as input of object-oriented design; analysis and design may occur in parallel, and in practice the results of one activity can feed the other in a short feedback cycle through an iterative process. Both analysis and design can be performed incrementally, and the artifacts can be continuously grown instead of completely developed in one shot.
Some typical (but common to all types of design analysis) input artifacts for object-oriented:
Conceptual model: Conceptual model is the result of object-oriented analysis, it captures concepts in the problem domain. The conceptual model is explicitly chosen to be independent of implementation details, such as concurrency or data storage.
Use case: Use case is a description of sequences of events that, taken together, lead to a system doing something useful. Each use case provides one or more scenarios that convey how the system should interact with the users called actors to achieve a specific business goal or function. Use case actors may be end users or other systems. In many circumstances use cases are further elaborated into use case diagrams. Use case diagrams are used to identify the actor (users or other systems) and the processes they perform.
System Sequence Diagram: System Sequence diagram (SSD) is a picture that shows, for a particular scenario of a use case, the events that external actors generate, their order, and possible inter-system events.
User interface documentations (if applicable): Document that shows and describes the look and feel of the end product's user interface. It is not mandatory to have this, but it helps to visualize the end-product and therefore helps the designer.
Relational data model (if applicable): A data model is an abstract model that describes how data is represented and used. If an object database is not used, the relational data model should usually be created before the design, since the strategy chosen for object-relational mapping is an output of the OO design process. However, it is possible to develop the relational data model and the object-oriented design artifacts in parallel, and the growth of an artifact can stimulate the refinement of other artifacts.
Life cycle[edit]
Management and control[edit]
SPIU phases related to management controls[12]
The 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.[12]
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.[12] The diagram shows coverage spans numerous phases of the SDLC but the associated MCD has a subset of primary mappings to the SDLC phases. For example, Analysis and Design is primarily performed as part of the Acquisition and Implementation Domain and System Build and Prototype is primarily performed as part of delivery and support.
Work breakdown structured organization[edit]
Work breakdown structure[12]
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 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.x. 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.[12]
Baselines[edit]
Baselines are an important part of the systems development life cycle. These baselines are established after four of the five phases of the SDLC and are critical to the iterative nature of the model .[13] 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.
Complementary methodologies[edit]
Complementary software development methods to systems development life cycle are:
Software prototyping
Joint applications development (JAD)
Rapid application development (RAD)
Extreme programming (XP);
Open-source development
End-user development
Object-oriented programming
Comparison of Methodology Approaches (Post, & Anderson 2006)[14]
SDLC
RAD
Open source
Objects
JAD
Prototyping
End User
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 and training Vital Limited Internal In Objects Limited Weak None
Integrity and security Vital Vital Unknown In Objects Limited Weak Weak
Reusability Limited Some Maybe Vital Limited Weak None
Strengths and weaknesses[edit]
Few people in the modern computing world would use a strict waterfall model for their 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 systems 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.
A comparison of the strengths and weaknesses of SDLC:
Strength and Weaknesses of SDLC [14]
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 Little parallelism
Development and design standards Automation of documentation and standards is limited
Tolerates changes in MIS staffing Does not tolerate changes in requirements
Projects canned early result in little or no value
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.
See also[edit]
Application lifecycle management
Decision cycle
IPO Model
Software development methodologies
System lifecycle
References[edit]
Jump up ^ SELECTING A DEVELOPMENT APPROACH. Retrieved 17 July 2014.
Jump up ^ Parag C. Pendharkara; James A. Rodgerb; Girish H. Subramanian (November 2008). "An empirical study of the Cobb–Douglas production function properties of software development effort". Information and Software Technology. 50 (12): 1181–1188. doi:10.1016/j.infsof.2007.10.019.
Jump up ^ "Systems Development Life Cycle from". FOLDOC. Retrieved 2013-06-14.
Jump up ^ Software Development Life Cycle (SDLC), PowerPoint – Powered by Google Docs
Jump up ^ James Taylor (2004). Managing Information Technology Projects. p.39.
^ Jump up to: a b Geoffrey Elliott & Josh Strachan (2004) Global Business Information Technology. p.87.
Jump up ^ Kay, Russell (May 14, 2002). "QuickStudy: System Development Life Cycle". ComputerWorld.
Jump up ^ Control and Audit, Information Systems. SDLC (August 2013 ed.). Chapter 5: Institute of Chartered Accountants of India. p. 5.28. |access-date= requires |url= (help)
Jump up ^ Radack, S. (n.d.). "The system development life cycle (SDLC)" (PDF). National Institute of Standards and Technology.
^ Jump up to: a b US Department of Justice (2003). INFORMATION RESOURCES MANAGEMENT Chapter 1. Introduction.
Jump up ^ Marakas, James A. O'Brien, George M. (2010). Management information systems (10th ed.). New York: McGraw-Hill/Irwin. pp. 485–489. ISBN 0073376817.
^ Jump up to: a b c d e U.S. House of Representatives (1999). Systems Development Life-Cycle Policy. p.13.
Jump up ^ Blanchard, B. S., & Fabrycky, W. J.(2006) Systems engineering and analysis (4th ed.) New Jersey: Prentice Hall. p.31
^ Jump up to: 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[edit]
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 is based on material taken from the Free On-line Dictionary of Computing prior to 1 November 2008 and incorporated under the "relicensing" terms of the GFDL, version 1.3 or later.
External links[edit]
Wikimedia Commons has media related to Systems Development Life Cycle.
The Agile System Development Lifecycle
Pension Benefit Guaranty Corporation – Information Technology Solutions Lifecycle Methodology
FSA Life Cycle Framework
HHS Enterprise Performance Life Cycle Framework
The Open Systems Development Life Cycle
System Development Life Cycle Evolution Modeling
Zero Deviation Life Cycle
Integrated Defense AT&L Life Cycle Management Chart, the U.S. DoD form of this concept.
[show]
v
t
e
Software engineering
Fields
Computer programming
Requirements engineering
Software deployment
Software design
Software maintenance
Software testing
Systems analysis
Formal methods
Concepts
Data modeling
Enterprise architecture
Functional specification
Modeling language
Orthogonality
Programming paradigm
Software
Software archaeology
Software architecture
Software configuration management
Software development methodology
Software development process
Software quality
Software quality assurance
Software verification and validation
Structured analysis
Orientations
Agile
Aspect-oriented
Object orientation
Ontology
Service orientation
SDLC
Models
Developmental
Agile
EUP
Executable UML
Incremental model
Iterative model
Prototype model
RAD
UP
Scrum
Spiral model
V-Model
Waterfall model
XP
Other
SPICE
CMMI
Data model
ER model
Function model
Information model
Metamodeling
Object model
Systems model
View model
Languages
IDEF
UML
USL
SysML
Software
engineers
Victor Basili
Kent Beck
Grady Booch
Fred Brooks
Barry Boehm
Peter Chen
Danese Cooper
Ward Cunningham
Tom DeMarco
Edsger W. Dijkstra
Delores M. Etter
Martin Fowler
Adele Goldstine
Margaret Hamilton
C. A. R. Hoare
Lois Haibt
Mary Jean Harrold
Grace Hopper
Watts Humphrey
Michael A. Jackson
Ivar Jacobson
Alan Kay
Nancy Leveson
Stephen J. Mellor
Bertrand Meyer
David Parnas
Trygve Reenskaug
Winston W. Royce
James Rumbaugh
Mary Shaw
Peri Tarr
Elaine Weyuker
Niklaus Wirth
Edward Yourdon
Related fields
Computer science
Computer engineering
Project management
Risk management
Systems engineering
Category
Commons
[show]
v
t
e
Systems engineering
Subfields
Aerospace engineering
Biological systems engineering
Configuration management
Earth systems engineering and management
Electrical engineering
Enterprise systems engineering
Performance engineering
Reliability engineering
Safety engineering
Processes
Requirements engineering
Functional specification
System integration
Verification and validation
Design review
Concepts
Business process
System
System lifecycle
V-Model
Systems development life cycle
Tools
Decision-making
Function modelling
IDEF
Optimization
Quality function deployment
System dynamics
Systems Modeling Language
Systems analysis
Systems modeling
Work breakdown structure
People
James S. Albus
Ruzena Bajcsy
Benjamin S. Blanchard
Wernher von Braun
Kathleen Carley
Harold Chestnut
Wolt Fabrycky
Barbara Grosz
Arthur David Hall III
Derek Hitchins
Robert E. Machol
Radhika Nagpal
Simon Ramo
Joseph Francis Shea
Katia Sycara
Manuela M. Veloso
John N. Warfield
Related fields
Control engineering
Computer engineering
Industrial engineering
Operations research
Project management
Quality management
Risk management
Software engineering
Category
Retrieved from "https://en.wikipedia.org/w/index.php?title=Systems_development_life_cycle&oldid=835694156"
Categories:
Systems engineering
Computing terminology
Software development process
Software engineering
Hidden categories:
Pages using citations with accessdate and no URL
All articles with unsourced statements
Articles with unsourced statements from December 2009
Articles needing cleanup from July 2015
All pages needing cleanup
Cleanup tagged articles with a reason field from July 2015
Wikipedia pages needing cleanup from July 2015
Articles needing additional references from September 2010
All articles needing additional references
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Article
Talk
Variants
Views
Read
Edit
View history
More
Search
Navigation
Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Wikipedia store
Interaction
Help
About Wikipedia
Community portal
Recent changes
Contact page
Tools
What links here
Related changes
Upload file
Special pages
Permanent link
Page information
Wikidata item
Cite this page
Print/export
Create a book
Download as PDF
Printable version
In other projects
Wikimedia Commons
Languages
العربية
Čeština
Español
Esperanto
فارسی
Français
한국어
हिन्दी
Bahasa Indonesia
Nederlands
日本語
Português
Русский
Svenska
தமிழ்
ไทย
Українська
Tiếng Việt
中文
10 more
Edit links
This page was last edited on 10 April 2018, at 06:21.
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.
Privacy policy
About Wikipedia
Disclaimers
Contact Wikipedia
Developers
Cookie statement
Mobile view
Enable previews

values: mw-page-base noprint

values: mw-head-base noprint

values: firstHeading firstHeading en

values: siteSub noprint

values: jump-to-nav mw-jump

attrs: href class title

values:
/wiki/SDLC_(disambiguation)
mw-redirect mw-disambig
SDLC (disambiguation)

values:
note
hatnote navigation-not-searchable

attrs: class style

values:
/wiki/Incremental_development
mw-redirect
Incremental development

values:
/wiki/Extreme_Programming
mw-redirect
Extreme Programming

values:
/wiki/Scrum_(development)
mw-redirect
Scrum (development)

values: This claim needs references to reliable sources. (December 2009)

values:
noprint Inline-Template Template-Fact
white-space:nowrap;

values:
/wiki/Anamorphic_development
mw-redirect
Anamorphic development

values:
/wiki/Project_life_cycle
mw-redirect
Project life cycle

values:
/wiki/Product_life_cycle_(engineering)
mw-redirect
Product life cycle (engineering)

values:
/wiki/Business_systems
mw-redirect
Business systems

values:
/wiki/Business_conglomerate
mw-redirect
Business conglomerate

values:
/wiki/Number_crunching
mw-redirect
Number crunching

values: Structured systems analysis and design method

values: plainlinks metadata ambox ambox-style ambox-Cleanup

values: Help:Introduction to referencing with Wiki Markup/1

values: plainlinks metadata ambox ambox-content ambox-Refimprove

values:
/wiki/Process_Diagram
mw-redirect
Process Diagram

values:
/wiki/Automation_testing
mw-redirect
Automation testing

values:
/wiki/User_acceptance_testing
mw-redirect
User acceptance testing

values: Edit section: Operations and maintenance

values:
/wiki/Object_oriented
mw-redirect
Object oriented

values: Edit section: Systems analysis and design

values:
/wiki/Interaction_diagram
mw-redirect
Interaction diagram

values:
/wiki/System_Sequence_Diagram
mw-redirect
System Sequence Diagram

values:
/wiki/Relational_data_model
mw-redirect
Relational data model

values: Edit section: Work breakdown structured organization

values: Edit section: Complementary methodologies

values:
/wiki/Joint_applications_development
mw-redirect
Joint applications development

values:
/wiki/Fabrycky,_W._J.
mw-redirect
Fabrycky, W. J.

values: -moz-column-width: 30em; -webkit-column-width: 30em; column-width: 30em; list-style-type: decimal;

values: commons:Category:Systems Development Life Cycle

values:
nofollow
external text
http://OpenSDLC.org

values:
nofollow
external text
http://www.0deviation.com

values: nowraplinks hlist collapsible autocollapse navbox-inner

values: Earth systems engineering and management

values:
/wiki/Barbara_Grosz
mw-redirect
Barbara Grosz

values: Category:Pages using citations with accessdate and no URL

values: Category:All articles with unsourced statements

values: Category:Articles with unsourced statements from December 2009

values: Category:Articles needing cleanup from July 2015

values: Category:Cleanup tagged articles with a reason field from July 2015

values: Category:Wikipedia pages needing cleanup from July 2015

values: Category:Articles needing additional references from September 2010

values: Category:All articles needing additional references

values: Discussion about edits from this IP address [ctrl-alt-n]

values: A list of edits made from this IP address [ctrl-alt-y]

values: You are encouraged to create an account and log in; however, it is not mandatory

values: You're encouraged to log in; however, it's not mandatory. [ctrl-alt-o]

values:
/wiki/Systems_development_life_cycle
View the content page [ctrl-alt-c]
c

values: Discussion about the content page [ctrl-alt-t]

values: p-namespaces navigation vectorTabs p-namespaces-label

values:
p-variants
navigation
vectorMenu emptyPortlet
p-variants-label

values: Past revisions of this page [ctrl-alt-h]

values: p-views navigation vectorTabs p-views-label

values:
p-cactions
navigation
vectorMenu emptyPortlet
p-cactions-label

values:
mw-wiki-logo
/wiki/Main_Page
Visit the main page

values:
/wiki/Main_Page
Visit the main page [ctrl-alt-z]
z

values: Featured content – the best of Wikipedia

values: Find background information on current events

values:
/wiki/Special:Random
Load a random article [ctrl-alt-x]
x

values: portal navigation p-wikibase-otherprojects p-wikibase-otherprojects-label

values: دورة حياة تطوير البرمجيات – Arabic

values: Životní cyklus informačního systému – Czech

values:
interlanguage-link interwiki-cs
display: none;

values: Systems Development Life Cycle – Spanish

values: Vivciklo de sistema konstruado – Esperanto

values:
interlanguage-link interwiki-eo
display: none;

values: چرخه حیات توسعه سیستم‌ها – Persian

values:
interlanguage-link interwiki-fa
display: none;

values: Cycle de développement (logiciel) – French

values: 소프트웨어 개발 수명 주기 – Korean

values:
interlanguage-link interwiki-ko
display: none;

values: सिस्टम डेवलपमेंट लाइफ साइकल – Hindi

values:
https://id.wikipedia.org/wiki/SDLC
SDLC – Indonesian
id
id
interlanguage-link-target

values:
https://nl.wikipedia.org/wiki/DOJ_SDLC
DOJ SDLC – Dutch
nl
nl
interlanguage-link-target

values:
interlanguage-link interwiki-nl
display: none;

values: システム開発ライフサイクル – Japanese

values: Ciclo de vida de desenvolvimento de sistemas – Portuguese

values: Жизненный цикл программного обеспечения – Russian

values:
interlanguage-link interwiki-sv
display: none;

values: ஒருங்கியம் விருத்திச் சுழற்சி வட்டம் – Tamil

values:
interlanguage-link interwiki-ta
display: none;

values: วงจรชีวิตของการพัฒนาซอฟต์แวร์ – Thai

values:
interlanguage-link interwiki-th
display: none;

values: Життєвий цикл програмного забезпечення – Ukrainian

values:
interlanguage-link interwiki-uk
display: none;

values: Vòng đời phát triển hệ thống – Vietnamese

values:
interlanguage-link interwiki-vi
display: none;

values: 系统发展生命周期 – Chinese

values: All languages (initial selection from common choices by you and others)

values: mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-Systems_development_life_cycle rootpage-Systems_development_life_cycle skin-vector action-view