22-09-2017, 10:54 AM
The Systems Development Lifecycle (SDLC), or Software Development Lifecycle 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 computer systems.
In software engineering, the SDLC concept supports many types of software development methodologies. These methodologies form the framework for the planning and control of the creation of an information system of the software development process.
Systems Development Lifecycle (SDLC) is a process used by a systems analyst to develop an information system, including requirements, validation, training and user ownership. Any SDLC should result in a high-quality system that meets or exceeds customer expectations, expires within time and cost estimates, works efficiently and efficiently in the current and planned information technology infrastructure, and is economical to maintain and cost-effective to improve.
Computer systems are complex and often (especially with the recent emergence of Service Oriented Architecture) linking multiple traditional systems potentially supplied by different software vendors. To handle this level of complexity, several SDLC models have been created: "cascade"; "source"; "spiral"; "build and fix"; "rapid prototyping"; "incremental"; and "synchronize and stabilize".
SDLC models can be described along a spectrum from agile to iterative to sequential. Agile methodologies, such as XP and Scrum, focus on light processes that allow rapid changes throughout the development cycle. Iterative methodologies, such as the Rational Unified Process and Dynamic Systems Development Method, focus on limited project reach and expand or enhance products across multiple iterations. Sequential or large-design-up-front (BDUF) models, such as Waterfall, focus on complete and correct planning to guide large projects and risks for successful and predictable results. 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 you can define a project with both a project life cycle (PLC) and an SDLC, during which slightly different activities occur. According to Taylor (2004), "the project lifecycle encompasses all project activities, while the systems development lifecycle focuses on the realization of product requirements."
In software engineering, the SDLC concept supports many types of software development methodologies. These methodologies form the framework for the planning and control of the creation of an information system of the software development process.
Systems Development Lifecycle (SDLC) is a process used by a systems analyst to develop an information system, including requirements, validation, training and user ownership. Any SDLC should result in a high-quality system that meets or exceeds customer expectations, expires within time and cost estimates, works efficiently and efficiently in the current and planned information technology infrastructure, and is economical to maintain and cost-effective to improve.
Computer systems are complex and often (especially with the recent emergence of Service Oriented Architecture) linking multiple traditional systems potentially supplied by different software vendors. To handle this level of complexity, several SDLC models have been created: "cascade"; "source"; "spiral"; "build and fix"; "rapid prototyping"; "incremental"; and "synchronize and stabilize".
SDLC models can be described along a spectrum from agile to iterative to sequential. Agile methodologies, such as XP and Scrum, focus on light processes that allow rapid changes throughout the development cycle. Iterative methodologies, such as the Rational Unified Process and Dynamic Systems Development Method, focus on limited project reach and expand or enhance products across multiple iterations. Sequential or large-design-up-front (BDUF) models, such as Waterfall, focus on complete and correct planning to guide large projects and risks for successful and predictable results. 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 you can define a project with both a project life cycle (PLC) and an SDLC, during which slightly different activities occur. According to Taylor (2004), "the project lifecycle encompasses all project activities, while the systems development lifecycle focuses on the realization of product requirements."