NETWORK ROUTING SIMULATOR

Title of the Project: NETWORK ROUTING SIMULATOR SDLC Methodologies: Waterfall/Spiral Model
Course: Roll No: Name of the Student: Technology And Language: Internal Guide: E-Mail ID: Mobile No (Student):

JAVA

Abstract of the Project: Introduction:

A simple definition of Network Routing Simulator is "learning how to get from here to there." In some cases, the term Network Routing Simulator is used in a very strict sense to refer only to the process of obtaining and distributing information, but not to the process of using that information to actually get from one place to. Since it is difficult to grasp the use fulness of information that is acquired but never used, we employ the term Network Routing Simulator to refer in general to all the things that are done to discover and advertise paths from here to there and to actually move packets from here to there when necessary. The distinction between Network Routing Simulator and forwarding is preserved in the formal discussion of the functions performed by OSI end systems and intermediate systems, in which context the distinction is meaningful. Network Routing Simulator is the act of moving information across an inter network from a source to a destination. Along the way, at least one intermediate node

typically is encountered. Network Routing Simulator is the process of finding a path from a source to every destination in the network. It allows users in the remote part of the world to get to information and services provided by computers anywhere in the world. Network Routing Simulator is accomplished by means of Network Routing Simulator protocols that establish mutually consistent Network Routing Simulator tables in every router in the Network. When a packet is received by the router or is forwarded by the host, they both must make decisions as to how to send the packet. To do this, the router and the host consult

a database for information known as the Network Routing Simulator table. This database is stored in RAM so that the lookup process is optimized. As the packet is forwarded through various routers towards its destination, each router makes a decision so as to proceed by consulting its Network Routing Simulator table.

Network Routing Simulator Algorithms

Flooding Hot-Potato Source Network Routing Simulator Distance Vector (Bellman-Ford) RIP (Network Routing Simulator Information Protocol) Link state

Environment:

Clients: CONSOLE

Operating System : - Microsoft Windows XP/2000 or Higher

Development Tools: Netbeans 6.8 Documentation Tools: : MS Office 2003/2007 Drawing Tools: IBM Rational Rose Enterprise, MS Office Visio 2007 User Interface: AWT & SWINGS Code Behind: AWT & SWINGS

Requirements:

Hardware Requirements:
Number 1 Description PC With Minimum 20 GB Hard-Disk And 1GB RAM

Software Requirements:
Number Description

1 2. 3.

Windows XP/2000 Or Higher With MS-Office 2003/2007 AWT & SWINGS CONSOLE

Milestones:
No. 1 Milestone Name Requirements Specification Milestone Description Complete specification of the system including defining hierarchies constitutes this milestone. A document detailing the same should be written and a presentation on that be made. Understanding of the technology needed to implement the project. Listing down all possible scenarios and then coming up with flow-charts or pseudo code to handle the scenario. Implementation of the main screen giving the login, screen that follows the login giving various options, screens for each of the options The front-end developed in the earlier milestone will now be able to update the database. Other features should be functional at this stage. In short, the system should be ready for integration testing. The system should be thoroughly tested by running all the test cases written for the system (from milestone 5). Issues found during the previous milestone are fixed and the system is ready for the final review. Remarks Attempt should be made to add some more relevant functionality other than those that are listed in this document. The presentation should be from the point of view of being able to apply it to the project, rather than from a theoretical perspective. The scenarios should map to the requirement specification During this milestone period, it would be a good idea for the team to start working on a test-plan for the entire system. This test-plan can be updated as and when new scenarios come to mind.

Technology Familiarization High-level Detailed Design and

Development of Front End Functionalities.

Integrating the Front-end with the Database

Integration Testing Final Review

Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged. During the final review of the project, it should be checked that all the requirements specified during milestone number 1 are fulfilled

The following steps will be helpful to start of the project:

Study and be comfortable with: JAVA. Gather some knowledge of product hierarchies and maintenance before starting the design. Start with creating the login screen. Create menus for navigation and group the functionalities as sub menus. Create the help-pages of the application in the form of FAQ. This will helps user.