| fullrecord |
[{"key": "dc.contributor.advisor", "value": "Kujala, Tuomo", "language": "", "element": "contributor", "qualifier": "advisor", "schema": "dc"}, {"key": "dc.contributor.author", "value": "Yl\u00f6nen, Janna", "language": "", "element": "contributor", "qualifier": "author", "schema": "dc"}, {"key": "dc.date.accessioned", "value": "2022-08-25T05:23:34Z", "language": null, "element": "date", "qualifier": "accessioned", "schema": "dc"}, {"key": "dc.date.available", "value": "2022-08-25T05:23:34Z", "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/82801", "language": null, "element": "identifier", "qualifier": "uri", "schema": "dc"}, {"key": "dc.description.abstract", "value": "T\u00e4m\u00e4n tutkimuksen tarkoituksena on kuvata kahden k\u00e4ytt\u00e4j\u00e4vaatimusten ker\u00e4ysmenetelm\u00e4n, haastattelujen ja \u00e4\u00e4neen ajattelun toteutus, ker\u00e4tyn materiaalin analysointi, siit\u00e4 k\u00e4ytt\u00e4j\u00e4vaatimusten johtaminen k\u00e4ytett\u00e4v\u00e4ksi j\u00e4rjestelm\u00e4n jatkokehityksess\u00e4 sek\u00e4 lopulta vertailla menetelmien tuloksia.\nKaikkiaan 8 istuntoa j\u00e4rjestettiin verkkokokouksina, jotka nauhoitettiin. J\u00e4rjestelm\u00e4 oli kaikille osallistujille ennest\u00e4\u00e4n tuttu ja jokaisessa istunnossa toteutettiin molemmat menetelm\u00e4t. Tallennettu materiaali analysoitiin siten, ett\u00e4 k\u00e4ytt\u00e4jien puheesta ja toimista j\u00e4rjestelm\u00e4ss\u00e4 pyrittiin tunnistamaan j\u00e4rjestelm\u00e4\u00e4n liittyvi\u00e4 haasteita. Haasteita tarkasteltiin sen perusteella mik\u00e4 voisi olla niiden taustalla oleva ongelma tai mihin ongelmiin ne voisivat johtaa. T\u00e4m\u00e4n j\u00e4lkeen ongelmista johdettiin ehdotuksia k\u00e4ytt\u00e4j\u00e4vaatimuksiksi, jotka voisivat toimia ratkaisuna l\u00f6ydettyihin ongelmakohtiin. Lopuksi sek\u00e4 ongelmat ett\u00e4 k\u00e4ytt\u00e4j\u00e4vaatimukset jaettiin kategorioihin ja laskettiin.\nOsallistujat olivat puheliaampia haastatteluissa, vaikka heit\u00e4 ohjeistettiin ja kannustettiin kertomaan ajatuksistaan \u00e4\u00e4neen ajattelu -menetelm\u00e4n teht\u00e4vi\u00e4 suorittaessaan. Kokonaism\u00e4\u00e4r\u00e4lt\u00e4\u00e4n enemm\u00e4n k\u00e4ytt\u00e4j\u00e4vaatimuksia saatiin ker\u00e4tty\u00e4 haastatteluista esimerkiksi Prosessit-kategoriaan, johon luokiteltiin vaatimuksia, jotka liittyv\u00e4t j\u00e4rjestelm\u00e4\u00e4n ja sit\u00e4 ymp\u00e4r\u00f6iviin prosesseihin. \u00c4\u00e4neen ajattelun avulla l\u00f6ydettiin enemm\u00e4n j\u00e4rjestelm\u00e4n k\u00e4ytett\u00e4vyyteen liittyvi\u00e4 k\u00e4ytt\u00e4j\u00e4vaatimuksia, osallistujien muistaessa ja kertoessa j\u00e4rjestelm\u00e4\u00e4n liittyvist\u00e4 ongelmista paremmin heid\u00e4n samalla k\u00e4ytt\u00e4ess\u00e4\u00e4n j\u00e4rjestelm\u00e4\u00e4. My\u00f6s vain tarkkailemalla osallistujien toimia voitiin huomata ongelmia ja vikoja j\u00e4rjestelm\u00e4ss\u00e4, joita ei olisi tullut esille haastatteluissa. N\u00e4in n\u00e4iden kahden menetelm\u00e4n voitiin todeta t\u00e4ydent\u00e4v\u00e4n toisiaan.\nKer\u00e4ttyjen k\u00e4ytt\u00e4j\u00e4vaatimusten m\u00e4\u00e4r\u00e4 oli suuri, vaikka siihen osallistui vain 8 henkil\u00f6\u00e4. Yksi syy haastattelu ja \u00e4\u00e4neen ajattelu -menetelmien valinnalle oli, ett\u00e4 ne eiv\u00e4t vaadi suurta otoskokoa ker\u00e4ttyjen tietojen monipuolisuuden vuoksi. T\u00e4m\u00e4 voitiin my\u00f6s t\u00e4ss\u00e4 tutkimuksessa todeta, varsinkin menetelm\u00e4t n\u00e4in yhdistett\u00e4ess\u00e4.", "language": "fi", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.abstract", "value": "The purpose of this study is to describe the implementation of two user requirements elicitation methods, Interviews and Protocol Analysis, analyse the gathered material and to derive problems and user requirements from it to be used in a system upgrade, and to finally compare the results from the methods.\nA total of 8 sessions were conducted as online meetings that were recorded. All of the participants were previously familiar with the system and each in session, both of the methods were executed. The recorded material was analysed so that issues with the system or the surrounding processes were identified from the users\u2019 input. The issues were considered based on what could be the underlying problem causing them or what problems they could lead to. Finally, user requirements were derived from the problems, suggesting what would solve the problems. The problems and user requirements were then divided into categories and their frequencies were counted.\nThe participants were more talkative in the conducted Interviews even though they were instructed and encouraged for thinking aloud while performing the Protocol Analysis tasks. The Interviews yielded more user requirements in total, and for an example, to categories such as Processes where we focused on finding out the processes surrounding and related to the system. With Protocol Analysis we gathered more user requirements related to the system\u2019s usability, as the participants were more likely to remember and point out problems with the system while interacting with it. Problems and bugs in the system could also be recognised by only observing the participants\u2019 actions in the system which would not have come up in the interview. This way the two methods were seen to complement each other.\nThe number of gathered user requirements was extensive even with only 8 participants. As it was one reason for selecting the Interviews and Protocol Analysis methods, this study also demonstrated that the two methods do not require a large sample size due to the richness of the collected data, especially when combined.", "language": "en", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Submitted by Paivi Vuorio (paelvuor@jyu.fi) on 2022-08-25T05:23:34Z\nNo. of bitstreams: 0", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Made available in DSpace on 2022-08-25T05:23:34Z (GMT). No. of bitstreams: 0\n Previous issue date: 2022", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.format.extent", "value": "62", "language": "", "element": "format", "qualifier": "extent", "schema": "dc"}, {"key": "dc.format.mimetype", "value": "application/pdf", "language": null, "element": "format", "qualifier": "mimetype", "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": "user requirements elicitation", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "elicitation methods", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "protocol analysis", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "selecting", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.title", "value": "User requirements elicitation with interviews and protocol analysis methods", "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-202208254334", "language": "", "element": "identifier", "qualifier": "urn", "schema": "dc"}, {"key": "dc.type.ontasot", "value": "Pro gradu -tutkielma", "language": "fi", "element": "type", "qualifier": "ontasot", "schema": "dc"}, {"key": "dc.type.ontasot", "value": "Master\u2019s 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": "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.collaborator", "value": "business", "language": "", "element": "contractresearch", "qualifier": "collaborator", "schema": "yvv"}, {"key": "yvv.contractresearch.funding", "value": "0", "language": "", "element": "contractresearch", "qualifier": "funding", "schema": "yvv"}, {"key": "yvv.contractresearch.initiative", "value": "student", "language": "", "element": "contractresearch", "qualifier": "initiative", "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": "vaatimustenhallinta", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "vertailu", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "tuotekehitys", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "k\u00e4ytett\u00e4vyys", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "haastattelut", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "requirements engineering", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "comparison", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "product development", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "usability", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "interviews", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.format.content", "value": "fulltext", "language": null, "element": "format", "qualifier": "content", "schema": "dc"}, {"key": "dc.rights.url", "value": "https://rightsstatements.org/page/InC/1.0/", "language": null, "element": "rights", "qualifier": "url", "schema": "dc"}, {"key": "dc.type.okm", "value": "G2", "language": null, "element": "type", "qualifier": "okm", "schema": "dc"}]
|