{"id":179,"date":"2014-03-26T11:43:18","date_gmt":"2014-03-26T11:43:18","guid":{"rendered":"http:\/\/blog.soton.ac.uk\/nabr\/?p=179"},"modified":"2014-05-02T16:38:20","modified_gmt":"2014-05-02T15:38:20","slug":"requirements-specifications","status":"publish","type":"post","link":"https:\/\/blog.soton.ac.uk\/nabr\/2014\/03\/26\/requirements-specifications\/","title":{"rendered":"Requirements Specifications"},"content":{"rendered":"\n\n\n\n\n\n\n\n
Scope of the system<\/td>\nThe system is intended to be a social payment system. It will allow the user to create a transaction (single payer or multiple payers) and send the transaction links to others to proceed with the payment. It is not intended to be use just to send payments to others. The transaction must be set by the receiver first in order for others to pay.<\/td>\n<\/tr>\n
Objectives<\/td>\nCreate single or multiple transactions for each user.User can share the transaction link through social networks, emails or as SMS.<\/p>\n

Allow payers to pay directly after following the link while giving them the option of registering or not.<\/p>\n

Provide transaction history for each user to allow management and track the status of each transaction.<\/td>\n<\/tr>\n

Timing<\/td>\nThe project shall start on 27th February and be completed in two months. Meetings will be done in weekly bases to manage the progress.<\/td>\n<\/tr>\n
Inputs<\/td>\nThe user registers in the system website providing his<\/p>\n
    \n
  • Name<\/li>\n
  • Address<\/li>\n
  • Email address<\/li>\n
  • Mobile number<\/li>\n
  • Bank account details.<\/li>\n<\/ul>\n

    To create a transaction the user should provide the following<\/p>\n

      \n
    • Title of the transaction<\/li>\n
    • Description<\/li>\n
    • Type of transaction (Single, Multiple)<\/li>\n
    • Amount<\/li>\n
    • Permission before process check box (Optional)<\/li>\n
    • Share method:\n
        \n
      • Email Address or<\/li>\n
      • Mobile Number or<\/li>\n
      • Share through social network<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n

        Payment:<\/p>\n

          \n
        • Payer has the option to register (not mandatory)\n
            \n
          • Name<\/li>\n
          • Payment method (Credit Card, Debit Card …etc)<\/li>\n
          • Card Details<\/li>\n
          • Email Address<\/li>\n<\/ul>\n<\/li>\n
          • Payment Screen\n
              \n
            • Name<\/li>\n
            • Address<\/li>\n
            • Email Address<\/li>\n
            • Card Number<\/li>\n
            • Security Code<\/li>\n
            • Expiry Month, Year<\/li>\n
            • Confirmation check box<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
Outputs<\/td>\nLink for each transactionConfirmation email for transaction generator<\/p>\n

Confirmation email for payer<\/p>\n

Transactions history and status<\/td>\n<\/tr>\n

Processing requirements<\/td>\nUser (Transaction Issuer):When user registers, the system will verify his banking details by connecting to the bank.System should validate the email address by sending a verification email.System should validate the mobile number by sending verification code.<\/p>\n

Transaction link should be a link with a unique reference number that is generated randomly.
\nUser (Payer):<\/p>\n

When payer submits the payment form, the system will check his banking details and the availability of required amount to pay.<\/p>\n

System will check the validity of the email address by sending an initial email.<\/p>\n

System:<\/p>\n

If the user (transaction issuer) checked the option of \u201cRequired Permission\u201d the payment will not be processed until getting the user approval.<\/p>\n

Payment should be processed after 3 hours to avoid the occurrence of duplicated payments (2 users pay at the same time through the same link).<\/p>\n

Transaction link should refer to \u201cTransaction Closed\u201d after the payment.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n ","protected":false},"excerpt":{"rendered":"

Scope of the system The system is intended to be a social payment system. It will allow the user to create a transaction (single payer or multiple payers) and send the transaction links to others to proceed with the payment. It is not intended to be use just to send payments to others. The transaction must be set by the… Read more → <\/a><\/span><\/p>\n","protected":false},"author":93977,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[720568],"tags":[720540,4020,720611,781883],"class_list":["post-179","post","type-post","status-publish","format-standard","hentry","category-requirements-specifications","tag-payment-system","tag-requirements","tag-social-payment-system","tag-specifications"],"acf":[],"_links":{"self":[{"href":"https:\/\/blog.soton.ac.uk\/nabr\/wp-json\/wp\/v2\/posts\/179","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.soton.ac.uk\/nabr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.soton.ac.uk\/nabr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.soton.ac.uk\/nabr\/wp-json\/wp\/v2\/users\/93977"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.soton.ac.uk\/nabr\/wp-json\/wp\/v2\/comments?post=179"}],"version-history":[{"count":6,"href":"https:\/\/blog.soton.ac.uk\/nabr\/wp-json\/wp\/v2\/posts\/179\/revisions"}],"predecessor-version":[{"id":518,"href":"https:\/\/blog.soton.ac.uk\/nabr\/wp-json\/wp\/v2\/posts\/179\/revisions\/518"}],"wp:attachment":[{"href":"https:\/\/blog.soton.ac.uk\/nabr\/wp-json\/wp\/v2\/media?parent=179"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.soton.ac.uk\/nabr\/wp-json\/wp\/v2\/categories?post=179"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.soton.ac.uk\/nabr\/wp-json\/wp\/v2\/tags?post=179"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}