Systems Development Life Cycle the (SDLC) was first developed in the 1960s to manage the large

software projects.

This approach to software development is very structured and risk averse, include multiple
programmers and systems.

It requires a clear, upfront understanding of what the software is supposed to do and is not amenable to
design changes.

This approach is roughly similar to an assembly line process, where it is clear to all stakeholders what
the end product should do and that major changes are difficult and costly to implement

SDLC Phases:

Preliminary Analysis.

The review includes questions such as:

1. What is the problem-to-be-solved?

2. Is creating a solution possible?
3. What alternatives exist?
4. What is currently being done about it?

A feasibility study is launched. The feasibility study includes an analysis of the technical feasibility, the
economic feasibility or affordability, and the legal feasibility.

System Analysis. Determine the specific requirements for the new system.

Procedures are documented, key players/users are interviewed, and data requirements are developed
in order to get an overall impression of exactly what the system is supposed to do.

The result of this phase is a system requirements document and is done by Systems Analyst

System Design. A designer takes the system requirements document and develops the specific technical
detail required for the system.

The business requirements are translated into specific technical requirements.

Design for the user interface, database, and data inputs and outputs, and reporting are developed.

The result of this phase is a system design document. This document will have everything a programmer
needs to actually create the system and is done by Systems Analyst, Developer, or Systems Architect.

Programming. The code finally gets written in the programming phase.

Using the system design document as a guide, programmers develop the software. The result of this
phase is an initial working program that meets the requirements.

These tasks are done by Developer, Software Engineer, Programmer, or Coder.

Testing. The software program developed in the programming phase is put through a series

Of structured tests.
The first is a unit test, which evaluates individual parts of the code for errors or bugs.

This is followed by a system integration test (SIT) in which the different components of the system are
tested to ensure that they work together properly.

Finally, the user acceptance test (UAT) allows those that will be using the software to test the system to
ensure that it meets their standards.

Any bugs, errors, or problems found during testing are resolved and then the software is tested again.

These tasks are done by Tester, Testing Analyst, or Quality Assurance.

Implementation. This phase includes training the users, providing documentation, and data conversion
from the previous system to the new system.

Implementation can take many forms, depending on the type of system, the number and type of users,
and how urgent it is that the system become operational.

Maintenance. In the maintenance phase the system has a structured support process in place.

Reported bugs are fixed and requests for new features are evaluated and implemented.

Also, system updates and backups of the software are made for each new version of the program.

Since maintenance is normally an Operating Expense (OPEX) while much of development is a Capital
Expense (CAPEX), funds normally come out of different budgets or cost centers.

RPID APPLICATION DEVELOPMENT PROCESS

RAD focuses on quickly building a working model of the software, getting feedback from users, and then
using that feedback to update the working model.

The RAD methodology consists of four phases.

Requirements Planning. This phase is similar to the preliminary analysis, system analysis, and design
phases of the SDLC. In this phase the overall requirements for the system are defined, a team is
identified, and feasibility is determined.

2. User Design. Representatives of the users work with the system analysts, designers, and
programmers to interactively create the design of the system.

Sometimes a Joint Application Development (JAD) session is used to facilitate working with all of these
various stakeholders.

3. Construction. The application developers, working with the users, build the next version of the

System through an interactive process. Changes can be made as developers work on the program.

This step is executed in parallel with the User Design step in an iterative fashion, making modifications
until an acceptable version of the product is developed.

4 Cutover. Cutover involves switching from the old system to the new softwareTiming of the
cutover phase is crucial and is usually done when there is low activity. (Mid-Night / Holidays)