1 / 9

CellBus Final Release

Prepare for the final release of our Java-based Bus Tracking System with essential software requirements. You'll need the Midlet software alongside Java SDK 1.4.1 and the J2ME Toolkit for emulation. Ensure your Tomcat 4.1 server is set up and running Java 1.4.1. Users will interact primarily with the intuitive Midlet UI, where they can inquire about bus locations. Key considerations include sufficient bandwidth and server maintenance. The project has resolved many bugs, and we are close to finalizing the release with a few final details to address before going public.

nodin
Télécharger la présentation

CellBus Final Release

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CellBus Final Release

  2. Software Preparation • Required Midlet Software • Java sdk 1.4.1 • J2ME Toolkit (for emulation) • See http://java.sun.com/j2me/ for installation help • Midlet.jar (our midlet) • Midlet.jad • Required Server Software • Tomcat 4.1 Server • Java 1.4.1 • server.war (our package)

  3. Site Preparation • Log files? • Socket • Files • Persistent connection to SDD server • Substantial bandwidth requirement • Images not quite working yet....

  4. People Preparation • Users • Those who ask “Where’s my bus?” • Operators • Keeping up the servers • Maintainers • Extending the code

  5. Users • Deal mostly with the Midlet • UI is intuitive. • Slightly difficult to read, but that’s a limitation of the medium

  6. Operators • Images cost a lot • Disk Space • Bandwidth • RAM • Streaming SDD socket to ITS • Bandwidth • Computation to extract information

  7. Maintainers • Reliant on sdd.its.washington.edu • Uses sdd package from its.washington.edu • Maps stored in servlet.war • Javadocs

  8. IOC Success • Images more resource intensive than first expected. • Location serving properly • Midlet using interfacing properly with servlet. • Of 26 bugs • 14 resolved Fixed • 5 implemented • 2 Unresolved

  9. Have we succeeded? • We’re close • A couple more details that should be worked out before it’s really public ready.

More Related