| fullrecord |
[{"key": "dc.contributor.advisor", "value": "Sepp\u00e4nen, Ville", "language": "", "element": "contributor", "qualifier": "advisor", "schema": "dc"}, {"key": "dc.contributor.author", "value": "Lampinen, Anu", "language": "", "element": "contributor", "qualifier": "author", "schema": "dc"}, {"key": "dc.date.accessioned", "value": "2020-09-21T07:17:06Z", "language": null, "element": "date", "qualifier": "accessioned", "schema": "dc"}, {"key": "dc.date.available", "value": "2020-09-21T07:17:06Z", "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/71820", "language": null, "element": "identifier", "qualifier": "uri", "schema": "dc"}, {"key": "dc.description.abstract", "value": "T\u00e4ss\u00e4 tapaustutkimuksessa esitettiin vaatimusm\u00e4\u00e4rittelyprosessi ja havainnollistettiin, miten se esiintyy kolmessa yleisess\u00e4 tietoj\u00e4rjestelm\u00e4n kehitt\u00e4misprosessissa: vaihejakomalleissa, RUP-kehyksess\u00e4 ja Scrum-prosessissa. Tutkielmassa avattiin vaatimusm\u00e4\u00e4rittelyprosessin vaiheita ja pureuduttiin niist\u00e4 yhteen, vaatimusten esitt\u00e4miseen. Yleisimm\u00e4t vaatimusten esitt\u00e4mistavat, kuten k\u00e4ytt\u00f6tapaus, sekvenssikaavio sek\u00e4 tilakaavio, esiteltiin, ja niit\u00e4 vertailtiin toisiinsa yleisyyden ja formaalisuuden perusteella. T\u00e4m\u00e4n j\u00e4lkeen tutkimuksessa kuvattiin tietoj\u00e4rjestelm\u00e4n yll\u00e4pidon konteksti ja yll\u00e4pitoon liittyvien teht\u00e4vien tyypit. Lis\u00e4ksi tarkasteltiin kolmea eri yll\u00e4pitoprosessia: pikakorjausmallia, iteratiivista parannusmallia ja IEEE 1219-1998 -standardia yll\u00e4pidolle. Yll\u00e4pitoprosessin esittelyn j\u00e4lkeen esitettiin yleisi\u00e4 tietoj\u00e4rjestelm\u00e4n yll\u00e4pitoon liittyvi\u00e4 haasteita sek\u00e4 dokumentaation hy\u00f6dynt\u00e4mist\u00e4 yll\u00e4pidossa. Tutkimuksessa tutkittiin viitt\u00e4 erilaista yll\u00e4pidossa olevaa j\u00e4rjestelm\u00e4\u00e4, niiden yll\u00e4pidon organisointia sek\u00e4 dokumentaation hy\u00f6dynt\u00e4mist\u00e4 yll\u00e4pidon aikana. Ominaisuuksiltaan erilaiset tietoj\u00e4rjestelm\u00e4n noudattelivat erilaista yll\u00e4pitoprosessia ja hy\u00f6dynsiv\u00e4t sen aikana eri vaatimusdokumentteja. Yleisimmin hy\u00f6dynnytetyt dokumentit olivat k\u00e4ytt\u00f6tapaukset ja k\u00e4ytt\u00f6liittym\u00e4n eritasoiset kuvaukset. Dokumenttien t\u00e4rkein teht\u00e4v\u00e4 oli toimia yll\u00e4pidon aikaisten muutosten l\u00e4ht\u00f6kohtana. Dokumentteja hy\u00f6dynnettiin my\u00f6s tietoj\u00e4rjestelm\u00e4n opettelussa ja tiedon l\u00e4hteen\u00e4. Dokumenttien hy\u00f6dynt\u00e4mist\u00e4 vaikeutti erilaiset ongelmat. Ongelmia yll\u00e4pidossa tuottivat mm. puutteellinen tai puuttuva dokumentaatio ja vaikeaselkoiset tai heikkolaatuiset dokumentit. Ongelmien korjaaminen ei vaatisi ihmeit\u00e4, vaan ongelmat olisivat selvitett\u00e4viss\u00e4 systemaattisella otteella ja hyv\u00e4ll\u00e4 harkinnalla.", "language": "fi", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.abstract", "value": "This case study presented the requirements engineering process in general and related to three well-known software engineering processes, life cycle model, Rational Unified Process and Scrum process. This thesis elaborated the phases of requirements engineering process and focused on one part of it, requirements presentation. A set of commonly used requirements presentation forms, such as use case diagram, use case, sequence diagram and state diagram, were presented and compared on the basis generality and formality. After that, software maintenance was introduced. The study then described the context of software maintenance and different types of maintenance tasks. In addition, three different maintenance processes were studied: quick-fix model, iterative-enhancement model and the IEEE 1219-1998 standard for software maintenance. After presenting the software maintenance process, general challenges related to software maintenance and the exploitation of documentation in maintenance were presented. This thesis studied five different software under maintenance. The characteristics of these software varied, they used different maintenance process and exploited different kind of documentation. The most commonly used documents were use cases and user interface descriptions at different levels. The most important function of documents was to serve as a starting point for maintenance tasks. They were also used in learning a new software and as a source of information. Some issues were found that complicated the exploitation of documents. Problems in maintenance had been caused by e.g. incomplete documentation, complete lack of documentation and documents that are hard to understand or of poor quality. Correcting these problems would not require miracles, but they could be overcome with a systematic approach and good judgement.", "language": "en", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Submitted by Paivi Vuorio (paelvuor@jyu.fi) on 2020-09-21T07:17:06Z\nNo. of bitstreams: 0", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Made available in DSpace on 2020-09-21T07:17:06Z (GMT). No. of bitstreams: 0\n Previous issue date: 2020", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.format.extent", "value": "77", "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": "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.title", "value": "Tietoj\u00e4rjestelm\u00e4vaatimusdokumenttien hy\u00f6dynt\u00e4minen yll\u00e4pidossa : tapaustutkimus", "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-202009215906", "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.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": "vaatimukset", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "tietoj\u00e4rjestelm\u00e4t", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "yll\u00e4pito", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "vaatimusm\u00e4\u00e4rittelyt", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "dokumentointi", "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"}]
|