| fullrecord |
[{"key": "dc.contributor.advisor", "value": "Pekkala, Kaisa", "language": "", "element": "contributor", "qualifier": "advisor", "schema": "dc"}, {"key": "dc.contributor.author", "value": "Kenias, Henri", "language": "", "element": "contributor", "qualifier": "author", "schema": "dc"}, {"key": "dc.date.accessioned", "value": "2022-12-21T10:51:46Z", "language": null, "element": "date", "qualifier": "accessioned", "schema": "dc"}, {"key": "dc.date.available", "value": "2022-12-21T10:51:46Z", "language": null, "element": "date", "qualifier": "available", "schema": "dc"}, {"key": "dc.date.issued", "value": "2022", "language": "", "element": "date", "qualifier": "issued", "schema": "dc"}, {"key": "dc.identifier.uri", "value": "https://jyx.jyu.fi/handle/123456789/84538", "language": null, "element": "identifier", "qualifier": "uri", "schema": "dc"}, {"key": "dc.description.abstract", "value": "Hyvien ohjelmistokehityksen k\u00e4yt\u00e4nteiden yhten\u00e4 tarkoituksena voidaan pit\u00e4\u00e4 pyrkimyst\u00e4 minimoida ohjelmiston jatkoty\u00f6st\u00e4miseen k\u00e4ytetty vaiva. Vaikka hyvien k\u00e4yt\u00e4nteiden noudattaminen tuottaakin monia hy\u00f6tyj\u00e4 ohjelmiston elinkaaren edetess\u00e4, eiv\u00e4t n\u00e4m\u00e4 pitk\u00e4aikaiset seuraukset aina ole ilmeisi\u00e4. Monet ohjelmistokehitysty\u00f6n ominaispiirteet, kuten kiireiset aikataulut ja kehitett\u00e4v\u00e4n ohjelmiston jatkuvasti muuttuvat vaatimukset, vaikeuttavatkin hyvien ohjelmistokehityksen k\u00e4yt\u00e4nteiden noudattamista. Kun k\u00e4yt\u00e4nteit\u00e4 ei pystyt\u00e4 noudattamaan, tuotetaan ohjelmistokehitysprosessissa ratkaisuja, jotka voivat lyhyell\u00e4 aikav\u00e4lill\u00e4 tuottaa hy\u00f6ty\u00e4 esimerkiksi ohjelmistokehitysty\u00f6n nopeutumisena. N\u00e4m\u00e4 hy\u00f6dyt saavutetaan kuitenkin j\u00e4tt\u00e4m\u00e4ll\u00e4 jokin hyvien k\u00e4yt\u00e4nteiden mukainen toimenpide toteuttamatta, jonka korvaava puutteellinen toteutus voi aiheuttaa pitk\u00e4ll\u00e4 aikav\u00e4lill\u00e4 erilaisia ongelmia. Ennen kuin toteuttamatta j\u00e4\u00e4nyt hyvien k\u00e4yt\u00e4nteiden mukainen toimenpide on toteutettu, aiheuttaa puutteellinen ratkaisu ohjelmiston ik\u00e4\u00e4ntyess\u00e4 jatkuvasti enemm\u00e4n ongelmia. Lopputu-loksena voivat ohjelmiston yll\u00e4pito ja jatkokehitys muuttua ongelmien takia mahdottomaksi. Edell\u00e4 kuvattua ilmi\u00f6t\u00e4, jossa puutteellisilla kehitysratkaisuilla voidaan tuottaa lyhyen aikav\u00e4lin hy\u00f6ty\u00e4, joka my\u00f6hemmin joudutaan korjaamaan isommilla kustannuksilla, kutsutaan tekniseksi velaksi. Sek\u00e4 tieteellinen yhteis\u00f6 ett\u00e4 ohjelmistoteollisuus tiedostavat teknisen velan hallitsemattoman kertymisen mittavaksi haasteeksi. Oikein hallinnoituna teknist\u00e4 velkaa voidaan kuitenkin kerrytt\u00e4\u00e4 my\u00f6s hallitusti, jolloin ohjelmistokehitysty\u00f6t\u00e4 pystyt\u00e4\u00e4n resursoimaan ja aikatauluttumaan tehokkaammin. T\u00e4m\u00e4 voidaan toteuttaa va-litsemalla lyhyen aikav\u00e4lin hy\u00f6ty\u00e4 tuottavat kohteet harkitusti niiden vaikutukset huomioiden ja huolehtimalla otetun velan takaisinmaksusta ennen sen tuottamien ongelmien kohtuutonta laajenemista. Ohjelmistoteollisuudessa ei kuitenkaan osata soveltaa teknisen velan hallinnoinnin menetelmi\u00e4 ja ty\u00f6kaluja, mink\u00e4 yhten\u00e4 syyn\u00e4 on teknist\u00e4 velkaa koskevan viestinn\u00e4n puute. T\u00e4m\u00e4 tutkielma on kirjallisuuskatsaus, jossa k\u00e4sitell\u00e4\u00e4n teknisen velan hallinnointia ja erityisesti sen viestinn\u00e4n osa-aluetta. Tutkielmassa teknisen velan viestint\u00e4\u00e4 tarkastellaan ohjelmistokehityst\u00e4 harjoittavan organisaation n\u00e4k\u00f6kulmasta. Viestint\u00e4\u00e4 toteuttavat organisaation toimijat jaotellaan vastuutahoihin heid\u00e4n ohjelmistokehityksen ty\u00f6nkuviensa mukaisesti. Tutkielman tarkoituksena on selvitt\u00e4\u00e4, miten vastuutahot voivat toteuttaa kesken\u00e4\u00e4n teknisen velan viestint\u00e4\u00e4. Tutkielman tuloksena on kooste teknisen velan viestint\u00e4\u00e4n k\u00e4ytett\u00e4vist\u00e4 menetelmist\u00e4 ja ty\u00f6kaluista.", "language": "fi", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.abstract", "value": "Software development best practices can be understood as working methods of which one aim is to minimize the effort needed to further develop the software. Although these practices provide many benefits as the software ages, these long-term benefits are not always obvious. Software development industry is characterized by many development hampering aspects, such as tight schedules and ever-changing requirements for the software-in-development, which can make the following of best practices extremely hard. In these cases, it is common to use sub-optimal solutions to quickly get the work done. These solutions may provide short-term benefits for the development process, such as increased productivity, but at the cost of missing the best practices solution. Sub-optimal solutions may cause otherwise avoidable problems in the continued development of the software. These problems cascade as time goes on until either the sub-optimal solution is replaced, or the software has become unmaintainable. This software development phenomenon is called technical debt. Technical debt management is recognized as one of the most critical challenges faced in software development. When technical debt is managed correctly it transforms from an issue into an effective tool, which can be used to resource and schedule development work more efficiently. Current software industry is unable to apply technical debt management methods and tools in a productive way. A central contributor in the current state of technical debt management is the lack of communication about technical debt. This systematic literature review is a study into technical debt management with a focus on technical debt communication, a sub-category of technical debt management. In this study, technical debt communication is researched from a point-of-view of the developer organization. Organization\u2019s personnel practicing technical debt communication are categorized as stakeholders based on their professional roles. The goal of this study is to find out how different stakeholders practice technical debt communication. As a result, a summary of tools and methods used in technical debt communication is presented.", "language": "en", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Submitted by Miia Hakanen (mihakane@jyu.fi) on 2022-12-21T10:51:46Z\nNo. of bitstreams: 0", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Made available in DSpace on 2022-12-21T10:51:46Z (GMT). No. of bitstreams: 0\n Previous issue date: 2022", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.format.extent", "value": "52", "language": "", "element": "format", "qualifier": "extent", "schema": "dc"}, {"key": "dc.language.iso", "value": "fin", "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": "tekninen velka", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.title", "value": "Teknisen velan viestinn\u00e4n menetelm\u00e4t organisaatiossa", "language": "", "element": "title", "qualifier": null, "schema": "dc"}, {"key": "dc.type", "value": "bachelor thesis", "language": null, "element": "type", "qualifier": null, "schema": "dc"}, {"key": "dc.identifier.urn", "value": "URN:NBN:fi:jyu-202212215784", "language": "", "element": "identifier", "qualifier": "urn", "schema": "dc"}, {"key": "dc.type.ontasot", "value": "Bachelor's thesis", "language": "en", "element": "type", "qualifier": "ontasot", "schema": "dc"}, {"key": "dc.type.ontasot", "value": "Kandidaatinty\u00f6", "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_7a1f", "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": "bachelorThesis", "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": "organisaatiot", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "viestint\u00e4", "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"}]
|