Writing Requirements to Develop API
How can a Business Analyst add value on project where the deliverable is API (Application Programming Interface) and NO user interface?
What kind of requirements artifacts to produce?
Any ideas appreciated?
People are not the only Actors who need to interact with your system, so do other systems. It would seem that you treat one or more systems as one type of Actor whose needs are met by the API. The interesting point when it is recognized that maybe some systems need a slightly different API, or changes to the API are needed to make it flexible enough to support different Actors., and from a Requirements perspective, those are different Actors no matter how an API is built.
brought to you by enabling practitioners & organizations to achieve their goals using: