a web based hypermarket supply chain management system

More documents

Recommendations

Info

could also have dedicated staff to respond to queries from suppliers by instant supplierhypermarket communication(Refer to Figure 4.8). This could do away with costs incurred in telecommunication between supplier-hypermarket in issue resolving hence benefiting both parties. Figure 4.8: Flow diagram for messaging 4.5 Sales and Supply Forecast We adapted a simple moving average model to incorporate forecasting capabilities within the system. This assisted in the estimation for future sales and demand being able to predict the quantity of products that need to be ordered and supplied. An unweighted mean of monthly sales for a period of a year were used as the data points for predicting sales and supply. 26
4.6 Security With web applications security is very vital since these applications are accessible over networks. Web applications provide access to backend databases and hence control valuable data and are much more difficult to secure since the have some form of data capture, transmission and retrieval . As a result, these are prone to a wide variety of threats/attacks (Figure 4.9). Figure 4.9: Flow diagram for web application security In the SCM, security has been implemented at three levels, application, database and network. 27
Page 1 and 2: A WEB BASED HYPERMARKET SUPPLY CHAI
Page 3 and 4: APPROVAL This project report has be
Page 5 and 6: ACKNOWLEDGEMENTS I am very grateful
Page 7 and 8: 3.1 Introduction . . . . . . . . .
Page 9 and 10: List of Figures 2.1 Basic supply ch
Page 11 and 12: ASP - Active Server Pages ACRONYMS
Page 13 and 14: Chapter 1 INTRODUCTION 1.1 Backgrou
Page 15 and 16: products supplied by different supp
Page 17 and 18: Modern SCM is regarded as the use o
Page 19 and 20: stability issues such as disaster r
Page 21 and 22: play an important role in the store
Page 23 and 24: Chapter 3 METHODOLOGY 3.1 Introduct
Page 25 and 26: used in system design. 3.3.1 System
Page 27 and 28: standards and procedures were set u
Page 29 and 30: 4.1 System Requirements In order to
Page 31 and 32: 4.1.3 Prototyping Figure 4.3: Progr
Page 33 and 34: security mechanism which uses SSL(r
Page 35 and 36: The Point Of Sale system Figure 4.6
Page 37: Figure 4.5 is a schema showing the
Page 41 and 42: Figure 4.10: Encrypted communicatio
Page 43 and 44: Figure 4.12: Supplier -supplier int
Page 45 and 46: as well as user friendliness. 5.2 R
Page 47 and 48: [9] Sommerville,I.(2004).Software I
Page 49 and 50: Appendix 1SQL statements used to cr
Page 51 and 52: ‘comment‘ VARCHAR(100) NOT NULL
Page 53 and 54: Appendix 2POS Home Page 41
Page 55 and 56: Appendix 4Logout Page into the Repo
Page 57 and 58: Appendix 6Home Page for Century Bot
Page 59 and 60: Appendix 8Home Page for Crown Bever
Page 61 and 62: Appendix 10An example of a web page
Page 63: Appendix 12An example of a web page

a web based hypermarket supply chain management system

Create successful ePaper yourself

Delete template?

Save as template?