Show simple item record

dc.contributor.authorde Silva, I
dc.contributor.authorRathnayaka, BMTN
dc.contributor.authorWickramatunga, M
dc.date.accessioned2020-02-06T15:49:47Z
dc.date.available2020-02-06T15:49:47Z
dc.date.issued2018
dc.identifier.urihttp://ir.kdu.ac.lk/handle/345/2521
dc.descriptionArticle Full Texten_US
dc.description.abstractA software project, whatever the size must go through defined stages which known as the Software Development Lifecycle (SDLC). Among five phases of the SDLC the first phase: Requirement Definition needs certain technique to gather requirements and identify functional and non-functional specifications. When conducting a requirement gathering method naturally occurs conflicts. The cause for the conflicts can define as: in single occurrence can be found multiple ideas with different viewpoints. Likely this situation can be called as Rashomon effect. By discussing what are the conflicts occurs when conducting a requirement gathering technique and how Rashomon Effect play on these identified problems, through this paper will discuss about effect and the relationship between Software Development Requirement Gathering Process and Rashomon Effect. Finally, this paper concludes that how to overcome the Rashomon Effect in Software Development Requirement Gathering Process.en_US
dc.language.isoenen_US
dc.subjectRashomon Effecten_US
dc.subjectRequirement gathering processen_US
dc.subjectInterviewen_US
dc.titleThe Rashomon Effect on Software Development Requirement Gathering Processen_US
dc.typeArticle Full Texten_US
dc.identifier.journalKDUIRC-2018en_US
dc.identifier.pgnos293-300en_US


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record