This is part of a solution implemented by Rachit Anurag and Me in our college.

1. SMS as an alternative in Information
Passing systems

2. Student – Student Network
Traditional Information Passing
Architectures
Teacher – Student Network

3. • Broadcasts
• Events
• Schedules
• Queries
• Updates
• Feedbacks
Student
Demands
Faculty
Demands
•Demands

4. • Money, Time, Effectiveness, Real Time
Flows?
• Information Bombardment, No Escape,
Real Time Flows, Feedbacks etc.
Road Not Taken Vs. The Beaten Path
A Cumulative Comparison of SMS and Packets

5. • Broadcasts
• Events
• Schedules
• Queries
• Updates
• Feedbacks
•SMS Types
PULL SMS’s.
PUSH SMS’s
•Academic Demands

6. A CENTRAL SERVER
• Sending PUSH Messages.
• Managing databases.
• Receiving Pull Requests.
• Embedding Results in XML
• Routing Messages and
ensuring the transmittal of
messages.
• Disabling Message Broadcast.
• Ensuring the client attention
towards application updates.
• Embedding Queries in XML
RESIDENT CLIENT APPLICATION
•Unifying Generations
The Tale of Old And New

7. • Efficient XML Interchange
• Intelligent Databases
• Mapping Behaviors
•Transmission Protocols

8. Stage 1
•Teacher/Support Staff Make an
Announcement on their Client Applications
Stage 2
•Message Reaches Server and Routing starts,
on the basis of embedded XML
Stage 3
•SMS Sent to user, to be caught by User End
Application.
Stage 4
•Message read receipt to be sent back to
server also the initiators
•Information Flow on PUSH

9. •Data Dictionary – Economizing SMS’es

10. •Picture Page Layout
Your picture caption can go here.
Image from PresenterMedia.com

11. Vision

12. ??