Menu
Why Hyperon

Context

When application uses parameter or function, its value depends on context. In other words - context is an object model containing all data that may affect parameters' or functions' values. Once we design context model, we can make our parameterization depends on any data from the context.

If you want to persist context information in any way, you can use the Persistence Engine. Context structure with values can be easily stored within any database (same as application or separate). The engine can be used out of the box and speed up development process.

Below you can see sample context definition:

[ROOT]
 - policy
 - cover        
 
[Policy]
 - policyNo
 - productCode
  - insured
 - year
 - covers          

[Client]
 - firstname
 - lastname
 - gender
 - age
 - professionCode
 - address        
  ...

[Cover]
 - code
 - sumInsured
 - basePremium
 - startDate
 - endDate
 ...

: Policy
: Cover


: string
: string
: Client
: integer
: Cover []


: string
: string
: string
: integer
: integer
: Address



: string
: number
: number
: date
: date
// root elements in context  



// Policy type definition






// definition of Client type








// definition of Cover type

Following listing shows some paths valid for this sample context:

policy.productCode
policy.insured.lastname
policy.insured.address.zipCode
policy.insured.age
cover.sumInsured

For instance, policy.insured.age is an integer and means the age of insured person on insurance policy.

Context designed inside Hyperon Studio is kind of contract between Hyperon and your application that specify object model which your application
will pass to Hyperon and on which parameters and functions will be based. It should be abstracted from application's or database model. Context design should focus on business needs. Such context will be conceptual bridge between development team and business analysts.

Read more on Domain in our Tutorials: