TECHNICAL CONSIDERATIONS

2.1. Software Product Perspective

Projects time could be enough if we know the project materials very well before the project implementations. Learning through the way, wants more time. So because of that, we needed to set limits to the functionality of the system. Also besides our part, the project needed more time and more specific details in the overall for implementation. Our part handled the all needed process just in time but it would be much more functional if we had more time.

2.2. Software Product Functions

As it was stated before, our language choice was PHP and when we started searching the most efficient way of using it, we found out about frameworks. The PHP had a lot of framework options and we needed to search for the most useful one. In the end, the choice was LARAVEL because it requires clean coding, use on API connection and it has better database support. Another product function decision was to choose the most efficient database for the project. As a result of our search, we decided that the most compatible database is MYSQL with PHP.

2.3. User Classes and Characteristics

There are two types of user in the system.

• Parents

• Childs

All users can see their transaction records and also can filter by the date. Parent user can see the other users’ information. It also works the same way in the failed transaction part. Except this part shows only failed transaction details. User can see the photographic evidence at these pages. All users can make a transaction with new transaction page for themselves.

2.4. Operating Environment

The system will be operated with web browsers such as Chrome, Firefox, Opera, etc. Our web server is Apache and located in the Raspberry Pi 3 B+. It must have a composer, PHP, Laravel configurations.

2.5 Design and Implementation Constraints

Software implementation platform with PHPStorm, Visual Studio Code. Software implementation with PHP, Laravel, HTML, CSS, Javascript. Mockaroo.com for testing. Database Management System Apache Web Server for Raspberry. Diagrams with Lucidchart, Draw.io

2.6 Assumptions and Dependencies

The user must have connected the Raspberry and the device itself in the same 3G or Wi-Fi. They must be in the same network. .