SASD - Systems Development Life Cycle From Wikipedia, the...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
Systems Development Life Cycle From Wikipedia, the free encyclopedia Model of the Systems Development Life Cycle with the Maintenance bubble highlighted. Systems Development Life Cycle (SDLC), or Software Development Life Cycle , in systems engineering and software engineering refers to 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. ontents 1 Overview 2 History 3 Systems Development Phases 3.1 Initiation/Planning 3.2 Requirements Gathering And Analysis 3.3 Design 3.4 Build or Coding 3.5 Testing 3.6 Operations and Maintenance 4 Systems Development Life Cycle topics 4.1 Management and control 4.2 Work Breakdown Structure Organization
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
4.3 Baselines in the SDLC 4.4 Complementary to SDLC 5 Strength and Weaknesses 6 See also 7 References 8 Further reading 9 External links Overview Systems Development Life Cycle (SDLC) is any logical process used by a systems analyst to develop an information system, including requirements, validation, training, and user ownership. An 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 have become more complex and often (especially with the advent of Service-Oriented Architecture) link multiple traditional systems potentially supplied by different software vendors. To manage this level of complexity, 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." Although the term SDLC can refer to various models, it typically denotes a waterfall methodology. In project management a project has both a life cycle and a "systems development life cycle," during which a number of typical activities occur. The project life cycle (PLC) encompasses all the activities of the project, while the systems development life cycle focuses on realizing the product requirements. [3] History Systems development life cycle is the oldest formalized methodology 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 traditional systems development life cycle originated in the 1960s to develop large scale functional business systems in an age of large scale business conglomerates. Information systems activities resolved around heavy data processing and number crunching routines. [4]
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 01/23/2011 for the course BMGT 301 taught by Professor Wang during the Spring '08 term at Maryland.

Page1 / 9

SASD - Systems Development Life Cycle From Wikipedia, the...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online