OutSystems Architecture Specialist (OutSystems 11) - Architecture-Specialist-11 模擬練習

A. Generic Library module.

B. several integration services with different systems, performing the same type of operation (e.g. printers) you can create several drivers exposing the same API, with specialized implementations (like the transparency services pattern).

C. Reusable UI Patterns for layout and display only - no Business logic.

D. Theme, look & feel elements, menu, etc.

E. technical wrapper to consume and normalize an external service.

A. Layer Modules Correctly

B. Layer Entities Correctly

C. Don't Mix Sponsers : Split the Apps based on the Lines of Business

D. Layer Applications Correctly

E. Don't Mix Owners

A. Information Architecture

B. Integration Technology

C. User Stories, Personas and Roles

D. User Experience Expectations

E. Architecture Canvas Modules

A. Only synchronize delta : Use control timestamps
C Avoid long synchronization in a single transaction

B. Sync only when strictly required
E Don't sync on every screen or online event

C. Sync only when required. p At session start: sync summary data to local storage At process start: sync process detail to local storage At process/transaction end, sync back to server

D. Only synchronize relevant data

E. Ensure sync granularity: Prepare for constant retries without repeating work due to network loss. Sync in chunks, incremental by entity

F. Do not use Entity Bulk Operation to ensure small lightweight updates

A. Join conceptually-related concepts

B. Don't join concepts with different lifecycles

C. Apply known design patterns

D. N/A

E. Isolate reusable logic from Integration logic

A. Same as ECS with local replica but API module is provided. So any changes to the external system can notify OS, which OS then gets update from the ERP system (subscription system)

B. ... tries to fetch data from local cache entity, if not there, get single entry from the external v system. Cache only that record (read-through caching) Use when whole database too big or costly to synchronize. Integration only touches a small portion of the database. Avoid if access to lists of data is needed up front

C. Same as Base ECS pattern, but have a local replica. Store data to serve as a local cache. Pro: Leverage Entity Use, Simpler Integration API. Con: Less impact on source system

D. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update

E. ... caches only summary data that is frequently lister, joined or searched. Full detail for a O single entry is fetched directly from external system. Use when whole database too big or costly to synchronize. Details are only required for single entities (not lists)

F. ... is a pattern with two modules, a connector module that can be used to encapsulate an ) external API with the input/output structures and a wrapper module to expose the normalized API to the consumers.

G. ... a wrapper used to contain the logic, actions and data that will expose code that is inside of O external library or to inspect external database and import the data structures so they can be used as entities inside of OS

H. Same as ECS with local replica but synchronization logic is separated. Pro: Code ^ independence. Consumers of CS is not affected by Sync. Sync can orchestrate several CS

I. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.

J. ... Entity is not in Outsystems but in an external ERP system. IS just makes remote call to p external system/database. No data is being kept inside OS. Data retrieval may not be optimized as it needs to traverse two different systems to get the information back. Con: Integration API must support all use cases

A. No business logic in the Foundational Modules

B. No front-end screens in Core Modules

C. No core entities in Foundational Modules

D. All public entities in Core Modules should be set to Read-only

E. No screens in the End User Layer

A. Library : Connector Pattern

B. Transparency Service Pattern

C. Transparency Service Pattern 1 way (simplification)

D. ECS Lazy Load variation

E. ECS with isolated synchronization logic

F. ECS with publish/subscribe through an ESB

G. Library : Extension Pattern

H. ECS Summary cache only variation

I. Base ECS pattern

J. ECS with direct integration

A. Architecture Dashboard performs a code analysis that uncovers patterns related to performance, security, architecture and maintainability.

B. Architecture Dashboard allows you to automatically apply a solution to solve a found code pattern.