Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Progressive Web applications för journalföring inom hälso- och socialvård: Mjukvaruarkitekturer för Progressive Web Applications
Jönköping University, School of Engineering, JTH, Computer Science and Informatics.
Jönköping University, School of Engineering, JTH, Computer Science and Informatics.
2018 (Swedish)Independent thesis Basic level (degree of Bachelor), 10 credits / 15 HE creditsStudent thesis
Abstract [en]

The purpose of this study is to examine and compare a small set of software stacks which can be used for a progressive web application to see if one stack is more suitable to build a journaling system with strict requirements on accessibility and traceability.

The study is a comparative case study where the development of a system with different software stacks were compared. First a literature study was conducted to find potential technologies to use. Then interviews were conducted with persons who have used journaling systems within their work to get a clear picture of the essential functionality of a journaling system. The purpose of this was to create a specification of a simple journaling system. This specification was used during the development of two software stacks.

The literature study showed that two databases and two javascript-framework of the researched potential technologies were more suitable than the other technologies. These technologies were then used in the two software stacks where code size and development time was measured.

In the end there was not a big difference between the two software stacks in terms of code size and development time. Though one of the stacks had a small advantage of having a marginally faster development time and smaller code size. The conclusion was that a more comprehensive study should be done to get a more conclusive answer but that the results of this study can be used together with other data as a decision guide when a software stack is chosen for a project for a progressive web application with strict requirements on accessibility and traceability.

A limitation had been set at only choosing two software stacks to compare because the lack of time. Also, the number of features in the finished systems has been limited, because of the lack of time only the essential parts of a journaling system will be included. The study also doesn’t present or take into account all the laws and requirements that affects a journaling system

Place, publisher, year, edition, pages
2018.
National Category
Software Engineering
Identifiers
URN: urn:nbn:se:hj:diva-41124ISRN: JU-JTH-DTA-1-20180054OAI: oai:DiVA.org:hj-41124DiVA, id: diva2:1238361
External cooperation
Carefox AB
Subject / course
JTH, Computer Engineering
Available from: 2018-09-10 Created: 2018-08-13 Last updated: 2018-09-10Bibliographically approved

Open Access in DiVA

fulltext(986 kB)57 downloads
File information
File name FULLTEXT01.pdfFile size 986 kBChecksum SHA-512
158c1fbead84856274618a005f848d784e604326077dbce18d9cfe2fc79feecb5cd15cd59b8c3dcd3b88c9f36d49585a9124f0d0f30666c9ecab1f5aa00e63ad
Type fulltextMimetype application/pdf

By organisation
JTH, Computer Science and Informatics
Software Engineering

Search outside of DiVA

GoogleGoogle Scholar
Total: 57 downloads
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

urn-nbn

Altmetric score

urn-nbn
Total: 192 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf