EMAIL:ETHELCOFIE@YAHOO.COM

.Net Version of the Payment Web Service

Tutorial Link

ABSTRACT
The proposed project is a system to provide pseudo online bank facilities to the University of Brighton Computing, Mathematical and Information Sciences School. The proposed project would provide CMIS department students with a simulated online bank/credit card system that they would be able to access when developing to systems that required online payment mechanisms.
The System would ideally be a web service for which the clients can access or implement.
The project would be twofold; the practical aspect is the actual development of a deliverable system as stated in the introduction and then the theoretical part which is the evaluation of the technologies that would be used in the development of the pseudo online payment system.
The proposed System would be developed in the two major technologies that are used in web services development .These technologies being the Microsoft.NET platform and the Java platform. Two versions of the system will be developed in these two platforms so as to enable the developer to evaluate them and assess how they perform in web service development and implementation.
Therefore as part of the proposed project the pseudo online bank system is developed in both the .NET and Java Platform on these initial three principles:
? Ease of development.
? In-depth analysis on how the above-mentioned platforms implement security and the tools that each platform provides for the implementation of security.
? Both platforms claim to implement Service Oriented Architecture, the proposed project will aim to research on the SOA-oriented ness of the .NET and Java attempting to discuss which is much more SOA oriented in its overall architecture and development approach.
The deliverable system would require the development of database that would keep track of credit/debit card accounts, and usage and this would be developed using SQL Server 2000.

INTRODUCTION

PROJECT REQUIREMENTS
Functional requirements:
According to the Client specifications the payment web service is to functionally fulfil the requirements below:
? Students should be able to use the web service to simulate their payments for customers
? There should be an Admin web front where Students can Register a Bank account
? The Admin web front should give students the permission to edit customer details
? Students should be allowed to create multiple accounts to mimic customers
? The System should be able to detect that a customer account has low funds or is does not have an account and react appropriately
? The System should produce confirmation results once payments have been successfully implemented
? Give back to user receipt of results (Payment successful or unsuccessful)
? The Students should be able to use the web front to view the Transactions details of customer accounts
Non functional requirements
? The Payment System should works on the Servers on the Computing Mathematical and Information Sciences computing environment
? Usability: the web services and the web front should be accessible via a web address
? Reliability: The web services are based on standards and proven technology like Java, .Net and Sql Server 2005. Hence, it should be dependable, robust and safe to the extent of the maturity of these state of the art technologies
? Performance: It should have reasonable performance as per web services and , with respect to Web Services lookup and invocation, as other deployed Web Services applications
? Adaptability: The Front end web application is likely to be modified to include more functionality along with the web service hence both applications must be easily adaptable and change and upgraded to newer evolving web standards.
? Maintainability: It should be upgradeable to the latest standard in web portal and Web Services implementation, without any degradation in performance
? Implementation: the web Application front end will be written in JSP and JavaScript the web services are to be developed in Java and .Net C#. It will also make use of WSDL, SOAP, BPEL, Sql Server 2005 and JDBC, compliant with the prevailing practices in similar development projects. The application development will be NetBeans for Java and Visual studio for integrated development environment
? Interoperability: The web services should be interoperable enough to be accessed by most web service platforms
[http://glycomics.ccrc.uga.edu/stargate/as2/Non-FunctionalRequirement.doc]

External Interface Requirements
Since the Web services would have to interface with student?s project they should adhere to these minimum requirements.
Java Client/Web Consumer
Client must be built with source level set at least to J2EE 1.5
.Net Client/Web Consumer
Due to problems with backward compatibility in .Net framework .The Client must be developed in .Net framework 3.0 .