Electronic payment system
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.
However, this document is written with the SEI staff in mind. The extension to the existing system will provide it with a Web component, allowing individual users to access photographs over the Internet. The users will also be able to buy and sell images to other users of the system. The benefit of this is that it will provide a much more interactive experience for the user. This design document will add a few additional functional and non-functional requirements to the existing requirements from the S3G design document to deal with the new payment system.
It will also remove several unnecessary features
Need essay sample on "Electronic payment system"? We will write a custom essay sample specifically for you for only $13.90/page
The IEEE has a recommended practice for Software Design Descriptions (SDD) and this will be used as a guide when developing the software system. 1. 2 Scope As many of the key elements of this system have already been developed by S3G 1 this design will place a strong emphasis on software reuse. This design document reuses aspects of the existing electronic photographic system, which is coded predominantly in PHP and uses a MySQL database. It will also incorporate various HCI aspects from a design written by SEG4 2 for the GUI.
There will be only one new software component developed for the system. This will be a Payment component which will add functionality to the system, allowing users to pay securely online for any images they wish to purchase. The payment module ties together the existing S3G system with third party software from a vendor that provides secure online purchasing software. The third party software will be provided by SecPay and will be hosted on an ITS server by the University of Durham ITS department.
When a customer wishes to purchase an image they will input their details into the data capture. Once the user clicks ‘submit details’ they are forwarded to the SecPay system and their software will deal with the validation of the details and process the payment. As the card processing is dealt with outside the scope of this project, references will only be made to the SecPay system and no details of that systems design will be included in this document.
Image delivery will also not be covered within the scope of this document. Design diagrams will be drawn to show how to implement the system, and in the case of the user interface, prototype screenshots will be produced but because of time constraints the system will not by physically implemented. S3G group designed and implemented the original system but did not include any non-functional requirements to help users of different nationalities or those users with disabilities.
Therefore our system will take this into account by providing GUI translation facilities which will provide the option for users to change the Interface language3. As well as this certain areas of the interface pages will vary in hue to help those users who are partially sighted differentiate between different areas. As mentioned in section 1. 1 of this document certain software aspects of the existing system will be removed (see section 1. 5).
Both the Messaging and the Games modules will be deleted, these modules fulfilled their original additional requirements to be able to send, store and compose a message and also to have a Jigsaw, Slide Puzzle and send an E-Card respectively, however their lack of relevance to the design brief of this system means they will be removed. 1. 3 Definitions, Acronyms, Abbreviations Administrator A built-in role responsible for administrating the site, the database and application users. Administrator has full access to the application data and functionality. CSV The 3 digit security code on the back of credit cards.
Provides a cryptographic check of the information embossed on the card. Validates that the customer placing the online order actually has the credit card in his/her possession, and that the credit/debit card account is legitimate. Database A collection of information organized in such a way that a computer program can quickly select desired pieces of data. From: www. webopedia. com IEEE Abbreviation of Institute of Electrical and Electronics Engineers, pronounced I-triple-E. The IEEE is best known for developing standards for the computer and electronics industry. From: www.webopedia.com