//Knowledge:Vocabulary/com/sphenon/Vocabulary (2.0)

Software has always been used to produce other Software: whether Assembler, Compiler, or IDE, the purpose of such tools is always to simplify the creation and make it more efficient, and to produce less erraneous and more secure systems.

The various procedures, which have been developed over the years, differ mainly in which kind of description they operate on to create the desired results. Still very widely used is program code, like Java or JavaScript. It contains many technical details, is translated by compilers into the target systems, and is only maintainable by IT-Experts.

For more than two decades there is ongoing research and development on how to produce Software from socalled Models. These describe the desired results from the perspective of business users much more directly than would be possible with the technical oriented languages. Thereby they are easier to comprehend and much easier to maintain.

EM/OS is such a tool. It enables domain experts to describe their requirements clearly and precisely, and to automatically produce the respective software from.

The businessboard is an integrated, collaborative online workplace for managing the full software production pipeline, from capturing requirements and designing specifications by editing lorescrolls, via controlling automated software production, up to designing landscapes and automated deployment into those.

businessboards are available on the fairyloom service website.

A Business Model here denotes an integrated Model, which contains all requirements as well as all organisational and business relevant facts to describe a Software, in a clear and precise way. Often, but not always, this is achieved by using graphics.

Usually such integrated Business Models consist of partial models, which describe a certain aspect, respectively. Typical partial models are Class-, Architecture, System- and Process-Models, yet this can dependingly be defined much narrower or broader (Strategy, Projects, Story Boards, technical details etc.).

EM/OS processes such comprehensive Business Models, which can be collaboratively edited in the businessboard. In the realm of fairyloom these models are known as lorescrolls.

A formal description of how respective technology specific artefacts can be created from domain specifications within EM/OS. Most prominent examples of such formal descriptions are Templates and Blueprints.

E.g., a Java code template may codify the implementation of a REST Service based on a given description of data sources and expected delivered content.

The Enterprise Model Operation Services (EM/OS) by Sphenon GmbH are a system to produce and operate ready-for-production business solutions directly from Business Models.

A Generator, or often historically called Code Generator, is a tool which is used to process Templates and automatically create artefacts from them, using a respective set of parameter values.

EM/OS is using a highly optimised and powerful Generator for that purpose.

Generally a model is understood as a simplified image of a given object, which in our context obviously is some IT- or Business System. Specifically, such models are formally constructed documents, whose individual elements have a precisely defined meaning.

Very often models are represented graphically as diagrams. The various elements are characterised by different symbols, colours or shapes. Some kinds of models are:

• Class-Models
• Architecture-Models
• System-Models
• Process-Models

The purpose of such models is often to describe the systems clearly comprehensible in domain oriented way, and to avoid technical details as far as possible. Comprehensive models are used as specifications to automatically produce software solutions.

The Object Assembler is an innovative and unique tool used by EM/OS to assemble software systems at runtime from small building blocks using socalled Object Construction Plans (OCPs) as blueprints.

An Object Construction Plan is a blueprint that describes how to assemble software systems at runtime from small building blocks, using the EM/OS Object Assembler.

There are many application areas for OCPs, e.g. to provide complex configurations, interaction structures or even act as a pwoerful modelling language.