Konzepte - Versionsgeschichte

Mawalch am 21. Februar 2018 um 11:36 Uhr

2018-02-21T11:36:22Z

← Nächstältere Version		Version vom 21. Februar 2018, 11:36 Uhr
Zeile 1:		Zeile 1:
	#REDIRECT[[Concepts/en]]		#REDIRECT[[Concepts/en]]

	[[Category:Temporary ~~short~~ ~~redirect~~]]		[[Category:Temporary Short Redirect]]

Mawalch: Content is an exact duplicate of Concepts/en. Replace with redirect.

2018-02-21T11:35:55Z

Content is an exact duplicate of Concepts/en. Replace with redirect.

Änderungen zeigen

Mawalch am 20. Februar 2018 um 11:58 Uhr

2018-02-20T11:58:02Z

← Nächstältere Version		Version vom 20. Februar 2018, 11:58 Uhr
Zeile 1:		Zeile 1:
	[[Category:Incomplete]]		[[Category:Incomplete]]
	[[Category:Work In Progress]]		[[Category:Work In Progress]]
			[[Category:Marked for Deletion]]

	== Introduction ==		== Introduction ==

Mawalch: Grafiken reparieren.

2018-01-06T23:49:31Z

Grafiken reparieren.

← Nächstältere Version		Version vom 6. Januar 2018, 23:49 Uhr
Zeile 711:		Zeile 711:
	==== Shell Script Blocks ====		==== Shell Script Blocks ====

			The [[Datei:PIC_GUI_IconSymbol_ProjectComponent_ShellScriptAction.png]] <span class="KEYWD">Shell Script Block element</span> is the element type used to implement an elementary functionality block in form of <span class="EMPH">shell script source code</span> in an OS dependent scripting language. The code contents are <span class="EMPH">directly passed</span> to the underlying operating system, so the scope of possible shell or batch script dialects depends on the platform on which the session is running.<br>

			Each element of this type contains exactly one <span class="KEYWD">Shell Script Content Property</span>, which holds the <span class="KEYWD">Shell Script Code Text Content</span> that is passed to the operating system at runtime. The features that are available to the script code depend on the used dialect. An Activity of this Block type will only run if the used dialect can be interpreted by the OS. Since the OS interprets the code in a process spawned by expecco, the current OS variable environment of the expecco session also is the initial OS variable environment for the
	The <img src="./pictures/PIC_GUI_IconSymbol_ProjectComponent_ShellScriptAction"></img>
	<span class="KEYWD">Shell Script Block element</span> is the element type
	used to implement an elementary functionality block in form of <span class="EMPH">shell
	script source code</span> in an OS dependent scripting language. The code contents
	are <span class="EMPH">directly passed</span> to the underlying operating system,
	so the scope of possible shell or batch script dialects depends on the platform
	on which the session is running.<br>

	Each element
	of this type contains exactly one <span class="KEYWD">Shell
	Script Content Property</span>, which holds the <span class="KEYWD">Shell
	Script Code Text Content</span> that is passed to the operating
	system at runtime. The features that are available to the script
	code depend on the used dialect. An Activity of this Block type
	will only run if the used dialect can be interpreted by the
	OS. Since the OS interprets the code in a process spawned by
	expecco, the current OS variable environment of the expecco
	session also is the initial OS variable environment for the
	shell process.<BR>		shell process.<BR>

Zeile 738:		Zeile 722:
	==== Shell Command Blocks ====		==== Shell Command Blocks ====

			The [[Datei:PIC_GUI_IconSymbol_ProjectComponent_ConsoleCmdAction.png]] <span class="KEYWD">Console Shell Command Block element</span> is the element type used to implement an elementary functionality block in form of a <span class="EMPH">console shell command</span> in an OS dependent manner. The command is <span class="EMPH">directly passed</span> to the underlying operating system, so the scope of possible executables to call depends on the platform on which the session is running.<BR>
	The <img src="./pictures/PIC_GUI_IconSymbol_ProjectComponent_ConsoleCmdAction"></img>
	<span class="KEYWD">Console Shell Command Block element</span> is the element
	type used to implement an elementary functionality block in form of a <span class="EMPH">console
	shell command</span> in an OS dependent manner. The command is <span class="EMPH">directly
	passed</span> to the underlying operating system, so the scope of possible executables
	to call depends on the platform on which the session is running.<BR>

	Each element		Each element
			of this type contains exactly one <span class="KEYWD">Console Shell Command Property</span>, which holds the command that is passed to the operating system at runtime. An Activity of this Block type will only run if the specified command can be executed by the OS. Since the OS runs the code in a process spawned by expecco, the current OS variable environment of the expecco session also is the initial OS variable environment
	of this type contains exactly one <span class="KEYWD">Console
	Shell Command Property</span>, which holds the command that
	is passed to the operating system at runtime. An Activity of
	this Block type will only run if the specified command can be
	executed by the OS. Since the OS runs the code in a process
	spawned by expecco, the current OS variable environment of the
	expecco session also is the initial OS variable environment
	for the shell process.<BR>		for the shell process.<BR>

	For the executing process, no direct access to the Data Pins is available. The reason is the nature of the command execution schema: The according process is running inside a shell, and communicates with the outside via the standard streams <span class="CODE">stdin</span>, <span class="CODE">stdout</span>, and <span class="CODE">stderr</span>. However, the output of the command can be captured by connecting the according Pins to some evaluating Steps.		For the executing process, no direct access to the Data Pins is available. The reason is the nature of the command execution schema: The according process is running inside a shell, and communicates with the outside via the standard streams <span class="CODE">stdin</span>, <span class="CODE">stdout</span>, and <span class="CODE">stderr</span>. However, the output of the command can be captured by connecting the according Pins to some evaluating Steps.

			The Shell Command Block element has restrictions regarding its Data Pin Definitions. These restrictions are described in <a href="#0b0a0611-17b4-11db-9ca4-0040c7999506">Chapter 5.4.5: Schema Definition Restrictions</a>. Accessing the Script Content Property through the GUI is described in <a href="./DOC_eXpeccoUserGuide_GUI.html#185a9140-f60c-11da-9610-0040c7999506">expecco GUI Documentation/Chapter 6.8: The Console Command Editor</a>.<BR>
	The Shell Command Block element
	has restrictions regarding its Data Pin Definitions. These restrictions are
	described in <a href="#0b0a0611-17b4-11db-9ca4-0040c7999506">Chapter 5.4.5:
	Schema Definition Restrictions</a>. Accessing the Script Content Property through
	the GUI is described in <a href="./DOC_eXpeccoUserGuide_GUI.html#185a9140-f60c-11da-9610-0040c7999506">expecco
	GUI Documentation/Chapter 6.8: The Console Command Editor</a>.<BR>

	==== Test Data Generator Blocks ====		==== Test Data Generator Blocks ====

	The ~~<img src="./pictures/~~PIC_GUI_IconSymbol_ProjectComponent_DataGeneratorAction~~"></img>~~ <span class="KEYWD">Test Data Generator Block element</span> is the element type used to <span class="EMPH">supply artificially generated data values</span> to other Steps. This is useful especially for simulating elements that are usually delivering the values, but are not always or not yet available. A second purpose for this Block type is to control the execution flow by yielding time scheduled values.		The [[Datei:PIC_GUI_IconSymbol_ProjectComponent_DataGeneratorAction.png]] <span class="KEYWD">Test Data Generator Block element</span> is the element type used to <span class="EMPH">supply artificially generated data values</span> to other Steps. This is useful especially for simulating elements that are usually delivering the values, but are not always or not yet available. A second purpose for this Block type is to control the execution flow by yielding time scheduled values.

	Each element of this type contains exactly one <span class="KEYWD">Generic Values List Property</span>, which holds a chronologically sorted list of Generic Values Entries. Every entry in that list consists of a Generation Time declaration, and for each Output Pin which is defined in the Block's Schema Definition, possibly one Generic Value. It is not obligatory to assign a Value to every Output Pin per Entry, but if, only one Value per Pin and Entry is possible.		Each element of this type contains exactly one <span class="KEYWD">Generic Values List Property</span>, which holds a chronologically sorted list of Generic Values Entries. Every entry in that list consists of a Generation Time declaration, and for each Output Pin which is defined in the Block's Schema Definition, possibly one Generic Value. It is not obligatory to assign a Value to every Output Pin per Entry, but if, only one Value per Pin and Entry is possible.
Zeile 797:		Zeile 765:
	== Test Plans and Test Results ==		== Test Plans and Test Results ==

	The ~~<img src="./pictures/~~PIC_GUI_IconSymbol_ProjectComponent_TestPlan~~"></img>~~ <span class="KEYWD">Test Plan element</span> is the element type used to <span class="EMPH">model and execute</span> individual <span class="KEYWD">Test Plans</span>. A Test Plan is a <span class="EMPH">sequence</span> of individual <span class="KEYWD">Test Items</span> that can be executed. A Test Item is either <span class="EMPH">a Block</span> element, or yet another <span class="EMPH">nested Test Plan</span> element. Each element of this type contains exactly one <span class="KEYWD">Test Items List Property</span>, which serves to set up and arrange the sequence of Test Items. When a Test Plan is processed, its Test Items are processed one by one along their arrangement sequence in the Test List.		The [[Datei:PIC_GUI_IconSymbol_ProjectComponent_TestPlan.png]] <span class="KEYWD">Test Plan element</span> is the element type used to <span class="EMPH">model and execute</span> individual <span class="KEYWD">Test Plans</span>. A Test Plan is a <span class="EMPH">sequence</span> of individual <span class="KEYWD">Test Items</span> that can be executed. A Test Item is either <span class="EMPH">a Block</span> element, or yet another <span class="EMPH">nested Test Plan</span> element. Each element of this type contains exactly one <span class="KEYWD">Test Items List Property</span>, which serves to set up and arrange the sequence of Test Items. When a Test Plan is processed, its Test Items are processed one by one along their arrangement sequence in the Test List.

	In the expecco GUI, arrangement and execution of Test Plans are performed in a single editor type, the <span class="KEYWD">Test Plan Editor</span>. This editor provides the editable representation of the <span class="KEYWD">Test Items List</span> Property, as well as the user interface needed to start, halt, stop, or debug the Test Plans execution. Accessing the Test Items List Property and executing Test Plans through the GUI is described in detail in <a href="./DOC_eXpeccoUserGuide_GUI.html#1abf5c40-f60c-11da-9610-0040c7999506">expecco GUI Documentation/Chapter 6.17: The Testplan Editor</a>.		In the expecco GUI, arrangement and execution of Test Plans are performed in a single editor type, the <span class="KEYWD">Test Plan Editor</span>. This editor provides the editable representation of the <span class="KEYWD">Test Items List</span> Property, as well as the user interface needed to start, halt, stop, or debug the Test Plans execution. Accessing the Test Items List Property and executing Test Plans through the GUI is described in detail in <a href="./DOC_eXpeccoUserGuide_GUI.html#1abf5c40-f60c-11da-9610-0040c7999506">expecco GUI Documentation/Chapter 6.17: The Testplan Editor</a>.
Zeile 851:		Zeile 819:
	=== Defining Skills ===		=== Defining Skills ===

	The ~~<img src="./pictures/~~PIC_GUI_IconSymbol_ProjectComponent_Skill~~"></img>~~ <span class="KEYWD">Skill element</span> serves to summarize the elementary <span class="KEYWD">Skill Attributes</span> that <span class="EMPH">characterize</span> a Skill. It is important that only the <span class="EMPH">nature</span> of the Skill is defined in the form of its Skill Attributes, but <span class="EMPH">no</span> concrete values are ever assigned directly to the Skill. Later on, one or more Skills can be assigned to a Resource, which is then concretizing them by <span class="EMPH">value assignments</span>. These specifications are taken into account during runtime to decide about the suitability of a Resource for a particular usage purpose.		The [[Datei:PIC_GUI_IconSymbol_ProjectComponent_Skill.png]] <span class="KEYWD">Skill element</span> serves to summarize the elementary <span class="KEYWD">Skill Attributes</span> that <span class="EMPH">characterize</span> a Skill. It is important that only the <span class="EMPH">nature</span> of the Skill is defined in the form of its Skill Attributes, but <span class="EMPH">no</span> concrete values are ever assigned directly to the Skill. Later on, one or more Skills can be assigned to a Resource, which is then concretizing them by <span class="EMPH">value assignments</span>. These specifications are taken into account during runtime to decide about the suitability of a Resource for a particular usage purpose.

	Each element of this type contains exactly one <span class="KEYWD">Skill Attributes Property</span>, which serves to set up and configure the Skill Attributes. This is done in expecco using the <span class="KEYWD">Skill Definition Editor</span>.		Each element of this type contains exactly one <span class="KEYWD">Skill Attributes Property</span>, which serves to set up and configure the Skill Attributes. This is done in expecco using the <span class="KEYWD">Skill Definition Editor</span>.
Zeile 867:		Zeile 835:
	=== Defining Resources ===		=== Defining Resources ===

	The ~~<img src="./pictures/~~PIC_GUI_IconSymbol_ProjectComponent_Resource~~"></img>~~ <span class="KEYWD">Resource element</span> is used to represent a concrete Resource <span class="EMPH">type</span>. The Resource element itself still does <span class="EMPH">not</span> represent a concrete <span class="EMPH">instance</span> of a Resource; this is achieved in a later step when setting up an Inventory. The Resource element however defines the type of the Resource using <span class="EMPH">concrete values</span>, thereby allowing to specify concrete Resource types, like e.g. a particular measurement unit model, a certain controller type, etc.		The [[Datei:PIC_GUI_IconSymbol_ProjectComponent_Resource.png]] <span class="KEYWD">Resource element</span> is used to represent a concrete Resource <span class="EMPH">type</span>. The Resource element itself still does <span class="EMPH">not</span> represent a concrete <span class="EMPH">instance</span> of a Resource; this is achieved in a later step when setting up an Inventory. The Resource element however defines the type of the Resource using <span class="EMPH">concrete values</span>, thereby allowing to specify concrete Resource types, like e.g. a particular measurement unit model, a certain controller type, etc.

	Each element of this type contains exactly one <span class="KEYWD">Skill Assignments Property</span>, which serves to set up and concretize the list of Skill Assignments. This is done using the <span class="KEYWD">Resource Definition Editor</span>.		Each element of this type contains exactly one <span class="KEYWD">Skill Assignments Property</span>, which serves to set up and concretize the list of Skill Assignments. This is done using the <span class="KEYWD">Resource Definition Editor</span>.

Mawalch: /* Code Blocks */ Convert bad HTML to Wiki syntax

2018-01-06T20:33:37Z

Code Blocks: Convert bad HTML to Wiki syntax

← Nächstältere Version		Version vom 6. Januar 2018, 20:33 Uhr
Zeile 701:		Zeile 701:
	==== Code Blocks ====		==== Code Blocks ====

			<DIV ALIGN="LEFT" STYLE="border:0px solid"> The <span class="KEYWD">Code Block element</span> is the element type used to implement an elementary functionality block in form of programmatic <span class="EMPH">source code</span> in a particular <span class="EMPH">programming language</span>. Currently, two syntax patterns are supported: [[Datei:PIC_GUI_IconSymbol_ProjectComponent_JavaScriptAction.png]] JavaScript syntax, and [[Datei:PIC_GUI_IconSymbol_ProjectComponent_SmalltalkAction.png]] Smalltalk syntax.
	<DIV ALIGN="LEFT" STYLE="border:0px solid"> The <span class="KEYWD">Code Block
	element</span> is the element type used to implement an elementary functionality
	block in form of programmatic <span class="EMPH">source code</span> in a particular
	<span class="EMPH">programming language</span>. Currently, two syntax patterns
	are supported: <img src="./pictures/PIC_GUI_IconSymbol_ProjectComponent_JavaScriptAction">
	JavaScript syntax, and <img src="./pictures/PIC_GUI_IconSymbol_ProjectComponent_SmalltalkAction">
	Smalltalk syntax.<BR>

	Each element of this type contains exactly one <span class="KEYWD">Code Content Property</span>, which holds the <span class="KEYWD">Source Code Text Content</span> that is interpreted according to the used languages syntax at runtime. It is also possible to <span class="EMPH">switch the syntax pattern</span> for already implemented Code Blocks, causing the code to be automatically converted to that particular syntax style.		Each element of this type contains exactly one <span class="KEYWD">Code Content Property</span>, which holds the <span class="KEYWD">Source Code Text Content</span> that is interpreted according to the used languages syntax at runtime. It is also possible to <span class="EMPH">switch the syntax pattern</span> for already implemented Code Blocks, causing the code to be automatically converted to that particular syntax style.

Mawalch am 6. Januar 2018 um 13:38 Uhr

2018-01-06T13:38:57Z

Mawalch am 6. Januar 2018 um 13:32 Uhr

2018-01-06T13:32:46Z

← Nächstältere Version		Version vom 6. Januar 2018, 13:32 Uhr
Zeile 901:		Zeile 901:
	=== Defining Resource Requirements ===		=== Defining Resource Requirements ===

	Each ~~<img src="./pictures/~~PIC_GUI_IconSymbol_ProjectComponent_UnspecifiedAction~~"></img>~~ <span class="KEYWD">Block element</span> - except for the Test Data Generation Block - can be assigned a set of <span class="KEYWD">Skill Requirements</span>, which describe the <span class="EMPH">abilities that have to be met</span> by a Resource to make it suitable for the Block's functionality. Resources are never directly addressed by a Block's Skill Requirements; instead, these define only what Skills a Resource should meet, and the requested Inventory decides about which Resource fits best and will be reserved for the particular Activity.		Each [[Datei:PIC_GUI_IconSymbol_ProjectComponent_UnspecifiedAction.png]] <span class="KEYWD">Block element</span> - except for the Test Data Generation Block - can be assigned a set of <span class="KEYWD">Skill Requirements</span>, which describe the <span class="EMPH">abilities that have to be met</span> by a Resource to make it suitable for the Block's functionality. Resources are never directly addressed by a Block's Skill Requirements; instead, these define only what Skills a Resource should meet, and the requested Inventory decides about which Resource fits best and will be reserved for the particular Activity.

	An Activity that refers to a Block element which has Skill Requirements assigned, will always first try to find and <span class="EMPH">allocate suitable Resource objects</span> in the Inventory of its surrounding context, before it starts its execution. Requirements of Blocks referred to by internal Steps of a Network (be it a user defined or an implicitly generated Network) thereby <span class="EMPH">propagate forward</span> to the top, and allocated resources are not released unless the execution of the Activity has finished. Note that in contrast to the Skill element, a Skill Requirement does <span class="EMPH">not</span> appear as an expecco Testsuite element. Skill Requirements <span class="EMPH">only</span> appear in the Block's Skill Requirement Property.		An Activity that refers to a Block element which has Skill Requirements assigned, will always first try to find and <span class="EMPH">allocate suitable Resource objects</span> in the Inventory of its surrounding context, before it starts its execution. Requirements of Blocks referred to by internal Steps of a Network (be it a user defined or an implicitly generated Network) thereby <span class="EMPH">propagate forward</span> to the top, and allocated resources are not released unless the execution of the Activity has finished. Note that in contrast to the Skill element, a Skill Requirement does <span class="EMPH">not</span> appear as an expecco Testsuite element. Skill Requirements <span class="EMPH">only</span> appear in the Block's Skill Requirement Property.

Mawalch am 6. Januar 2018 um 13:29 Uhr

2018-01-06T13:29:02Z

Emi: Die Seite wurde neu angelegt: „Category:Incomplete Category:Work In Progress == Introduction == === The Situation === Since graphical and interactive modeling came up in computer …“

2017-10-06T11:36:44Z

Die Seite wurde neu angelegt: „Category:Incomplete Category:Work In Progress == Introduction == === The Situation === Since graphical and interactive modeling came up in computer …“

Änderungen zeigen

← Nächstältere Version		Version vom 6. Januar 2018, 13:38 Uhr
Zeile 148:		Zeile 148:
	be covered by multiple distinct persons. However, the pivotal thing is that		be covered by multiple distinct persons. However, the pivotal thing is that
	the division of the roles allows a well defined limitation of the required		the division of the roles allows a well defined limitation of the required
	skills, as well as the competencies of the people involved.~~</p>~~		skills, as well as the competencies of the people involved.

	=== The User Roles ===		=== The User Roles ===
Zeile 224:		Zeile 224:
	possible when working directly inside its project. However, if desired, you		possible when working directly inside its project. However, if desired, you
	can still make a copy of an in-lib element, and <span class="EMPH">modify		can still make a copy of an in-lib element, and <span class="EMPH">modify
	that copy</span> to fit your needs.~~</p>~~		that copy</span> to fit your needs.

	Note that the included Libraries each contain an <span class="EMPH">own</span>		Note that the included Libraries each contain an <span class="EMPH">own</span>
Zeile 240:		Zeile 240:
	Technically seen, this is the only difference between them, and you can use		Technically seen, this is the only difference between them, and you can use
	both for import, also your own projects. A Testsuite will be named <span class="CODE">.xlib</span>		both for import, also your own projects. A Testsuite will be named <span class="CODE">.xlib</span>
	only if the author intended it to be a Library.~~</p>~~		only if the author intended it to be a Library.

	=== Arranging Elements ===		=== Arranging Elements ===
Zeile 297:		Zeile 297:
	a <span class="EMPH">topical unit of information</span> that is characteristic		a <span class="EMPH">topical unit of information</span> that is characteristic
	for the element's <span class="EMPH">purpose</span>, and which is editable		for the element's <span class="EMPH">purpose</span>, and which is editable
	or at least displayable to the user.~~</p>~~		or at least displayable to the user.

	A element never has two properties of the same type, and properties are		A element never has two properties of the same type, and properties are
Zeile 317:		Zeile 317:
	made before storing its new state. You get detailed information on the GUI		made before storing its new state. You get detailed information on the GUI
	Browser's Page and Editor management in <a href="./DOC_eXpeccoUserGuide_GUI.html#b1f2aa20-f609-11da-9610-0040c7999506">expecco		Browser's Page and Editor management in <a href="./DOC_eXpeccoUserGuide_GUI.html#b1f2aa20-f609-11da-9610-0040c7999506">expecco
	GUI Documentation/Chapter 3: The GUI Browser Window</a>.~~</p>~~		GUI Documentation/Chapter 3: The GUI Browser Window</a>.


Zeile 534:		Zeile 534:
	Output Pins (because they pass the incoming values from the outside to the		Output Pins (because they pass the incoming values from the outside to the
	Workflow), and the Interface Output Pins behave as Input Pins (because they		Workflow), and the Interface Output Pins behave as Input Pins (because they
	pass the outgoing values from the Workflow to the outside).~~</p>~~		pass the outgoing values from the Workflow to the outside).

	Also note that Interface Pins can also be added and deleted directly inside		Also note that Interface Pins can also be added and deleted directly inside
Zeile 556:		Zeile 556:
	[[Bild:PIC_Concepts_Workflows_MovingSteps.png]]		[[Bild:PIC_Concepts_Workflows_MovingSteps.png]]

	<SPAN class="PICTUREENUM">Figure 5.3.2-2: Positioning Steps </SPAN>		<SPAN class="PICTUREENUM">Figure 5.3.2-2: Positioning Steps</SPAN>

	The building blocks can be <span class="EMPH">moved around</span> solely or in groups inside the Activity Diagram. To do so, one or more building blocks are selected, and then dragged to a different location with the mouse. Connections that are inbetween two of the moved building blocks will be moved directly with them, Connections between moved and non-moved building blocks will be rerouted automatically.		The building blocks can be <span class="EMPH">moved around</span> solely or in groups inside the Activity Diagram. To do so, one or more building blocks are selected, and then dragged to a different location with the mouse. Connections that are inbetween two of the moved building blocks will be moved directly with them, Connections between moved and non-moved building blocks will be rerouted automatically.
Zeile 821:		Zeile 821:
	When an Activity is executed, it locally holds its individual <span class="EMPH">logging information</span>, called its <span class="KEYWD">Activity Log</span>. An Activity Log consists of a chronological list of input and output value events, and of the Notice, Warning, and Error messages that are generated during the Activity's execution.		When an Activity is executed, it locally holds its individual <span class="EMPH">logging information</span>, called its <span class="KEYWD">Activity Log</span>. An Activity Log consists of a chronological list of input and output value events, and of the Notice, Warning, and Error messages that are generated during the Activity's execution.

	While a nested Test Plan element is only an <span class="EMPH">organizational</span> part of the containing Test Plan, the Block elements which are embedded make up the <span class="EMPH">functional </span>part of it. However, it would not be precise to say that the Blocks were executed; when a Test Plan is about to be executed, an <span class="EMPH">implicit Workflow</span> is created first, which simply creates one Step instance for each included Block in the sequence, and then chains these Steps using Enable Triggers to arrange the modeled sequence.		While a nested Test Plan element is only an <span class="EMPH">organizational</span> part of the containing Test Plan, the Block elements which are embedded make up the <span class="EMPH">functional</span> part of it. However, it would not be precise to say that the Blocks were executed; when a Test Plan is about to be executed, an <span class="EMPH">implicit Workflow</span> is created first, which simply creates one Step instance for each included Block in the sequence, and then chains these Steps using Enable Triggers to arrange the modeled sequence.

	In addition to the Workflow, a <span class="KEYWD">Test Wrapper</span> object is created. The Test Wrapper is an Activity that <span class="EMPH">embraces and processes</span> the given Test Item sequence. This artificially generated Workflow is then assigned to the Test Wrapper object, which is also created in the beginning of the execution. Items that are not activated for execution will not produce an implicit Step inside the Test Wrapper objects Internal Workflow. Finally, the Test Wrapper is started and executes the Workflow.		In addition to the Workflow, a <span class="KEYWD">Test Wrapper</span> object is created. The Test Wrapper is an Activity that <span class="EMPH">embraces and processes</span> the given Test Item sequence. This artificially generated Workflow is then assigned to the Test Wrapper object, which is also created in the beginning of the execution. Items that are not activated for execution will not produce an implicit Step inside the Test Wrapper objects Internal Workflow. Finally, the Test Wrapper is started and executes the Workflow.

← Nächstältere Version		Version vom 6. Januar 2018, 13:29 Uhr
Zeile 142:		Zeile 142:
	every subject of one of these roles to act independent of the others. Black-box		every subject of one of these roles to act independent of the others. Black-box
	means, that for the usage of building blocks, not their internal structure,		means, that for the usage of building blocks, not their internal structure,
	but only the interface to the outside, has to be known. <BR>		but only the interface to the outside, has to be known.<BR>

	Depending on the extent and complexity of the conceptual formulation, the		Depending on the extent and complexity of the conceptual formulation, the
Zeile 148:		Zeile 148:
	be covered by multiple distinct persons. However, the pivotal thing is that		be covered by multiple distinct persons. However, the pivotal thing is that
	the division of the roles allows a well defined limitation of the required		the division of the roles allows a well defined limitation of the required
	skills, as well as the competencies of the people involved. </p>		skills, as well as the competencies of the people involved.</p>

	=== The User Roles ===		=== The User Roles ===
Zeile 224:		Zeile 224:
	possible when working directly inside its project. However, if desired, you		possible when working directly inside its project. However, if desired, you
	can still make a copy of an in-lib element, and <span class="EMPH">modify		can still make a copy of an in-lib element, and <span class="EMPH">modify
	that copy</span> to fit your needs. </p>		that copy</span> to fit your needs.</p>

	Note that the included Libraries each contain an <span class="EMPH">own</span>		Note that the included Libraries each contain an <span class="EMPH">own</span>
Zeile 240:		Zeile 240:
	Technically seen, this is the only difference between them, and you can use		Technically seen, this is the only difference between them, and you can use
	both for import, also your own projects. A Testsuite will be named <span class="CODE">.xlib</span>		both for import, also your own projects. A Testsuite will be named <span class="CODE">.xlib</span>
	only if the author intended it to be a Library. </p>		only if the author intended it to be a Library.</p>

	=== Arranging Elements ===		=== Arranging Elements ===
Zeile 274:		Zeile 274:
	wide</span>. A special algorithm ensures that two elements		wide</span>. A special algorithm ensures that two elements
	that are not identical will <span class="EMPH">never</span>		that are not identical will <span class="EMPH">never</span>
	have the same internal ID. <BR>		have the same internal ID.<BR>

	The user usually		The user usually
Zeile 297:		Zeile 297:
	a <span class="EMPH">topical unit of information</span> that is characteristic		a <span class="EMPH">topical unit of information</span> that is characteristic
	for the element's <span class="EMPH">purpose</span>, and which is editable		for the element's <span class="EMPH">purpose</span>, and which is editable
	or at least displayable to the user. </p>		or at least displayable to the user.</p>

	A element never has two properties of the same type, and properties are		A element never has two properties of the same type, and properties are
Zeile 317:		Zeile 317:
	made before storing its new state. You get detailed information on the GUI		made before storing its new state. You get detailed information on the GUI
	Browser's Page and Editor management in <a href="./DOC_eXpeccoUserGuide_GUI.html#b1f2aa20-f609-11da-9610-0040c7999506">expecco		Browser's Page and Editor management in <a href="./DOC_eXpeccoUserGuide_GUI.html#b1f2aa20-f609-11da-9610-0040c7999506">expecco
	GUI Documentation/Chapter 3: The GUI Browser Window</a>. </p>		GUI Documentation/Chapter 3: The GUI Browser Window</a>.</p>


Zeile 534:		Zeile 534:
	Output Pins (because they pass the incoming values from the outside to the		Output Pins (because they pass the incoming values from the outside to the
	Workflow), and the Interface Output Pins behave as Input Pins (because they		Workflow), and the Interface Output Pins behave as Input Pins (because they
	pass the outgoing values from the Workflow to the outside). </p>		pass the outgoing values from the Workflow to the outside).</p>

	Also note that Interface Pins can also be added and deleted directly inside		Also note that Interface Pins can also be added and deleted directly inside
Zeile 542:		Zeile 542:
	as it does in the Schema Definition Editor. However, frozen values are not		as it does in the Schema Definition Editor. However, frozen values are not
	displayed here, and the Triggering Condition Type can't be modified from here		displayed here, and the Triggering Condition Type can't be modified from here
	either. <BR>		either.<BR>

	==== Arranging Steps ====		==== Arranging Steps ====
Zeile 707:		Zeile 707:
	are supported: <img src="./pictures/PIC_GUI_IconSymbol_ProjectComponent_JavaScriptAction">		are supported: <img src="./pictures/PIC_GUI_IconSymbol_ProjectComponent_JavaScriptAction">
	JavaScript syntax, and <img src="./pictures/PIC_GUI_IconSymbol_ProjectComponent_SmalltalkAction">		JavaScript syntax, and <img src="./pictures/PIC_GUI_IconSymbol_ProjectComponent_SmalltalkAction">
	Smalltalk syntax. <BR>		Smalltalk syntax.<BR>

	Each element of this type contains exactly one <span class="KEYWD">Code Content Property</span>, which holds the <span class="KEYWD">Source Code Text Content</span> that is interpreted according to the used languages syntax at runtime. It is also possible to <span class="EMPH">switch the syntax pattern</span> for already implemented Code Blocks, causing the code to be automatically converted to that particular syntax style.		Each element of this type contains exactly one <span class="KEYWD">Code Content Property</span>, which holds the <span class="KEYWD">Source Code Text Content</span> that is interpreted according to the used languages syntax at runtime. It is also possible to <span class="EMPH">switch the syntax pattern</span> for already implemented Code Blocks, causing the code to be automatically converted to that particular syntax style.
Zeile 736:		Zeile 736:
	expecco, the current OS variable environment of the expecco		expecco, the current OS variable environment of the expecco
	session also is the initial OS variable environment for the		session also is the initial OS variable environment for the
	shell process. <BR>		shell process.<BR>

	Inside the code, no direct access to the Data Pins is available. The reason is the nature of the shell and batch execution schema: The according process is running inside a shell, and communicates with the outside via the standard streams <span class="CODE">stdin</span>, <span class="CODE">stdout</span>, and <span class="CODE">stderr</span>. However, the output of the command can be captured by connecting the according Pins to some evaluating Steps.		Inside the code, no direct access to the Data Pins is available. The reason is the nature of the shell and batch execution schema: The according process is running inside a shell, and communicates with the outside via the standard streams <span class="CODE">stdin</span>, <span class="CODE">stdout</span>, and <span class="CODE">stderr</span>. However, the output of the command can be captured by connecting the according Pins to some evaluating Steps.
Zeile 749:		Zeile 749:
	shell command</span> in an OS dependent manner. The command is <span class="EMPH">directly		shell command</span> in an OS dependent manner. The command is <span class="EMPH">directly
	passed</span> to the underlying operating system, so the scope of possible executables		passed</span> to the underlying operating system, so the scope of possible executables
	to call depends on the platform on which the session is running. <BR>		to call depends on the platform on which the session is running.<BR>

	Each element		Each element
Zeile 759:		Zeile 759:
	spawned by expecco, the current OS variable environment of the		spawned by expecco, the current OS variable environment of the
	expecco session also is the initial OS variable environment		expecco session also is the initial OS variable environment
	for the shell process. <BR>		for the shell process.<BR>

	For the executing process, no direct access to the Data Pins is available. The reason is the nature of the command execution schema: The according process is running inside a shell, and communicates with the outside via the standard streams <span class="CODE">stdin</span>, <span class="CODE">stdout</span>, and <span class="CODE">stderr</span>. However, the output of the command can be captured by connecting the according Pins to some evaluating Steps.		For the executing process, no direct access to the Data Pins is available. The reason is the nature of the command execution schema: The according process is running inside a shell, and communicates with the outside via the standard streams <span class="CODE">stdin</span>, <span class="CODE">stdout</span>, and <span class="CODE">stderr</span>. However, the output of the command can be captured by connecting the according Pins to some evaluating Steps.
Zeile 768:		Zeile 768:
	Schema Definition Restrictions</a>. Accessing the Script Content Property through		Schema Definition Restrictions</a>. Accessing the Script Content Property through
	the GUI is described in <a href="./DOC_eXpeccoUserGuide_GUI.html#185a9140-f60c-11da-9610-0040c7999506">expecco		the GUI is described in <a href="./DOC_eXpeccoUserGuide_GUI.html#185a9140-f60c-11da-9610-0040c7999506">expecco
	GUI Documentation/Chapter 6.8: The Console Command Editor</a>. <BR>		GUI Documentation/Chapter 6.8: The Console Command Editor</a>.<BR>

	==== Test Data Generator Blocks ====		==== Test Data Generator Blocks ====
Zeile 857:		Zeile 857:
	=== Defining Skills ===		=== Defining Skills ===

	The <img src="./pictures/PIC_GUI_IconSymbol_ProjectComponent_Skill"></img> <span class="KEYWD">Skill element</span> serves to summarize the elementary <span class="KEYWD">Skill Attributes</span> that <span class="EMPH">characterize</span> a Skill. It is important that only the <span class="EMPH">nature</span> of the Skill is defined in the form of its Skill Attributes, but <span class="EMPH">no</span> concrete values are ever assigned directly to the Skill. Later on, one or more Skills can be assigned to a Resource, which is then concretizing them by span class="EMPH">value assignments</span>. These specifications are taken into account during runtime to decide about the suitability of a Resource for a particular usage purpose.		The <img src="./pictures/PIC_GUI_IconSymbol_ProjectComponent_Skill"></img> <span class="KEYWD">Skill element</span> serves to summarize the elementary <span class="KEYWD">Skill Attributes</span> that <span class="EMPH">characterize</span> a Skill. It is important that only the <span class="EMPH">nature</span> of the Skill is defined in the form of its Skill Attributes, but <span class="EMPH">no</span> concrete values are ever assigned directly to the Skill. Later on, one or more Skills can be assigned to a Resource, which is then concretizing them by <span class="EMPH">value assignments</span>. These specifications are taken into account during runtime to decide about the suitability of a Resource for a particular usage purpose.

	Each element of this type contains exactly one <span class="KEYWD">Skill Attributes Property</span>, which serves to set up and configure the Skill Attributes. This is done in expecco using the <span class="KEYWD">Skill Definition Editor</span>.		Each element of this type contains exactly one <span class="KEYWD">Skill Attributes Property</span>, which serves to set up and configure the Skill Attributes. This is done in expecco using the <span class="KEYWD">Skill Definition Editor</span>.