Mobile Audience Survey System (MASS)

This project was first developed during my internship at Motorola Brazil Test Center, where I had to explore the integration of J2EE using Tomcat and J2ME. I chose to use serialized objects in XML produced by the J2EE server and consumed by any J2ME MIDP 1.0 client running on a cellphone device. One of the most interesting problems was that such device offers a very limited environment for the development of XML consumption. That's when I found out the application of XML Pull-Parser very useful.

M.A.S.S. enables people to make mobile surveys using a wireless device with MIDP 1.0 enabled. There are 2 midlets on this test build: The M.A.S.S. Client and Manager.

CHECK THE UML OBJECT-ORIENTED ANALYSIS AND DESIGN;
M.A.S.S. Manager is used to create a new session and close the current existing one; The session can be optionally created using a web browser.
(J2EE Middleware Server Java Docs API);
M.A.S.S. Client is used to answer (vote) on an opened session, as well as viewing the current votes results and saving them on the mobile device.
(J2ME MIDP Java Docs API).

This project is a result of the J2ME Classes from the CIn-Motorola Internship program, that took place on July, 2004. Special Thanks to Prof. Paulo Borba for the original classes and all the motorolans.

Marcello de Sales Jr.
http://www.cin.ufpe.br/~masj2 - masj2@cin.ufpe.br

August 07, 2004. Recife, Pernambuco, Brazil / Motorola Brazil Test Center

Different use cases were implemented to exercise the data exchange from the J2EE and the J2ME Java applications. The project was documented using Object-Oriented Analysis and Design using UML. Check the UML Documentation. You can also view a sample of the source-code.

Creating a new Session Form

When the user accesses the new Session Form, the server sends an XML message signing that there are no new session and he/she is ready to create a new session.

Request for Session Creation

When the user confirms the creation in the client-side, the J2EE middleware receives the serialized XML containing the information from the POJO. Then, it persists the information in the database and confirms the creation of the session by sending an acknowledge message back to the client.

Viewing the current session results

While the votes for the current session are being entered by different users, the client can request the current values.

Viewing all available sessions in the server

As different sessions are created, the server retains the list of existing sessions. The client may view the list of existing sessions by requesting the list.

Closing the current session

The administrator/professor/manager may choose to close the session. This action closes the session and no user may enter their votes for that given session anymore.