Web Development Life Cycle (WDLC) by Sally King

Web Development Life Cycle
(WDLC)
by
Sally King
Initiation/
Inception
Quality
Assurance
Design
Construction
2
Initiation/Inception
 Who?
 Communication and/or Marketing Manager
 How?
 Self-promotion
Your own Web Page and Advertisements
 Response to an RFP
 Industry contacts
 Employment (by an Advertising Firm)
 What?
 Initial expectations of the client (know who site is
trying to reach - audience)
 Write a proposal:
Include timeline – the more complex, the longer
the timeline for delivery of product
 End of Process:
 Proposal acceptance
3
 Contract negotiated and signed
Analysis & Requirements
Definition
 Who?
 Information Architect [Team]
Creates the site navigation and logic of the
directory structure and databases.
 Interacts with Communication/Marketing Manager
Server
(Database(s))
Web Server
(Web Page)
Internet
4
Analysis & Requirements
Definition
 How?
 Takes specifications from Communication
Marketing Manager.
 Does a network/system design on how
software and hardware will interact.
 Why?
 Client may not be current with their software
and hardware -- obsolescence?
 Software and hardware installed needs to be
updatable -- accept upgrades and be
expandable.
 What?
 Puts together software and hardware needs
for client and pricing of products.
 Prospectus on possible new process for client
interface with new e-business software and
5
Analysis & Requirements
Definition
 End of Process:
 Agreement from Communication/Marketing
Manager on your assessment of client needs.
 Perhaps agreement from client on prospectus (may
want to present web design with the needs
assessment and pricing prospectus).
6
Design
 Who?
 Graphic Designer - creative responsibility.
 How?
 Creates a story board -- defines look of Web Site.
Main Page
with placement of
text and company
logo / trademark
picture
Page 2
with placement of
text and graphics
Page 3
with placement of text
and graphics
7
Design
 Why?
This is what will sell the Web Site to the
client as this is how they will see
themselves represented on the Internet.
 End of Process:
Present story board to Communication/
Marketing Manager for their review and
approval.
Works with HTML Programmer during
this phase.
8
Construction
 Who?
 Web Script Programmer - works with graphic designer and
Information Architect.
 How?
 Programming languages used: HTML, Java Script, XML, etc.
 Software used: Dreamweaver or Frontpage (graphical user
friendly software that is scripted in English and manipulates
HTML and JavaScripts) and Web browser.
 Why?
 To show client exact representation of how Web Site will look
on the Internet.
 End of Process:
 Ensures site works - interfaces with data bases and is
navigable.
 Works with graphic designer and information architecture to
ensure it works and presents to Communication/Market
Manager for approval, who then seeks approval from client.
9
Installation/Deployment
 Who?
 Information Architect, Programmer and Client
(Content Editor) work together to install Web Site at
client site.
 How?
 Placement of server, installation of software and
installation of Web Site software.
 Ensure compliance with legal licensing and
copyright laws.
 Why?
 Clean product delivery
 End of Process:
 Once installed, test installation.
10
Quality Assurance
 Who?
 Quality Assurance Tester - Creates performance and
user testing.
 Hacker - to ensure integrity of information and
firewall is working.
 How?
 Blind shopper - goes onto Web Site and tests
usability from outside computer.
 Works with Information Architect to ensure
integrity of data base and information processing
smoothly.
 Why?
 Smooth delivery of product.
 End of Process:
 Delivered to Client and working.
11
Administration/Maintenance
 Who?
 Server Administrator - either outsourced unless big
company where it will be an internal process at client site.
 How?
 Understands Web based technology and upgrades
appropriately.
 Client Interfaces with outsourced Web Development
Company (Information Architect, Graphic Designer and
Programmer).
 Why?
 To keep integrity of information intact with current
firewall technology.
 Usability by Internet users - keeping up with current
technology.
 Keep it fresh AND logical.
 Process: Ongoing
12
References
 http://www.alistapart.com/stories/process/
 http://intranetjournal.com/articles/200201/l
c_01_23_02a.html
 http://www.ucc.ie/xml/#acro
 http://www.clienthelpdesk.com/dictionary/ja
vascript.html
 System Development Life Cycle (SDLC)
Process, Graphic Adapted from IGeneration,
Inc. 1260 Class -- Handout.
13