About HiberSource

What is HiberSource?

There are many free version control systems (such as SVN) but there is no free configurations system to support projects (like Razor or PVCS). HiberSource was started to be a configuration system to support full software life cycle with certification activities and has the following advantages:

  1. 100%-compatible with DO-178B(C);

  2. Free;

  3. Useful and comfortable to work;

  4. Ability to change life cycle dynamic;

  5. Data-safe.

What are the main objectives?

Main objectives are obtained from DO-178(B) point 7.1. There are:

  1. Creating a defined and controlled configuration of the software to support full software life cycle;

  2. Providing change control;

  3. Providing the ability to replicate executable object code;

  4. Providing process’ input and output control;

  5. Providing the ability to appreciate the state of project;

  6. Providing base version and approval control;

  7. Providing the ability to archive, backup/restore and manage data.

The system is based on controlling configurations and changes. To achieve this principle the system stores the states of controlled objects and all actions that lead to these states.



What are the main functions?

Main data-management functions:

  1. Version control. The system stores all versions of an object. The versions are available to retrieve but not for update (a user has to create a new version to update the object).

  2. Configuration control. The system controls the objects’ life cycle using states. Any version of any object has a state at a moment.

  3. Change control. The system controls object changes using ‘documents’ – an electronic records with requests to update objects and project specific attributes.

  4. Baseline management. The system manages baselines and provides independent baseline life cycle. To produce the product release a baseline is created and related to the required versions of objects and documents.

  5. View control. Each view in a project has its own access rules and stored objects.

  6. Access management. The system uses authorization and authentication service to control the users’ actions.

  7. Audit service. Each action in the system is stored and can be retrieved at any moment.



What is the architecture?

System architecture is based on 4 levels:

  1. Database management system stores all project and user data. The third party vendors to be used.

  2. Application server (container) manages the server side application and systems resources such as network connections or pool of database connections. The third party vendors to be used.

  3. Server side application implements the system logic and requirements. To be developed.

  4. Client side application uses graphic user interface to interact with end users. To be developed.



What is the current state?

The 0.9.b (Beta) version has been published.