Posts

Posted on

SMS Based Vehicle Location Finder for Parking ECE Seminar Topic

Introduction to SMS Based Vehicle Location Finder for Parking ECE Seminar Topic:

In present day life cars have become a common commodity to every family living in cities. With cars some problems such as security and parking is a common thing. Car parking has some glitches to it such as parking at right place and finding it back when we want to move out. In huge parking lots and multi storied parking lots there will be some confusion in finding the car because where we had parked the car and how to get it out. To solve this problem here is a simple system designed to give the direction where the car is. This system is based on microcontroller and GSM technology which is called as “SMS based vehicle location finder”.

We use a mobile phone to trigger a microcontroller which in turn controls an appliance such as a buzzer to ring an alarm and also the microcontroller acknowledges by sending an SMS that the buzzer is ringing or the lights of tail lam are flashing.

The main components in this system are AT command supporting GSM mobile phone, 89S52 Microcontroller, Max 232 IC, Relays, Relay driver IC ULN 2803, Voltage regulator 7805, Diode IN4007 and GSM Phone. The software used is Keil-U-Vision 3.0 in this software by using Keil tool set we can generate embedded applications virtually with supported microcontrollers. AT command is the communication protocol used between GSM phone and microcontroller.

The theory/principle used in this project can be used in different fields apart from just car parking application. We can use it to trigger a security alarm for vaults, to turn ON motors remotely using GSM handsets and many more.

Download SMS Based Vehicle Location Finder for Parking ECE Seminar Topic.

Posted on

MS Dissertation Ad Hoc Network Project

With the introduction of technology in communication, there are many considerable changes across the basic communication patterns and there are many trends evolved in this context. Transfer of simple data items was the basic aspect introduced across the communication and later there many trends and due to heavy requirements from the customer’s side, the transfer applications (Hermeking,2005). In general to transfer the video and voice across a network, there are many requirements which include bandwidth and data rate and to provide these requirements a network should be build in a sophisticated manner. Transferring the voice and video applications across the wired networks is far easy when compared to the scenario with wireless networks like ad hoc networks. Supporting the multimedia applications requires lot of network requirements and the corresponding networks should made ready to support these multimedia applications as well(Brambley,2007).

Maintaining quality of service is the primary concern to be considered to support the multimedia applications across the ad hoc networks and there is lot of research done in this context. In general there are different types of ad hoc network and the key among them are mobile ad hoc networks and these networks are infrastructure less networks and can be deployed easily using any existing infrastructure and the requirements of maintaining the quality of service is high when compared to the other networks (Plagemann, 2005). There are many applications that range in different aspects that are supported across the mobile ad hoc networks and these applications include battle field applications and military applications. With the increase in communication requirements from the end users side, support to these applications across the mobile ad hoc networks is also increased and thus to support these applications the quality of service requirements are also required on a top standard. In general the quality of service requirements can be defined in terms of level of support provided to the applications and the guarantee provided to the applications across the network and these QoS standards depends on the application being supported across the network(Chlamtac,2003).

Bandwidth and delay are the important aspects to be considered while dealing with the quality of service requirements for the applications and suppose if an of data has taken application is delay. 

sensitive the corresponding QoS should support the delay metrics and when the case with the multimedia applications is considered bandwidth and delay plays the major role. Reliability is another important factor to be considered across providing the QoS standards if the applications are in need of a reliable packet delivery from a desired source to the corresponding destination. In general these QoS requirements vary against the number of applications as well and if the applications are added on the top of the network, the requirements of QoS standards are also automatically increased in different forms and the main principle behind applying these QoS standards is to ensure a safe and reliable communication (Liu, 2005).

Thus with the increase in the wireless communication technologies the expectations on the data transfer are also increased and in this context, the customers need more QoS standards to usage the sophisticated applications which include multimedia, video conferencing and gaming applications and all these applications are need of a high standard QoS requirements. As the ad hoc networks are dynamic in nature, maintain the QoS standards at the required levels is a tedious task and that too within the context and video and voice applications as they need high bandwidth and delay sensitive applications(Grami,2009). In general the quality of service requirements also depends on the type of traffic being generated across the network which will vary in the range of TCP, CBR and VBR traffic and by considering all these aspects, providing the required QoS standards is really a tedious job and the actual aims and objectives identified for this project are as given below

Posted on

Introduction to Methodology of Research

Introduction to Methodology of Research:

Methodology is a systematic Process which Deals with finding solutions to the problems that are faced in a particular research process. To achieve maximum accuracy level for a particular process or procedure the schedule of rules and set of principles are to be followed which will tend to be more beneficial to increase the productivity of that process.

 Types of Research Methodologies

The research methodology can be categorised into two sub types on the basis of data generated from the type of method used for carrying out the research.

  1. Quantitative research methodology
  2. Qualitative research methodology

 Quantitative research methodology

Quantitative research methodology is research methodology which contains descriptive and analytical studies about the article and case studies which are under research objective. The Data Obtained for empirical analysis is generated from various digital sources viz. Internet which provides a connecting link with the research topic.

 Primary Data     

  • Articles
  • Case Studies
  • Reviews
  • Internet documents
  • Journals
  • Magazines
  • Research documents
  • surveys

Source of Primary Data

After forming an outline to the required research topic the primary data is collected from different sources to carry out the analysis. Necessary information required for the research is obtained from the raw data gained. The available primary data can be optimally used by the researcher for final decision making (Sasha Hurrell, 2004).

 Ethical Issues

Set of ethical values and principles are to be followed by the researcher while collecting data from primary sources for the research purpose. Ethical behaviour of the researcher will give honest and valued based performance.

Posted on

Introduction to Software Development Lifecycle Models

Introduction to Software Development Lifecycle Models:

Cloete (2011) explains that software development cycle phases are best described using software life cycle models. The description priority of these phases is similar to their execution priorities. Many companies use self made life cycle model but all of them follow similar phases. Described here are general and most common life cycle models. First is deliverables which are always required to produce next phase and are manufactured in earlier stages. Then first comes requirement phase, they are kept first in order to convert them in design accordingly in the design phase. After the design phase comes the implementation phase and in implementation phase implementation code is produced in order for coding phase. At last in testing modes, coding implementation deliverables are verified.

Out of much software development life cycle models below are some of the most popular models described:

Waterfall model

Waterfall model in 2007 was stated as one of the most traditional and equally common life cycle models by KORKMAZ and it was also known as linear – sequential life cycle model. The waterfall model is one of the most easy to implement and easily understood life cycle model. In a waterfall model in order to step forward towards next phase previous phase must always be completed in whole before. Another amazing feature of this model is that one can review the project by the end of every phase in order to check whether the project is on track and one can decide to continue or discard the project according to its directions. Waterfall model does not allow overlapping of phases.

 Structured evolutionary prototyping models

In this model after gathering all requirements, developers first build a prototype. The prototype is then sent to end users for evaluation and in order to obtain feedbacks from end users. Based on feedbacks, developers make improvements and resend prototype to end users. The whole cycle continues until end users are satisfied and after the satisfaction, code is introduced to match final product requirements.

Prototyping steps involved in the structured evolutionary prototyping model:

  • A prior project plan is designed
  • High level paper model is created at partial levels
  • This model works as a source for requirement specifications
  • A prototype is then constructed with basic and critical attributes
  • Designer improvises database, algorithm functions and user interface

The designer then explains the prototype functionality to users and allows them to evaluate, after evaluation, the user suggests problems and improvements required in project if any.

The design phase continues till the user feels satisfied

Structured Evolutionary prototyping strengths

According to Griffith (2008), “code and fix” is not an accurate way in development. It also reflects bad reputation leading to dirty and quick methods. This may bypass the maintenance, process will thus continue forever.

 When to use a structured evolutionary prototyping

It is recommended the usage of this SLDC only when requirements status is unstable. It is used when improvements in user interface are required and also to demonstrate a view of project development and is thus also used to analyze design portions of the object oriented project development.

Consider it as follows:

  • Requirements are not clear or unstable
  • Requirement clarification stage follows waterfall model examples
  • Improve user interface
  • Short demonstrations
  • Original and latest developments
  • Analysis and object oriented design portions.

Considered Philosophies:

Structure evolutionary prototyping and waterfall models are mainly used in research process related to application development for Adhoc networks. 

Posted on

Technical Paper Presentation on Software Development Methodology

In 2006 Madsen mentioned software development has evolved from many forms of the past and today, almost daily, new and much simpler but effective techniques are being introduced in software development areas. Software development is a process which requires many steps and procedures within a single cycle that’s why software development is considered one of the biggest tasks in its developing industries. In literatures of software engineering, many software development models are present and no one of them is able to qualify the maximum level in development feasibility.

No matter any software development philosophy you consider, the one phase which always gains the top priority is the resource gathering phase. More than 30 to 40 percentage of time in software development process is consumed gathering resources by many software vendors as mentioned by Leon in 2008.

Resource or requirement gathering phase is one of the key phases in software development process. Different software organizations follow different strategies in requirement gathering phase but Sanjay (2005) mentions that sometimes either clients or software vendors fail to deliver their best in gathering requirements mainly due to their buried efforts. As far as traditional way is considered for software development it involves a number of meetings among software vendors and clients in order to decide projects common point of view according to availability of requirements. In many cases it comes a stage where changes in work done are required and requirements are frozen and the main cause behind most cases are miscommunications in meetings while the requirement gathering stage is on. All of this results in a lot of rework with respect to project and project delivery dates are affected too.

Miscommunication and less interaction are the two events if happen in requirement gathering phase in most cases result to project failure according to Korson (2008). It also results in issues between clients and software vendors at the end of failed projects. Thus a requirements gathering phase always has lots of issues hidden and in order to avoid any of those issues its required clients and software vendors explain their requirements in details and every step of software must undergo discussion in order to reduce requirement changes or software modification in future. However issues are a part of software development and it mainly cannot be fully avoided but one can reduce them as there are many tools present for implementing perfect requirement gathering methods.

If you consider Vliet (2008) views, its true requirement gathering is the most important step in software development and one must also consider the presence of a whole separate area says requirements engineering in which different procedures and frameworks are tested and introduced to enhance requirement gathering phase by all factors and introduce new requirement gathering techniques for this phase.

Posted on

Paper Presentation Topic on The Performance of TCP across Dynamic Supply Routing

Usually the movable nodes to the MANETs are connected by using radio frequency furthermore, during this specific scenario the mounted infrastructure isn’t conserved. Within the recent times several analysis are worked out on the economical routing of the MNAET however though if it’s the subject of the analysis attributable to the huge motion of the nodes furthermore the path volatility.

The functionality of the TCP for the MANETS is taken into account as the major issue and it is described that the functionality of the TCP is often reduced towards the architecture less networks like the MANETS during comparing them with the various types of the networks.

Generally there are few conciliations so as to control this sort of things the primary step is to get over from the warning and provide the coaching to the TCP so as to overlook the various sorts of the packet loses however not to attract the blocking management routines at the chance of the small packet loses. By following this the performance of the TCP might be protected and saved the harms occurred within these packet losses might be simply reduced.

Another vital methodology to develop or enhance the functionality of the TCP is to allocate the role or job to regulate or control the packet losses in the way of the routing algorithm instead of claiming for the managing routines which related to the TCP and by using this method the functionality of the TCP is simply developed.

Posted on

Route Maintenance Method Seminar Reference Material

To identify the present status of the topology varies against the network the path maintenance method might be used. It’s been come into notice that the degree of motion of the nodes is extremely large towards the MANETS then there are a lot of chances for the variation in the topology furthermore the variation against the route is conserved towards the cache by using the nodes.

The spaces in between the links ranging from one node to the opposite sorts of the hops should be determined through different nodes and primarily there are many sorts of the present standards so as to attain or complete this specific operation.
To identify the link miscarriage towards the routes the DSR can use the method of the passive response.

In this entire procedure if the source forwards the packets to the target destination then the intermediate nodes can find the issues associated with the link of the adjacent nodes then within the moment it’ll transmit the RERR- route error packet to the source node.

Posted on

Paper Presentation on Route Discovery Method

Introduction to  Route Discovery Method:

It is essential for the routing protocols present inside the MANETs to follow the route invention process. The DSR can create an investigation relating to this route targeted to the destination initialized from the source which is needed to pass on few packets. In the whole method if it’s recognized and regarded for the fresh route then the packets that are published towards the destination using similar path and the communication method. If the source being failed to recognize the current path then the DSR sends the request towards the nodes in order to validate the path.

Usually the path request is forwarded in the form of packet that is termed as the RREQ-route request packet furthermore as this specific packet is sent towards the whole nodes situated in the network. The most important attributes like the source and the IP address of target are  preserved by the RREQ in the form of single request id which is present by the sender.

By the whole method if  every node determines the dummy path request then immediately it will be occurred to be unimportant and after that it can investigate that whether they are related to the specified targeted nodes. The unicast function that is troublesome is administrated so as to forward the RREP messages to the source instead of sending the message to complete the whole network.

In the transmission method while performing the unicast function every node is able of changing the path at the side of its route cache.

Posted on

Dynamic Supply Routing Protocol Seminar Topic

Introduction to Dynamic Supply Routing Protocol Seminar Topic:

The terminology of source routing is the main fundamental task of the dynamic source routing. The route invention method that is been employed at intervals in this specific routing protocol doesn’t match with routing protocols. The dynamic data is used so as to reduce the published messages furthermore the publicity of the regular routing.

The routes identification is been administrated during a dynamic approach relying upon the cache info that is accessible otherwise the routing data that is been received by utilizing the requests associated with the sources of the same kind of the dispersed in the whole networks.

The first step while processing the routing is situating the complete information related the whole nodes by the sender that are needed to be carried out by the packets. This particular information is recognized from the the packet header before the method of original routing is completed.

One, among the many advantages about this routing is that the data associated with the routing conserved via the intermediate nodes is been left furthermore the significant data for the method is been maintained at the header of packet. By using this routing protocol the statements associated with the periodic route might be totally separated and also the overhead management are going to be reduced.

The final operation of the DSR routing protocol is further more partitioned into two separate steps like the Route invention and the Route maintenance that are explained below.

Posted on

Recent CSE Seminar Topic on Optimized link state routing protocol (OLSR)

Introduction to Optimized link state routing protocol (OLSR) :

 OLSR is referred as the optimized link state routing protocol and it belongs to the proactive routing protocol in which the different types of the routes are always offered and available for the purpose of the routing. Topological changes decrease the transparency which is happened because of the network this protocol will make use of the MPR- multi points relays.

 Flooding can happen in the continuous process if more number of the topological changes takes within the networks and if there is a possibility that the similar types of the message is been transmitted towards the similar area for several times, this can leads to the typical situation which is already mentioned known as flooding. For reducing the flooding which is been happened because of the fake transmission the multi point relays could be utilized.  .

 By the means of the hello messages and by making use of the OLSR routing protocol and the Topology control, the identification and broadcast about the information and the link status that belongs to the node could be done towards the entire network in order to know the current status of the topology if it changes within the network. Generally the hello messages are  transmitted  at the specific node level, but while comparing to the messages of the Topology changes are been transmitted all over the network in order to identify the changes that will take place because of the process of the mobility of the nodes which are towards the topology that is been built.

The forwarding of topology is done by using the MPR- multipoint relays and it changes the messages and then this particular message can be transmitted as well as forward in a periodic manner towards the network every time when there is any alteration in the topology that is generated in the network. By the efficient use of MPR the information exchange which is towards the network could be easily decreased to a certain large level for the efficient working and it is even capable of decreasing the broadcast flooding to a certain amount. The OLSR is considered to be one of the most developed and is a one of the advanced versions of the link state algorithm by which the link state information is a kind of similar to that of the equivalent nodes. Establishment of  the OLSR  routing protocol insures that there are more chances to decrease the size of the control packets as well as the information that belongs to the subset of the links is been sustained rather than the entire link information of the particular network. By making the proper use of the MPR the optimization aspect can be easily attained by which the control information is been optimized.

From all the existing routing protocols available in the MANETs this particular protocol is to be considered as one of the best protocol. And  in order to obtain the optimality each and every node will be given the permit and subject to the hello message in order to recognize the information about the adjacent nodes of the network and then this process is required to recognize the numbers of the hop node. The size of topology changes size is high and it is forwarded towards the direction of networks and to complete this also there is a particular necessity for having the required knowledge if we had to change generate the topology for making some of the change in the adjacent available node .