Final Project

CHAPTER 7

WEBSITE DESIGN

7.1 Website Development

Over the past few years, we’ve witnessed some incredible changes in
the way we think about computers. We are no longer bound on the large
cumbersome applications on the desktop. With the introduction of the Internet
and the World Wide Web, we can now access information and ever do
business from virtually anywhere. The challenge that we, as application
developers, now face is that of raising the bar yet again. With these resent
advances in technology also comes the demand for faster, lighter, and more
robust applications that can deliver across the web. For designing of web Site
we consider following design.

7.2 Conceptual Design

7.2.1 Screen Resolution:
This web site can be best viewable on 800X 600 resolutions.

7.2.2 Page Margins:
By default all web pages exhibit margins around all sides that can be
eliminated to provide extra space and /or enhance visual appeal. Hot wear
shop website will not have any page margins.

7.2.3 Horizontal Scrolling:
Horizontal scroll is eliminated almost from all pages.

7.2.4 Browsers:
It will have all the tags compatible with both major browsers, IE 6.0 or higher
and Netscape 4.0 or higher.

7.2.5 Display Speed:
The web site will contain lighter graphics, so that it may be loaded easily even
if ISP’s bandwidth is not up to the mark.

41

GLOSSARY

Actor
Represent role, external to system interact with the system.

Use Cases
Represent interaction between system and actor.

Scenario
It is the case for actual input and expected output.

Use Case Diagram
Represent the use, services and functionality of the system with actor.

Use Case Realization
How the use case realizes in the design table model.

Activity Diagram
Represent the process flow of use case.

View Frame
Represent the GUI.

Collaboration Diagram
It is alternative representation of sequence diagram.

Class
Describe the group related object having same attribute, operation,

relationship etc.
Object

Represent something having identity, state and behavior.
Class Diagram

Represent the static structure of the system in terms of classes.
42

Data Model
Represent the persistence object model.

Component
Represent standalone components.

Component Diagram
Represent how components are interdependent on each other.

Deployment Diagram
Represent the deployment view of set of nodes

43

{UML] BIBLIOGRAPHY
[Web Interface]
http://www.rational.com
http://www.ebay.com
http://www.shopping.com
http://www. beliscity.com

[General] http://www.w3.org\dom\
http://www.informit.com
http://www.amazon.com
http://www.wikipedia.com

[Search]

http://www.google.com
http://www.yahoo.com
http://www.altavista.com
http://www.ask.com

44