Chap09 Development

7/31/2019 Chap09 Development

1/32

9-1


2/32

9-2

Chapter 9

Website

Development

Process

McGraw-Hill/Irwin Copyright 2004 by The McGraw-Hill Companies, Inc. All rights reserved.


3/32

9-3

Chapter 9: Website Development Process

Questions answered in this chapter: What are the steps involved in building a

website?

How is the user experience definitioncreated?

What is the architecture design process?

What is the implementation process?

What is involved in the test process? What factors are involved in launching a

website?


4/32

9-4

Website Development Process

The goal of website development is topresent functionality and content

through some type of visual interface.


5/32

9-5Three External Forces That

Shape This Goal: Time:

What is the deadline for this project?

Is the deadline flexible or nonnegotiable?

Can the site be phased in over time, or do all of the desiredfeatures have to be built immediately?

Budget:

How much money has been allocated to the project, and how wasthat number derived?

Is there enough in the budget to hire additional staff if the deadlineis too tight?

Can the project be outsourced in part or entirety?

Resources:

Does the organization have the right mix of skills internally todeliver the project as specified?

Does it have enough of each type of skill given the timetable thathas been laid out?

Are these resources available, or could the resources needed be

pulled off another projectand what is the relative importance ofthis project to the organization versus the other project?


6/32

9-6

Exhibit 9

-1: Process for Building a Website

Strategy Formulation

User Experience Definition

Architecture Design Process

Implementation

Test/Fix

Launch


7/32

9-7

Process for Building a Website from Scratch

Important aspects that need to be known or in place:

A well defined set of business objectives for the site

Executive support

A general definition of the audience segments

A clearly articulated project plan

A succinct definition and description of the relevant brandingsystems

A competitive analysis for the industry and theproduct/service offered by the site

a budget

development resources

a steering committee of senior stakeholders and executives


8/32

9-8

Process for Building a Site from Scratch(contd)

User Experience: refers to how a user perceives andinterprets the website (content, functions and features

of the website)

Functional Specification: provides a highly detailedguide to what every page on the website does ( add toshopping cart and recalculate shipping)

Change-management Process: a framework foridentifying problems within the project (e.g., softwarebugs or a change in site requirements), prioritizingthese problems, assigning the task of resolving theseproblems, and tracking the progress of the tasks until

all problems are resolved Project Plan: Lays out the checkpoints, milestones,

and resources that are expected to be required tomove the project forward to completion


9/32

9-9

Process for Building a Site from Scratch(contd)

Discipline Areas key to successful site

development include: Business Strategy

Functional/subject-matter expertise

Information architecture

Content development/writing

Visual design

Interface design

Technical architecture

Database administration

Data modeling

Technical development

Quality assurance team lead

Quality assurance testing


10/32

9-10

Exhibit 9-2: Project PlanID Task Name Duration

1 Acme.com Version 1.0 145 days?

2 User Experience Definition 70 days?

3 Audience Definition 45 days

4 ID initial audience groups 5 day s

5 Brainstorm user intentions 5 day s6 Brainstorm f eatures / f unctions to satisf y intenti 5 day s

7 Test assumptions on intentions 5 day s

8 Test assumptions on f eatures / functions 5 day s

9 Build user personea guides 10 day s

10 Dev elop Functional Matrix 10 day s

11 Dev elop Audience Def inition Findings Document 10 day s

12 Functional Definition 25 days

13 Create Functional Matrix 10 day s

14 Process Flows 5 day s

15 Site Architecture 10 day s

16 Nav Model 2 day s

17 Directory Structure 2 day s

18 Page inventory 2 day s

19 Content Matrix 5 day s

20 Page Schematics 10 day s

21 Visual Definition 30 days?

22 Gather Interf ace Dev elopment Requirements 15 day s

23 Dev elop Interface Findings Document 5 day s?

24 Dev elop Visual Identity Sy stem 2 wks

25 Dev elop Sty le Guide 2 wks

26 Architecture Design Process 85 days

27 Technical Discovery and Definition 80 days

28 Existing Technology Discov ery 10 day s

29 Gather Technical Dev elopment Requirements 10 day s

30 Dev elopment Env ironment Setup 1 wk

31 Liv e Env ironment Setup 1 wk

32 Implementation 45 days

33 Findings Validation 1 wk

34 Visual Design Development 2 wks

35 Interf ace Dev elopment 4 wks

36 Application Dev elopment 8 wks

37 Testing 65 days

38 Unit Testing 8 wks

39 Component Integration Testing 5 day s

40 UI Integration Testing 5 day s

41 Integration Testing 5 day s

42 Sy stems Testing 5 day s

43 Perf ormance and Stress Testing 5 day s44 Go Liv e 5 day s

2 13 24 5 16 27 7 18 29 10 21 1 12 23 3 14 25 6 17 28 8 19 30 11 22 2 13 24 4 15

ar 31, '02 Apr 28, '02 May 26, '02 Jun 23, '02 Jul 21, '02 Aug 18, '02 Sep 15, '02 Oct 13, '02 Nov 10, '02 Dec 8, '02 Jan 5, '03 Feb 2, '03


11/32

9-11

User Experience Identification

By developing the online offering through:

Identifying the scope of the offering Identifying the customer decision process

Mapping the offering to this decision process

The following can be defined:

User types: The discrete types of users whowill use the site (customers, prospects, partners,

vendors, media and employees)

User intentions: What tasks users want to accomplishwhen they visit the site (the output of thisinvestigation is a descriptive list of each of the usersintentions, a list that more than likely contains severaldiscrete intentions per user type.


12/32

9-12

User personas: Fictitious, archetypal examplesof real users that allow the development teamto focus on the collective core needs of theusers within a group

Use case: Describes how a user and a systeminteract to accomplish a specific goal,typically a step-by-step guide describing allthe actions that the user takes, and what the

system does in return


13/32

9-13

Exhibit 9-3: User Profile

Personal Profile

Age: 20

Education: 4 years of high school

Car: Saturn SC1

Shops at:Old Navy, Starbucks, Abercrombie and Fitch,

Gap, Newbury Comics, Tower Records

OccupationJob: Full-Time Student

Company Size N/A

Company Industry: N/A

Typical Task on Acme.com: Product Research and Purchase

Familiarity with Acme: Somewhat familiar: Cindy has seen Acme's

adds, and a few of her friends have computers

from Acme.

Usage Scenario Description: Cindy needs a computer, but is uncertain as to

what her options areshe is a bit afraid of the

whole process, to be honest. Her parents have

agreed to buy her a computer, but have told her

that she needs to do the research.

Reason for choosing to work with

Acme: Recommendations from her friends, cool-looking

computers, good price, and Acme appears to bean easy, no-pressure company to buy froma

company that will take care of her.

Desired Experience: Cindy wants to be able to research her computer

options, understand the pros and cons, and buy

a computer.

But, she wants to buy a computer that is at least

as cool as her friends computers, so she would like to be

able to make a case to her parents for a slightly

better computer than what she might actually

need.

When she decides what to buy, she would like to

understand the financing options available to

her.

Key Points:

User Profile: Cindy the College Student


14/32

9-14

Exhibit 9-4: Intentions Matrix

IntentionsNeeds

(Features and Functions)

Actions

(user objectives)

Acme's business objectives

Research and Buy a Computer

Lookup Products Get Product Information Increase customer base

- Genera l Product In fo rmati on Learn the d if fe rences be tween produc ts and p roduct op ti ons Educate customer to better understand benefits of the technology

- Quick comparison of products Upsell / Crosssell customers into new products / peripherals

- Upgrade and Accessory information Leverage user's circle of community to advertise Acme

Research the Technology

- System to explain what the system pieces are

and how they compare to each other

- Have products suggested based on needs Have a product suggested to her based on her needs

Pick the System Show friends what system she is getting

- Pick a solution(s) Show parent's 2-3 systems and have them buy one - pursuade them tobuy the better machine

- configure / customize the system

- Store picked solutions for viewing later / sharing

to parents / friends

- Allow friends/parents to vote on system if she

can't make up her mind

Buy the System Buy the best system she can get

- Send Parents to her customized computer to

have them buy it on her behalf

Check Purchase Status

owledge base, documentation, troubleshooting wizard, live csr

contact information

customer service - rma, swap parts

Cindy needs a computer, but is uncertain as to

what her options are. She needs to be able to

show her parents the options that she has, and

ideally let them purchase the computer for her.

E hibit 9 5 F ti l M t i


15/32

9-15Exhibit 9-5: Functional Matrix vs.

Functional Specification

Functional Matrix Purpose:

Define project scope, used to build project plan

Communication with executives, project team, any

external contractors Track enhancements as they are discovered during

development

Plan future release functionalityby priority

E hibit 9 5 F nctional Matri s


16/32

9-16Exhibit 9-5: Functional Matrix vs.

Functional Specification (contd)

Functional Specification Purpose:

Provide detailed design of system processes and

pages

Provide details of the life cycle of different objects(search, payments, etc.)

Defines the details of each page (list of fields on a

page, their validation requirements, their data sources)

Defines all actions on each page (save shopping cart,send e-mail, update account, checkout)


17/32

9-17

Architecture Design Process

At this point the team needs to generate the next set of important

documents:

The Site Map:

Typically a hierarchical view of the proposed website and

encompasses all the primary pages, or templates, to be developed.

Allows the development team to logically group content into content

areas and to understand how different content types relate and link

to one another

The challenge is to develop a navigation system that is meaningful

to the user and also fits within the visual design of the site

Page Schematics:

Simple drawings or diagrams that serve as a conceptual layout forwhat each page on the site will look like

The schematic provides the team with a way to brainstorm how and

where certain functionality and content will appear on a particular

page


18/32

9-18

Exhibit 9-6: Sample Site Map


19/32

9-19

Exhibit 9-7: Page Schematic


20/32

9-20

Technical Discovery

The technology vision is strongly informed

and structured by many elements, includingthe following: The business objectives for the site

User persona

Existing technology Internal skill set

User intentions

Time and budget

Traffic Uptime requirements

Security requirements


21/32

9-21

Technology Discovery (contd)

The technology summary document shoulddetail the following: Existing corporate systems, including relevant

back-end systems and databases

How the proposed site differs from those of thecompanys competitors

Conceptual technical architecture to support thesite

An analysis of and recommendations for the

software components to be used during thedevelopment process

Experience Definition and Architecture


22/32

9-22Experience Definition and Architecture

Design Outputs At this point, the development team should be

able to create the following outputs: User experience and functional definition

document

User type definition document

User intentions definition document User persona definition document

Functionality matrix

Content matrix

Use cases Site map

Page schematics


23/32

9-23

Implementation

Validation Finalize the visual design of the site

Create a functioning prototype

9 24


24/32

9-24

Implementation (contd)

Build Phase

The building process boils down to some very simplesteps: Design the technical infrastructure

Design the technical components so that they will be bothflexible and extensible

Build the components (both visual and functional) that willmake up the website

Integrate those components so that they work together asexpected

Test those components, both individually and after they have

been integrated Refine the system and components based on these tests

Launch the website

9 25


25/32

9-25


Development Environment Deciding which language should be used is guided

by a number of factors:

Available skills

Portability

Scalability/enterprise features

Cost

9 26


26/32

9-26


Page Design Unique pages: are pages that have a design

that is different from any other page on thesite

Template pages: the design and layout ofthese pages are repeated more than once,usually on a section of the site that has

multiple pages of similar content (e.g., pressreleases)

9 27


27/32

9-27


Interface Development The choice of which technologies to implement within

an interface is difficult because not all pages require

the same set of functionality or deliver the same type

of information

The success of an interface is determined by whether

its users are successful in getting the information

they need and understanding the information that ispresented to them

9 28


28/32

9-28


Application Development The application development is shaped by the

functionality matrix and the functional specification

The team creates modules that meet all the

capabilities the website needs to have

9 29


29/32

9-29

Test/Fix

Steps in the testing process: Unit testing

Integration testing

Systems testing Load testing

9 30Exhibit 9-8: Number of Bugs Over


30/32

9-30Exhibit 9-8: Number of Bugs Over

Testing Days

Bugs

0

20

40

60

80

100

120

140

160

1 3 5 7 9 11 1 3 15 17 19 2 1 23 25 27 2 9 31 33 3 5 37 39 4 1 43 45 47 4 9 51 53 5 5 57 59

Days

Bugs

Bugs

9 31


31/32

9-31

Launch

Basic issues that need to be solved beforelaunching a site:

A hosting facility/ISP must be selected

The servers must be built and tested

The connectivity of the site must be tested

The security of the overall system must be audited

9 32


32/32

9-32

Criteria for evaluation of websites

Load time Response time

Page link

Frequency of update

Traffic Design

Size

Number of items

Accessibility error Mark up validation

Broken links

Date post:	05-Apr-2018
Category:	Documents
Upload:	nurul-izzah
View:	241 times
Download:	0 times

Chap09 Development

Documents