Microsoft Word - CONTENT.docx

weaverchurchSoftware and s/w Development

Aug 15, 2012 (5 years ago)

254 views

CHAPT
E
R 5


IMPLEM
E
N
TATION AND TE
ST
ING



5.1 Implementation and Testing


Several

hardware

and

software

are

used

in

the

develop
m
ent

and

docu
m
entation
of

the

application

prototype.

This

chapter

is going to talk about

those

hardware
and software required in order to imple
m
ent
a
nd run the application prototype
properly.

This

chapter

also discusses

how

to

i
m
ple
m
ent

and

run

the

application
prototype in the
m
obile device. Moreov
e
r, nu
m
e
rous testing on the application
also i
n
clud
e
d in this ch
a
pter.




5.2 System Specification


The

whole

process

of

paper

writing

and

p
r
ogram

develop
m
ent

is

done

in

author’s
notebook.
T
he specifications of the notebook are:

VAIO
V
G
N
-
SZ79GN/C


-


Processor: Intel Core 2 Duo T9300 (2.50GHz)


-


RAM:
2GB DDR2 SDRAM


-


VGA:

NVIDIA

GeForce

8400M

GS

(SPEED

MODE)

/

Intel

Graphics

Media


Accelerator X3100 (STAMINA
M
ODE)


-


Screen: 13.3”
W
i
de (
W
FGA: 1280 x 800) TFT Colour Display


-


Hard disk: 250GB (Serial ATA, 5400 rp
m
)


-


Operating
S
yste
m
:
W
i
ndows Vista Service Pack 2









50

51




The

testing

of

the

application

prototype

is

conducted

using

the

e
m
ulator

of
wireless toolkit software
and on aut
h
or’s
m
obile phones which is Nokia N73.
NOKIA

N
7
3

-

D
i
m
ensions : 110 x 49 x 19 mm


-

Display: T
F
T, 256K colors, 240 x 320 pixels, 2.4 inches, 36 x 48 mm


-

Me
m
ory: 42 MB storage, 64 MB RAM internal
m
e
mory


-

GPRS: Class 10 (4+1/3+2 slots), 32
-

4
8 kbps


-

3G: Yes, 384 kbps


-

WL
A
N
:

No


-

Bluetooth: Yes, v2.0 with A2DP (latest fir
m
ware)


-

Infrared port: Yes


-

USB: Yes, v2.0, Pop
-
Port


-

OS: Sy
m
bian OS 9.1, S60 3rd edition


-

CPU: Dual ARM 9 220 MHz processor


-

Java: Yes, MIDP 2.0





The

i
m
pl
e
m
entation

and

docu
m
entation

of

the

application

prototype

is

possible
with existences of several nu
m
ber of software that support the author:

-

W
i
ndows V
i
sta Ser
v
ice Pack 2


-

Netbeans I
D
E 6.5


-

Sun Java
W
i
reless Toolkit version 2.5.2 for CLDC


-

Notepad


-

Microsoft
O
ffice 2007

52




5.3 Soft
w
are Configuration


In

order

to

build

and

run

the

application

prototype

p
r
operly,

there

are

several
necessary procedures needs to be followed:

1. Download

and

install

the

Sun

Java

W
i
reless

Toolkit

for

CLDC.

This

toolkit
act

as

plat
f
orm

for

J2ME

on

W
i
ndows

environ
m
ent

and

as

the

emulator
which co
m
p
iles and runs the applicat
i
on

prototype.

Version

2.5.2

is

used

in
the application develop
m
ent.

2. Download

and

install

t
h
e

Netbeans

ID
E

f
or

W
i
ndows.

This

IDE

helps

in

the
develop
m
ent of the application since

it has support for library co
m
pletion and
it

is

easy

to

include and

configure

external

libraries

into

a

project

using

this
IDE. Version 6.5 is used in the application develop
m
ent

3. Copy the project a
nd all of the libraries into any
W
i
ndows directory / folder.


4. From

Netbeans IDE, try to open the pre
v
ious
p
r
o
j
ect that
h
as been copied.


5. If

there

is

a

problem

with

the

reso
ur
ces,

t
r
y

to

fi
x

the

re
f
e
r
e
n
ces

o
r

j
u
st

d
elete
the

exi
s
ting

lib
r
aries

and

re
-
in
c
lude

the

libraries

using

add

Jar/Zip

from the
ones that has been copied before.

6. Run the application prototype.





To be tested in a
m
obile device another procedure need to be co
m
pleted:


1. Check the MIDP and CLDC of the mo
b
ile phone that is

going to be used.


2. Match

the

configuration

and

the

profile

of

the

project

with

the

m
obile

phone.


The

MIDP

and

CLDC

of

the

project

can

be

set

from

the

project’s

properties.
Please

note

that

differe
n
t

configuration

and

profile

of

the

p
roje
c
t

with

the

53




ones

in

m
obile

phone

can

caused

the

application

cannot

be

r
u
n

in

the

m
o
bile
phone.

3. Run and compile the application prototype


4. Send

the

JAR

of

the

application

(which

is

loc
a
ted

in

the

dist

f
older

in
s
i
de

the
application

directory)

to

the

m
obile

d
e
vice.

The

easie
s
t

way

to

send

it

is via
Bluetooth

or

infrared,

however

it

also

can be

sent

using

cable

data

or

USB.
Note that for so
m
e mobile phone the MIDP JAD (Java Application
Descriptor)

also

required

in

o
rder

to

install

t
h
e

a
pplication to

the

m
obile
phone.

5. Open

the

received

JAR

which

usually

will

be

i
n
stalled

by

t
h
e

m
obile

phone
auto
m
atically.

6.
The

application

now

is

ready

to

be

used.

The

applic
a
tion

is

usually

inst
a
lled
inside the application directory in
N
okia
m
obile phone and
m
ay be different
for other type and brand of
m
obile phone.




5.4 Testing


This

part

provides

the

actions

that

the application

can

do

and

m
akes

s
ure

that
those

actio
n
s

work

properly

and

appropriately according

to

what

they

have
designed
for. Included in this part are t
h
e browser’s functionality

and

the

p
arse
r
’s
functionality.

The

browser’s

f
uncti
o
nality

con
s
ists

of a
c
ti
o
ns

th
a
t

t
h
e

browser
supposes

to

do

while

the

parser’s

functional
i
ty

consists

of

list

of

WML

t
a
gs

that
is

supported

and

not

supported

by

this

cur
r
ent application prototype. One thing
that

n
eed

to

be

re
f
l
e
ct

on is

that

not

a
ll

of

t
h
e

W
ML

tags can be

p
a
rsed

y
et

u
s
i
n
g
this

ap
p
lic
at
ion

prot
o
t
y
pe

since

t
h
ere

a
r
e

a

l
o
t

of

W
ML

tags

with

t
h
eir

own

54




attributes

a
n
d

to

li
s
t

all

the

co
m
binations

of

W
ML

tags

within

a

doc
u
m
ent,

a
further researches is needed.




Bro
w
ser’s

Functionality


No.

Functionality

Expected Output

Status

1

Ho
m
e web
a
ddress

Showing the web pages of


ho
m
e web address

OK

2

Book
m
arks

Show list of

book
m
arks and


show the web pages when
selected

OK

3

Last
W
eb Address

Show the web pages of the last


web pages the user have
navigated into

OK

4

Setting

Show so
m
e setting to c
o
n
f
igure


the browser such as appearance
and security

Not OK

5

Load Plug
-
ins

Load all pre
-
installed plug
-
ins


into t
h
e br
ow
ser

OK

6

Browser’s interface


custo
m
izati
o
n again
s
t
plug
-
in

Show so
m
e

custo
m
ization in


the browser’s interface
d
ue to
the plug
-
ins loaded

OK

7

Browser’s process


custo
m
izati
o
n again
s
t
plug
-
in

Show so
m
e

custo
m
ization in


the browser’s process due to the
plug
-
ins

loaded

OK

8

Browse web address

Show the resulting web pages


of the browsed web address

OK

9

Navigate between web


pages through hyperlinks

-

OK

10

Processing

input

-

Not OK

55




11

Successfully parse
W
ML


into J2ME inter
f
ace

Show the parsed result of
W
ML


docu
m
ent in fo
r
m

of J2ME


int
e
r
f
ace

OK

Ta
b
le

4


List

o
f Br
o
wser’s F
un
ctio
n
ality









Parser’s F
u
nctionality


No.

Tag

Purpose

Status

1.

access

Defines access control info
r
m
ation of a


deck

Not OK

2

card

Defines a card in a deck

OK

3

head

Contains in
f
or
m
ation about the


docu
m
ent

Not OK

4

m
eta

Defines
m
eta infor
m
ation about the


docu
m
ent

Not OK

5

te
m
plate

De
f
i
nes a c
o
de te
m
plate
f
or all t
h
e c
a
rds


in a deck

Not OK

6

w
m
l

Defines a WML deck (WML root)

OK

7

br

Defines a line break

OK

8

p

Defines a paragraph

OK

9

table

Defines a table

Not OK

10

tr

Defines a table row

Not OK

11

td

De
f
i
nes a t
a
ble c
e
ll
(
t
a
b
le dat
a
)

Not OK

12

b

Defines bold
text

OK

13

big

Defines big text

Not OK

14

em

Defines e
m
phasized text

Not OK

15

i

De
f
i
nes it
a
lic text

OK

16

s
m
all

De
f
i
nes s
m
all text

Not OK

17

strong

Defines strong text

Not OK

56




18

u

Defines underlined text

OK

19

a

Defines an
anchor (a link)

OK

20

anchor

Defines an anchor (a link)

Not OK

21

i
m
g

Defines an i
m
age

OK

22

do

Activates

a

task

when

the

user

clicks

on


a word/phrase on the screen

Not OK

23

onevent

Contains

code

to

be

executed

when

one


of the following events
oc
curs:
onenterbackward, onenterfor
w
ard,
onpick, onti
m
er

Not OK

24

postfield

Contains

in
f
or
m
ation

to

be

sent

to

the


server along with a <go> tag

Not OK

25

go

Represents

the

action

of

switching

to

a


new card

Not OK

26

noop

Says

that

nothing

should

be

done

(noop


stands

for

"no

oper
a
tion").

Used

to
overri
d
e deck
-
level elements

Not OK

27

prev

Represents

the

action

of

going

back

to


the pre
v
ious

card

Not OK

28

refresh

Refreshes

so
m
e

specified

card


variables.

If any

of

the

variables

are
shown

on

the

screen,

this task

also
refreshes the

screen

Not OK

29

fieldset

Used

to

group

togeth
e
r

rel
a
ted

elements


in a card

Not OK

30

input

Defines

an

input

field

(a

text

field


where the u
s
er can e
n
ter so
m
e text)

OK

31

optgroup

Defines

an

option

group

in

a

selectable


list

Not OK

32

option

De
f
i
nes an option in a s
e
lectable li
s
t

Not OK

33

sele
c
t

De
f
i
nes a s
e
lectable li
s
t

Not OK

57




34

setvar

Sets

a

v
ari
a
ble

to

a

sp
e
ci
f
ied

v
a
lue

in

a


<go>, <prev>, or <refresh> task

Not
OK

35

ti
m
er

Defines a card ti
m
er

Not OK

Table

5



List

of

W
M
L

tags


Source of WML tags and purpose:


http://www.w3schools.c
o
m
/
W
A
P/w
m
l_reference.asp


For
m
ore references on configuring and
testing the application prototype, screen
captures are available in the Append
i
x section of the thesis paper.


For the byte codes executed during browser startup and the nu
m
ber of dyna
m
i
c
object

allocated

for

the

application

prototype

testing

is

conducted

using
NetBeans output result:





No.

Number of Plug
-


ins

Bytes exec
u
ted

Number of dynamic


object allocated

1

0

3526521

17734

2

1

3462258

18931

3

2

3465975

19013

4

3

3520491

19206

5

4

3473274

19162

Table

6



B
y
tes

Exe
c
uted a
n
d D
y
na
m
ic

O
b
j
e
ct Allocated for Nu
m
b
er

of P
l
ug
-
ins

58








3540000

B
y
t
es

e
x
ecu
t
ed


3520000


3500000


3480000



3460000


Bytes

executed


3440000


3420000



0

plug

ins

1

plug

ins

2

plug

ins

3

plug

ins

4

plug

ins




Fig
u
re

2
4

-

B
y
tes

Exe
c
uted
fo
r

N
u
m
b
er

of P
l
u
g
-
ins

in

B
r
ow
ser





19500

Dynamic

Object

Allo
c
a
t
ed


19000


18500


18000


17500


Dynamic

Object

Allocated


17000


16500



0

plug

ins

1

plug

ins

2

plug

ins

3

plug

ins

4

plug

ins




Figure

25
-

D
y
na
m
ic Object

Allocated

f
o
r Nu
m
b
er of Pl
u
g
-
i
ns

in B
r
o
ws
er