• Join over 1.2 million students every month
  • Accelerate your learning by 29%
  • Unlimited access from just £6.99 per month
Page
  1. 1
    1
  2. 2
    2
  3. 3
    3
  4. 4
    4
  5. 5
    5
  6. 6
    6
  7. 7
    7
  8. 8
    8
  9. 9
    9
  10. 10
    10
  11. 11
    11
  12. 12
    12
  13. 13
    13
  14. 14
    14
  15. 15
    15
  16. 16
    16
  17. 17
    17
  18. 18
    18
  19. 19
    19
  20. 20
    20
  21. 21
    21
  22. 22
    22
  23. 23
    23

The purpose of this document is to provide a design for an electronic payment system as an extension to an already existing electronic photographic database created by S3G.

Extracts from this document...

Introduction

Table of Contents 1 Introduction 4 1.1 Purpose 4 1.2 Scope 4 1.3 Definitions, Acronyms, Abbreviations 5 1.4 References 6 1.5 Changes to S3G Requirements 6 1.6 Overview 7 2 Decomposition Descriptions 8 2.1 Module Decomposition 8 2.1.1 Payment Component 9 2.1.2 Entity Relationship Diagram for the Payment Component 10 2.1.3 Overview of Database Alterations 12 2.1.4 Links to Requirements Document 13 3 Dependency Descriptions 14 3.1 Inter-module Dependencies 14 3.1.1 Use Case Diagram of the Payment System 14 3.2 Inter-process Dependencies 14 3.2.1 Sequence Diagrams 14 3.2.2 Analysis Model 16 4 Interface Descriptions 17 4.1 Component Interface 17 4.1.1 Payment Component 17 4.2 Process Interface 19 4.2.1 Home Page Prototype 20 4.2.2 Checkout Prototype 21 4.2.3 Payment Prototype 22 5 Appendix 23 5.1 Appendix A - SEG 3 Group Document 23 5.2 Appendix B - SEG 4 Group Document 23 List of Figures Figure 1 Deployment Diagram 8 Figure 2 Payment Component 9 Figure 3 Activity Diagram for Purchasing an Image using the payment component 10 Figure 5 Member Functionality 14 Figure 6 Choose a Picture to Buy Instance Sequence Diagram 15 Figure 7 Fill in and Submit Card Details Instance Sequence Diagram 16 Figure 8 Analysis Model 17 Figure 9 Home Page Interface Design Prototype 20 Figure 10 Shopping Basket Interface Design Prototype 21 Figure 11 Checkout Interface Design Prototype 22 1 Introduction 1.1 Purpose The purpose of this document is to provide a design for an electronic payment system as an extension to an already existing electronic photographic database created by S3G. The document will adhere to the IEEE standard 1016 - 1998 and as a consequence will be easy to read and well structured. The aim therefore being that a variety of users can understand the project and be able to implement the design from this document alone. Both the ISEB class and the SEI staff will be able to read this document with clarity, as it will use natural language and diagrams. ...read more.

Middle

The payment module, Payment, whose implementation will be explained in section 2.1.2 allows the user to input their card details and then connects them to a third party program from a company called SecPay 4, which is hosted on separate secure server, to process the payment. 2.1.1 Payment Component The Payment component contains all the functionality required to process a users payment details when they wish to purchase an image. The Payment component incorporates the Payment class, the Shopping Basket class, the User class and an Archive class. When the user finds an image they wish to purchase they add it to their Shopping Basket. To do this the user clicks the "Add to Basket" button next to the desired image. The image ID and user ID are stored together as a pair in the Shopping Basket class thus making it possible run searches on this table to find what images a client has in their basket. The Payment class then deals with taking all of the user's card details and passing them onto the 3rd party SecPay database. Figure 2 Payment Component The activity diagram below shows the process of an image being selected, added to the basket, purchased using a credit/debit card and then the purchase data is then stored in an archive table. Figure 3 Activity Diagram for Purchasing an Image using the payment component 2.1.2 Entity Relationship Diagram for the Payment Component The images that are uploaded will be stored in the database since it would provide a security risk if images were kept in a publicly accessible place. Currently on the ITS systems it is not possible to write to files outside of the public web directory and so images must be kept inside the database for security reasons. All of the information held on dynamic web pages throughout the system will be held in the database. This means that the data structures used inside the database will be used throughout the system for consistency. ...read more.

Conclusion

4.2.1 Home Page Prototype This is the home page for the website. It is structured into three main sections. The first section on the left is an interactive drop-down menu. Depending on what is selected in the menu section the main part of the web page will change appropriately. The far right column on the web page shows what items the user currently has in their shopping basket. Figure 9 Home Page Interface Design Prototype 4.2.2 Checkout Prototype Once the user has finished browsing for images and wishes to purchase their selection they click on the Checkout button in the shopping basket section of the homepage. That page will bring the user to the Checkout page. This page allows the user to view all the details of the images they have in the Shopping basket and remove any images they don't wish to purchase. Figure 10 Shopping Basket Interface Design Prototype 4.2.3 Payment Prototype When the user has confirmed that they which to purchase all the images in their shopping basket they click on the Checkout in Figure 10. This page will appear and the drop-down menu on the left will be disabled so that the user cannot accidentally click on something while their card details are being processed causing an error. Once the details have been entered the user clicks the "Charge Card" button and they are linked securely over a SSL to the SecPay server who will then charge the card. Figure 11 Checkout Interface Design Prototype 5 Appendix 5.1 Appendix A - SEG 3 Group Document For Appendix A please see the SEG 3 (S3G) group document at the following location. http://www.dur.ac.uk/cs.seg03/seg03_design.doc 5.2 Appendix B - SEG 4 Group Document For Appendix B please see the SEG 4 group document at the following location. http://www.dur.ac.uk/cs.seg04/seg04_design.doc 1 See Appendix A 2 See Appendix B 3 This functionality will initially be limited to the following languages: Chinese, Hindi, Arabic and English. 4 http://www.secpay.com/ for more details 5 http://www.secpay.com/sc_api.html#normal contains further details of the implementation. ?? ?? ?? ?? Electronic Photographic Database Design Group 3 1 ...read more.

The above preview is unformatted text

This student written piece of work is one of many that can be found in our AS and A Level Management & Manipulation of Information section.

Found what you're looking for?

  • Start learning 29% faster today
  • 150,000+ documents available
  • Just £6.99 a month

Not the one? Search for your essay title...
  • Join over 1.2 million students every month
  • Accelerate your learning by 29%
  • Unlimited access from just £6.99 per month

See related essaysSee related essays

Related AS and A Level Management & Manipulation of Information essays

  1. Designing a booking system for an Estate Agent.

    For evaluation of properties the person responsible for this is the Sales Manager. For details of what each job title involves look at 1.3 Identification of client and users. 1.3 Identification of client and users. The client is Burnet Ware Sales & Lettings and the users will be the employees

  2. ICT coursework: Designing and implementing a book rental system

    * You can search very quickly. Access 2002 has the following: * Create and edit table * Create and edit relationships * Create reports and forms based on tables * Create customised input screens and using visual basic facilitate searches and validation procedures * Create quires to find specific data * Crate a menu driven system

  1. Database Design

    date of which the employee was hired 00/00/0000;0;_ Order Table: Attribute name Data type Size Validation rule Description Input Mask Order ID Number 3 Cannot exceed 3 characters ID number for the order made Customer ID Number 3 Cannot exceed 3 characters ID number of the customer Order date Date

  2. I have been asked by a General Sports shop using a manual system to ...

    You could password files or use encrypting packages to password folders and files as well. The computer could also be virused so an anti-virus program could be used. Here are some that are available: MCAFEE VIRUS SCAN Price including VAT �24.99 Features - Stop viruses from attacking your PC -

  1. Planning a payroll system for a martial arts school.

    Justification of reasons for the Solution At the moment the current system consists of manually calculating the details on a form that the employee fills in and is signed by their manager. The employee fill in a form with his details (employee number, surname and forename, grade, hours worked...)

  2. In this document I will begin to explain why I have included the following ...

    IF statement - I used an IF statement in my sheet 'Find area' in cell E10. Its purpose was to inform the user what category their window size fell into. The reason this is important is because our company doesn't specialise in industrial windows, and we will charge extortionate prices.

  1. Evalution of my database

    I knew what flow diagrams were and how to use them to show information also I already knew how to create a table of data through the software called Microsoft access. I had some basic skills on how security works and the different types of threats there is and how

  2. Using the Internet to research UFOs.

    For example, when I initially began my search I focused primarily on UFO?s. Having found that to be such a broad subject, I was able to narrow it down to a commonality I had found in many of the sites--alien abduction.

  • Over 160,000 pieces
    of student written work
  • Annotated by
    experienced teachers
  • Ideas and feedback to
    improve your own work