OutSystems Architecture-Specialist-11 - Architecture Specialist (OutSystems 11) Exam

End-User layer

Core layer

Foundation layer

One small change in a component cause a series of cascading effects on other components

Hinder future changes as they become less flexible and difficult to manage

Any changes is maintainable and easy to deploy

Non-core Entities

Entities to save UI states

Core Entities (exposed as read-only)

CRUD actions for Entities

Usability : Usability from the point of view of the users

Efficiency : Efficiency which relates to the performance to the amount of resources used

Portability : Portability which defines the ability to move software between environments

Security : Security which relates to the strength of the of the software against cybersecurity attacks

Reliability : Reliability which ensures that a software solution can maintain it performance over a period of time

Maintainability : Maintainability which relates to the effort needed to make modifications

Functionality : Functionality as a set of functions that satisfy needs

Logic to Synchronize data in CS's with an external system. Isolating this logic makes the CS completely system agnostic and it's easier to decouple or replace the external system.

A BL becomes a Calculation Engine if it performs complex calculations, (e.g. an invoice calculation engine or an insurance simulator). Engines are usually subject to versions.

Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.

Core Widgets (blocks), to manage complexity, composition or to have its own lifecycle.

Reusable Core Services with public entities, actions, and blocks.

Compatibility : Compatibility was also added as a way to ensure that a piece of software can work together with other systems

Security : Security ensure software solutions can protect information and data

Integration : Integration to allow data exchange with other software

It's an automatic way to find and fix architecture issues.

It's a systematic approach to architecture design

It promotes the business users' collaboration and understanding

It's a faster architecture design

It optimizes lifecycle independence.

It identifies possible performance bottlenecks.

It minimizes the impact of changes.

It promotes a correct abstraction of reusable services.

to have 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).

technical wrapper to consume and normalize an external service.

Theme, look & feel elements, menu, etc.

Generic Library module.

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

Concepts are disclosed to the Architecture team

Concepts are assembled into Modules

Concepts are added to the layers of the Architecture Canvas