-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathindex.html
More file actions
209 lines (206 loc) · 10.5 KB
/
index.html
File metadata and controls
209 lines (206 loc) · 10.5 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8"><!--Untuk standarisasi bahasa pemrogramman -->
<title>Web Development Life Cycle</title>
<link rel="stylesheet" type="text/css" href="style.css"/>
</head>
<body>
<div class="navbar">
<div class="textheader">
Web Development Life Cycle
</div>
</div>
<div class="container">
<br/>
<br/>
<br/>
<p>Any software development project, a methodology should be followed to ensure project consistency and completeness.</p>
<p>The Web development life cycle includes the following phases: <b><i>planning, analysis, design, and development, testing</i></b>, and <b><i>implementation and maintenance. </i></b></p>
<br/>
<table width="607" cellspacing="0" cellpadding="0" border="0">
<tr >
<td colspan="2" align="center" ><b >Web Development Phase and Questions</b></td>
</tr>
<tr>
<td align="">Web development phase</td>
<td align="center">Questions to ask</td>
</tr>
<tr>
<td align="center"><b>Planning</b></td>
<td>
<ul >
<li>What is the purpuse if the Website </li>
<li>Who will use this Web site </li>
<li>What are the Computing environment</li>
<li>Who owns and authors the information on the Web site</li>
</ul>
</td>
</tr>
<tr>
<td align="center"><b>Analysis</b></td>
<td>
<ul >
<li>What information is useful to the user</li>
</ul>
</td>
</tr>
<tr>
<td align="center"><b>Design and development</b></td>
<td>
<ul >
<li>What type of Web site layout is appropriate </li>
<li>What forms of multimedia is helpful to the user</li>
<li></li>
</ul>
</td>
</tr>
<tr>
<td align="center"><b>Testing</b></td>
<td>
<ul >
<li>Is the Web site content correct</li>
<li>Does the Website funtion correctly</li>
<li>Are users able to find the information they need</li>
<li>Is the navigation easy to use?</li>
</ul>
</td>
</tr>
<tr>
<td align="center"><b>Implementtation and Maintenance</b></td>
<td>
<ul >
<li>How is the Web site published</li>
<li>How is the Web site Update</li>
<li>Who is responsible for content updates</li>
<li>Will the Web site be monitored</li>
</ul>
</td>
</tr>
</table>
<br/>
<br/>
<br/>
<h3><i><b>Web site Planning:</b></i></h3>
<p>Involves the identification of the Web site goals or purpose. The question to ask is: What is the purpose of this Web site?</p>
<br/>
<p>In addition to understanding the Web site purpose, you should also ask: Who will use the Website? or knowing the target audience in terms of: age, gender, computer literacy, etc.</p>
<p>Understanding the computing environment will allow the designer to know what type of Technologies to use.</p>
<h3><i><b>Web Site Analysis:</b></i></h3>
<p>During this phase, the Web designer needs to make decisions about the Web site content and functionality.</p>
<p>It includes a detailed analysis of the content of the Website in terms information covered, processing required, etc.</p>
<h3><i><b>Web Site design and Development</b></i></h3>
<p>After, the purpose of the Website has been found and the content has been defined, we need to organize the content of the Website. Many ways to organize the Website exists. Here are some general pointers: </p>
<table width="607" cellspacing="0" cellpadding="0" border="1">
<tr>
<td><b>Elements</b> </td>
<td><b>Purpose</b></td>
</tr>
<tr>
<td align="center"><b>Titles</b></td>
<td>Use simple titles that clearly explain the purpose of the page</td>
</tr>
<tr>
<td align="center"><b>Headings</b></td>
<td>Use Headings to separate main topics</td>
</tr>
<tr>
<td align="center"><b>Horizontal rules</b></td>
<td>Use horizontal rules to separate main topics</td>
</tr>
<tr>
<td align="center"><b>Paragraphs</b></td>
<td>Use paragraphs to help divide large amount of data</td>
</tr>
<tr>
<td align="center"><b>Lists</b></td>
<td>Utilize list. Numbered or bullet when appropriate</td>
</tr>
<tr>
<td align="center"><b>Page length</b></td>
<td>Maintain suitable Web page lengths; about one or two pages are adequate</td>
</tr>
<tr>
<td align="center"><b>Information</b></td>
<td>Emphasize the most important information by placing it at the top of a Web page</td>
</tr>
<tr>
<td align="center"><b>Other</b></td>
<td><br/>
<ul style=" list-style-type: '- '">
<li>Incorporate a contact e-mail address</li>
<li>Include the date of the last modification</li>
</ul>
</td>
</tr>
</table>
<h3><i><b>Web Site layouts:</b></i></h3>
<p>Websites are designed using any of several different types of layouts, including linear, hierarchical, and Webbed. Each layout links, or connects, the Web pages in a different structure to define how users navigate through the site and view the Web pages. You should select a layout for your Web site based on how users will most easily navigate through the site to complete tasks and view the Web site contents.</p>
<p>A <b>linear</b>Web site layout connects Web pages in a straight line. A linear Web site layout connects Web pages in a straight line. A linear Web is appropriate if the information on the Web pages should be read in a specific order. </p>
<h4><b>Linear Web Site Layout</b></h4>
<div class="imga">
 <img src="image/image003.gif"> <img src="image/image001.gif"><img src="image/image003.gif"> <img src="image/image001.gif"><img src="image/image003.gif">
</div>
<br/>
<p>A <b>hierarchical</b> Web site layout connects Web pages in a tree-like structure. A hierarchical Web site layout works well on a site with a main index or table of contents page that links to all other Web pages. With this layout, the main index page would display general information and secondary pages include information that is more detailed.</p>
<p>A <b>Webbed</b> Web site layout has no set structure. A Webbed Web site layout works best on Web sites with information that does not need to be read in a specific order and with many navigation options that users can select.</p>
<h4><b>Hierarchical Web Site layout
<br/>
<br/>
<br/> Webbed Web Site Layout</b></h4>
<div class="imgb">
<img src="image/image009.gif" id="img3"><img src="image/image003.gif" id="img1"></img>         <img src="image/image008.gif" id="img4"><img src="image/image003.gif" id="img2"></img>
</div>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<p>Most Web sites are a combination of the <b>linear</b>, <b>hierarchical</b> and <b>Webbed</b> layouts. Some of information on the Web site might be organized hierarchically from an index page; other information might be accessible from all areas of the site while other information might be organized linearly to be read in a specific order.</p>
<p>Using a combination of the three layouts is appropriate, if it helps users navigate through the site easily. </p>
<p>During the design and development phase, you should also consider what types of multimedia could contribute positively to the Web site experience. </p>
<p>Types of multimedia are graphics, photos, video and audio. </p>
<h3><i><b>Web site testing:</b></i></h3>
<p>A Web site should be tested at various stages of the Web design and development. This testing should include a review of page content, functionality and usability. Some basic steps to test content and functionality are:</p>
<ul >
<li>Reviewing for accurate spelling and proofreading content including page titles.</li>
<li>Checking links to ensure that they are not broken and are linked correctly</li>
<li>Checking graphics to confirm they display properly and are linked correctly</li>
>1li>Testing forms and other interactive page elements</li>
<li>Testing pages to check for speed of loading on lower speed connection</li>
<li>Printing each page to check how page s print</li>
<li>Testing each Web in several different browser types and versions to verify they display correctly</li>
</ul>
<p>Usability is the measure of how well product, allows users to accomplish their goals. Usability testing is a method by which users of a Web site are asked to perform certain tasks in an effort to measure the ease of use of the product.</p>
<br/>
<h3><i><b>Site Implementation and Maintenance:</b></i></h3>
<p>Once the Web site testing is complete and any required changes have been made, the Web site can be implemented. Implementation of a Web site means publishing the Web site or uploading it into a Web server. </p>
<br/>
<p>Once, the Web site has been implemented, its maintenance will include updating the information content by removing the outdated one and putting in the new one.<br/>Periodical checking of the links is also necessary to ensure that they are still active. </p>
<br/>
<p>Finally, Website monitoring is another key aspect of maintenance. Usually, the Web servers that host the Web sites keep logs about Web site usage. </p>
<br/>
<p>A <b>log</b> is the file that lists all the Web pages that have been requested from the Web site.</p>
<p>Analyzing the logs allows you to determine the number of visitors to your site and the browser types and versions they are using, as well as their connection speeds, most commonly requested pages.</p>
<h3><i><b>Cookies:</b></i></h3>
<p><b>Internet cookies</b> are very small files that are downloaded from a Web server to a Web browser. Cookies are embedded in the HTML code related to downloading requested pages from a Web site. </p>
<p>When a Web browser first asks for a file from a Web server, the server creates a cookie containing information about the request and sends the cookie to the browser along with the requested file. </p>
<p>The next time a request is made from the browser to the server, the cookie is sent to the server along with the request. When the server returns the requested file, an updated cookie is also returned.</p>
<br/>
<br/>
<br/>
<br/>
<br/>
</div>
<div class="footer">
Web Development Life Cycle
</div>
</body>
</html>