Building an app with OutSystems : learning materials
Zamora Lopez, Elina-Maria (2022)
Zamora Lopez, Elina-Maria
2022
All rights reserved. This publication is copyrighted. You may download, display and print it for Your own personal use. Commercial use is prohibited.
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:amk-2022120526494
https://urn.fi/URN:NBN:fi:amk-2022120526494
Tiivistelmä
The thesis aims to develop a simple to-do list application on OutSystems' low-code platform and create learning material from this for HAMK's English-language OutSystems-related course, which is based on OutSystems' Reactive Web Developer certification path.
In addition to low-code, no-code and high-code are discussed in the theory part, the history of low-code is looked at a little, and the concept and phenomenon of citizen development are discussed. In addition to these, OutSystems, OutSystems Service Studio 11 with its features, and the different stages of development with Service Studio are discussed.
In the practical part, the design process of the application is described in terms of the development work, and the main points are discussed in detail, also with screenshots. The application has been deliberately kept simple so that the student gets an idea of how easy low-code can be. The development work is handled by main stages, starting from starting the work by creating the entities/databases, continuing to making the first screens using the information initially brought into the application, and ending with finishing and publishing.
The result of the work is a description of creating a simple application using OutSystems' Service Studio 11 application, as well as different learning materials for the course. The reader should get a basic understanding of how OutSystems works and an understanding of developing a simple application. Teachers receive material to teach the lesson and distribute it to the students.
The development of the application was simple and straightforward, and the biggest challenge was to keep the finished application reasonable in scope. However, the purpose is also to show that low-code development is simple.
The finished application works as intended. In the application, it is not currently possible to delete already marked tasks. Still, it could be considered a challenge for students to develop the application itself further and if they want to add other features besides deletion.
In addition to low-code, no-code and high-code are discussed in the theory part, the history of low-code is looked at a little, and the concept and phenomenon of citizen development are discussed. In addition to these, OutSystems, OutSystems Service Studio 11 with its features, and the different stages of development with Service Studio are discussed.
In the practical part, the design process of the application is described in terms of the development work, and the main points are discussed in detail, also with screenshots. The application has been deliberately kept simple so that the student gets an idea of how easy low-code can be. The development work is handled by main stages, starting from starting the work by creating the entities/databases, continuing to making the first screens using the information initially brought into the application, and ending with finishing and publishing.
The result of the work is a description of creating a simple application using OutSystems' Service Studio 11 application, as well as different learning materials for the course. The reader should get a basic understanding of how OutSystems works and an understanding of developing a simple application. Teachers receive material to teach the lesson and distribute it to the students.
The development of the application was simple and straightforward, and the biggest challenge was to keep the finished application reasonable in scope. However, the purpose is also to show that low-code development is simple.
The finished application works as intended. In the application, it is not currently possible to delete already marked tasks. Still, it could be considered a challenge for students to develop the application itself further and if they want to add other features besides deletion.