Introduction to Simantics Architecture - Revision history

Juha Kortelainen: /* Background and motivation */

2011-02-10T10:02:38Z

Background and motivation

← Older revision		Revision as of 10:02, 10 February 2011
Line 1:		Line 1:
	== Background and motivation ==		== Background and motivation ==

	The synthesis of the Simantics architecture has its foundation on a series of research projects at [http://~~intra~~.vtt.fi/?lang=en VTT Technical Research Centre of Finland] on software architectures and data models [http://lib.tkk.fi/Diss/2002/isbn9513860124/] and 20 years of experience from implementation of an industrial process simulator [http://apros.vtt.fi]. The resulting synthesis was put into motion in 2005 when a decision was made to start a development of an ontology-based approach for modelling and simulation. The synthesis is a balance between concepts of theoretical computer science and mathematical logic and concrete user needs in industrial simulation and modelling. The position of VTT between the academia and the industry has given the development team a broad view of the state of the art in modelling and simulation.		The synthesis of the Simantics architecture has its foundation on a series of research projects at [http://www.vtt.fi/?lang=en VTT Technical Research Centre of Finland] on software architectures and data models [http://lib.tkk.fi/Diss/2002/isbn9513860124/] and 20 years of experience from implementation of an industrial process simulator [http://apros.vtt.fi]. The resulting synthesis was put into motion in 2005 when a decision was made to start a development of an ontology-based approach for modelling and simulation. The synthesis is a balance between concepts of theoretical computer science and mathematical logic and concrete user needs in industrial simulation and modelling. The position of VTT between the academia and the industry has given the development team a broad view of the state of the art in modelling and simulation.

	== On objectives and the architecture ==		== On objectives and the architecture ==

Juha Kortelainen: /* Team architecture */

2011-02-10T08:34:37Z

Team architecture

← Older revision		Revision as of 08:34, 10 February 2011
Line 110:		Line 110:
	=== Team architecture ===		=== Team architecture ===

	The emphasis on teamwork in Simantics is implemented using the following means		The emphasis on teamwork in Simantics is implemented using the following means:

	* A shared semantic database with history and access management. The approach follows the example of highly successful and popular systems such as CVS and SVN		* A shared semantic database with history and access management. The approach follows the example of highly successful and popular systems such as CVS and SVN.
	* Integrated documentation tools with fast manual content creation and support for transferring user interface data (e.g. diagrams, tables, requests) into documents		* Integrated documentation tools with fast manual content creation and support for transferring user interface data (e.g. diagrams, tables, requests) into documents.
	* Emphasis on diagramming and diagram self-documentation for making models accessible		* Emphasis on diagramming and diagram self-documentation for making models accessible.

	== Structure of the technical specification ==		== Structure of the technical specification ==

Juha Kortelainen: /* Layered architecture */

2011-02-10T08:34:12Z

Layered architecture

← Older revision		Revision as of 08:34, 10 February 2011
Line 95:		Line 95:
	=== Layered architecture ===		=== Layered architecture ===

	Simantics aims to increase modelling productivity by adopting best practices in modelling such as hierarchical decomposition and component-based reuse. Simantics does this by		Simantics aims to increase modelling productivity by adopting best practices in modelling such as hierarchical decomposition and component-based reuse. Simantics does this by:

	* Providing a few well-thought templates (e.g. structural, DEVS co-simulation) with support for modelling cases in typical engineering systems.		* Providing a few well-thought templates (e.g. structural, DEVS co-simulation) with support for modelling cases in typical engineering systems.
Line 101:		Line 101:
	* Providing implementation frameworks for common tasks such as solver distribution.		* Providing implementation frameworks for common tasks such as solver distribution.

	A focal use case of Simantics is user interface development. Simantics aims to make this quick and easy by		A focal use case of Simantics is user interface development. Simantics aims to make this quick and easy by:

	* Including a common set of typical user interface tools. These include 2D diagramming, Model browsing, Property sheets, Charts, Spreadsheet and Documentation editing.		* Including a common set of typical user interface tools. These include 2D diagramming, Model browsing, Property sheets, Charts, Spreadsheet and Documentation editing.
	* Using a semantic data driven configuration of the tools		* Using a semantic data driven configuration of the tools.
	* Making the tools extensible via plugins		* Making the tools extensible via plugins.
	* Providing frameworks for easy interaction between the tools including clipboard, DnD, workspace selection and requests.		* Providing frameworks for easy interaction between the tools including clipboard, DnD, workspace selection and requests.

Juha Kortelainen: /* Integration architecture */

2011-02-10T08:33:42Z

Integration architecture

← Older revision		Revision as of 08:33, 10 February 2011
Line 88:		Line 88:
	=== Integration architecture ===		=== Integration architecture ===

	A central goal of Simantics is to be able to bring existing tools and models into the Simantics framework for integration with other tools and models already in Simantics. Simantics does this by		A central goal of Simantics is to be able to bring existing tools and models into the Simantics framework for integration with other tools and models already in Simantics. Simantics does this by:

	* Implementing the native data model of the integration target in Simantics. The emphasis is on easy synchronisation and is supported by automatic tools and frameworks (solver toolkit).		* Implementing the native data model of the integration target in Simantics. The emphasis is on easy synchronisation and is supported by automatic tools and frameworks (solver toolkit).

Juha Kortelainen: /* Plugin architecture */

2011-02-10T08:33:18Z

Plugin architecture

← Older revision		Revision as of 08:33, 10 February 2011
Line 81:		Line 81:
	=== Plugin architecture ===		=== Plugin architecture ===

	Simantics products are built up from a set of plugins. The main implications of a plugin architecture are		Simantics products are built up from a set of plugins. The main implications of a plugin architecture are:

	* Plugins are software components with well-defined interfaces and dependencies		* Plugins are software components with well-defined interfaces and dependencies.
	* Plugin-based software products can be configured by adding and removing plugins		* Plugin-based software products can be configured by adding and removing plugins.

	=== Integration architecture ===		=== Integration architecture ===

Juha Kortelainen: /* Data driven architecture */

2011-02-10T08:32:59Z

Data driven architecture

← Older revision		Revision as of 08:32, 10 February 2011
Line 67:		Line 67:
	=== Data driven architecture ===		=== Data driven architecture ===

	Simantics is a set of services built on top of a semantic data model. The main focus points of the architecture are		Simantics is a set of services built on top of a semantic data model. The main focus points of the architecture are:

	* Emphasis on agility and expressivity. Arbitrary different models can co-exist in the same database.		* Emphasis on agility and expressivity. Arbitrary different models can co-exist in the same database.

Juha Kortelainen: /* Quality */

2011-02-10T08:32:36Z

Quality

← Older revision		Revision as of 08:32, 10 February 2011
Line 48:		Line 48:
	=== Quality ===		=== Quality ===

	* Increase the semantic content of data		* Increase the semantic content of data.
	* Increase automation both in model creation and in quality assurance		* Increase automation both in model creation and in quality assurance.
	* Understand the end user process you are developing a feature for. Design and implement logical, easy-to-follow functionalities.		* Understand the end user process you are developing a feature for. Design and implement logical, easy-to-follow functionalities.

Juha Kortelainen: /* Accumulation */

2011-02-10T08:32:26Z

Accumulation

← Older revision		Revision as of 08:32, 10 February 2011
Line 43:		Line 43:
	=== Accumulation ===		=== Accumulation ===

	* Develop standard models and toolkits which support abstraction, decomposition and reuse		* Develop standard models and toolkits which support abstraction, decomposition and reuse.
	* Focus on long term shared data management inside organisations		* Focus on long term shared data management inside organisations.

	=== Quality ===		=== Quality ===

Juha Kortelainen: /* Quality */

2011-02-10T08:30:40Z

Quality

← Older revision		Revision as of 08:30, 10 February 2011
Line 50:		Line 50:
	* Increase the semantic content of data		* Increase the semantic content of data
	* Increase automation both in model creation and in quality assurance		* Increase automation both in model creation and in quality assurance
			* Understand the end user process you are developing a feature for. Design and implement logical, easy-to-follow functionalities.

	=== Teamwork ===		=== Teamwork ===

Juha Kortelainen: /* Architectural reasoning */

2011-02-10T08:27:06Z

Architectural reasoning

← Older revision		Revision as of 08:27, 10 February 2011
Line 24:		Line 24:
	=== Availability ===		=== Availability ===

	* Make integration of existing data and tools into Simantics as easy as possible. Make sure that existing models can be represented using generic semantic representations. Bring existing data models into Simantics as is. Provide toolkits for implementing communications with the tools.		* Make the integration of existing data and tools into Simantics as easy as possible. Make sure that existing models can be represented using generic semantic representations. Bring existing data models into Simantics as is. Provide toolkits for implementing communications with the tools.
	* Create powerful generic tools for integrating data and tools inside Simantics.		* Create powerful generic tools for integrating data and tools inside Simantics.
	* Keep solutions to different problems as clean and as separate as possible. Integrate these solutions.		* Keep solutions to different problems as clean and as separate as possible. Integrate these solutions.
	* Make most useful all-purpose tools freely available parts of the platform.		* Make the most useful, all-purpose tools freely available parts of the platform.

	=== Accessibility ===		=== Accessibility ===

	* Keep down complexity. Use few powerful abstractions to accomplish many tasks.		* Keep down the complexity. Use few powerful abstractions to accomplish many tasks.
	* Concentrate ~~effort~~ on a few powerful and generic tools to make ~~then~~ highly productive.		* Concentrate efforts on a few powerful and generic tools to make them highly productive.
	* Use layered approaches to expose powerful tools step by step.		* Use layered approaches to expose powerful tools step by step.