In Structuraid we need to have a system where we centralize all the information regarding design requirements coming from codes and standards. Since these codes are usually mandatory on a regional/country basis, it would be useful for us to be able to support multiple design codes and use one of them according to the project setup.

Here’s the following diagram that explains how the DesignCodes system will work

The system is composed of the following abstractions

• A Resolver class that will provide functionality to point to the namespace that corresponds to the desired design code
• A namespace for each design code that the app will support. As examples, the diagram above illustrates namespaces for the Colombian NSR-10 and US ACI 318-19
• Inside each code namespace there will be a series of abstractions, each one will correspond to one requirement or process that needs to be performed following each design code. The file structure of these abstractions needs to be identical on each design code namespace.
• A namespace of Schemas that will ensure that the contract of each requirement abstraction is kept the same no matter which design code is going to be followed.

System Usage

The first thing to do before using the design codes system is to call the resolver in order to point to the right namespace that the project will need to use:

design_code = DesignCodes::Resolver.use('nsr_10')

The resolver will return as a result the namespace that should be used later to call any requirement that needs to be made. For example, if you need to compute the elastic modulus according to the design code, do this:

design_code::RC::ElasticModulus.call(design_compression_strength: 28)

Error Handling

Each Code Requirement abstraction will raise one of the following errors if something went wrong: