Show simple item record

dc.contributor.authorTörnlund, Mikaela
dc.contributor.authorAhraz Asif, Mohammad
dc.date.accessioned2017-06-22T09:54:03Z
dc.date.available2017-06-22T09:54:03Z
dc.date.issued2017-06-22
dc.identifier.urihttp://hdl.handle.net/2077/52656
dc.description.abstractAPIs 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.isoengsv
dc.subjectAPIsv
dc.subjectAPI strategysv
dc.subjectrequirements elicitationsv
dc.subjectDigital Innovation Objectsv
dc.titleAPIs as Digital Innovation Objects - Implications on Requirements Elicitationsv
dc.typetext
dc.setspec.uppsokTechnology
dc.type.uppsokM2
dc.contributor.departmentGöteborgs universitet/Institutionen för data- och informationsteknikswe
dc.contributor.departmentUniversity of Gothenburg/Department of Computer Science and Engineeringeng
dc.type.degreeStudent essay


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record