SYSTEMS DEVELOPMENT LIFE-CYCLE
The Systems development life-cycle (SDLC) is a methodology that also forms the framework for planning and controlling the creation, testing, and delivery of an information system.
Itis a process that is composed of a number of clearly defined and distinct work phases which are used by a information technology resources, such as 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.
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".
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 system development life cycle (SDLC) models have been created: waterfall, fountain, spiral, build and fix, rapid prototyping, incremental, and 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:
* Preliminary Analysi
* Conduct the preliminary analysis
*Propose alternative solutions
*Describe the costs and benefits.
*Systems analysis, requirements definition
*Development
*Integration and testing
* Acceptance, installation, deployment
*Maintenance
*Evaluation
Full Post
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment