Independent Study
Visual LookVisual Look IntroductionIntroduction SRSSRS SDDSDD ImplementationImplementation TestsTests Conclusion and Future PlansConclusion and Future Plans ReferencesReferences
Robot Driver interaction Server Interaction Apache Derby Database Interaction Web Application Interaction. These diagrams cover the SRS and the SDD
The Robot Driver The Fedora Core Server The Web Application
Capacity to be an application It will be updating the robot wirelessly Future work will be done on this.
The Robot Driver The Web Application Data Packets Sent Robot GUI Program Data Packets Sent Robot Logic
Receives data from the Web application Updates the web application Stores user login information Restricts access to the robot webpage
The Robot Driver The Web Application
Receives data from the internet cloud Updates the Database Sends data to the Robot Driver Contains Servlets Contains Deployment Descriptor (web.xml) Contains.JSP (Java Server Pages)
The Robot Driver The Web Application Data Packets Sent Java Server Pages (.JSP) Java Servlet
Introduction This project was based from the “Bluetooth Robot Remote Joystick Control” project The goal is to achieve the same effect via the internet More can be done over the web. Due to time constraints the projects potential was streamlined.
Previous Project Make the Ridgesoft three wheel robot work wirelessly using Bluetooth and control it via a joystick. This goal was accomplished. GridConnect Bluetooth devices were used. Standard USB joystick was used The Java jjoystick and the rxtx API was used.
Transition Most of the same features can be done via the web Similar movement and control Joystick would be too challenging to implement over the internet due to the embedded part of the joystick More information on this project: s/robotjoystick/ s/robotjoystick/
SRS
Follows the IEEE format Gives a brief design plan Defines uncommon computer terms. References all the sources that I have acquired for this project SRS Basic Overview
SRS Purpose It is assumed that this document acts like a “Project Proposal” in the business world So there is clarity between the engineer and the project benefactor. To acquire this document: ojects/robotweb/ ojects/robotweb/
SRS Design It covers the study of basic robotics over the internet Defines clear goals Displays pictures and diagrams
SDD
SDD Overview Project proposal Definitions, and technical terms References Software requirements Software anatomy
SDD Content The diagrams, references and definitions were the same. More content and design details More focus was on the software rather than hardware requirements Sample code is given in the appendix part of the document Acquiring this document: otprojects/robotweb/ otprojects/robotweb/
Implementation Reasons for this choice of technology Applets VS Servlets Current Progress Design
Implementation Choice I already knew Java Java is very versatile Java can be on almost any device Java is free
Applets vs Servlets While Applets and Servlets have the same super class, that is where the similarity ends In Web browser verse on the server Networking issues Servlet is combining an applet with CGI script – this makes it superior to Applets
Current Progress The Project web application is up and available Only backend work is needed now Since Tomcat is installed, most of the pulmonary work is done To see the current status: cts/robotweb/robowebframe.html cts/robotweb/robowebframe.html
Testing Procedures First, to correctly install the needed software packages Correctly startup the Tomcat service Understand the basics
Testing Deployment Understanding the basics of Tomcat Understanding the basics of Servlets and JSP To see the actual test deployment:
Implement a database into the web application. Making a more robust web application Creating well commented and well designed web application
A lot of changes were made – the project became a lot more streamlined in the end. Most assistance abandoned the project. Only backend needs to be completed
nbot.htmhttp:// nbot.htm