The sharpblocks works with an architecture of an MVC (Model View Controller), its entire development is based in this way to separate the display layer (View), business rules (Model) and the view from the navigation (Controller), to give a better reusable components. mvc


When we are developing applications, we create Sharpblocks that have the same approaches as MVC component.

ShapBlocks Architecture

View layer of Sharpblocks

A View described in SSP pages (Sharp Server Pages) that will contain the graphics elements that will appear to the end user.

The SSP enables content that are generic to all types of presentation (web, phone, tablet, or others) or specific for each type of presentation.

To draw content, we can describe in platform of generic components or writing to a particular type of presentation.

For example we can write the html, javascript to be displayed in a browser, but this makes this view only usable for the Web.

The generic content is based on DEC (dynamic element control). DEC is a element that defines an agnostic form of which it will be presented to the end user and permit creating the views.

These elements (DEC) have the ability to render for the Web, phone, tablets or in future other types of equipment, readjusting to give the user best experience.

Model Layer of Sharpblocks

The Model allows you to load data, business rules, data transformations and in the end we get the data to be passed to the View layer and then rendered on the platform that you most prefer.

The way to implement the Model is trough programming in java.

Control Layer of Sharpblocks

It allows the application flow chart in which the operation can be made.

The flows can be:

  • Jump to a Sharpblock
  • Return to the previous Sharpblock
  • Go to a new application
  • Allowing Paging lists

Flow Sharpblocks

The sequence of a Sharpblocks flow is:



But the three components are optional, it is not necessary that a flow have all components indicated.


For example:

• If View  is not defined, the model component can configure the flux to be guide by  the Control Model.

• The model is not filled, the View do not need data or can use previous data form another Sharpblock.

• If there is no control the View can have direct links or does not require flow control because is a dead end.