1 / 13

DISTRIBUTED DATABASE FOR POINT OF SALE

DISTRIBUTED DATABASE FOR POINT OF SALE. By Ghislaine Ngangom Supervisor: Prof Isabella Venter 3261404. CONTENT. INTRODUCTION USER REQUIREMENTS REQUIREMENTS ANALYSIS PROJET PLAN CONCLUSION

abdalla
Download Presentation

DISTRIBUTED DATABASE FOR POINT OF SALE

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. DISTRIBUTED DATABASE FOR POINT OF SALE By Ghislaine Ngangom Supervisor: Prof Isabella Venter 3261404

  2. CONTENT • INTRODUCTION • USER REQUIREMENTS • REQUIREMENTS ANALYSIS • PROJET PLAN • CONCLUSION • REFERENCES

  3. INTRODUCTION • What is a Distributed database system? From the architectural point of view, a distributed database system consists of a collection of sites, connected together via a communication network, in which • Each site is a database system site in its own right, but • The sites have agreed to work together (if necessary), so that a user at any site can access data anywhere in the network exactly as if the data were all stored at the user’s own site.

  4. INTRODUCTION(cont.) • Some Advantages of distributed system: • Fault Tolerance and multiple point of failure • Site autonomy • Scalability

  5. USER REQUIREMENTS DOCUMENT • Problem Domain The problem domain is to design a distributed database application a for point of sale system that can serve as a platform for point of sale transactions as well as retail management.(we used documents analysis to gather the requirements).

  6. USER REQUIREMENTS DOCUMENT(cont.) • Description of the problem

  7. REQUIREMENTS ANALYSIS DOCUMENT • Architecture of the proposed solution Site1

  8. REQUIREMENTS ANALYSIS DOCUMENT(cont.) • Functional requirement • Perform point of sale transaction • Generation of report • Management of promotional items or products • Point of sale retail and stock management • Management of staff and customer account • Non functional requirement • Availability • Survivability • Decentralized data • Concurrency transparency

  9. REQUIREMENTS ANALYSIS DOCUMENT(cont.) • Some difficulties and ways to solve them: • Synchronisation between databases • Security of databases • Concurrency, coherence, consistence • Tools to use : • UML • Cobra and RMI • Mysql, Php, Apache, JavaScript

  10. PROJET PLAN

  11. CONCLUSION The principals aims of the project: • Offer a secure and robust environment for point of sale transactions as well as stock management. • To allow administrative User to make important decision using generated report. • Availability. • Survivability. • Decentralized data.

  12. REFERENCES • DEAKIN, u. o. Session1 - Basics concepts of distributed database systems. • Dye, C. (April 1999). Oracle Distributed Systems. O'Reilly. • Emmerich, W. (1997). Distributed System Principles. • www.barsnstripes.com, P. b. (11/29/2005). Point of Sale-A beginners guide. • Petru Eles, I. L. Distributed Systems. • sommerville, I. (2004). Distributed Systems Architectures,software Engineering (7th edition ed.). • faq.cfm.htm. (2008). Retrieved from www.RetailSystems.com.

  13. THANK YOU!!!! QUESTIONS??

More Related