Quick Links: Articles MA Blog Community Blog Templates Books BA Humor Events Jobs Interview Questions RSS Feeds
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.
Craig Brown -General Analysis -Project & Personnel Management View Posts View Expert's Biography
Guy Beauchamp -Data Analysis & Modeling -Structured Systems Analysis View Posts View Expert's Biography
Jarett Hailes -Agile Methods View Posts View Expert's Biography
Kieran Creaton -Requirements Gathering & Facilitation Techniques View Posts View Expert's Biography
Perry McLeod -UML Modeling -Project & Personnel Management View Posts View Expert's Biography
The Community Expert is just one way that Project Members volunteer their time to help the Modern Analyst Community. Want to become a Community Expert in one of the following areas? Submit yourself to be selected as a Project Member.
Available topics include:
Advertising Opportunities | Contact Us