| fullrecord |
[{"key": "dc.contributor.advisor", "value": "Sepp\u00e4nen, Ville", "language": "", "element": "contributor", "qualifier": "advisor", "schema": "dc"}, {"key": "dc.contributor.author", "value": "Lokka, Aleksi", "language": "", "element": "contributor", "qualifier": "author", "schema": "dc"}, {"key": "dc.date.accessioned", "value": "2020-12-07T13:05:54Z", "language": null, "element": "date", "qualifier": "accessioned", "schema": "dc"}, {"key": "dc.date.available", "value": "2020-12-07T13:05:54Z", "language": null, "element": "date", "qualifier": "available", "schema": "dc"}, {"key": "dc.date.issued", "value": "2020", "language": "", "element": "date", "qualifier": "issued", "schema": "dc"}, {"key": "dc.identifier.uri", "value": "https://jyx.jyu.fi/handle/123456789/72998", "language": null, "element": "identifier", "qualifier": "uri", "schema": "dc"}, {"key": "dc.description.abstract", "value": "Liiketoiminnan ymp\u00e4rist\u00f6jen ja yritysj\u00e4rjestelmien k\u00e4ytt\u00e4jien vaatimusten kehittyess\u00e4 jatkuvasti kiihtyv\u00e4ll\u00e4 tahdilla yritysj\u00e4rjestelmien toimittajien on kehitett\u00e4v\u00e4 tuotteitaan yh\u00e4 nopeammin, samalla s\u00e4ilytt\u00e4en ohjelmistojen korkean laadun. Vastatakseen n\u00e4ihin vaatimuksiin, ohjelmistoyritykset ovat viimeisen vuosikymmenen aikana ottaneet k\u00e4ytt\u00f6\u00f6n jatkuvana toimittamisena tunnetun ohjelmistotuotannon menetelm\u00e4n, jossa ohjelmisto pidet\u00e4\u00e4n jatkuvasti julkaisukelpoisena. Tietyt ohjelmistotyypit, kuten toiminnanohjausj\u00e4rjestelm\u00e4t, joilla yritykset hallinnoivat kaikkia keskeisi\u00e4 liiketoiminnan osa-alueitaan, eiv\u00e4t kuitenkaan erityisesti sovellu jatkuvasti toimitettaviksi niiden toiminnan kriittisyyden, laajuuden, tai monimutkaisuuden vuoksi. Samat vaatimukset koskettavat kuitenkin toiminnanohjausj\u00e4rjestelmien toimittajia kuin muitakin ohjelmistotoimittajia, mink\u00e4 vuoksi my\u00f6s toiminnanohjausj\u00e4rjestelmien toimittajat pyrkiv\u00e4t liitt\u00e4m\u00e4\u00e4n jatkuvan toimittamisen menetelmi\u00e4 osaksi ohjelmistokehityst\u00e4\u00e4n.\nT\u00e4m\u00e4n tutkimuksen tavoitteena on tunnistaa ja analysoida pienten ja keskisuurien toiminnanohjausj\u00e4rjestelmien toimittajien haasteita jatkuvan toimittamisen k\u00e4ytt\u00f6\u00f6nottoon liittyen. Tutkimus on jaettu kahteen osaan: kirjallisuuskatsaukseen ja empiiriseen laadulliseen tutkimukseen, jossa haastateltiin viitt\u00e4 alan asiantuntijaa, jotka edustivat nelj\u00e4\u00e4 eri j\u00e4rjestelm\u00e4toimittajaa. Tutkimuksen tuloksena esitell\u00e4\u00e4n viitekehys, joka sis\u00e4lt\u00e4\u00e4 yhteens\u00e4 12 jatkuvan toimittamisen k\u00e4ytt\u00f6\u00f6noton haastetta luokiteltuna viiteen erilliseen, mutta toisiinsa liittyv\u00e4\u00e4n teemaan.", "language": "fi", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.abstract", "value": "As the business environments and the requirements of enterprise software users are evolving increasingly faster, enterprise system vendor organizations have to develop their products increasingly faster, while maintaining a high level of software quality. To address these demands, software companies have in the recent decade adopted a software engineering practice known as Continuous Delivery (CD), in which the software is maintained in a releasable state, but not deployed necessarily automatically. However, there are certain application domains that do not facilitate the adoption of Continuous Delivery, such as Enterprise Resource Planning (ERP) systems, as they are mission-critical, large, and complex software systems designed to manage all central business functions of an organization, yet the ERP system vendors are facing the same demands as other software vendors and are therefore seeking to adopt the Continuous Delivery practice in their development activities.\nThe objective of this study is to identify and analyze the challenges related to adoption of Continuous Delivery practice in small to medium sized Enterprise Resource Planning (ERP) system vendors. The study is divided into two sections: a literature review of previous research, and an empirical qualitative study, in which five industry professionals representing four organizations were interviewed. As a result, a framework consisting of 12 identified Continuous Delivery adoption challenges classified into five separate, but interconnected challenge themes is presented.", "language": "en", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Submitted by Paivi Vuorio (paelvuor@jyu.fi) on 2020-12-07T13:05:54Z\nNo. of bitstreams: 0", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Made available in DSpace on 2020-12-07T13:05:54Z (GMT). No. of bitstreams: 0\n Previous issue date: 2020", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.format.extent", "value": "70", "language": "", "element": "format", "qualifier": "extent", "schema": "dc"}, {"key": "dc.language.iso", "value": "eng", "language": null, "element": "language", "qualifier": "iso", "schema": "dc"}, {"key": "dc.rights", "value": "In Copyright", "language": "en", "element": "rights", "qualifier": null, "schema": "dc"}, {"key": "dc.subject.other", "value": "continuous delivery", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.title", "value": "Continuous Delivery adoption challenges for small and medium sized ERP system vendors", "language": "", "element": "title", "qualifier": null, "schema": "dc"}, {"key": "dc.type", "value": "master thesis", "language": null, "element": "type", "qualifier": null, "schema": "dc"}, {"key": "dc.identifier.urn", "value": "URN:NBN:fi:jyu-202012076945", "language": "", "element": "identifier", "qualifier": "urn", "schema": "dc"}, {"key": "dc.type.ontasot", "value": "Master\u2019s thesis", "language": "en", "element": "type", "qualifier": "ontasot", "schema": "dc"}, {"key": "dc.type.ontasot", "value": "Pro gradu -tutkielma", "language": "fi", "element": "type", "qualifier": "ontasot", "schema": "dc"}, {"key": "dc.contributor.faculty", "value": "Informaatioteknologian tiedekunta", "language": "fi", "element": "contributor", "qualifier": "faculty", "schema": "dc"}, {"key": "dc.contributor.faculty", "value": "Faculty of Information Technology", "language": "en", "element": "contributor", "qualifier": "faculty", "schema": "dc"}, {"key": "dc.contributor.department", "value": "Informaatioteknologia", "language": "fi", "element": "contributor", "qualifier": "department", "schema": "dc"}, {"key": "dc.contributor.department", "value": "Information Technology", "language": "en", "element": "contributor", "qualifier": "department", "schema": "dc"}, {"key": "dc.contributor.organization", "value": "Jyv\u00e4skyl\u00e4n yliopisto", "language": "fi", "element": "contributor", "qualifier": "organization", "schema": "dc"}, {"key": "dc.contributor.organization", "value": "University of Jyv\u00e4skyl\u00e4", "language": "en", "element": "contributor", "qualifier": "organization", "schema": "dc"}, {"key": "dc.subject.discipline", "value": "Tietoj\u00e4rjestelm\u00e4tiede", "language": "fi", "element": "subject", "qualifier": "discipline", "schema": "dc"}, {"key": "dc.subject.discipline", "value": "Information Systems Science", "language": "en", "element": "subject", "qualifier": "discipline", "schema": "dc"}, {"key": "yvv.contractresearch.funding", "value": "0", "language": "", "element": "contractresearch", "qualifier": "funding", "schema": "yvv"}, {"key": "dc.type.coar", "value": "http://purl.org/coar/resource_type/c_bdcc", "language": null, "element": "type", "qualifier": "coar", "schema": "dc"}, {"key": "dc.rights.accesslevel", "value": "openAccess", "language": null, "element": "rights", "qualifier": "accesslevel", "schema": "dc"}, {"key": "dc.type.publication", "value": "masterThesis", "language": null, "element": "type", "qualifier": "publication", "schema": "dc"}, {"key": "dc.subject.oppiainekoodi", "value": "601", "language": "", "element": "subject", "qualifier": "oppiainekoodi", "schema": "dc"}, {"key": "dc.subject.yso", "value": "ohjelmistokehitys", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "ohjelmistotuotanto", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "toiminnanohjausj\u00e4rjestelm\u00e4t", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "software development", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "software engineering", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "enterprise resource planning systems", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.rights.url", "value": "https://rightsstatements.org/page/InC/1.0/", "language": null, "element": "rights", "qualifier": "url", "schema": "dc"}]
|