Purpose of System
——————–
1. The system were developed to cater problems while using social micropayment system, whereby most of the system available are complex to used, and (requester or payer) must know the account number before doing transaction.

2. Better cater social micropayment in social network environment. Seller can share links to his/her friends in social network(facebook, twitter, blog, etc) or share short URL for payment in email or forums. If the person doesn’t have access to either services, details/link can be sent through text messages.

3. Ability to request money from others by using email, text messages or by sending links using Social Network system. Besides, it can cater problems to send/accept from multiple person.

Screen Layout
———————-
1. The layout design has been posted in Mockup

Inputs
———————-
1. Forms. The system will be form for 3 purposes.
– Registering Form. Add new user into the system.
– Transaction Form. Form that will be used for each transaction.
– Edit Tranasction Form. This can be used by user to ammend details of transaction
– Edit User Form. This can be used by user to ammend user details.

2. Buttons. Buttons will implement closely with forms as submit mechanism.

3. Checkbox. This input will be used in 3 occasion; on checking amount, sending through email and sending details in text messages. The checkbox will be implement using javascript. Whenever checkbox is ticked(triggered), textfield input will be shown. For example, if the user triggered a checkbox to send links through email, a textfield will be appear, and the user can insert the email addresses.

4. Dropdown-List. This input type will be used for selecting type of credit/debit card. This will be easier for user to choose rather than typing into textfield.

Output
———————-
1. Onscreen Output
– The system will displayed on screen status for each success or fail operation. For example, after the payer click a link in social network, the payer will be redirected to the QuidLink System. In the system, the payer will key-in bank details. If the payment has successfully being done, there will a message(green color) on screen, saying that “payment completed”. Otherwise, an

2. Printed Output
– This output will be available for user(requester or payer) to keep as proof of transaction has been generate or payment being done. For example, after the payer click a link in social network, the payer will be redirected to the QuidLink System. In the system, the payer will key-in bank details. If the payment has successfully being done, there will be a printer(or pdf) icon; which indicate the user can download the file or print it as proof of payment.

Validation
———————-
1. User validation. The user need to login into the system, and the system will verify by matching username and password; and 2 level authentication between password and security passphrase.

2. Complete Registration. In this part, the system will check the forms, ensure that all required field are not empty, before continue to store data into the database.

3. Checking for equal amount. The requester(or seller) can select checkbox/tickbox to tell the system that the equal amount being set for each person. Thus, only single link should be provide to share to the payer.

4. Checking Details. This is crucial part for social micropayment system. This steps ensure to counterfit money laundring action. The system will only allow £2500 to be transferred, and 10 transaction within a week.

Payer

5. Cheking Balance with Bank. The system will check with the bank, to ensure that the payer has sufficent amount left in the account, before proceed to pay.

6. Payment trial. The system will count for each times the payer tries to make a payment. If the system detected that the payer fails to complete after 3rd attempt, the system will automatically block the user for certain period. And at the same time, a report will be generate and send to adminstrator. This steps were taken as part of security option, to prevent intrusion or bruteforce attack into the system.

Error Messages
——————–
1. User validation. Error username or passwords. The system will not mentioned specificly if it’s username or password. Because it will allow user to continue guessing.

2. Complete Registration. Incomplete registration. There’s some empty field in the form, that require to be inserted by the user.

3. Checking Details. Error – You have reached weekly limit or you have reached limit of transaction.

Payer
4. Checking Balance with Bank. Incomplete transaction – Incomplete amount in account. Please contact your bank provider if any mistakes or problems.

5. Payment Trial. Transaction fails. You have attempt more than 3 times, your account will be block for certain period. Contact your bank for any mistakes or problems.

Modelling diagrams
———————
1. UML Diagram has been post in Refer UML & flow-chart

Hardware
———————
1. Server – Specification has been post in System Specification and Prices is Costing
2. Computers – 4 Computers will be used for development purposes.

Software
———————

1. Visual Studio 2013 – using Microsoft ASP.net. The system will be fully programmed by using .Net language because of user friendly, and good community support for development.

2. MS SQL will be used as Database Software used to store all the data regarding user, transaction, etc.
3. Notepad++
4. Adobe Package – For web designer to create mockup, samples, and marketing purposes.

testing design
———————-
design phase
-usability testing. The usability testing will be done twice, once in the design phase, and again during the development phase. In design phase, usability testing will
-browser compatibility. One of crucial test phase to ensure that the system working, and the interface are identical when being opened in different browser. Most of the time, the testing and adjustment will focus on IE browser.
-accessibility testing. Another important testing to make sure that the system provides short-cut key as an alternative, text magnification as well other accessibility feature is functional as expected. This testing is to make sure that those with disablity can use the system with less hasle.

development.
-security testing. The team will hire a penetration-testing group, that will try to breach the system, find security flaws, as well helps development group to patch loopholes.
-usability testing. During the second test, the testing team will collect input from user based on their experience on using the system, problems and suggestion that will help improve