IIS Temple Edu Users Pascucci CIS 3342 Project 3

Httpcis Iis2templeeduuserspascuccicis3342cis 3342 Project 3

This project will give you experience working with web services. In this project, you will create a Web Service used by retailers to manage credit card accounts and transactions. You will create a Web Application (ASPX pages) that will be the Web Service Client for the Web Service you will create. Important: only the Web Service can access and use the database. You need to create a Web Application that utilizes a Web Service for a credit card processing gateway.

The Web service will be responsible for working with the database, and it will be responsible for verifying, charging, and searching for credit card accounts. The ASPX page should allow the user to enter credit card information, verification information, and purchase information, and record the credit card transaction. The ASPX page (Web Service Consumer) should not contain any database connection code; it should rely on the Web Service to handle all database actions.

Paper For Above instruction

Developing a comprehensive credit card gateway web service involves meticulous design and implementation, emphasizing security, data integrity, modularity, and usability. By leveraging ASP.NET technologies, this project simulates a real-world retail environment where credit card accounts are managed centrally and transactions are processed securely through web services.

Design and Data Modeling

The backbone of this project is a robust data model that captures all essential information related to credit cards, transactions, and account management. A normalized relational database schema will be designed to facilitate efficient data retrieval and integrity. Tables such as CreditCards, Transactions, and Accounts will form the core, with primary and foreign keys ensuring referential integrity. Additional tables for security measures like verification codes or audit trails could enhance reliability. Proper naming conventions and documentation will be maintained to improve clarity and future scalability.

Component-Based Software Design

Encouraging modularity, classes and components will be created to encapsulate specific functionalities such as account validation, transaction processing, and security operations. For instance, classes like CreditCardAccount, TransactionProcessor, and SecurityManager will be developed. These classes will enable code reuse, simplify testing, and promote separation of concerns. Private helper methods will be used within classes for tasks like account verification and funds charging, ensuring the main methods remain clean and maintainable.

Web Service Development

The Web Service, built with ASMX, will expose methods such as ProcessTransaction, AddAccount, UpdateAccount, and RetrieveTransactions. Each method will accept well-defined parameters, including custom classes representing credit card accounts and transactions. The ProcessTransaction method will accept an array encapsulating all necessary transaction details, perform validations, attempt the transaction, and return an array indicating success, error codes, and timestamp. Proper exception handling will ensure graceful error recovery, and security measures—such as API keys or verification codes—will be integrated to prevent unauthorized access.

Security and Validation

Given the sensitivity of credit card data, security is paramount. The Web Service will implement verification via dynamic security tokens, not hard-coded keys, to prevent fraudulent account creation. Server-side validation will be employed to verify data correctness, including format checks for credit card numbers, expiration dates, and amounts. Transport security protocols like HTTPS will be used to encrypt data during transmission, ensuring confidentiality and integrity.

Web Application (ASPX Pages)

The ASPX-based Web Application will serve as the user interface, providing pages for entering account details, viewing transaction history, and performing transaction operations. Navigation will be designed for a seamless flow, preventing the need for using browser back and forward buttons. The interface will include clear instructions, validation prompts, and error messages to guide users effectively. All database logic will be handled exclusively by the Web Service—meaning the ASPX pages will simply invoke Web Service methods through generated proxies, adhering to the component-based architecture.

Features include:

  • Account management: creating, updating, deactivating accounts
  • Transaction processing: entering credit card info and amount, recording success or failure
  • Retrieval of transaction histories for specific accounts
  • Security and validation controls at the page level

Design principles focus on intuitive navigation, data consistency, security, and the prevention of application crashes through proper exception handling and validation.

Implementation Phases

Initially, development will focus on creating the data model and the Web Service with the necessary methods. Next, components and classes will be implemented for business logic, emphasizing code reuse and security. Then, the ASPX pages will be developed to interact with the Web Service, ensuring user inputs are validated server-side before invoking web methods. Finally, testing will be conducted to verify transaction accuracy, security features, and user experience. Deployment involves publishing the Web Service to a designated folder and referencing it correctly in the client application, with due diligence to prevent class definition issues.

Throughout development, adherence to best practices such as consistent naming conventions, exception handling, input validation, and security protocols will be enforced. This ensures a reliable, scalable, and secure credit card gateway system capable of serving large retail and financial organizations.

References

  • Alzahrani, S., & Gaafar, M. (2020). Design of a Secure Credit Card Processing System. Journal of Information Security, 11(2), 150-165.
  • Gibson, D. (2018). Building Secure Web Services. IEEE Software, 35(1), 76-84.
  • Heiser, S. (2019). Component-Based Design in .NET Applications. Software Engineering Journal, 24(4), 250-264.
  • Kaufman, C., & Perlman, R. (2016). Network Security and Cryptography. Prentice Hall.
  • Marinescu, D. (2017). Software Component Technologies. Springer.
  • Microsoft. (2021). ASP.NET Web Services Documentation. Retrieved from https://docs.microsoft.com/en-us/aspnet/web-services/
  • O’Reilly, T. (2020). Developing Secure Web Applications. Tech Publishing.
  • Patel, V., & Shah, R. (2022). Encryption and Secure Data Transmission in Web Applications. International Journal of Cybersecurity, 8(3), 215-232.
  • Rahman, M., & Sultana, S. (2019). Object-Oriented Design Principles in Web Application Development. ACM Computing Surveys, 44(2), 1-36.
  • Williams, H. (2018). Best Practices for Web Service Security. Network World, 24(4), 45-50.

Related Assignments