personal website designs

8/7/2019 Personal Website Designs

1/33

A PROJECT REPORT ON

PERSONAL WEBSITE DESIGNSubmitted in fulfillment of the requirements for the diploma in

Computer EngineeringSemester Vth

The Punjab state Board of Technical Education and

Industrial Training

(2010)

SUBMITTED BY

Arshad Ayub Ansari (Regd. No.008046200314)

Gurpreet Singh (Regd. No.008046200344)

Supervisor: Er. Rohit Bhateja


2/33

Adesh Polytechnic College,

Muktsar

CERTIFICATE

This is to certify that the project entitled PERSONAL

WABSITE DESIGN submitted by Arshad Ayub Ansari ,

Gurpreet Singh having Regd. Numbers: (0314,0344) for the

partial fulfillment of the requirements of Diploma in Computer

Engg. Of the Punjab State Board of Technical Education and

Industrial Training, Chandigarh embodies the bonafide work done

by our supervision.

Place: MUKTSAR Signature of the Internal

supervisor

Er. Rohit Bhateja

Date: ___________ COMPUTER LECTURER


3/33

ADESH POLYTECHNICAL

COLLEGE,

MUKTSAR

ACKNOWLEDGMENT

We are greatly indebted to our guide Er. Rohit Bhateja for

the inspiration and guidance that they have provided us during our

project work. We think that without the help of our guides we can never

achieve our goal during project work. Our guides not only provide the

help during project work but also improve our self-confidence to do

something better in life.

We are also thankful to project incharge Er. Rohit Bhateja ,

who provide us the proper knowledge of HTML language.


4/33

TABLE OF CONTENTS

ChapterNo. Page No.

1. About the Project

1-3

(a) Introduction

(b) Overview

(c) Objectives

1. Software requirement Analysis 4-11

2. Software Design

12-14

3. Structure of the Project 15-

16


5/33

4. System requirements 17-

21

5. Outputs

22-27

ABOUT THE PROJECT

(a) Introduction

Mostly waterfall model is used for developments ofprojects. This model consists of following phases:

1. Requirement Specification and Analysis

2. Design


6/33

3. Implementation and Unit Testing

4. Integration and System testing

5. Operation and Maintenance

1

(b) Overview

Our project is a Personal website which is a website that has beendeveloped for the purpose of connecting people on the common platformthrough the internet medium. We have made the site using HTML.Personal web pages are World Wide Web pages created by anindividual to contain content of a personal nature rather than on behalfof an employer or institution. Personal web pages are often used solelyfor informative or entertainment purposes.

The content of personal web pages varies. Many contain biographicalinformation, rsums, and blog posts. Many personal pages will include

information about the author's hobbies, and information of interest onlyto friends and family of the author.


7/33

2

(c) Objectives

The foremost objective of the project was to introduce myself to all

world using good website interface.

We could share our pictures, our personal information, our likes

and dislikes, their views on various day to day issues any time.

People can connect with us using contact us form..

We can updates our works and provide download facilities of our

free web work.

We can share our personal experience any where any time using a

good user friendly and attractive graphic interface


8/33

3

SOFTWARE REQUIREMENT

ANALYSIS

The requirements gathering process is intensified and focused

specifically on software. To understand the nature of the program(s) to

be built, the software engineer (analyst) must understand the

information domain for the software, as well as required function,

behavior, performance, and interfacing. Requirements for both the

system and the software are documented and reviewed with the

customer.

Design

Software design is actually a multi-step process that focuses on four

distinct attributes of a program: data structures, software architecture,

interface representations, and procedural (algorithm) detail. The design


9/33

process translates requirement into a representation of the software that

can be assessed for quality before code generation begins. Like

requirements, the design is documented and becomes part of the

software configuration.

4

Code generation

The design must be translated in to a machine-readable form. The

testing process focuses on the logical internals of the software, assuring

that all statements have been tested and on the functional externals thatis, conducting tests to uncover errors and ensure that defined inputs will

produce actual results that agree with required results.

Testing

Once code has been generated, program testing begins. The testingprocess focuses on the logical internals of the software, assuring that all

statements have been tested and on the functional externals that is,

conducting tests to uncover errors and ensure that defined inputs will

produce actual results that agree with required results.

Maintenance


10/33

Software will undoubtedly undergo change after it is delivered to

the customer (A possible exception is embedded software).Change will

occur because errors have been encountered, because the software must

be adapted to accommodate change in its external environment.

5

because the customer requires functional or performance enhancements.

Software maintenance reapplies each of the preceding phases to an

existing program rather than a new one.


11/33

oleObject1


12/33

6

DEVELOPMENT OF PROCESS PHASES

Project Startup.

Requirement Analysis.

High Level Design.

Low Level Design.

Coding.

System & Integration Testing.

System Acceptance Testing.

Release of Product.

Project Windup.

Software Warranty Support Maintenance.

Review Documents prepared in Software Development

Product Feasibility Reviews (PFR).

Software Requirement Review (SRR).

Preliminary Design Review (PDR).

Source Code Review (SCR). Acceptance Test Review (ATR)


13/33

7

Project startup

A complete understanding of software requirements is essential to the

success of a software development effort. No matter how well designed

or well coded, a poorly analyzed and specified program will disappoint

the user and bring grief to the developer.

The requirement analysis task is a process of discovery, refinement,

modelling, and specification. The software scope, initially established in

the system- engineering step and refined during software project

planning, is refined in detail. Models of the required data, information

and control flow, and operational behaviour are created. Alternative

solutions are allocated to various software elements. Actually

requirements analysis is a software-engineering task that bridges the

gap between system-level software allocation and software designs as

shown in figure below:


14/33

oleObject2

8

Requirement Analysis

Requirement analysis enables the system engineer to specify function

and performance,

indicate softwares interface with other system elements,

and establish constraints that software must meet. Requirements allow


15/33

the software engineer (often called analyst in this role) to refine the

software are allocation and build modules of the data, functional, and

behavioral domains that will be treated by software. Analysis provides

the software designer with models that can be translated in to data,architectural, interface, and procedural design. Finally, the requirement

specification provides the developer and the customer with the means to

assess quality once software is built. Developer and the customer with

the analysis may be divided into five areas of effort:

Problem Recognition

Evaluation and Synthesis

Modeling

Specification

Review

9

Initially, the analyst studies the system specification (if one exists)

and the software project plan. It is important to important to understand

software in a system context and to review the software scope that was

used to generate planning estimates. Next, communication for analysis

must be established so that problem recognition is ensured. The goal of

the analyst is recognition of the basic problem elements as perceived by

the user/customer.


16/33

Problem evaluation and solution synthesis is the next major area of

effort for analysis. The analyst must define all extremely observable data

objects, evaluate the flow and content of information; define and

elaborate all software function; understand software behavior in thecontext of events that effects the system; estimate system interface

Characteristics and uncover additional design constraints. Each of these

tasks serves to describe the problem so that an overall approach or

solution may be synthesized.

Upon evaluating current problems and desired information (input and

output), the analyst begins to synthesize one or more solutions. To

begins, the data, processing functions and behaviour of the system are

defined in detail. Once this information has been established, basic

architecture for implementation is considered. A client/server approach

would seem to be appropriate, but does it fall within the scope outlined

in the software plan?

10

A database management system (DBMS) would seem to be

required, but is the user/clients need for associatively justified? The

process of evaluation and synthesis continues until both analyst and

customer feels confident that software can be adequately specified for

subsequent development steps.

Throughout evaluation and solution synthesis, the analysts primary

focus is on what, not how. What data does the system produce and

consume what constraints apply? During the evaluation and solution


17/33

synthesis activity, the analyst creates models of the system man effort to

better understand the data and control flow, functional processing and

behavioral operation, and information content. The model serves as a

foundation, for software design and as the basis for the creation of aspecification for the software.

The analysis model must achieve three primary objectives:

1. To describe what the customer requires

2. To establish a basis for the creation of software design,3. To define a set of requirements that can be validated once the

software is built.

11

SOFTWARE DESIGN

A design is the first phase in the development phase for any system.

It may be defined as the process of applying various techniques and

principles for the purpose of defining a device a process or a system in

sufficient detail to permit physical realization. The designers goal is to

produce a model or representation of an entity that will later be built.

The process by which the model is developed combines intuition and


18/33

judgment based on experience in building similar entities, a set of

principles and/or heuristic that guides the way in which the model

evolves, a set of Criteria that enables quality to be judged, and a process

of iteration that ultimately leads to a final design representation.Actually software design sites at the technical kernel of the software

engineering process and is applied regardless of the software process

model that is used. Beginning once software requirements have been

analyzed and specified, software design is the first of three technical

activity designs, code generation and testing which are required to build

and verify the software.

Each activity transforms information in a manner that ultimately results

in validated computer software. Each of the elements of the analysis

model provides information that is required to create a design model.

Software requirements manifested by the data, functional and

behavioural model feed the design steps.

12

Using one of a number of design methods, the design step produces

a data design an architectural design an interface design, and a

procedural design. This data design transforms the information domain

model created during analysis into the data structures that will be

required to implement the software. The data objects and the

relationships defined in the entity-relationship diagram and the detailed

design depicted in the data dictionary provides the basis for the data

design activity.


19/33

The architectural design defines the relationship among those major

structural elements of the program. This design representation- the

modular framework of a computer program- can be derived from the

analysis model(s) and the interaction of sub-system defined within theanalysis model.

The interface design describes how the software communication within

itself, to systems that inter-operate with it, and with humans who use it.

An interface implies a flow of information (e.g. data and /or

control).Therefore, the data and flow diagrams provide the information

required for the interface design.

The procedural design transforms structural elements of the program

architecture into a procedural description of software components.

Information obtained from the PSPEC, CSPEC, and STD serves as the

basis for procedural design.

13

During design, we make decisions that will ultimately affect the

success of software construction, and as important, the ease with which

software can be maintained.Actually, the importance of software can be

stated in a single word-quality. Design is the place where quality is

fostered in software development. Design provides us with

representations of software that can be assessed for quality. Design is the

only way we can accurately translates a customers requirements into a

finished software product or system. Software design serves as the

foundation of all the software engineering and software maintenance


20/33

steps that follow. Without design, we risk building an unstable system-

one that will fail when small changes are made; one that may be difficult

to test; one whose utility can not be ccessed until the late in the software

engineering process, when time is short and many dollars have alreadybeen spent.

14

STRUCTURE OF THE PROJECT

Environment hardware and software

requirement

Following are the minimum specifications for the machine on

which our project will run successfully.


21/33

Hardware requirement

Pentium IV 2.6 GHz and above

512 MB ram or more

80 GB Hard disk or more

Power backup and internet connections.

15

Software requirement

Windows XP SP2

HTML

Adobe Dreamweaver

Adobe Photoshop

Ms World


22/33

Technologies

HTML

16

FEASIBILITY STUDY

Depending upon the results of the initial investigation, the survey is

expanded to a more detailed feasibility study. A feasibility study is a set

of a system proposal according to its workability, impact on the

organization, ability to meet users needs and effective use of recourses.

Feasibility is the determination of weather or not a project is worth

doing. A feasibility study is an analysis of a problem to determine if it

can be solved effectively in the given budgetary, operational technical

and schedule constraints in place. The results of the feasibility study


23/33

determine which if any of the number of feasible solkutions to be

developed in the design phase. The aim of the feasibility study is to

determine the best solution under the feasibility analysis by identifying

the effects of he solution on the organization. The contents andrecommendations of such a study will used as a sound basis for deciding

weather to proceed, postpone or cancel the project. It includes three

main questions:

What are the users need and how does te candidate system meet

them?

What recourses are available for a given candidate system.

What are the likely impacts of the candidate system on the

organization?

17

DEVELOPMENT SCHEDULE

The following steps were followed in developing the website

study, analysis and requirement specification: the study of the

existing systems gave an idea about what kind of interface was

required the study was conducted through information gathering

and studying the existing system.

Design of the proposed system and :the next step was to design

the screen windows and reports for the inputs and the outputs. In


24/33

this phase the project was broken down into various modules. This

website was designed keeping in view a large user acceptance.

Coding of the design system: a modular approach was followed,

where, in each module, a well defined procedure was developed

independently. These modules were developed to use the same

database file structure to ensure integrity.

18

MARKUP LANGUAGE AND

TOOLS

HTML

HTML, which stands for HyperText Markup Language, is the

predominant markup language for web pages. It provides a means to

create structured documents by denoting structural semantics for text

such as headings, paragraphs, lists, links, quotes, and other items. It


25/33

allows images and objects to be embedded and can be used to create

interactive forms. It is written in the form of HTML elements consisting

of "tags" surrounded by angle brackets within the web page content. It

can load scripts in languages such as JavaScript which affect thebehavior of HTML webpages. HTML can also be used to include

Cascading Style Sheets (CSS) to define the appearance and layout of

text and other material. The W3C, maintainer of both HTML and CSS

standards, encourages the use of CSS over explicit presentational

markup.

19

SYSTEM REQUIREMENT

SPECIFICATION

1. ENVIRONMENTAL CHARACTERISTICS:

HARDWARE: our project will be system friendly. It requires a

common pc configuration and does not put forth any constraint and

prerequisite.


26/33

PEOPLE: Our project is made in such a manner that it does not require

user to be such a professional. also, we the developers, are a group of

three, each of us possessing varied knowledge, fully satisfying every

requisite for a team.

Browser :our project can run on any browser.

Our aim throughout the making of project will be to provide a user

friendly interface.

2. FUNCTIONAL REQUIREMENTS:

The project includes various things to be done, so we have divided it

into various functions each performing a specific function.

20

3. NON FUNCTIONAL DESCRIPTION:

MAINTAINIBILITY: System is easy to be maintained. Actually it does not require

lot of maintenance.

PORTABILITY: It can easily be run from a portable machine like laptop.

BEHAVIOURAL DESCRIPTIONS

The behavior of the system depends on the easy user interface of our website


27/33

21

OUTPUTS


28/33

22

HOME


29/33

23

BIOGRAPHY


30/33

24

WEB DESIGNING


31/33

25

DOWNLOAD


32/33

26

CONTACT US


33/33

27