| fullrecord |
[{"key": "dc.contributor.advisor", "value": "Sepp\u00e4nen, Ville", "language": "", "element": "contributor", "qualifier": "advisor", "schema": "dc"}, {"key": "dc.contributor.author", "value": "Lehoj\u00e4rvi, Jaana", "language": "", "element": "contributor", "qualifier": "author", "schema": "dc"}, {"key": "dc.date.accessioned", "value": "2016-03-11T06:50:10Z", "language": "", "element": "date", "qualifier": "accessioned", "schema": "dc"}, {"key": "dc.date.available", "value": "2016-03-11T06:50:10Z", "language": "", "element": "date", "qualifier": "available", "schema": "dc"}, {"key": "dc.date.issued", "value": "2016", "language": "", "element": "date", "qualifier": "issued", "schema": "dc"}, {"key": "dc.identifier.uri", "value": "https://jyx.jyu.fi/handle/123456789/49037", "language": "", "element": "identifier", "qualifier": "uri", "schema": "dc"}, {"key": "dc.description.abstract", "value": "Teknisen velan m\u00e4\u00e4r\u00e4\u00e4 nykyisiss\u00e4 ohjelmistoissa ei tiedet\u00e4 tarkasti, eik\u00e4 ole\r\ntarkkaa tietoa my\u00f6sk\u00e4\u00e4n sen hinnasta, mutta globaalin IT-velan on ennustettu\r\nmahdollisesti nousevan yhteen triljoonaan dollariin vuoden 2015 aikana. Teknisen\r\nvelan vaikutukset taas ulottuvat kaikkiin ohjelmistotuotantoyrityksiin ja\r\nniiden kautta k\u00e4ytt\u00e4jiin ja n\u00e4in ollen koko ymp\u00e4r\u00f6iv\u00e4\u00e4n maailman. Tutkielmassa\r\nk\u00e4sitell\u00e4\u00e4n teknist\u00e4 velkaa, mit\u00e4 tekninen velka on, mist\u00e4 teknisen velan hallinnointi\r\nkoostuu ja kuinka teknist\u00e4 velkaa hallinnoidaan. Tutkielman tutkimusmenetelm\u00e4n\u00e4\r\non kirjallisuuskatsaus, jonka kautta asioita k\u00e4sitell\u00e4\u00e4n. Teknisen\r\nvelan metafora on esitelty jo 1990-luvulla, jolloin sen perusteena oli h\u00e4t\u00e4isesti\r\ntehty koodi. T\u00e4m\u00e4n j\u00e4lkeen metaforaa, ja m\u00e4\u00e4ritelm\u00e4\u00e4 yleisesti, on laajennettu\r\nkoskemaan l\u00e4hes kaikkia ohjelmistotuotantoon kuuluvia asioita ja t\u00e4t\u00e4kin\r\nlaajemmin. Yleist\u00e4en voitaneen sanoa, ett\u00e4 tekninen velka on jokin ohjelmistossa\r\noleva tai siihen liittyv\u00e4 asia, joka haittaa sujuvaa ohjelmiston jatkokehityst\u00e4\r\ntai yll\u00e4pitoa ja lis\u00e4ksi sill\u00e4 on merkitt\u00e4v\u00e4 rahallinen vaikutus. Toisaalta tekninen\r\nvelka on hyvin monitahoinen, vivahteikas ja hankalakin asia, johon ei l\u00f6ydy\r\nyht\u00e4 yksiselitteist\u00e4 vastausta, vaan se on aina riippuvainen my\u00f6s kontekstista,\r\njossa sit\u00e4 k\u00e4ytet\u00e4\u00e4n. On hyv\u00e4 my\u00f6s huomata, ett\u00e4 teknist\u00e4 velkaa syntyy kaikilla\r\norganisaation tasoilla ja ett\u00e4 tekninen velka on koko organisaation yhteinen\r\nasia. Teknisen velan hallinnoinnilla hoidetaan ja seurataan muun muassa teknisten\r\nvelkojen hinnan muodostumista, priorisointia, takaisinmaksua ja koron\r\nkasvua. Teknisen velan hallinnointi n\u00e4hd\u00e4\u00e4n hyvin t\u00e4rke\u00e4n\u00e4 v\u00e4lineen\u00e4 hallita\r\nniin ohjelmistojen laatua kuin niiden kustannuksiakin, unohtamatta kilpailutilanteita\r\nja liiketoiminnallisia strategioita. Teknisen velan hallinnointiin on v\u00e4h\u00e4nlaisesti\r\nty\u00f6kaluja, eiv\u00e4tk\u00e4 ne kata kaikkia hallinnoinnin osa-alueita. Toisaalta\r\nse, mill\u00e4 v\u00e4lineill\u00e4 hallinnointia hoidetaan, ei lopulta ole ratkaisevaa, kunhan\r\nkaikki osapuolet ovat aina tietoisia teknisen velan kulloisestakin tilanteesta.\r\nTutkielman lopputuloksena ovat yleiskuvaukset teknisest\u00e4 velasta, sen hallinnoinnista\r\nsek\u00e4 n\u00e4iden merkityksest\u00e4.", "language": "fi", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.abstract", "value": "The amount of the technical debt in existing software is not known, and there is\r\nno accurate information on either of its price, but it has been estimated that the\r\nglobal IT debt has potential to rise to one trillion dollars in 2015. Implications of\r\ntechnical debt are reaching out to all software engineering companies and\r\nthrough them to the surrounding world. This thesis concerns technical debt and\r\ntechnical debt management. Research method used in this thesis is a literature\r\nreview, through which the issues will be addressed. Technical debt metaphor\r\nhas been introduced already in the 1990s, when it based on the \u2018not-so-good\u2019\r\ncode. After this, the metaphor, and the definition in general, has been extended\r\nto almost all matters falling within the software development process and even\r\nmore broadly. In general, it can be said that the technical debt is any issue in the\r\nsoftware or any related issue that hampers the smooth software further development\r\nor its maintenance, and in addition, that issue has a significant financial\r\nimpact. On the other hand, the technical debt is very complex, nuanced and a\r\ndifficult subject. Technical debt is also always dependent on the contexts in\r\nwhich it is used. It is also very important to notice that technical debt can be\r\ncaused by all levels of an organization. Technical debt management is used for\r\nexample to handle technical debt principal, prioritization, repayment and interest\r\nrate growth. Management of technical debt is seen as a very important tool\r\nto manage both software quality and its costs, not forgetting the competition\r\nconditions and business strategies. The management of technical debt has only\r\nfew tools, and those do not cover all areas of technical debt management. On\r\nthe other hand, it is not important which tools are used to manage technical\r\ndebt, as long as all stakeholders are always aware of the situation with the respective\r\ntechnical debt. As a result, this thesis gives general descriptions of the\r\ntechnical debt and its management with associated activities.", "language": "en", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Submitted using Plone Publishing form by Jaana Lehoj\u00e4rvi (jamaleho) on 2016-03-11 06:50:10.127373. Form: Kandidaatintutkielma -lomake (https://kirjasto.jyu.fi/julkaisut/julkaisulomakkeet/kandin-tutkielma-lomake). JyX data: [jyx_publishing-allowed (fi) =True]", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Submitted by jyx lomake-julkaisija (jyx-julkaisija.group@korppi.jyu.fi) on 2016-03-11T06:50:10Z\r\nNo. of bitstreams: 2\r\nURN:NBN:fi:jyu-201603111821.pdf: 270019 bytes, checksum: 26cc721ea3d4a00533b6b2a7298d9ecf (MD5)\r\nlicense.html: 4823 bytes, checksum: e7887c89460e88b08941c1d5d181bd38 (MD5)", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Made available in DSpace on 2016-03-11T06:50:10Z (GMT). No. of bitstreams: 2\r\nURN:NBN:fi:jyu-201603111821.pdf: 270019 bytes, checksum: 26cc721ea3d4a00533b6b2a7298d9ecf (MD5)\r\nlicense.html: 4823 bytes, checksum: e7887c89460e88b08941c1d5d181bd38 (MD5)\r\n Previous issue date: 2016", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.format.extent", "value": "37", "language": "", "element": "format", "qualifier": "extent", "schema": "dc"}, {"key": "dc.language.iso", "value": "fin", "language": "", "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.subject.other", "value": "teknisen velan hallinnointi", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.title", "value": "Tekninen velka hallinnoinnin n\u00e4k\u00f6kulmasta : tunnusta, tunnista ja rajoita", "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-201603111821", "language": "", "element": "identifier", "qualifier": "urn", "schema": "dc"}, {"key": "dc.type.ontasot", "value": "Kandidaatintutkielma", "language": "fi", "element": "type", "qualifier": "ontasot", "schema": "dc"}, {"key": "dc.type.ontasot", "value": "Bachelor's thesis", "language": "en", "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": "University of Jyv\u00e4skyl\u00e4", "language": "en", "element": "contributor", "qualifier": "organization", "schema": "dc"}, {"key": "dc.contributor.organization", "value": "Jyv\u00e4skyl\u00e4n yliopisto", "language": "fi", "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": "dc.date.updated", "value": "2016-03-11T06:50:11Z", "language": "", "element": "date", "qualifier": "updated", "schema": "dc"}, {"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": "fi", "element": "rights", "qualifier": "accesslevel", "schema": "dc"}, {"key": "dc.type.publication", "value": "bachelorThesis", "language": null, "element": "type", "qualifier": "publication", "schema": "dc"}, {"key": "dc.rights.url", "value": "https://rightsstatements.org/page/InC/1.0/", "language": null, "element": "rights", "qualifier": "url", "schema": "dc"}]
|