Functional Design

Implications of Technical
Architecture
 Plugins Client Infrastructure Transfer Protocols Vendor Cloud

Client UI Service Provider

SCHEMA Cloud Schema
Application UI
Server
Solution UI
Server
UI DB

Client Legacy
Systems APP Standard
Client Staging SCHEMA
Schema

APP CONFIG
STG_IN_ Client Staging STG_APP_IN

STG_IN_ERR DB STG_APP_OUT

STG_OUT_ERR
STG_OUT APP_STG_IN
STG_ERR
STG_ARCHIVAL
Solution Design Considerations of Technical
Architecture
• Run Times – Heavy Lifting for intensive procedures run by Staging (Single Minute Exchange of Die Concept)

• Confidentiality – Staging can be Private Owned (Remove labels and pass on aggregate data for analysis)

• Volume of data movement – Are there large volumes of data required to be transferred to the cloud? Can I reduce the data
volume by pre-processing the data?

• Service Contract Nature – SLAs (Maintenance?) Who will support and maintain which schema and scripts? Can user update data
and run ad hoc scenarios without assistance?

• Archiving – Does Archiving / Flushing take exceedingly large space? Can we move it to Staging?

• User Experience – Is the user required to swap screens when comparing data? Functional Requirements?

• Data Flow Between the solutions of a single vendor

How will the functional design be
different if implemented on cloud vs
In Premise?