Talk:System Development Life Cycle

System Development Life Cycle, or SDLC, is the process of developing information systems through investigation, analysis, design, implementation and maintenance. SDLC is also known as information systems development or application development. SDLC is a systems approach to problem solving and is made up of several phases, each comprised of multiple steps: • The software concept - identifies and defines a need for the new system • A requirements analysis - analyzes the information needs of the end users • The architectural design - creates a blueprint for the design with the necessary specifications for the hardware, software, people and data resources • Coding and debugging - creates and programs the final system • System testing - evaluates the system's actual functionality in relation to expected or intended functionality. Here are the six official phases: 1. Preliminary Investigation 2. Systems Analysis 3. Systems Design 4. Systems Developement 5. Systems Implementation 6. Systems Maintenance

Systems Planning is the function of the life cycle that seeks to identify and prioritize those technologies and applications that will return the most value to the organization. Systems’ planning involves three basic phases:

• Study the organization's mission • Define an information architecture • Data architecture • Network architecture • Activities or applications architecture • People architecture (i.e., Information Systems organization structure) • Technology architecture • Evaluate organization area or specialty

Business Area Analysis is the study of the current business and information system, and the definition of user requirements and priorities for a new information system. Business Area Analysis involves three basic phases:

• Feasibility assessment (Project Survey Phase) o Interviews o Project scope o Problem statement and classification o Proposed project plan • Organization problem statement (Project Study Phase) o Project roles o Learn current system (use repository) o Model the current system o Analysis of problems and opportunities o New system's objectives o New project scope and plan • Organization requirements statement (Definition Phase) o Identify requirements o Model system requirements o Discovery prototype o Prioritization o Review requirements

Business System Design Systems Design is the evaluation of alternative solutions and the specification of a detailed computer-based solution. It is also called Physical Design. Systems Design is composed of three phases:

• Select a design target from candidate solutions (Selection Phase) • Acquire necessary hardware and software (Acquisition Phase) • Design and integrate the new system (Design and Integration Phase) o General design o Detailed design

Systems Implementation Systems Implementation is the construction of the new system and delivery of that system into "production" (meaning "day-to-day" operation). Systems Implementation involves three phases:

• Build and test networks and databases (if necessary) • Build and test the program • Install and test the new system • Deliver the new system into operation

Systems Support the ongoing maintenance of a system after it has been placed into operation. This includes program maintenance and system improvements. Systems Support is composed of four activities, in no particular order, but rather as problems arise: • Correct errors • Software bugs • Documentation errors or omissions • Recover the system • Assist the users • Adapt the system to new requirements

The Systems Planning function of the life cycle seeks to identify and prioritize those technologies and applications that will return the most value to the organization. Systems Planning involves three basic phases:

• Study the organization's mission • Define an information architecture o Data architecture o Network architecture o Activities or applications architecture o People architecture (i.e., Information Systems organization structure) o Technology architecture • Evaluate organization area or specialty

Merge?

This article should probably be merged with Systems development life cycle. // Liftarn

Phasist orientation?

Extreme Programming is listed as an example of an SDLC. The phase-structured breakdown in the article sounds very waterfall-oriented, and is more or less antithetical to to the Extreme Programming approach. Would it be better to remove the non-phasist methods from the list, or should the description be rewritten to be more inclusive? --William Pietri 21:12, 1 Jun 2005 (UTC)