| fullrecord |
[{"key": "dc.contributor.author", "value": "Tammenoja, Anton", "language": "", "element": "contributor", "qualifier": "author", "schema": "dc"}, {"key": "dc.date.accessioned", "value": "2018-04-26T13:49:33Z", "language": "", "element": "date", "qualifier": "accessioned", "schema": "dc"}, {"key": "dc.date.available", "value": "2018-04-26T13:49:33Z", "language": "", "element": "date", "qualifier": "available", "schema": "dc"}, {"key": "dc.date.issued", "value": "2018", "language": "", "element": "date", "qualifier": "issued", "schema": "dc"}, {"key": "dc.identifier.uri", "value": "https://jyx.jyu.fi/handle/123456789/57779", "language": "", "element": "identifier", "qualifier": "uri", "schema": "dc"}, {"key": "dc.description.abstract", "value": "T\u00e4m\u00e4n tutkielman tarkoituksena on luoda k\u00e4sitys ketter\u00e4st\u00e4 vaatimusm\u00e4\u00e4rittelyst\u00e4 ja siihen liittyvist\u00e4 k\u00e4yt\u00e4nn\u00f6ist\u00e4 ohjelmistoprojekteissa. Vaatimusm\u00e4\u00e4rittelyyn panostaminen voi v\u00e4hent\u00e4\u00e4 suuresti ohjelmistoprojektin j\u00e4lkeist\u00e4 lis\u00e4ty\u00f6t\u00e4 sek\u00e4 parantaa kustannustehokkaasti ohjelmiston eri ominaisuuksia. Muuttuva toimintaymp\u00e4rist\u00f6, jossa monet organisaatiot nykyisin toimivat, aiheuttaa kuitenkin haasteita perinteiselle vaatimusm\u00e4\u00e4rittelylle. Ketter\u00e4 vaatimusm\u00e4\u00e4rittely ja sen k\u00e4yt\u00e4nn\u00f6t pyrkiv\u00e4t tarjoamaan apua n\u00e4ihin haasteisiin ja kartoittamaan asiakkaan tarpeet muuttuvassa toimintaymp\u00e4rist\u00f6ss\u00e4. Ketter\u00e4 vaatimusm\u00e4\u00e4rittely eroaa perinteisest\u00e4 vaatimusm\u00e4\u00e4rittelyst\u00e4 ohjelmistoprojekteissa. Se on jatkuva prosessi, jossa painotetaan v\u00e4h\u00e4ist\u00e4 dokumentointia sek\u00e4 asiakkaan osallistumista kehitysty\u00f6h\u00f6n. Ketter\u00e4 vaatimusm\u00e4\u00e4rittely on perinteisten menetelmien innovaatio, joka sis\u00e4lt\u00e4\u00e4 optimoidun joukon ketteri\u00e4 k\u00e4yt\u00e4nt\u00f6j\u00e4. Tutkielmassa k\u00e4sitell\u00e4\u00e4n nelj\u00e4\u00e4 ketter\u00e4n vaatimusm\u00e4\u00e4rittelyn k\u00e4yt\u00e4nt\u00f6\u00e4, joita ovat kasvokkain kommunikointi, iteratiivinen vaatimusm\u00e4\u00e4rittely, vaatimusten priorisointi ja jatkuva suunnittelu. Vaikka ketter\u00e4n vaatimusm\u00e4\u00e4rittelyn k\u00e4yt\u00e4nn\u00f6t tarjoavat hy\u00f6tyj\u00e4 ohjelmistoprojektien vaatimusm\u00e4\u00e4rittelylle, liittyy niihin my\u00f6s haasteita. Ketter\u00e4n vaatimusm\u00e4\u00e4rittelyn k\u00e4yt\u00e4nn\u00f6t auttavat muuttuvien vaatimusten tilanteissa kehitysprosessin aikana, mutta haasteita voi esiinty\u00e4 muun muassa kustannusten ja aikataulujen kontrolloimisessa. Tutkielma on toteutettu kirjallisuuskatsauksena, johon on pyritty hy\u00f6dynt\u00e4m\u00e4\u00e4n alan laadukasta l\u00e4hdekirjallisuutta.", "language": "fi", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.abstract", "value": "The purpose of this thesis is to create an understanding of agile requirements engineering and its practises in software projects. Devoting effort to requirements engineering can greatly reduce the amount of rework needed after the software project and can cost-effectively improve the qualities of the software system. The changing business environment in which most organizations nowadays operate is challenging traditional requirements engineering. Agile requirements engineering and its practices strive to offer help for these challenges and understand customer\u2019s needs in the dynamic environment. Agile requirements engineering differs from the traditional requirements engineering in software projects. It is an ongoing process which emphasizes minimal documentation and customer participation in the development process. Agile requirements engineering is the innovation of traditional methods which includes an optimized set of agile practises. The thesis discusses four agile requirements engineering practises which are face-to-face communication, iterative requirements engineering, requirements prioritization and continuous planning. Although agile requirements engineering practices offer benefits to the requirements engineering process in software projects, challenges are also associated with them. Agile requirements engineering practises help to deal with changing requirements through the development process, but controlling costs and schedules might cause several challenges. The thesis was conducted as a literature review aiming to use quality source material in the field.", "language": "en", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Submitted using Plone Publishing form by Anton Tammenoja (anmitamm) on 2018-04-26 13:49:32.809426. Form: Kandidaatintutkielma -lomake (https://kirjasto.jyu.fi/julkaisut/julkaisulomakkeet/kandin-tutkielma-lomake). JyX data: [jyx_publishing-allowed (fi) =False]", "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 2018-04-26T13:49:33Z\r\nNo. of bitstreams: 2\r\nURN:NBN:fi:jyu-201804262381.pdf: 365598 bytes, checksum: 58bc94f7ebf3bb345956754f4696a2a1 (MD5)\r\nlicense.html: 1108 bytes, checksum: be0ebfe1d5117b1d217706062ed1a111 (MD5)", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Made available in DSpace on 2018-04-26T13:49:33Z (GMT). No. of bitstreams: 2\r\nURN:NBN:fi:jyu-201804262381.pdf: 365598 bytes, checksum: 58bc94f7ebf3bb345956754f4696a2a1 (MD5)\r\nlicense.html: 1108 bytes, checksum: be0ebfe1d5117b1d217706062ed1a111 (MD5)\r\n Previous issue date: 2018", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.format.extent", "value": "25", "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": "vaatimusm\u00e4\u00e4rittely", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "ketter\u00e4 vaatimusm\u00e4\u00e4rittely", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "ketter\u00e4t menetelm\u00e4t", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.title", "value": "Ketter\u00e4n vaatimusm\u00e4\u00e4rittelyn k\u00e4yt\u00e4nn\u00f6t ohjelmistoprojekteissa", "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-201804262381", "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.department", "value": "Informaatioteknologia", "language": "fi", "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": "", "element": "subject", "qualifier": "discipline", "schema": "dc"}, {"key": "dc.date.updated", "value": "2018-04-26T13:49:33Z", "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": "restrictedAccess", "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"}, {"key": "dc.rights.accessrights", "value": "Aineistoon p\u00e4\u00e4sy\u00e4 on rajoitettu tekij\u00e4noikeussyist\u00e4. Aineisto on luettavissa Jyv\u00e4skyl\u00e4n yliopiston kirjaston arkistoty\u00f6asemalta. Ks. https://kirjasto.jyu.fi/fi/tyoskentelytilat/laitteet-ja-tilat.", "language": "fi", "element": "rights", "qualifier": "accessrights", "schema": "dc"}, {"key": "dc.rights.accessrights", "value": "This material has a restricted access due to copyright reasons. It can be read at the workstation at Jyv\u00e4skyl\u00e4 University Library reserved for the use of archival materials: https://kirjasto.jyu.fi/en/workspaces/facilities.", "language": "en", "element": "rights", "qualifier": "accessrights", "schema": "dc"}]
|