Model-Based Systems Engineering (MBSE)
Occam’s Model Based Systems Engineering suite is the only solution of its kind.
Model-Based Systems Engineering (MBSE)
Occam’s Model Based Systems Engineering suite is the only solution of its kind…
Elegant Simplicity
Occam’s Razor, AKA the “principle of parsimony”, asserts when attempting to explain a phenomena, “entities must not be multiplied beyond necessity”. Most people hear Occam’s Razor expressed as: “The simplest explanation is usually the best one”.
Occam’s Systems Modeling tool is called “Razor” because it was designed with this tenant in mind. Because its design was driven by this principle, users find the following to be true of Razor:
- maximizes the density of knowledge in systems models
- maximizes the productivity of modelers
- minimizes the effort required to learn the language
- minimizes the difficulty of accessing knowledge in systems models from other tools
Open Platform
In addition, to minimize operating cost, Razor is a 100% web-based client with cloud compatible infrastructure. To facilitate integrations, Razor stored models in GitHub/GitLab and serializes model content using W3C RDF Linked-Data.
Knowledge Re-Use
Razor was also designed from the ground-up to support “Pattern-Based Systems Engineering” (PBSE). Razor supports PBSE by allowing users to use it to effortlessly create and publish re-usable system model constructs (patterns) via the same user interface used do build systems models. Conversely, from this interface a user can browse and draw from the universe of patterns created via other Razor users. Last to ensure easy secure, easy access to models and patterns, Razor stores and version manages its models in GitHub/GitLab.
Elegant Simplicity
Occam’s Razor, AKA the “principle of parsimony”, asserts when attempting to explain a phenomena, “entities must not be multiplied beyond necessity”. Most people hear Occam’s Razor expressed as: “The simplest explanation is usually the best one”.
Occam’s Systems Modeling tool is called “Razor” because it was designed with this tenant in mind. Because its design was driven by this principle, users find the following to be true of Razor:
- maximizes the density of knowledge in systems models
- maximizes the productivity of modelers
- minimizes the effort required to learn the language
- minimizes the difficulty of accessing knowledge in systems models from other tools
Open Platform
In addition, to minimize operating cost, Razor is a 100% web-based client with cloud compatible infrastructure. To facilitate integrations, Razor stored models in GitHub/GitLab and serializes model content using W3C RDF Linked-Data.
Knowledge Re-Use
Razor was also designed from the ground-up to support “Pattern-Based Systems Engineering” (PBSE). Razor supports PBSE by allowing users to use it to effortlessly create and publish re-usable system model constructs (patterns) via the same user interface used do build systems models. Conversely, from this interface a user can browse and draw from the universe of patterns created via other Razor users. Last to ensure easy secure, easy access to models and patterns, Razor stores and version manages its models in GitHub/GitLab.