dc.contributor.author | Törnlund, Mikaela | |
dc.contributor.author | Ahraz Asif, Mohammad | |
dc.date.accessioned | 2017-06-22T09:54:03Z | |
dc.date.available | 2017-06-22T09:54:03Z | |
dc.date.issued | 2017-06-22 | |
dc.identifier.uri | http://hdl.handle.net/2077/52656 | |
dc.description.abstract | APIs as a way to expose business assets have become
common across industry. Consequently insights into strategic API
development practices are becoming more and more relevant.
However domain specific knowledge for making strategic design
decisions for APIs is often lacking. In this study we present and
analyse a method for requirement elicitation for APIs created
through use of the design science methodology alongside careful
consideration of standard requirements elicitation practices and
API strategies - specifically insights from the ’API as Digital
Innovation Objects’ model on API strategy. We consider this due
to a lack of awareness about what information is significant for
such strategic design decisions, especially during requirements
elicitation. Our findings show that there are several aspects
of strategic API design that can be considered in order to
improve requirements elicitation. The results imply that strategic
API considerations change requirements elicitation by changing
how it is carried out - not necessarily the tasks and activities
conducted. | sv |
dc.language.iso | eng | sv |
dc.subject | API | sv |
dc.subject | API strategy | sv |
dc.subject | requirements elicitation | sv |
dc.subject | Digital Innovation Object | sv |
dc.title | APIs as Digital Innovation Objects - Implications on Requirements Elicitation | sv |
dc.type | text | |
dc.setspec.uppsok | Technology | |
dc.type.uppsok | M2 | |
dc.contributor.department | Göteborgs universitet/Institutionen för data- och informationsteknik | swe |
dc.contributor.department | University of Gothenburg/Department of Computer Science and Engineering | eng |
dc.type.degree | Student essay | |