System Development Life Cycle

Software development
life cycle(SDLC)

Problem Description
 Creating a web application platform enabling e-
commerce for “Slicekart pvt. Ltd.”
We will work out for the solution through SDLC

Software Development Methodology
The systems development life cycle (SDLC), also referred to as the application
development life-cycle, is a term used in systems engineering, information systems and
software engineering to describe a process for planning, creating, testing, and deploying an
information system
There are two basic approaches for SDLC for which
we will try to implement
To solve the customer problem:
1) Waterfall Model
2) Evolutionary model

Phase I : Requirement Analysis
 Personnel Involved : System Analyst
 Catchy Domain Name ex.Google,Yahoo
 Domain to host the site
ex.:hostgator.com , godaddy.com
This is generally the most time consuming phase of web
software development.

Phase II : Design Phase
 Personnel Involved: Web Developer/Designer
 The design phase is generally far less time consuming. The
only important design elements to tie down are those that
affect the project's buzzword compliance.
 The project must be implemented using trendy technology
and some forethought is required as trends may change
over the three months it will take to implement.
 Trendy Software : Dreamweaver, .NET frameworks

Phase III : Implementation & Module
Testing
 Personnel Involved : Software Programmers
 Testing databases ,web applications and their
relationships
 Testing the domain
 Output:
Each module works properly and co-ordinates with each
other

Phase IV : System Testing
 It has been naively suggested that web application
developers simply write 'Beta' at the top of all pages
 You need to generate buzz among alpha-nerds and only let
people use your Beta system if they have been invited by
a friend. That way, they will feel so special that they will
only want to give positive feedback. Positive feedback is
all you are interested in as there is little point in
gathering defects that you have no intention of correcting
before sale.
 Output : Web application Prepared to launch on domain.

Phase V : Maintenance Phase
 Errors not discovered during the previous stages are
corrected.
 The system may require improving or enhancement as new
requirements are discovered.
 Regular Updation of application according to the current
techno-trends
 Application should withstand with the growing traffic on
the application server 

Implementing Evolutionary Model

Outline Description
 Basic Requirements of the customer
For Ex.: Filtration of products
Database Memory Requirements
Platforms : PHP,JavaScript.etc;
 Develop Initial Prototype for the customer interface

Developing the BETA Version 1.O
 Modules Development and Integration
1) Software Requirements
2) Domain / IP addressing
3) Personnel involved : Web Developers, Debuggers
having specific skills to works on the platform needed

Validation & Feedback Process
 For a system to be useful, it must evolve through use in its
intended operational environment. A product is never
"done;" it is always maturing as the usage environment
changes…
 Customer Feedback Interfaces through every possible
communication methods

Intermediate Versions 1.1,2.3,3.4………
 According to feedbacks , modifying our existing BETA version
 Implementing ADD-ONS, modifying databases
 Ex.: adding the feature of filtering the products according to the end
user requirements

Final Version .0=Product
 The application which caters the needs of the end-user
 This is finally launched and hosted on the server
 Final Product according to user specifications

Why is Evolutionary Model Better 
 It has been found that prototyping is very effective in the
analysis and design of on-line systems, especially for
transaction processing, where the use of screen dialogs is
much more in evidence.
 The greater the interaction between the computer and
the user, the greater the benefit is that can be obtained
from building a quick system and letting the user play
with it
 Prototyping is especially good for designing good human-
computer interfaces.

Why Waterfall model not efficient 
 The inflexible partitioning into stages sometimes demands
a stage is frozen to allow progress to the next.
 Design problems unresolved in earlier stages are passed on
to subsequent levels possibly leading to badly structured
systems.
 No Updation in the application according to techno-
trends

System Development Life Cycle

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (18)

Similar to System Development Life Cycle

Similar to System Development Life Cycle (20)

Recently uploaded

Recently uploaded (20)

System Development Life Cycle