Difference between revisions of "PKC API/Context"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
=Summary of Context= | =Summary of Context= | ||
<onlyinclude> | <onlyinclude> | ||
* | * There is a critical need to enable OpenAPI Implementation to enable dataflow communication within internal PKC's instrument and inbound/outbound PKC Implementation. | ||
* | * PKC API functions as gateway of data flow between: | ||
** PKC's instrument. | |||
** PKC's custom application. | |||
** another PKC implementation through Apache Kapfka. | |||
</onlyinclude> | </onlyinclude> | ||
Latest revision as of 03:09, 10 November 2022
| This page is part of logic model: PKC API | ||||
|---|---|---|---|---|
| Context | PKC API/Context | Inputs | Process | Output |
| Goal | PKC API/Goal | PKC API/Input | PKC API/Process | PKC API/Output |
| Success Criteria | PKC API/Criteria | |||
| Boundary/Safety Conditions | PKC API/Boundary | |||
Summary of Context
- There is a critical need to enable OpenAPI Implementation to enable dataflow communication within internal PKC's instrument and inbound/outbound PKC Implementation.
- PKC API functions as gateway of data flow between:
- PKC's instrument.
- PKC's custom application.
- another PKC implementation through Apache Kapfka.