- This topic has 2 replies, 3 voices, and was last updated 7 years, 12 months ago by
.
-
Posts
-
An application Developed an UI and API. UI is the graphical user interface. API has business logic to retrieve the data.
As per CPM guidelines EQ/EO definition an elementary process which “retrieve the data with or without processing logic”(API) and display(UI).
Only UI or API does not leave the business in consistence state. So my conclusion is only one transaction.
But the same API may be used by more than one application to retrieve the data(API) to use it in their transactions.
So is it only one transaction “(UI) and API” together or Separate?
some FP counters counting API and UI separate transaction.
Please provide your views.
If the API is used by more applications = more users, then that requirements is indeed a separate logic path.
The UI and the API together make one transactional function type, that is correct.
If the API is used in combination with other UI’s, then each unique combination of API and UI should be seen as different transactional function types.
And, if the UI is used in combination with other API’s, then each unique combination of API and UI should be seen as different transactional function types as well.
- You must be logged in to reply to this topic.