A

PROJECT REPORT ON

“Kangra Valley”

Submitted in partial fulfillment of requirement for the award of the degree

Bachelor OF COMPUTER APPLICATIONS

OF

Himachal Pradesh University

By

Akshay kumar Roll No. 10219

Meher Chand Mahajan Dayanand Anglo Vaidic college Kangra

(2013-2014)
 A

PROJECT REPORT ON

“Kangra Valley”

Submitted In Partial Fulfillment of Requirement for the Award of the Degree

Bachelor OF COMPUTER APPLICATIONS

OF
Himachal Pradesh University

By

Sakshi Choudhary Roll No. 10219

UNDER THE GUIDANCE OF

Mr. Atul Choudhary

Project Co-Coordinator

Himachal Pradesh University

(2011-2014)
 Acknowledgement

“The successful completion of any task would be incomplete without accomplishing the people who made it all
possible and whose constant guidance and encouragement secured us the success.”
I am grateful to Mr. Atul Choudhary, Project Leader for his astute guidance, constant encouragement and sincere support for
this project work.

Akshay kumar
B.C.A(Bachelor Of Computer Applications)
Table of Contents
 Introduction
o About the Organization
o About the project
 System Analysis
o System Analysis Introduction
o Software Requirement Specification
o Feasibility Study
o Choice of Platform
 System Design
o What is System Design?
o Panels In project
o Architectural Diagram
o Three Layers of Project
 Database layer
 Business Logic layer
 Presentation layer
 System Implementation
o Implementation
o Implementation Tools
o Testing
o Maintenance
 Conclusion and Future Scope
o Conclusion
 Bibliography
o Books
o URLs
 INTRODUCTION OF PROJECT

Project Title: Kangra Valley

Project Incharge: Mr. Atul Choudhary
Project category: Web Application

This project is developed in HTML. This project has been developed in partial fulfillment of Requirements for the degree of
BCA (2011-2014) Himachal Pradesh University.
Kangra Valley is a web-based application Developed.

OBJECTIVES OF PROJECT
One of the biggest problems when building a web site is how to work out
and communicate what your site is going to do and who is the site for:
This site contains information about kangra valley. And it’s historical places.
This site gives the overview of all the places of kangra valley.

METHODOLOGY

Software development refers to a group of software development methodologies based on iterative development, where
requirements and solutions evolve through collaboration between self-organizing cross-functional teams. Software application
breaks tasks into small increments with minimal planning, and do not directly involve long-term planning. Iterations are short
time frames that typically last from one to four weeks.
Technologies to be used
 OS required Microsoft Windows XP / higher version of Windows OS required.
 Browser requirement is Google chrome Version 34.0.1847.131 m only.

SYSTEM ANALYIS

System Analysis Introduction

System analysis is the process of studying the business processors and procedures, generally referred to as business
systems, to see how they can operate and whether improvement is needed. This may involve examining data movement and
storage, machines and technology used in the system, programs that control the machines, people providing inputs, doing the
processing and receiving the outputs.

Investigation Phase
The investigation phase is also known as the fact-finding stage or the analysis of the current system. This is a detailed study
conducted with the purpose of wanting to fully understand the existing system and to identify the basic information
requirements. Various techniques may be used in fact-finding and all fact obtained must be recorded. A thorough investigation
was done in every effected aspect when determining whether the purposed system is feasible enough to be implemented.

Investigation

As it was essential for us to find out more about the present system, we used the following methods to gather the information: -

 Observation: - Necessary to see the way the system works first hand.

 Document sampling: - These are all the documents that are used in the system. They are necessary to check all
the data that enters and leaves the system.

 Questionnaires: - These were conducted to get views of the other employees who are currently employed in the
system.

Strengths of the System

 No complex equipment: - The equipment that is used is very simple and no special skills have to be mastered to be
able to operate the system. Therefore no training is required for the employees.
 Low cost: - There is little money spent in maintaining the present system other than buying the necessary office
equipment and the ledgers.

Feasibility Study

 System feasibility

Prior to stating whether the system we have to develop is feasible or not we believe that we should emphasize on what is
implied by the word “Feasibility”. Feasibility is the measure of how beneficial or practical the development of the system will be
to the organization. It is a preliminary survey for the systems investigation. It aims to provide information to facilitate a later in-
depth investigation.

Types

There are various measures of feasibility that helps to decide whether a particular project is feasible

or not. These measures include –

 Operational Feasibility
 Technical Feasibility
 Economical Feasibility

Each of these types will be explained in detail throughout the project report
  Operational Feasibility

A proposed system is beneficial only if it can be turned into an information system that will meet the operational requirements
of an organization. A system often fails if it does not fit within existing operations and if users resist the change.

Important issues a systems developer must look into are:

Will the new system be used if implemented in an organization?

Are there any major barriers to implementation or is proposed system accepted without destructive resistance?

The whole purpose of computerizing the Complaint Management is to handle the work much more accurately and efficiently
with less time consumption. There will be additional work to be completed, because now the cellular company will have to
maintain database of both their employees as well as their Customers.

Compared to the semi-computerized system the chances of avoiding errors in a computerized system is much higher because
the user need not stress himself unnecessarily resulting in recklessness. Unlike the semi-computerized system there would be
backup data for all the information concerning the daily transactions occurred within the organization.

Whether the new system affects the current users in the system?
The new proposed system will affect the users in the following areas

Accuracy

Efficiency

Productivity

Robustness

Lesser time consuming

 Technical Feasibility

Based on the outline design of the system requirements in terms f inputs, output, Procedures, the technical issues raised
during technical feasibility include:

Does the necessary technology exist to do what is proposed?

Does the proposed equipment have the technical capacity to hold the data required to use in the new system?
Adequate responses provided by the proposed system?
Is the system flexible enough to facilitate expansion?
Is there any technical guarantee of accuracy, reliability, ease of access and data security?

The system developer’s task is to view needed capabilities in light of currently available technology. Our site works hand in
hand with high technology. A database has to be maintained in order to update and backup data whenever required. To create
databases we use SQL server. After taking the above facts into consideration we can state that the new proposed system is
technically feasible.

 Economical Feasibility

In making recommendations a study of the economics of the proposed system should be made. Even though finding out the
costs of the proposed project is difficult we assume and estimate the costs and benefits as follows. According to the
computerized system we propose, the costs can be broken down in two categories.

 Costs associated with the development of the system.

 Costs associated with operating the system.

System Security

System security is a vital aspect when it comes to developing a system. The system should ensure the facility Of preventing
unauthorized personnel from accessing the information and the data within the system. The system should provide total
protection for each user’s information so that the integrity of data is sustained and also prevent hackers from hacking the
system.

The proposed system ensures the security and the integrity of data. This is done by providing a password login system for
each authorized users. And for example the System Administrator has access to all kinds of information.

By providing this facility information is properly managed and information is protected. For example the system administrator’s
day to day tasks are lessened and easier because he doesn’t have to have a constant eye on the system and worry about
hackers hacking the system.

SYSTEM DESIGN

In order to design a web site, the relational database must be designed first. Conceptual design can be divided into
two parts:
 Data model
 Process model.

 Data model
The data model focuses on what data should be stored in the database while the process model deals with how the
data is processed. To put this in the context of the relational database, the data model is used to design the relational tables.

 Process model
 The process model is used to design the queries that will access and perform operations on those Tables.

Design of software involves conceiving, planning out and specifying the externally observable characteristics of the
software product. We have data design, architectural design and user interface design in the design process. These are
explained in the following section. The goal of design process is to provide a blue print for implementation, testing and
maintenance activities.

 DATA DESIGN:
The primary activity during data design is to select logical representations of data objects identified during
requirement analysis and software analysis. A data dictionary explicitly represents the relationships among data objects and
the constrains on the elements of the data structure. A data dictionary should be established and used to define both data and
program design.

 FESIBILITY STUDY:
Feasibility study is conducted once the problem is clearly understood. Feasibility study is a high level capsule version
of the entire system analysis and design process. The objective is to determine quickly at a minimum expense how to solve a
problem. The purpose of feasibility is not to solve the problem but to

Determine if the problem is worth solving. The system has been tested for feasibility in the following points
 Technical Feasibility
 Economical Feasibility
 Operational Feasibility.

 Technical Feasibility: -
The project entitles "Project Monitoring System" is technically feasibility because of the below mentioned feature. The
project was developed in Java which Graphical User Interface It provides the high level of reliability, availability and
compatibility. All these make Java an appropriate language for this project. Thus the existing software Java is a powerful
language.

 Economical Feasibility: -
The computerized system will help in automate the selection leading the profits and details of the organization. With
this software, the machine and manpower utilization are expected to go up by 80-90% approximately. The costs incurred of
not creating the system are set to be great, because precious time can be wanted by manually.

 Operational Feasibility:
In this project, the management will know the details of each project where he may be presented and the data will be
maintained as decentralized and if any inquires for that particular contract can be known as per their requirements and
necessaries.
  IMPLEMENTATION:
Implementation is the stage where the theoretical design is turned into a working system. The most crucial stage in
achieving a new successful system and in giving confidence on the new system for the users that it will work efficiently and
effectively. The system can be implemented only after thorough testing is done and if it is found to work according to the
specification. It involves careful planning, investigation of the current system and its constraints on implementation, design of
methods to achieve the change over and an evaluation of change over methods a part from planning. Two major tasks of
preparing the implementation are education and training of the users and testing of the system. The more complex the system
being implemented, the more involved will be the systems analysis and design effort required just for implementation. The
implementation phase comprises of several activities. The required hardware and software acquisition is carried out. The
system may require some software to be developed.

IMPLEMENTATION METHODOLOGY

 DATA FLOW DIAGRAM

Data Flow Diagrams show the flow of data from external entities into the system, and from one process to another
within the system. There are four symbols for drawing a DFD:
 Rectangles representing external entities, which are sources or destinations of data.
 Ellipses representing processes, which take data as input, validate and process it and output it.
 Arrows representing the data flows, which can either, be electronic data or physical items.
 Open-ended rectangles or a Disk symbol representing data stores, including electronic stores such as databases or
XML files and physical stores such as filing cabinets or stacks of paper.

The Data Flow Diagrams for the current system are explained below. Each process within the system is first shown
as a Context Level DFD and later as a Detailed DFD. The Context Level DFD provides a conceptual view of the process and
its surrounding input, output and data stores. The Detailed DFD provides a more detailed and comprehensive View of the
interaction among the sub-processes within the system.
Data Flow Diagram

In our DFD, we give names to data flows, processes, and data stores. Although the names are descriptive of the
data, they do not give details. So the following the DFD, our interest is to build some structured place to keep details
of the contents of data flow, processes, and data store. A data dictionary is a structured repository of data about data.
It is a set of rigorous definition of all DFD data element and data structure

DFD Symbols
In the DFD, there are four symbols,
 A Square defines a source (originator) or destination of system data.
 An Arrow identifies data flow- data in motion .It is pipeline through which information flows.
 A circle or a bubble (or a oval bubble) represents a process that transforms incoming data flow(s) into outgoing data
flow(s)
 An Open rectangle is a data store-data at rest, or temporary repository of data.
The DFD was first developed by “Larry Constatine” as a way of expressing system requirements in a graphical form. A DFD,
also referred to as a bubble chart has a purpose of clarifying system requirements and identifying major transformations that
will become the program in this system design.

A square defines a source of destination or system data.

 An arrow line identifies the data flow or data in motion. It is a pipeline through which
Information flows.

 A circle or bubble represents a process transform incoming data flow in to outgoing data flow.
  A horizontal line represents data stored or data at rest or a temporary rest repository of
Data.

 An open rectangle refers to the database storage

BUISNESS LOGIC LAYER:

This layer consist of DLL(dynamic link library) naming ClassLibraryHangout having namespace hangout and one class naming
clscon for connection with sqlserver database and 18 interfaces naming int-tablename having property declaration for each
field in the respective table, class naming 18 property class naming cls-tablename-prp which inherit its respective interface for
definition of each property declared in the interface, class naming 18 methods class naming cls-tablename which inherit class
clscon for definition of methods like : save_rec(), update_rec(), delete_rec(), display_rec(), find_rec() etc. Methods.

Dynamic Link Library:

Compiled class

 Reusable Scope:

 Multiple application

 No Graphical user interface

 In process component

 Self described

It contains following:

 Interfaces

 Main Classes
PRESENTATION LAYER:
Presentation layer consists of web pages which include:

MAIN PAGE:

 Master Page is Common Template that can be implemented on more than one Page. We can make changes whenever
needed.
 Master page extension is. Master
 It can never be start up page.
 We can create properties, methods, classes in master pages.
 Multiple master pages can be there in single application.

CONTENT PAGES:

 Content pages are web pages which can be made as startup page.
 Content page extension is .html
 Multiple content pages can be there in single master page

SYSTEM IMPLEMENTATION

Implementation

Implementation is the stage in the project where the theoretical design is turned into the working system and is giving
confidence to the new system for the users i.e. will work efficiently and effectively. It involves careful planning, investigation of
the current system and its constraints on implementation, design of method to achieve the change over, an evaluation, of
change over methods. A part from planning major task of preparing the implementation is education of users. The more
complex system is implemented, the more involved will be the system analysis and design effort required just for
implementation. An implementation coordinating committee based on policies of individual organization has been appointed.
The implementation process begins with preparing a plan for the implementation for the system. According to this plan, the
activities are to be carried out, discussions may regarding the equipment has to be acquired to implement the new system

Implementation is the final and important phase. The most critical stage is in achieving a successful new system and in giving
the users confidence that the new system will work and be effective. The system can be implemented only after thorough
testing is done and if it found to working according to the specification. This method also offers the greatest security since the
old system can take over if the errors are found or inability to handle certain types of transaction while using the new system.

The major elements of implementation plan are test plan, training plan, equipment installation plan, and a conversion plan.
There are three types of implementation:

 Implementation of a computer system to replace a manual system.

 Implementation of a new computer system to replace an existing system.

 Implementation of a modified application to replace an existing one, using the same computer.

Successful implementation may not guarantee improvement in the organization using the new system, but improper
installation will prevent it. It has been observed that even the best system cannot show good result if the analysts
managing the implementation do not attend to every important detail. This is an area where the systems analysts
need to work with utmost care.

Implementation Tools:

 Training personnel

 Conversion Procedures

 Post-implementation review

Training of Personnel involved with system

Even well designed system can succeed or fail because of the way they are operated and used. Therefore, the
quality of training received by the personal involved with the system in various capacities helps or hinders and may
even prevent the successful implementation of management information system.

System Operators Training

Running of the system successfully depend on the personnel working in the Computer Centre. They are Responsible
for providing the necessary support. Their training must ensure that they are able to handle all possible operations,
both routine and extra-ordinary in nature.

If the system calls for the installation of new equipment, such as new computer system, special terminals or different
data entry machines, the operators training should include such fundamentals as how to turn the equipment on and
use it, how to power off and a knowledge of what constitutes normal operations. The operators should also be trained
on different type of malfunctioning, how to recognize them and what steps should also be taken whenever they arise.

User Training

User may be trained on use equipment, particularly in the case where, e.g. a micro computer is in use and individual
involved is both operator and user. In such cases, user must be given training on how to operate and user. In such
cases, user must be given training on how to operator the system also. Questions that may be trivial to the analyst,
such as how to turn on a terminal, how to insert a diskette into a micro-computer or when it is safe to turn off
equipment with out danger of data loss are significant problems to new users who are not familiar.

Inmost of the cases user training deals with the operation of the system itself, with proper attention given to data
handling techniques. It is imperative that users be properly trained in methods of entering transaction, editing data,
formulating inquiries, deleting and inserting of records. No training is complete without familiarizing users with simple
systems maintenance activities. Weakness in any aspect of training may lead of awkward situation that creates user
frustration and error.

Conversion Methods

A conversion is the process of changing from the old system to the new one. It must be properly planned and
executed. Four methods are common in use. They are Parallel Systems, Direct Conversion, Pilot System and Phase
In method. Each method should be considered in the light of the opportunities that it offers and problems that it may
create. In general, system conversion should be accomplished in shortest possible time. Long conversion periods
create problems for all persons involved including both analysts and users.

Parallel Systems:

The most secure method of converting from an old to new system is to run both systems in parallel. This method is
safest one because it ensures that in case of any problem in using new system, the organization can still fall back to
the old system without the loss of time and money.

The Disadvantages Of Parallel Systems Approach Are:

 It doubles operating costs.

 The new system may not get fair trial.

Direct conversion:

This method converts from the old system to new system abruptly, sometimes over a weekend or even overnight.
The old system is used until a planned conversion day, when it is replaced by the new system.

Pilot System:

Pilot approach is often preferred in the case of the new system which involves new techniques or some drastic
changes in organization performance. In this method, a working version of the system is implemented in one part of
the organization, such as a single work area or department.

Phase –IN- Method:

This method is used when it is not possible to install a new system throughout an organization all at once. The
conversion of files, training of personnel or arrival of equipment may force the staging of the implementation over a
period of time, ranging from weeks to months.
Post Implementation Review

After the system is implemented and conversion is complete, a review should be conducted to determine whether the
system is meeting expectations and where improvements are needed. A post implementation review measures the
systems performance against predefined requirement. It determines how well the system continues to meet the
performance specifications.

Testing Phase

The basic goal of the software development process is to produce software that has no errors or very few errors. In an effort to
detect errors soon after they are introduced, each phase ends with verification activity such as a review.

As testing is the last phase before the final software is delivered, it has the enormous responsibility of detecting any type of
error that may in the software. Software typically undergoes changes even after it has been delivered. And to validate that a
change has not affected some old functionality of software regression testing is performed

Levels of Testing:
The basic levels of testing are unit testing, integration testing and system and acceptance testing. These different levels of
testing attempt to detect different types of faults.

Client Needs Acceptance Testing

Requirements System Testing
Design Integration Testing
Code Unit Testing

Levels of testing

Code/Unit Testing:

Code testing and implementation is a critical process that can even consume more than sixty percent of the development time.

Testing:
The system development life cycle involves the phases of testing and debugging after the requirement analysis, designing and
coding. The project in question was tested, debugged and implemented successfully.
Two strategies of software testing adopted for the new system are as follows:

 Code testing
 Specification testing

Code testing:
Code testing was carried out to see the correctness of the logic involved and the correctness of the modules. Tests were
conducted based upon sample and live data as well. All the modules are checked separately for assuming correctness and
accuracy in all the calculations.

Specification testing:
It examines the specification stating about what program should do and how it performs under various conditions. This testing
strategy is better strategy since it focuses on the way the software is expected to work.

Unit Testing:
During the phase of unit testing different constituent modules were testing against the specifications produced during the
design for the modules. Unit testing is essentially for the verification of the code produced during the coding the phase, and
goal is to test the internal logic of the modules. The modules once tested were then considered for integration and use by
others.

 White Box Testing Done

During this phase of the testing phase SDLC, server developed was tested while considering a valid value corresponding to
each of variable defined and corresponding to each function defined. During this phase values corresponding to each variable
viz. URL filtering, word filtering and scheduling was done and desired results were obtained.

 Black Box Testing Done

This phase of testing deals with input/output testing. Black box testing was performed on the software developed;
corresponding to valid inputs provided desired outputs were obtained.

Integration Testing:
The next level testing that was performed is often referred to as integration testing. During this phase many unit tested
modules were combined into subsystems, which were then tested. The goal here was to see if modules can be integrated
properly. Here the emphasis was on testing interfaces between different constituent modules of system.

Functionality Testing:
Here the entire software system was tested. The reference document for this process is the requirements document, and the
goal was to see if software solution meets its requirements.
This level of testing is essentially a validation exercise, and in many situations it is the only validation activity.

Stress Testing:
Proxy server developed for the specified purpose was testing under heavy load, i.e. a large no. of clients were made to sit in
lab and were asked to send requests for logging in and then were asked to request for text on internet. System responded to
request as desired.

Acceptance Testing:
Acceptance was performed in the real environment with realistic data of the client to demonstrate if the software developed is
working satisfactorily. Here the main focus was on the external behavior of the system; the internal logic of the program was
not emphasized.

Test Data and Test Cases:

The primary objective of test case design is to derive a set of tests that have the highest likelihood of uncovering errors in
software. The test case specification is the major activity in the testing process. Careful selection of test cases that satisfy the
criterion on approach specified is essential for proper testing. Various characteristics of test cases that are required for portal
are:
 A good test has a high probability of finding an error.
 A good test is not redundant.
 A good test should be “Best of Breed”.
 A good test should be neither too simple not too complex.

Test Data for This Application:

 Member Details like Name, Address, Ticket details etc.
 Project Details like Ticket Status, Country Dropdowns, States Dropdowns, telephone and unique E-Mail Ids etc.
 Content to be displayed on the site.

Test plan
Testing commences with a test plan and terminates with acceptance testing. A test plan is a general document for the entire
project that defines the scope, approach to be taken and schedule of testing as well as identifies the test item for the entire
testing process and the personnel responsible for the different activities of testing.

Overview of Testing
 Testing: Testing involves executing the program (or part of it) using sample data and inferring from the output whether
the software performs correctly or not. This can be done either during module development (unit testing) or when
several modules are combined (system testing).

 Defect Testing: Defect testing is testing for situation where the program does not meet its functional specification.
Performance testing tests a system's performance or reliability under realistic loads. This may go some way to ensuring
that the program meets its non-functional requirements.

 Debugging: Debugging is a cycle of detection, location, repair and test. Debugging is a hypothesis testing process. When
a bug is detected, the tester must form a hypothesis about the cause and location of the bug. Further examination of the
execution of the program (possible including many returns of it) will usually take place to confirm the hypothesis. If the
hypothesis is demonstrated to be incorrect, a new hypothesis must be formed. Debugging tools that show the state of the
 program are useful for this, but inserting print statements is often the only approach. Experienced debuggers use their
knowledge of common and/or obscure bugs to facilitate the hypothesis testing process. After fixing a bug, the system
must be reset to ensure that the fix has worked and that no other bugs have been introduced. This is called regression
testing. In principle, all tests should be performed again but this is often too expensive to do.

Test Planning
Testing needs to be planned, to be cost and time effective. Planning is setting out standards for tests. Test plans set out the
context in which individual engineers can place their own work. Typical test plan contains:
Overview of testing process
 Requirements trace ability (to ensure that all requirements are tested)
 List of item to be tested
 Schedule
 Recording procedures so that test results can be audited
 Hardware and software requirements
 Constraints

Overview of Testing Strategies

Large systems are usually tested using a mixture of strategies. Different strategies may be needed for different parts of the
system or stages of the process.

 Top-down testing: This approach tests high levels of system before detailed components. This is appropriate when
developing the system top-down and is likely to show up structural design errors early (and therefore cheaply). But this
often has advantage that a limited, working system is available early on. Validation (as distinct from verification) can
begin early. Its disadvantage is that stubs need to be generated (extra effort) and might be impracticable if component
is complex (e.g. converting an array into a linked list; unrealistic to generate random list; therefore end up implementing
unit anyway). Test output may be difficult to observe (needs creation of artificial environment). This is not appropriate
for OO systems (except within a class).

 Bottom-up testing: This is opposite of top-down testing. This tests low-level units then works up the hierarchy. Its
advantages and disadvantages mirror those of top-down testing. In this testing there is need to write test drivers for
each unit. These are as reusable as the unit itself. Combining top-down development with bottom-up testing means
that all parts of system must be implemented before testing can begin, which does not accord with incremental
approach discussed above. Bottom-up testing is less likely to reveal architectural faults early on. However, bottom-up
testing of critical low-level components is almost always necessary. Appropriate for OO systems.

 Stress testing: Tests system's ability to cope with a specified load (e.g. transactions per second). Tests should be
planned to increase load incrementally. This type of testing goes beyond design limit until system fails (this test is
particularly important for distributed systems like checking degradation of performance and network traffic increases).

 Back-to-back testing: Comparison of test results from different versions of the system (e.g. compare with prototype,
previous version or different configuration). Process – Run first system, saving test case results. Run second system,
again saving its results. Compare result files. The key point to be noted is that no difference does not mean no bugs.
 Both systems may have made the same mistake.

 Defect testing: A successful defect test is a test that causes the system to behave incorrectly. Defect testing is not
intended to show that a program meets its specification. If tests do not show up defects it may mean that the tests are
not exhaustive enough. Exhaustive testing is not always practically applicable. Subset has to be defined (this should
be part of the test plan, not left to the individual programmer).

Possible Methods:
 Usual method is to ensure that every line of code is executed at least once.
 Test capabilities rather than components (e.g. concentrate on tests for data loss over ones for screen layout).
 Test old in preference to new (users less affected by failure of new capabilities).
 Test typical cases rather than boundary ones (ensure normal operation works properly).

CONCLUSION AND FUTURE SCOPE

This chapter provides me an opportunity to do self-introspection of what value I have added to my knowledge and skill to
develop this project.

Domain Experience
M.C.M D.A.V College is working on various technologies. Also the individual responsibilities are more. So, I
have learnt a lot.

Exposure to entirely different technology

Working on HTML and CSS for the first time was a very enriching experience. I had never worked on this
platform earlier. So it added to my list of know how and the Programming languages known to me.
Screen Shots
CODING
BIBILOGRAPHY

 [Link]
 [Link]
 [Link]