1. COMP3241 E-Commerce Technologies Richard Henson University of Worcester December 2014

2. Week 10: Documenting a Client-Server System n n Explain the fundamental differences between documenting client-server and documenting conventional systems n n Explain the importance of presenting a data model in the documentation n n Use software tools to assist documentation of web pages, web sites, and database design

3. What is client-side and what is server side? n n Everything that is displayed using HTML… client side n n Everything that interrogates databases, and databases themselves… server side n n What about the rest of the coding?   JavaScript?   C#?   Asp.net controls?

4. Putting this into a write up n n More challenging than a conventional website/set of programme coding n n It helps to have separate headings for “client side” and “server side” n n Site will be marked as a Visual Studio 2010 project   essential that all server code and the database to run the site are included on the media handed in with the assignment write up!!!

5. How to document… n n Project usually have four phases:   Analysis   Design   Implementation   Evaluation n n Your assignment 2 can be considered to be a mini-project…

6. What to include in the write up n n The assignment brief is your spec (no analysis section therefore necessary!!!) n n Requirements:   “Design” (client & server)   “Implementation”   “Evaluation”

7. Design n n Should include:   site & database design diagrams   screen dump(s) to show common page format(s)   should refer to code (e.g. scripts) by filename so marker can cross-check with file(s) on removable media   test plan…

8. Test Plan n n An empty table that lists the tests to be performed, & expected outcomes… ActionExpected outcome Actual Outcome Click on “ add to cart ” Product added to cart, which is displayed containing correct costs Click on “ new customer ” New customer form allows customer to add personal data

9. Relative and Absolute Paths n For small databases and simplicity Access works well…. n Note that…  Access requires an absolute path »e.g. X:\myfolder\yourfolder\database.accdb  SQL Server, and MySQL can cope with a relative path: »e.g...yourfolder\database.mdf

10. Implementation n n Should include some of:   code sections that you may want to explain or bring to the attention of the marker   database connection string(s) & path to Access (or other…) database in working project n n A description of some problems encountered and how overcome

11. Testing n n Test plan put into effect… n n “Actual v Expected” table completed ActionExpected outcomeActual Outcome Click on “ add to cart ” Product added to cart, which is displayed containing correct costs Yes Click on “ new customer ” New customer form allows customer to add personal data No. Goes back to products page

12. Retesting n n Any differences between expected/actual results need to be resolved n n Changes made as a result of testing should also be documented   retest table also included… n n Repeat retest & retest table if necessary, and if you have time!

13. Rollout n n Retried and retested product copied to removable medium n n Zip up and send to SOLE   keep your own copy!

14. Evaluation n n You should include:   what others (i.e. prospective shoppers) think of the site   how well the completed site meets the spec (or goes beyond it… or could do…)   A personal reflection of your experiences in doing the assignment, and anything else you’d like to have done with it, if you had more time…

15. Further Activities…

16. Creating a login page for different access levels n n Different users can be given different levels of access to resources, based on username   e.g. only users can be identified as “administrators” » »using a user category field in the customers/users table   administrators may be able to access a further HTML form or webform » »allows write access the products table » »can add new product details » »and change details (e.g. price) of an existing product

17. Restricting page access to unauthorized users n n Essential to prevent the unauthorised user “cheating” the system by typing in the URL of the restricted page and displaying it manually n n Readily achieved using a server script that automatically brings the user back to a pre- defined page if they HAVEN’T successfully logged on   e.g. takes control back to the home page

18. Restricted Pages and Secure Pages (2) n n Such an intercept and redirect facility will ONLY protect HTML pages   problem: HTML can easily be hacked… n n Secure pages use the https protocol, and are protected from the server end by a server (SSL) certificate

19. https, and e-commerce systems n n Before payment, the user will also have to be authenticated by the International Banking Network (IBN) before payment can proceed   this MUST happen at a fully protected page » »via https » »logged in checking » »(additionally) a system-defined “time out”   control then passes to a merchant services provider for interaction with the IBN n n Much more about https in COMP3221 module…   also see COMP3123-7,8 via link to RH’s old website if interested

20. Order information and the Merchant System n n With a real system, at least one parameter needs to be passed to the bank system with the credit/debit card details   e.g. “GrandTotal”   from Orders Table n n Needed to check whether the customer has enough funds in their account to allow the transaction…   actual funds “taken” after this check has a positive outcome

21. The “Sendmail” control n n The WebXelCart control that allows an email to be sent when the order passes through payment n n Email contains a copy of the online invoice… n n Can be implemented from the “Payments” page”…

22. How to submit electronically n n As with assignment 1…   put write up.doc(x) through Turnitin…   send all docs as a zipped folder   this time also include practical project n n Project should be saved as a.sln file and associated folders   when.sln opens in Visual Studio all files should be appropriate places   marker will adjust database path (if necessary)

23. Good Luck and have a Great Xmas! Two timetabled sessions in January If you can’t make it to either, practical workshops may be available by appointment until the day before hand-in: email me