Abstract

The problem of updating shortest paths in networks whose topology

dynamically changes over time is a core functionality of many nowadays networked systems. In
fact, the problem finds application in many real-world scenarios such as Internet routing and
route planning in road networks. In these scenarios, shortest-path data are stored in different
ways and have to be updated whenever the underlying graph, representing the network,
undergoes dynamic updates. where new dynamic shortest-path algorithms for various real-
world applications are proposed, engineered, analyzed and compared to the literature, both
theoretically and experimentally.

This thesis investigates the problem of efficiently computing exact and approximate shortest
paths in graphs, with the main focus being on shortest path query processing. Strategies for
computing answers to shortest path queries may involve the use of pre-computed data
structures (often called distance oracles) in order to improve the query time.

Page 1 of 18
 CHAPTER-1
Introduction

Page 2 of 18
1.1 Object (NAME/VARIABLE/EXPECTED OUTPUT)

1.2 Software Development Life Cycle:-

SDLC is a process followed for a software project, within a software organization. It consists
of a detailed plan describing how to develop, maintain, replace and alter or enhance specific
software. The life cycle defines a methodology for improving the quality of software and the
overall development process.

Figure :-1.3.1 software development life cycle

Page 3 of 18
A typical Software Development life cycle consists of the following stages:

1.3 Planning and Requirement Analysis:

Requirement analysis is the most important and fundamental stage in SDLC. It is performed by the
senior members of the team with inputs from the customer, the sales department, market surveys and
domain experts in the industry. This information is then used to plan the basic project approach and to
conduct product feasibility study in the economical, operational, and technical areas. Planning for the
quality assurance requirements and identification of the risks associated with the project is also done in
the planning stage. The outcome of the technical feasibility study is to define the various technical
approaches that can be followed to implement the project successfully with minimum risks.

Requirements: -
Once the requirement analysis is done the next step is to clearly define and document the
product requirements and get them approved from the customer or the market analysts. This is
done through ‘SRS’ – Software Requirement Specification document which consists of all the
product requirements to be designed and developed during the project life cycle.

Designing the product architecture:-

SRS is the reference for product architects to come out with the best architecture for the
product to be developed. Based on the requirements specified in SRS, usually more than one
design approach for the product architecture is proposed and documented in a DDS - Design
Document Specification. This DDS is reviewed by all the important stakeholders and based on
various parameters as risk assessment, product robustness, design modularity , budget and
time constraints , the best design approach is selected for the product.
A design approach clearly defines all the architectural modules of the product along with
its communication and data flow representation with the external and third party modules .
Building or Developing the Product:
Page 4 of 18
 In this stage of SDLC the actual development for coding. The programming language is
chosen with respect to the type of software being developed.

1.4 HARDWARE AND SOFTWARE REQUIREMENT

To be used efficiently, all computer software needs certain hardware components or
other software resources to be present on a computer. These prerequisites are known as
(computer) system requirements and are often used as a guideline as opposed to an absolute
rule. Most software defines two sets of system requirements: minimum and recommended. With
increasing demand for higher processing power and resources in newer versions of software,
system requirements tend to increase over time. Industry analysts suggest that this trend plays
a bigger part in driving upgrades to existing computer systems than technological
advancements. A second meaning of the term of System requirements is a generalization of
this first definition, giving the requirements to be met in the design of a system or sub-system.
Typically an organization starts with a set of Business requirements and then derives the
System requirements from there.

HARDWARE REQUIREMENT:-

Processor : Intel core i3

RAM : 1GB & above
Hard disk : 5GB
Printer : HP DeskJet
Keyboard : multimedia
Mouse : 3 Button scroll

SOFTWARE REQUIREMENT:-

Page 5 of 18
 Operating system: window 7
Technology : Networking

CHAPTER-2
Analysis

Page 6 of 18
FRONT END TECHNOLOGY

Page 7 of 18
 CHAPTER-3
DESIGN

Page 8 of 18
 3.1 Flow chart Or DFD

3.2 ER Diagram

3.3 UML

3.4 Functional Diagram

Page 9 of 18
 CHAPTER-4
TESTING

Page 10 of 18
4.1 Test Strategies

 The objective is to design tests that systematically uncover different classes of errors
and do so with minimal amount of time and effort.
 It is a process of executing a program with the intent of finding an error.
 A good testing case is one that has a high probability of finding a uncovered errors.
 All testing should be traceable to customer requirement.
 Test should be planned long before testing begins.
 Testing should begins in the small and progress towards testing in the large.

4.2 White box testing:

This testing is based on knowledge of the internal logic of an application code. Also
known as glass box testing. Internal software and coding works should be known for this type of
testing. Tests are based on coverage of code statements, branches, paths, condition.

4.2.1 Unit testing:

Testing of individual software components or modules. Typically done by the

programmer and not by testers, as it requires detailed knowledge of the internal program
design and code may require developing test deriver modules.

4.2.2 Integration testing:

modules, individual application etc. This type of testing is especially relevant to the
distributed Testing of integrated modules to verify combined functionality after integration.
Modules are typically code system.

Page 11 of 18
 4.3 Black box testing:

Black box testing treats the software as black box without any knowledge of internal
system design is not considered in this type of testing. Tests are based on requirements and
functionality. Black box tester has no bonds with the code and a tester perception is very
simple, a code must have bugs. Therefore, black box testing has the advantage of an

unaffiliated opinion on the other hand, disadvantage of blind exploring

Page 12 of 18
 CHAPTER 5
EXPECTED OUTPUT WITH
SCREEN SHOTS

Page 13 of 18
Page 14 of 18
 CHAPTER 6
CONCLUSION AND
FUTURE SCOPE

Page 15 of 18
CONCLUSION AND SCOPE

CONCLUSION:-
For an increase in the Transmission Rate, AEMAC scheme could receive a much higher
Bandwidth compared to the SMAC scheme. In wireless sensor networks, increase in the
Transmission Rate can be opted for increasing the Bandwidth in the network .
On an increase in the Transmission Rate, Fairness increases considerably for the AEMAC
scheme compared to the SMAC scheme. So to achieve better Fairness in a wireless sensor
network, the increase in Transmission Rate can be selected as an optimum method.
The Bandwidth decreases in a wireless sensor network having a higher Error Rate. But the
decrease is lesser in a network which adopts channel adaptive schemes thus proving the better
performance of the AEMAC scheme compared to the SMAC scheme.

FUTURE SCOPE:-
This work had implemented an Energy efficient Channel Adaptive MAC protocol in a
wireless sensor network with static nodes. This scheme had provided improvement gains in
Energy efficiency, Throughput, Delay, Bandwidth and Delivery Ratio. But the superior nature of
this scheme depends on many environmental factors such as operation scenarios, specific data
types etc. Thus more research work needs to be done in future to find the respective application
scenarios for this scheme with all the related factors taken into consideration.

Page 16 of 18
 REFERENCES

Page 17 of 18
REFERENCE
 B.A . Frozen, Data Communications and Networking, Fourth Edition McGraw Hill, 2007.
 N. Selvanathan and W. J. Tee, "A Genetic Algorithm Solve The Shortest Path Problem
OSPF and MPLS", Malaysian Journal of Computer Science, pp. , 2003.

(NOTE:- You have to mention at least 7 book references /

journals/ web sites mentioned in the above format.)

Page 18 of 18