MOBILE WORKFORCE COURIER SERVICE

- BY L.HARITHA K.G.SWETHA

CURRENT SCENARIO
To approach the courier agency directly at

their workstation. To utilize their services available online.

With the current trends of MOBILIZATION, these methods seem dreadful. Reasons being SYSTEM AVAILABILITY BUSY SCHEDULE OF THE USER ACCESS TO THE INTERNET AUTHENTICATED DELIVERY REPORT
2

and the list goes on...

SOLUTION
Proposed solution for these problems in the current scenario can be the usage of a handheld device, Mobile . The usage of this device is an attempt to cope up with the present lifestyle of the people and in a way to understand their needs.

TECHNOLOGY INVOLVED
The Technologies involved are as follows: J2ME GPRS (General Packet Radio Service)

J2ME
The micro edition of Java 2 platform provides an application environment that specifically addresses the needs of commodities in the vast and rapid growing consumer and embedded space which includes modile phones. It consists of a collection of packages and classes for application development on mobile devices.

GPRS
General Packet Radio Service. A standard for wireless communication. It applies a packet radio principle to transfer user data packets in an efficient way between mobile stations and external packet data networks.

APPLICATION AREA
This is a Vertical application which enables the user to interact with the courier agency and even allows the user to track the status of the parcel/package which was to be delivered.

SCOPE OF PROJECT
This application of the COURIER SERVICE on the GPRS connected mobile phone is an innovative idea to assure better business with profits and also making it more user friendly.

SRS
Software Interface:
WAP Gateway. J2ME. ORACLE 9i.

Hardware Interface:
Mobile phones enabled with MIDP 2.0. GPRS connectivity.
9

SYSTEM DESIGN
Architectural Design:

10

Usecase diagram:

Road & Rail

<<extends>>

<<extends>> Air <<includes>> updates

<<includes>> Express services products User Available services

Admin customer details

Agent details

Get Status

<<includes>>

Login login

update status get request

<<includes>> Order details <<includes>> Agent Mode of Payment Select Product

11

Class Diagram:
Admin id name address contact_no getser_id() getdetails() getPID()

Agency Location Web Address Contact_no getid() getc_id() getagent_id()

Agent agent_id name address contact_no qualification getrequest() setrequest() givestatus() getinfo() Customer c_id password Name Address contact_no Email_id Payment_id getid() getpassword()

Package PID content weight date charges getPID() getcontent() getweight() getdate() setPID()

Services ser_id name offers rate setser_id() setname() getser_id() getname() updation()

Products product_id name price getdetails() getprice() setprice() update() delete() substitute()

Order Details ser_id info date des_address contact_no payment_id New User r_form options register() services() offers() getser_id() grtinfo() getaddress() getpayment_id()

Existing User list options viewlist() purchase() additional services()

Payment id mode date getamount() getmode()

12

Activity Diagram:
User Administrator

Enter details

Load into Database

Receive details and Login

Create user Id and Password

Validate the details

Verify No Yes Provide Access to the user

Error message

13

Sequence Diagram:
Agent Login:
agnt:agent login admin:administ rator for validation validate confirmation

enter details

14

MODULE DESCRIPTION
USER MODULES: Registration. Services. Place order. Check status. AGENT MODULES: Check orders. Update status.
15

CODING
Mobile screens (user and agent). Database connectivity through Servlets. Classes like MyMidlet, Login, Registration etc..

16

TESTING/RESULTS
Let us look at one of the screens that play a maximum role in our application it being a mobile application. The screen showed here is the general pattern with two text fields basically for login purpose In this application we have two login forms one for user login and another for agent login

Agent_id: Password: invalid

Valid if the id and the password matches with the database else invalid.
17

FEASIBILITY OF APPPLICATION
GUI based. User Friendly. Moving a step further towards mobilization.

18

ENHANCEMENTS
This application can be further enhanced To a larger agency which includes services across the entire globe. Various transport facilities available. More services and advantages to the user.

and the list can go on..

19

CONCLUSION

EASY TO HANDLE CLARITY OF WHEREABOUTS OF GOODS FLEXIBLE. CONSUMES LESS TIME..

20

REFERENCES
IEEE Std 830-1998, IEEE recommended practice for System Requirements Specifications. http://java.sun.com/products http://en.wikppedia.org http://www.mobilelin.com http://www.bluedart.com http://www.dtdc.biz

21

ANY QUERIES ???

22