Diploma thesis is devote to creation commercial and administration internet portal for selling and managing products. By creating means specify user's requirement from concrete company, created application architecture and implement all of this. Developed portal is a SPA Web application type based on JavaScript library named React and PHP Symfony framework.

<p>This report follows the process of developing a website for cognitive behavioural therapy using the web development framework Symfony. The purpose was to find out if it is appropriate to use Symfony to ease development and maintenance of a website for therapy. For this to be true the framework had to be able to help create a website that was secure, user-friendly and easy to maintain.</p><p>The website was developed using several features of the framework including database abstraction, automatic code generation and URL-rewriting. A plugin was used to enhance the security by adding a complete solution for user authentication. The website was tested by using built-in test functionality of the framework that could run test on functions or emulating a browser visiting the website.</p><p>During the development the framework was tested and evaluated. The worst drawback turned out to be Symfonys steep learning curve, its security solution that only worked if the website was installed correctly and its slow loading time. Except those faults the framework performed well and was easy to use ones the initial learning time was over.</p><p> </p>

The aim of this work has been to suggest e-commerce implementations to a partially complete web shop using the script language PHP: Hypertext Preprocessor and the related framework Symfony. The motivation behind the work has been the rapidly changing requirements which web sites have seen during the past few years as a result of the introduction of smart phones and tablets. This in turn led to the company behind the web shop Persiennbutiken needing a new web site.   In addition to taking the latest web design trends into consideration, the work is also studying behavioural economics in order to provide a solution which not only work, but also helps increasing profit with the help of clever technology. The importance of relevant statistics when developing new features is also highlighted and how to gather that statistics in a non-intrusive way.   Each suggested implementation is measured against quite a few performance measures emphasising functionality, performance and security. All very important aspects when building a web shop as is seen in this report.   The results indicate that the suggested implementations are able to fulfil the set requirements to a varying degree with different estimated development time. This leads to a recommended final solution which tries to balance development time versus features, relying on existing libraries where possible.   Finally, the report also suggests a new way of dealing with database cache invalidation when using Symfony in conjunction with the object-relational mapping tool Doctrine.

This report follows the process of developing a website for cognitive behavioural therapy using the web development framework Symfony. The purpose was to find out if it is appropriate to use Symfony to ease development and maintenance of a website for therapy. For this to be true the framework had to be able to help create a website that was secure, user-friendly and easy to maintain. The website was developed using several features of the framework including database abstraction, automatic code generation and URL-rewriting. A plugin was used to enhance the security by adding a complete solution for user authentication. The website was tested by using built-in test functionality of the framework that could run test on functions or emulating a browser visiting the website. During the development the framework was tested and evaluated. The worst drawback turned out to be Symfonys steep learning curve, its security solution that only worked if the website was installed correctly and its slow loading time. Except those faults the framework performed well and was easy to use ones the initial learning time was over.

Dažnai būna taip, kad internetiniame tinklapyje yra daug svarbių duomenų, tačiau jie nėra pateikti lengvai suprantamoje formoje. Būtent pateiktos informacijos interaktyvumo stoka, sąlygoja ne tik esamos informacijos sudėtingesnį suvokimą ar įsisavinimą, bet taip pat tiesiogiai siejasi su lankytojų srauto mažėjimu. Pastarosios situacijos buvimas ypač aktualus internetiniams tinklapiams, kuriuose kaupiama ir publikuojama daug specifinės srities duomenų. Šiame magistriniame darbe siekiama Exhibit įrankį pritaikyti korektiškam ir pilnavertiškam informacinės sistemos duomenų bazėje kaupiamų duomenų publikavimui ir vizualizavimui. Esamų sprendimų analizė leido atskleisti, kad Exhibit pritaikytas dirbti su statine, tai yra failuose saugoma informacija. Be to Exhibit vidinės duomenų struktūros formavimas gana ilgai užtrunka [Zhao et al., 2008]. Taigi, magistriniame darbe surastos ir pritaikytos priemonės leidžiančios Exhibit įrankį pritaikyti dažnai kintančios ir nuolatos atsinaujinančios informacijos atvaizdavimui. O taip pat, patobulintas metodas, kuris leidžia greičiau suformuoti vidinę Exhibit duomenų struktūrą. / There is common situation where are much of important data on the website, but the data are given in an inconvenient form to use. The lack of information interactivity determines complicated understanding and acquisition of the given information, also it directly determines the decline of website visitors. The being of the mentioned situation is topical to websites where collecting and publishing a lot of specific data. An aim of this research is to find a way to realize qualitatively publishing and visualization of the data stored in information system database. An analysis of the present decisions showed that Exhibit is great tool to solve existing problem. But this tool have a limitation. Exhibit is working with static (stored in files) information. Also creation of internal Exhibit data structure takes too long time. In this research were found and adapted facilities that let to use an Exhibit tool for publishing dynamic information. Also was improved method for faster internal Exhibit data structure creation.

Context Considering the rising popularity of Node.js and the fact that a very largepercentage of websites today are based on PHP, there is a need to understand thesimilarities and differences between these languages.  Comparing their most popularserver-side  frameworks  is  valuable  to  developers  in  seeing  the  advantages  of  usingone over the other - for both user and developer. Objectives In this study we investigate how Express.js and Symfony compareagainst each other in terms of installation, functionality and performance. Thiswill provide understanding of when to use JavaScript frameworks and when to usePHP frameworks for server-side projects. Method A literature study was done to answer what similarities and differences existbetween the frameworks. To explore how they compare in performance when mul-tiple users are actively sending requests to the server, an experiment was performed.Another experiment was carried out to measure performance in CPU-intensive ap-plications. Results The result shows that both frameworks are quick to install and it is a fastprocess to setup a basic application. Both frameworks are highly cuztomizable andconfigurable because they are supported by a big open source community and theonly difference is that Express is supportive of single-page applications which Sym-fony can not do on its own. Express was better than Symfony to handle multipleconcurrent users when it comes to CPU usage and time it takes for the requests. For100 and 1000 requests, Express CPU usage varied more than Symfony, but at 10000and 100000 it varied less. In all tests with concurrent users, Express was faster. Testsperformed in the second experiment showed that Symfony is only able to use 1 corewhen making the requests while Express is able to use multiple cores. Even thoughSymfony was limited by 1 core it was faster, most likely because it used more memory. Conclusions This study shows that there are more similarities than differencesbetween Express and Symfony. They both strive for high customization and highflexibility with a goal to make tedious tasks easier for the developer. Both rely onopen source modules and components to add additional functionality. Out of thebox, Express comes with less functionality as it strives to be minimalistic. However,to install Symfony is slightly quicker than Express and requires no code. Thereare currently more daily downloads of Express than Symfony, and therefore it’sconsidered more popular. It’s supportive of JavaScript-only for front- and back-endand is able to handle more concurrent users than Symfony, and is therefore betterfor high-traffic websites. But Symfony is able to handle CPU-intensive applicationsbetter than Express, and is able to load in large data sets faster, making it a goodchoice for applications with a lot of data and high CPU usage.

The objective of this study is to evaluate performance of four popular PHP frameworks Laravel, Symfony, CodeIgniter and Phalcon together with the plain PHP. The decision of making this study was based on the fact that there is a lack of comparison tests between the most popular PHP frameworks. Visiting the official websites of these frameworks, the first thing to notice is the slogans that have been made by the core teams. The majority of these slogans contain quality attributes like speed and high performance. As a developer looking for performance in your next project, choosing the right PHP framework by these slogans is not that easy. Therefor, the performance of these frameworks is put to the test. And to do that, three experiments are conducted in which five functionally equivalent PHP applications are developed and used as targets. One version of these applications represents the plain PHP and the other four represent the four mentioned frameworks. The experiments are conducted in two sessions. The first session deals with the execution time and the stack trace measurements while the second one is covering the measurement of the memory usage consumption. The result outcome of these experiments has been analyzed and interpreted in order to expose the performance of the targeted frameworks. The experiment results prove that the targeted frameworks perform differently compared with each other and the PHP stack. Plain PHP and Phalcon are performing well while the other three frameworks have both mediocre and low performance.

Master thesis deals with a comparison of two web application frameworks in PHP. The aim of this work is to provide a comprehensive view of the possibilities, differences and advantages of the selected frameworks. The main source for comparison is sample web applications that demonstrate these possibilities. For a comprehensive comparison, various criteria were chosen to analyze the properties of frameworks. These criteria are divided into five categories. Technology support examines the compatibility of framework for different versions of the platform. The most important and most widespread category is the analysis of options for creation of web applications, which discusses the most common tasks in developing applications and how frameworks approaches it. Other categories are design and architecture of framework, testing and general support for developers, which analyzes both online and offline sources of information used to learn and solve problems using the selected framework . Comparison results based on above mentioned criteria can help developers when choosing a modern web development framework for PHP platform.

The objective of this thesis is analysis, design and development of an application used for the Process-State Diagram (PSD). Purpose of this thesis is to make PSD tool available for as many users as possible in order to make it a standard tool for managers and analysts. The theoretical part analyzes the basic functionality that should be included in the first version of this app and the strategy and the method of implementation. An important part of the analysis is to compare the three types of applications: desktop, web and mobile; and their relevance to a given problem. The practical part includes the actual implementation and the necessary steps to deploy the application.

This thesis deals with all web application development phases, analyses key activities and common issues of each phase and shows suitable principals and practices used to solve those issues. Described principals and practices do not only solve partial development problems just as isolated segments, but also takes into account overall web application solution. This thesis targets mostly junior developers, who through it might connect to their theoretical knowledge gained during studies and also gain knowledge representing the base knowledge of each developer. This thesis includes examples, findings and benefits resulting from an application of stated principals and practices during Leduvio platform development.