![Theme ,[object Object],[object Object],[object Object],SZABIST](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (15)
Similaire à Case Study: Synchroniztion Issues in Mobile Databases
Similaire à Case Study: Synchroniztion Issues in Mobile Databases (20)
Dernier
Dernier (20)
Case Study: Synchroniztion Issues in Mobile Databases
- 1. MIT’s Case Study Synchronization Issues in Mobile Databases SZABIST Submitted by: G. Habib Uddin Khan SZABIST Mr. Kamran Abid PTCL 12 th National Research Conference
- 5. Business Case SZABIST MIT: Workorder Processing [11]
- 17. Findings & Evaluations SZABIST
- 18. Generations SZABIST Gen 1 Gen 2 Gen 3 Gen 4 Architecture Streaming DC Computing DC Computing Peer 2 Peer Technology Data dumping Wired Sync. Wireless Sync. Server less Management Only on Servers Flat Filing & Semi -Structured DBs + Servers Embedded DBs + Global Services + Multiple Servers Embedded DBs + Mobile Apps Resources RAM (can hold only transient data) Flash Memory Memory on Smart Cards WLAN on Smart Cards Usage Low Mobility High Mobility High Mobility 100% Mobility
- 19. Graphical Representation SZABIST Gen1 Gen2 Gen3 Gen4 Usage Resources Management Technology Architecture Streaming DC Computing DC Computing DC Computing Data Dumping Serverless Wired Sync. Wireless Sync. Semi Structured Embedded DB’s + Global Services + Multiple Severs Embedded DB’s + Mobile Apps Only on Servers RAM Flash Memory Memory on Smart Cards WLAN on Smart Cards Low mobility High Mobility High Mobility 100% Mobility
Notes de l'éditeur
- MIT is the largest IT vendor of Pakistan having sales/service/support franchises and labs in Karachi Lahore and Islamabad. Their business operations are obvious from the 3 departments I have just mentioned. MIT is running their customer support business on a web based portal that process their customer complains step by step in form of a workorder. The purpose of this study is to provide this same system, on a new operating channel i.e. mobile devices (PDA’s, Mobile Phone’s, etc.).
- The arrangement of the slides has been kept in such a way that the audience will first get some idea of theory. Then I will move on to the Business Case and with this we will discuss what operations can be migrated to be done by mobile devices. Or we can say how to improve this system using the mobile technologies. Implementations hurdles or milestones will be the next right after the business cum technical case. Then, technologies to cope up with these implementation barriers will be discussed. By using these technologies I will deduce the solution to the above problems that will definitely lead to some process improvement.
- Databases provides us away to store and manage data, whether we talk about Normal BBMS or Mobile/Embedded Databases. Mobile databases are for such application that needs the data on the move. For example doctors use to carry it on their round to the wards; and maintain patients’ information Or a mineral water distributor may use to carry a PDA equipped with Mobile Application and Mobile Database.
- Customer lodge a complain on helpdesk It will then made visible to all the FT’s in service pool and anyone can fetch it depending on his availability. The FT may work on it to resolve / reject the complain depending on the technical activity.
- In moving this business case on mobile devices we have number issues. Where to store data If everyone has their own copy with permissions to insert/update the records; then how to find out that what is the latest and the final version.
- In the early ages of mobile devices the data has been transported to the central server as is without any pre-processing. Computation is performed by the Central Server.
- Disconnected mode in the sense that the handheld/mobile device can be operated even if it is away from any network connectivity. This has been only made possible only due to the enhancements in memory technology. High memory and Ram made it easy to store and manipulate data in an isolated environment on the device.
- If user wants to perform operations in the disconnected mode then their must be some mechanism to store the data and to retrieve it on demand by the mobile application. The challenges of the time are here.
- Though semi-structured databases are widely used and portable too. But still there is an issue of their standardization. Any Semi-structured set of data is meant for a single application due to its non-standardization. If any other application needs to consume such datasets then they must have to share and follow the same data contract and this is quite a bit costly in terms of volume of unnecessary source code. So the solution is the Embedded databases. Having all the abilities of a standard DBMS
- LDAP – Lightweight Directory Access Protocol
- Any DDL update in shared entities must be reflected to the devices I order to synchronize successfully. Audit Attributes to check the integrity and validness of data. (InsertDTTM, InsertedBY, UpdateDTTM, UpdatedBY). Most of the embedded databases do not provide provision to execute compiled statements. As far as the synchronization is concerned the device must be kept free from complex logic, for scalability purpose.
- At any time T1, multiple mobile user synchronize their devices to fetch the new data. Perform some calculations on their local set that is just received. Submit the changes at day end. Server will commit the changes after some pre-processing.
- The comparisons among the 3 techniques is based on the connectivity, synchronization logic, multiple user provision Clique A group of 3 or more users in which they are isolated from the outer world/ network.
- I have deduce a generation table all the available technologies discussed inthe