Training Guide For C.R.

LEVEL .1
What is S.D.L.C
Stages in SDLC
 Requirement & Analysis Gathering
Phase
 This is commonly done via formal and informal meetings, e-mails
and phone calls. Analyzing requirements is the tasks of using standard
tools and practices to generate a single unambiguous baseline of the
requirements

 Requirements defines needed information, function, behavior,

performance and interfaces.

 Requirements Analysis is done in order to understand the problem

for which the software system is to solve. For example, the problem
could be automating an existing manual process, or developing a
completely new automated system.

 The developer usually does not understand the client's problem

domain, and the client often does not understand the issues involved
in software systems. This causes a communication gap, which has to
be adequately bridged during requirements Analysis.
 Validation is often done through requirement review, in which a group of people
including representatives of the client, critically review the requirements
specification

 Requirements analysis can be broken down into two distinct activities: capturing
requirements and analyzing requirements.

 When in the Requirements & Analysis phase, a considerable amount of time will be
spent interacting with stakeholders and reviewing the input they provide.

 There are a variety of techniques that can be used to gather the requirements, but
some key points to remember are that the requirements must be systematic,
verifiable, related to identified business needs or opportunities, and defined to a
level of detail sufficient for system design.
 Design Phase

 The purpose of the design phase is to plan a solution of the problem specified by
the requirement document

 This phase is the first step in moving from problem domain to the solution domain.

 This document is similar to a blue print or plan for the solution, and is
used later during implementation, testing and maintenance.

 The design activity is often divided into two separate phase-system design and
detailed design

 System design, which is sometimes also called top-level design, aims to identify the
modules that should be in the system, the specifications of these modules, and how
they interact with each other to produce the desired results

 During detailed design the internal logic of each of the modules specified in system
design is decided
 Coding Phase
The goal of the coding phase is to translate the design of the system into code in a given
programming language

A well written code reduces the testing and maintenance effort.

Since the testing and maintenance cost of software are much higher than the coding cost,
the goal of coding should be to reduce the testing and maintenance effort.

Simplicity and clarity should be strived for, during the coding phase.

An important concept that helps the understandability of programs is structured

programming. The goal of structured programming is to arrange the control flow in the
program.
 Testing Phase
 Put all pieces together and check for errors/bugs.  During this phase, code
modules are integrated to ensure that they function together in the expected
manner.

 Once the coding is done, the software program testing begins. Different testing
methodologies are available to fix the bugs that were committed during the
previous phases

 Developers have to make sure their created programs will work well in
different environments

 Different testing tools and methodologies are already available but some
companies build their own testing tools that are tailor made for their own
development operations.
 Acceptance/ Implementation
 Acceptance, installation, deployment: This is the final stage of initial
development. At this phase team puts the software into production and runs
actual business

 At this stage the application/software is release to the client side (deployed).

Maintenance
 The maintenance of software is an important aspect of SDLC. The software will
definitely undergo change once it is delivered to the customer. Change could
happen because of some unexpected input of values into the system/software
or the changes in the system could directly affect the software operations.
Sometimes new changes are implemented which requires the system updates.
Thank You