The purpose of this thesis was to find and create a better solution for handling customer data in Botisto. During this project, it was decided that the customer information system would be built from scratch. The system was developed using the PHP programming language and the MySQL database management system using the Waterfall development model.
The project was successful and the software was put into use at the Botisto store.
About Botisto
Development goal
Included in scope
Out of scope
Customer process in Botisto shop
The next step is for the customer to choose the model and leather he likes. The order is then sent to the Botisto factory where the shoes will be manufactured. When the shoes are made, the shoes are delivered to the customer or alternatively the shoes can be collected from the Botisto store.
When the project was started, different approaches were considered to achieve the development objective.
Requirements for the solution
Proprietary software
Developing new software from scratch
What the models do not tell are the people and roles involved in software projects.
Waterfall
Agile
Why Waterfall model was chosen?
Why PHP and MySQL combination was chosen?
What is PHP?
Brief history of PHP
Lerdorf continued the development of PHP and the users of PHP also contributed to the PHP development. After a few years and releases, the PHP has aged from a script collection to a programming language.
PHP Frameworks
What is MySQL?
Brief history of MySQL
The Swedish company TcX developed its own database server software because they were dissatisfied with the speed of the commercial products available.
Other development approaches considered?
At Haaga-Helia University of Applied Sciences, thesis work is always carried out as a project. The project plan consisted of the following phases which were executed sequentially during the project.
Requirements phase
Design phase
Before the design document for the software was written, the basic idea of the software construction was drawn up on paper. In addition to Microsoft Office tools, Microsoft Visio was used to create the diagram found in the software design document. Screenshots were added to the software design document after the layout was created in the software implementation phase.
Implementation phase
Verification phase
After the document was prepared, the software was tested as described in the test plan. The software has passed the tests and functionality and non-functionality requirements specified in the software requirements document (in Appendix A). After the verification phase, the software developed in this project was put into use in the Botisto store.
After the software was in use, an interview was conducted (referred to in the next chapter).
Evaluation of software requirement analysis phase
Evaluation of software design phase
Evaluation of software implementation phase
Evaluation of software verification phase
Customer feedback on the project
Evaluation of development methods and tools
Evaluation of project management
Impediments during the project
Evaluation of the learning during the project
The software supports the Botisto business as it facilitates the day-to-day work of the entire organization. During this analysis, it would be good to review the software as part of the customer process and consider whether its support for day-to-day work could be improved. It should also be considered how the software can provide more value for the company.
When a customer enters the Botisto store, the customer's feet are scanned with a foot scanning device. Now the customer can place an order, which will be processed and sent to Botisto's factory. Until now, customer information was written on paper by store employees.
To increase the use of customer data and speed up daily work, a customer information handling system should be developed. They will usually be the ones to register new customers into the system when the customer decides to measure their feet. Botisto management will be able to use this information when processing customer shoe orders.
The customer data is collected after the customer has decided to scan his feet. After the customer is selected from the customer list, the employees and managers can view all the information stored for the customer. After selecting the customer from the customer list, the employees and managers can change the information stored for the customer.
Postal Code Customer Postal Code Text Yes 12 Country Code Country code where. The software should be easy to use as no user manual will be created during this project. The software should be simple enough that performance is not an issue.
The user interface of the software will be implemented in English, as all employees at Botisto have the necessary knowledge of English. The style will be adapted from the Botisto website when the software is ready to ship.
Database schema
Table descriptions
Column descriptions
Customer table
Country table
Language table
SQL script to create tables
CONSTRAINT `FK_LANGUAGE_CODE_1` FOREIGN KEY (`LAN- GUAGE_CODE`) REFERENCE `LANGUAGE` (`LANGUAGE_CODE`) ) ENGINE=INNODB DEFAULT CHARSET=UTF8;. After successful login, user can navigate from each page to first page, customer registration page and customer list page. The Customer View and Customer Change pages can only be accessed from the Customer List page.
The page requested by the customer will include for header, menu, footer and db_sql files.
Front page screenshot
New customer screenshot
Customer list screenshot
View customer screenshot
Modify customer screenshot
The purpose of testing is to ensure that there are no errors in the software. In software testing, it is very rare that all possible scenarios and functionalities are tested in the application. In most cases, the number of combinations is practically infinite, so it is not really possible to test everything.
The test volume should be set to a level that should be good enough for the applications intended use. Time and budget applicable to the project should also be considered. Botisto's customer information processing system is not business critical in the sense that it does not disrupt business if it is down.
Because the software in its first release does not have user input validation, use cases that are known to fail are excluded from testing. This means that all mandatory data will be filled in when creating a new customer.
Test sequence
Question: How has the software changed the daily work in the store (front/back office). Before we had the functionality, we had to manage our customer information manually and there was always a risk of problems arising due to human error. It is clear that we still have to do our work with care, but in general it is much easier now.
Employees also like it because they don't have to deal with so much paper anymore. It also gives a more professional image of our business to our customers when we use software instead of "Mom and Pop Store" style paper and pen. Management's life has also been made easier because before it was necessary to go to the store to check some customer information, but today we just log into our website to update customer information.
There are now seven people using the software and no one has had any problems with the software. Because its web-based software is also convenient to access your information anywhere. However, this has its downsides: I once needed some information from one of our clients, but I couldn't get the information because my internet connection wasn't working properly.
It is always possible that when we add customer information to the software, the software will not work because the internet connection is not working.
