[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
|
[news.eclipse.technology.almiif] Re: Proposal question
|
Thanks,
I'm still a little fuzzy on this...
> For example, a QA tool might need to access information from a business
> modeling tool that describes the various process flows and use cases
> associated with a new business application in order to auto-generate the
> associated test scripts.
How can the QA tool do this without knowing the vocabulary (i.e. API) of the
description of those flows? Does this mean there is some sort of wrapper
around the API? If so, who is responsible for developing and maintaining the
wrapper - ALMIIF or the tool providing the API?
> In contrast, the ALMIIF limits the functionality directly accessible via
> the API, but enables all the tools to be applied to the common application
> model, surpassing the functionality provided by any single vendor.
Isn't that what an API already does - limit the surface to provide a common
public interface?
Thanks,
Darin