Optimizing Invoice Management: A Case Study of PT. Madina Mitra Teknik's Transition to a Laravel-Based Information System

,


INTRODUCTION
A business in the information technology industry, PT.Madina Mitra Teknik is situated in Depok City, specifically at Rukan Pesona View Jl.Ir. H. Juanda.One of the administrative tasks carried out by the corporate management division is keeping track of invoice entrance and exit of The Collection and Billing department of PT.Madina Mitra Teknik handles data processing for outgoing invoices and payments.
However, there are still several issues with this process, such as the continued use of Microsoft Excel for recording and updating purchase orders, which frequently results in duplicate data, The progress invoice has been released.This will be a challenge if management requests a report as soon as possible and the information is not current and accurate.

Laravel Project Organization
• app/ This folder serves as a default location for written or configured code; all application project code, ranging from logic and configuration to other topics, is stored here.There are several other folders and files within the app folder, which will be discussed in more detail below.
• bootstrap/ This folder includes Laravel framework procedure files; several files in this folder should only be modified by seasoned Laravel users.
• vendors/ This folder contains all of the composer packages that we use in our application; it also contains the framework files for Laravel.
• public/ This folder contains assets that we use to store CSS, Javascript, Image files, or the necessary files (usually closely related to View -to build the front end).

• gitattributes
This file is a standard configuration file for version control systems, specifically Git, which are very popular these days.This file contains some details about which folders Git will ignore.

• phpunit.xml
This file contains the default PHP Laravel Unit Testing configuration; it also handles loading composer dependencies and runs all tests in the app/tests directory.artisan This file is a file that functions to execute or run CLI artisan commands for Laravel.
• composer.jsonand composer.lockThese two files contain information about the composer packages that we will use for application requirements.
• server.phpThis file contains procedures for running Laravel with an internal web server introduced in PHP version 5.4.
Model-View-Controller (MVC) is an approach to application development that divides data (model), display/frontend (View), and application logic (Controller).Based on these divisions, MVC builds applications by separating their main components, which include data manipulation, user interface, and control.The model is used to process queries or manipulate data to and from a database, while View is closely related to the interface/frontend of a web display, including HTML, CSS, and JS, as well as client data.A controller is the logic of a web, bridging communication between Model and View.Laravel has the following benefits:

• Expressive
Laravel is an expressive PHP framework; this means that, despite never having studied or used it, a programmer is expected to understand the syntax when they see it.Laravel adopts a different strategy by eliminating flagging parameters and opting to create two distinct functions.

• Easy to use
The Eloquent ORM is one of the things that makes Laravel so easy to use.Laravel has minimal complexity when it comes to routing issues.Creating a website is just a matter of sending a request for page x and expecting the user to respond.In such cases, Laravel uses a very basic routing principle.
• Easily accessible Laravel was developed with the most comprehensive documentation available.The Code Developer from Laravel itself is dedicated to always including complete documentation whenever the latest version is released.
One of the drawbacks of using Laravel is that it contains default files, such as vendors, which should not be removed arbitrarily because doing so will result in a very large website.In addition, installing and downloading the Laravel library requires an internet connection.

• Login Page
The files for the login data input system design in the form of user and password can be seen in the image below.The login page is a form for the Invoice Recording system's main page.As seen in the image below, the user's page design is a collection for managing system users.

The purpose of this black box testing
The purpose of this black box testing method is to identify functional errors in the program.The invoice recording information system program is being implemented using the black box testing method, which is a program test that prioritizes testing the functional requirements of a program.Black box testing is conducted by giving the program several inputs, which are then processed by the application to produce output that is desired and also by the program's basic function.The method is to identify functional errors in the program.The invoice recording information system program is being implemented using the black box testing method, which is a program test that prioritizes testing the functional requirements of a program.Black box testing is conducted by giving the program several inputs, which are then processed by the application to produce output that is desired and also follows the program's basic function.Enter the password and username that correspond to the user that registered.
Click the "Login" button.
The main course will appear on the login menu.

In line with expectations
Valid 2 Enter a password and username that differ from those you registered.
Click the "Login" button.
The error message "Login Failed!" In line with expectations Valid 3 You entered your username but left out your password.
Click the "Login" button.
The message "Please fill in this field" displays.
In line with expectations Valid 4 e-exit button Click the "Logout" button.
The Dashboard is where the system reacts.shows statistics from search results

As predicted Valid
3 View the report list on the following page.
Select "Next" from the menu.
On the following page, there is a report list.

As predicted Valid 4
Go back to the "Previous" page.
Select "Previous" Go back to the report's earlier page.
As predicted Valid 5 modifies the "show entries" that are shown On "Show," 10 turns into 25.
There were initially 10 to 25 entries on the report list page.

As predicted Valid 6
Get the report's data.
Click the "Export" button.

downloaded report information
As predicted Valid

Testing Testing
Conclusio n 1 Choose the "Payment" menu.
Select the "Payment" menu.
Payment information is displayed.

Valid 2
Click on the "Add Payment" option.
Go to "Add" payment.
A payment form appears.

Valid 3
Enter payment details.
Activate the "Plus" button.

Stored information As predicted
Valid 4

Changing payment details
Press the "Update" button.

Adapt stored payment information
As predicted

Valid 5
View the invoice list on the following page.
Activate the "Next" button.
The next page displays the payment list.

Valid 6
Go back to the previous payment page.
Select the "Previous" button.Go back to the payment page from earlier.
As predicted

Valid 7
Look up payment information.
Activate the "Search" button.

Shows statistics from search results
As predicted

As predicted Valid
3 View the report list on the following page.
Activate the "Next" button.
On the following page, there is a report list.

4
Go back to the "Previous" page.
Select the "Previous" button.
Go back to the report's earlier page.

Testing -Testing Conclusion 1
Choose the "Report" menu.
Go to the "Report" menu.
A report data list shows up.

As predicted
Valid 2 Look up report information.
Activate the "Search" button.
shows statistics from search results

As predicted Valid
Examine the report's next-page list.
Activate the "Next" button.
On the following page, there is a report list.

As predicted Valid 4
Go back to the "Previous" page.
Select the "Previous" button.Go back to the report's earlier page.
As predicted Valid 5 modifies the "show entries" that are shown On "Show," 10 turns into 25.
Page 10 of the original report list is now 25 entries.

As predicted Valid 6
Get the report's data.Click the "Export" button.

Functional Testing
Three browsers have been chosen as comparisons for the system function testing, which is conducted by opening the page containing the function and simulating the system.Following functional testing, the following test results were obtained:

Figure 1 .
Figure 1.Process flow of MVC

Figure 2 .
Figure 2. Laravel simulation of the MVC procedure

Figure 3 .
Figure 3. UI/UX Login Data Input System

Figure 6 .
Figure 6.UI/UX the payment Page

Figure
Figure 8. UI/UX Users Page

A Case Study of PT. Madina Mitra Teknik's Transition to a Laravel-Based Information System
Rinaldo, Juwari, Diantoro, Rohman, Sitorus 53 | Digitus : Journal of Computer Science Applications Insight

Table 5 : Test Table for Black Box Collection Viewing Reports No Scenario Testing Test Case Results Expected Results Testing Testing Conclusion Optimizing Invoice Management: A Case Study of PT. Madina Mitra Teknik's Transition to a Laravel-Based Information System Rinaldo
, Juwari, Diantoro, Rohman, Sitorus 55 | Digitus : Journal of Computer Science Applications Insight

Table 6 . Black Box Collection Testing Table Manage Users
56 | Digitus : Journal of Computer Science Applications Insight

Valid Optimizing Invoice Management: A Case Study of PT. Madina Mitra Teknik's Transition to a Laravel-Based Information System Rinaldo
, Juwari, Diantoro, Rohman, Sitorus 57 | Digitus : Journal of Computer Science Applications Insight