Report On Software Development Life Cycle
Report On Software Development Life Cycle
Report On Software Development Life Cycle
Software testing
Analysis
Post process maintenance
3) Analysis:
In this phase, the system analyst analyses the system needs.
Special tools and techniques help the analyst in determination
of requirements.
At this phase detailed study of objective is done and analyze
no. of solution available for solving the problem/achieve the
objective
There are two major activities performed as part of this phase:
Existing system is studied to solve the problem i.e.
1) Find out no of possible solutions, the strengths
,weaknesses and compared this with the current system must
be defined to serve as evaluation of other alternatives.
2) Other alternatives are identified and evaluated.
4) Design
In this phase the requirement specifications from first phase
are studied in this phase and system design is prepared.
System Design helps in specifying hardware and system
requirements and also helps in defining overall system
architecture or layout.
Different architectures are use
Technical architecture - defines the hardware, software, and
telecommunications equipment required to run the system.
Modeling - the activity of drawing a graphical
representation of a design
Graphical user interface (GUI) - the interface to an
information system.
GUI screen design - the ability to model the information
system screens for an entire system.
Document should be prepared in design phase are:
SRDD-system requirement design document
FSD- functional specification document
PS- programmed specification
GAD- gap analysis document
5) Development
Take all of detailed design documents from the design
phase and transform them into an actual system.
The analyst works with programmers to develop any
original software that needed.
Some of the structured techniques for designing and
documenting software include structure charts and
pseudo code.
6) Testing
We need to discuss what is being tested, when testing
must occur, the steps in testing, the properties to test for
and the definition of the overall testing effort.
Verifies that the system works and meets all of the
business requirements defined in the analysis phase.
With inputs from system design, the system is first
developed in small programs called units, which are
integrated in the next phase.
Each unit is developed and tested for its functionality
which is referred to as Unit Testing.
It is relatively less expensive to detect problems before
The system is being used by the users.
Test conditions - the detailed steps the system must
perform along with the expected results of each step.
7) Implementation
In this phase acquisition of hardware and software site
preparations users training and installation of the system
User documentation - How to use the system.
Online training - runs over the Internet or off a CD-
ROM.
Workshop training - is held in a classroom
System Installation: There are five topics which
describe the process of converting from the existing
system to the new one:
Data Conversion- is the process of translating the data
from the existing data formats and data definitions to
those required by the new system.
Training- Training is the process of teaching all users of
the system how to use the functions
Hardware/Software Installation- Hardware/software
installation is the process of installing the vendor
supplied computer configuration and supplemental
applications required to support the system being
developed.
Strengths of SDLC
Methodologies incorporating this approach have been
well tried and tested.
Divides development into distinct phases:
a) Makes tasks more manageable
b) Offers opportunity for more control over development
process
Provides standards for documentation
Much better than trial and error
Weaknesses of SDLC
Fails to see the big picture of strategic management
Too inflexible to cope with changing requirements
Emphasis on hard thinking (which is often reflected in
documentation that is too technical)
Unable to capture true needs of users
SDLC Summary
1. Determine the requirements of the desired software
(Requirements Study Phase).
2. Produce a design that meets the requirements (Design
Phase).
3. Build (code) the designed software (Development
Phase).
4. Verify that the software meets the requirements (Testing
Phase).
5. Maintain the software throughout its lifetime
(Maintenance Phase).