Software Development Process Described Through a Case Study

The customer owns a payment gateway service and is developing anti-fraud protection. For this, the customer requires up to 500 simulated users per batch, complete with relevant information and credit card numbers that comply with geographical, payment network, and checksum rules.

Creating a batch of this size manually for every test is a straightforward but time-consuming process. Therefore, a software solution is to be built.

The full requirement can be accessed in the Test Client Data Generation Service.

By analyzing the customer's description, the following characteristics have been identified: Product scope is final and the problem falls into the Repeating Tasks category.

The chosen development approach is the Waterfall development approach, since it is the most reasonable choice when both the problem and solution are clearly known (without the need for continuous feedback).

Having a clear goal that is to be achieved with the software solution, and having chosen a development approach, the requirements and offer can be prepared.

Usually, in cooperation with the customer, both are combined into one document, which serves both as the specification and for legal obligations.

In this case, the customer provided a clearly defined requirement, as is visible in the previous section.

To begin with the technical solution, the code architecture should be chosen. The goal is to apply general conventions and rules that best fit the requirements.

For the complete application, the MVC pattern has been chosen.

In the integration part, modules are loosely coupled, with the TestClientsModule depending on the TestBasicDataModule, TestEmailDataModule, and TestFinanceDataModule.

The responsibilities include CSV generation and process coordination, generating basic data, generating email data, and generating finance data, respectively.

To successfully generate country-specific names and addresses, the 'faker' library is utilized, with localization included.

For credit card generation, an open-source BIN list is utilized, and the Luhn checksum is respected.

Finally, for temporary email services, Temp Mail is utilized.