Studio:Reference Overview - Revision history

Marku: /* References */

2010-06-02T23:16:30Z

References

← Older revision		Revision as of 23:16, 2 June 2010
Line 110:		Line 110:
	* [[Platform Abstraction Layer]]		* [[Platform Abstraction Layer]]
	* [[SCL Overview]]		* [[SCL Overview]]
	* [[Sandbox_Evaluation\|SDKs]]

	[[Category:Studio:Reference]]		[[Category:Studio:Reference]]

Marku: moved Reference Overview to Studio:Reference Overview

2009-09-24T17:27:40Z

moved Reference Overview to Studio:Reference Overview

← Older revision	Revision as of 17:27, 24 September 2009
(No difference)

Marku: /* References */

2009-09-24T17:27:18Z

References

← Older revision		Revision as of 17:27, 24 September 2009
Line 112:		Line 112:
	* [[Sandbox_Evaluation\|SDKs]]		* [[Sandbox_Evaluation\|SDKs]]

	[[Category: Reference]]		[[Category:Studio:Reference]]

Marku: /* STRIDE and the Target Device */

2009-06-07T16:45:14Z

STRIDE and the Target Device

← Older revision		Revision as of 16:45, 7 June 2009
Line 42:		Line 42:
	* Intercept Modules Intercept modules allow remote function calls across hardware (e.g., processor or machine) or software (operating system) platform boundaries.		* Intercept Modules Intercept modules allow remote function calls across hardware (e.g., processor or machine) or software (operating system) platform boundaries.
	* The [[Runtime_Reference \|STRIDE Runtime]] routes messages both within and between platform boundaries and manages the conversion of interface data as it crosses from one platform to another. This "transparent messaging" model means that your test cases can be located on one platform (e.g., as a script running off-target) and your code on another (on-target).		* The [[Runtime_Reference \|STRIDE Runtime]] routes messages both within and between platform boundaries and manages the conversion of interface data as it crosses from one platform to another. This "transparent messaging" model means that your test cases can be located on one platform (e.g., as a script running off-target) and your code on another (on-target).
	* The Platform Abstraction Layer (PAL) isolates STRIDE from the details of your target hardware/software platform, and therefore makes it both portable across target platforms and forward-compatible with future RTOS and/or hardware changes.		* The [[Platform Abstraction Layer\|Platform Abstraction Layer (PAL)]] isolates STRIDE from the details of your target hardware/software platform, and therefore makes it both portable across target platforms and forward-compatible with future RTOS and/or hardware changes.

	== The STRIDE Communication Model (SCM) ==		== The STRIDE Communication Model (SCM) ==

Marku: /* References */

2009-06-07T16:44:28Z

References

← Older revision		Revision as of 16:44, 7 June 2009
Line 108:		Line 108:
	* [[Reporter]]		* [[Reporter]]
	* [[Runtime Reference]]		* [[Runtime Reference]]
			* [[Platform Abstraction Layer]]
	* [[SCL Overview]]		* [[SCL Overview]]
	* [[Sandbox_Evaluation\|SDKs]]		* [[Sandbox_Evaluation\|SDKs]]

	[[Category: Reference]]		[[Category: Reference]]

Marku at 16:42, 7 June 2009

2009-06-07T16:42:04Z

← Older revision		Revision as of 16:42, 7 June 2009
Line 41:		Line 41:
	== STRIDE and the Target Device ==		== STRIDE and the Target Device ==
	* Intercept Modules Intercept modules allow remote function calls across hardware (e.g., processor or machine) or software (operating system) platform boundaries.		* Intercept Modules Intercept modules allow remote function calls across hardware (e.g., processor or machine) or software (operating system) platform boundaries.
	* The STRIDE Runtime routes messages both within and between platform boundaries and manages the conversion of interface data as it crosses from one platform to another. This "transparent messaging" model means that your test cases can be located on one platform (e.g., as a script running off-target) and your code on another (on-target).		* The [[Runtime_Reference \|STRIDE Runtime]] routes messages both within and between platform boundaries and manages the conversion of interface data as it crosses from one platform to another. This "transparent messaging" model means that your test cases can be located on one platform (e.g., as a script running off-target) and your code on another (on-target).
	* The Platform Abstraction Layer (PAL) isolates STRIDE from the details of your target hardware/software platform, and therefore makes it both portable across target platforms and forward-compatible with future RTOS and/or hardware changes.		* The Platform Abstraction Layer (PAL) isolates STRIDE from the details of your target hardware/software platform, and therefore makes it both portable across target platforms and forward-compatible with future RTOS and/or hardware changes.

Marku at 16:41, 7 June 2009

2009-06-07T16:41:17Z

← Older revision		Revision as of 16:41, 7 June 2009
Line 39:		Line 39:
	* [[Build Tools\|STRIDE Build Tools]], a set of command line utilities, allow performing the Stride compile/build process, which may be easily invoked through makefiles or similar build utilities (eg. ANT).		* [[Build Tools\|STRIDE Build Tools]], a set of command line utilities, allow performing the Stride compile/build process, which may be easily invoked through makefiles or similar build utilities (eg. ANT).

	== STRIDE and the Target ~~Platform~~ ==		== STRIDE and the Target Device ==
	* Intercept Modules Intercept modules allow remote function calls across hardware (e.g., processor or machine) or software (operating system) platform boundaries.		* Intercept Modules Intercept modules allow remote function calls across hardware (e.g., processor or machine) or software (operating system) platform boundaries.
	* The STRIDE Runtime routes messages both within and between platform boundaries and manages the conversion of interface data as it crosses from one platform to another. This "transparent messaging" model means that your test cases can be located on one platform (e.g., as a script running off-target) and your code on another (on-target).		* The STRIDE Runtime routes messages both within and between platform boundaries and manages the conversion of interface data as it crosses from one platform to another. This "transparent messaging" model means that your test cases can be located on one platform (e.g., as a script running off-target) and your code on another (on-target).

Marku: /* STRIDE and the Host Platform */

2009-06-07T16:38:14Z

STRIDE and the Host Platform

← Older revision		Revision as of 16:38, 7 June 2009
Line 33:		Line 33:
	* [[Stride Runner\| STRIDE Runner]] provides a command line utility to execute [[Test Units]]		* [[Stride Runner\| STRIDE Runner]] provides a command line utility to execute [[Test Units]]
	* [[STRIDE Studio]] provides a graphical environment allowing software engineers to interactively exercise and verify code during implementation.		* [[STRIDE Studio]] provides a graphical environment allowing software engineers to interactively exercise and verify code during implementation.
			* [[STRIDE Test Space]] is a hosted web application for storing and analyzing your test results.
	* [[AutoScript\|STRIDE AutoScript]] extends your device software’s interfaces with the objects, properties, and methods to make them accessible in a script. This facilitates automated testing and allows you to break dependencies by simulating missing software or hardware components.		* [[AutoScript\|STRIDE AutoScript]] extends your device software’s interfaces with the objects, properties, and methods to make them accessible in a script. This facilitates automated testing and allows you to break dependencies by simulating missing software or hardware components.
	* The STRIDE Runtime routes messages both within and between platform boundaries and manages the conversion of interface data as it crosses from one platform to another. This "transparent messaging" model means that your test cases can be located on one platform (e.g., as a script running off-target) and your code on another (on-target).		* The [[Runtime_Reference \|STRIDE Runtime]] routes messages both within and between platform boundaries and manages the conversion of interface data as it crosses from one platform to another. This "transparent messaging" model means that your test cases can be located on one platform (e.g., as a script running off-target) and your code on another (on-target).
	* The STRIDE ~~platform~~ leverages your host-target connection to support on-target verification. You can select from off-the-shelf host-target connections (media and protocol), or configure your own custom connection.		* The STRIDE environment leverages your host-target connection to support on-target verification. You can select from off-the-shelf host-target connections (media and protocol), or configure your own custom connection.
	* [[Build Tools\|STRIDE Build Tools]], a set of command line utilities, allow performing the Stride compile/build process, which may be easily invoked through makefiles or similar build utilities (eg. ANT).		* [[Build Tools\|STRIDE Build Tools]], a set of command line utilities, allow performing the Stride compile/build process, which may be easily invoked through makefiles or similar build utilities (eg. ANT).
	* [[STRIDE Test Space]] is a hosted web application for storing and analyzing your test results.

	== STRIDE and the Target Platform ==		== STRIDE and the Target Platform ==

Marku: /* See Also */

2009-06-07T16:28:28Z

Marku: /* STRIDE and the Host Platform */

2009-06-07T16:26:35Z

STRIDE and the Host Platform

← Older revision		Revision as of 16:26, 7 June 2009
Line 31:		Line 31:

	* The STRIDE Communication Model is a standard that defines how embedded software components, such as threads and functions, can communicate with each other within an embedded application, as well as with scripts, Windows applications, and other software applications, regardless of the platform on which they are hosted. The SCM also defines each platform's runtime environment requirements to support seamless messaging, remote function calls, and tracing across platform boundaries. The SCM itself is defined by the STRIDE Communication Language (SCL), which is a collection of compiler pragmas, standard C-based data types, and limited C++ extensions. Using the SCL, developers can define unambiguous interfaces between components that allow for communications, regardless of where the components are located. The SCL Wizard streamlines and simplifies working with the SCL by allowing you to quickly capture interfaces and accurately qualify payloads and types.		* The STRIDE Communication Model is a standard that defines how embedded software components, such as threads and functions, can communicate with each other within an embedded application, as well as with scripts, Windows applications, and other software applications, regardless of the platform on which they are hosted. The SCM also defines each platform's runtime environment requirements to support seamless messaging, remote function calls, and tracing across platform boundaries. The SCM itself is defined by the STRIDE Communication Language (SCL), which is a collection of compiler pragmas, standard C-based data types, and limited C++ extensions. Using the SCL, developers can define unambiguous interfaces between components that allow for communications, regardless of where the components are located. The SCL Wizard streamlines and simplifies working with the SCL by allowing you to quickly capture interfaces and accurately qualify payloads and types.
			* [[Stride Runner\| STRIDE Runner]] provides a command line utility to execute [[Test Units]]
	* [[STRIDE Studio]] provides a graphical environment allowing software engineers to interactively exercise and verify code during implementation.		* [[STRIDE Studio]] provides a graphical environment allowing software engineers to interactively exercise and verify code during implementation.
	* [[AutoScript\|STRIDE AutoScript]] extends your device software’s interfaces with the objects, properties, and methods to make them accessible in a script. This facilitates automated testing and allows you to break dependencies by simulating missing software or hardware components.		* [[AutoScript\|STRIDE AutoScript]] extends your device software’s interfaces with the objects, properties, and methods to make them accessible in a script. This facilitates automated testing and allows you to break dependencies by simulating missing software or hardware components.
Line 36:		Line 37:
	* The STRIDE platform leverages your host-target connection to support on-target verification. You can select from off-the-shelf host-target connections (media and protocol), or configure your own custom connection.		* The STRIDE platform leverages your host-target connection to support on-target verification. You can select from off-the-shelf host-target connections (media and protocol), or configure your own custom connection.
	* [[Build Tools\|STRIDE Build Tools]], a set of command line utilities, allow performing the Stride compile/build process, which may be easily invoked through makefiles or similar build utilities (eg. ANT).		* [[Build Tools\|STRIDE Build Tools]], a set of command line utilities, allow performing the Stride compile/build process, which may be easily invoked through makefiles or similar build utilities (eg. ANT).
			* [[STRIDE Test Space]] is a hosted web application for storing and analyzing your test results.

	== STRIDE and the Target Platform ==		== STRIDE and the Target Platform ==

← Older revision		Revision as of 16:28, 7 June 2009
Line 96:		Line 96:


	== ~~See Also~~ ==		== References ==
			* [[Stride Runner\|STRIDE Runner]]
			* [[STRIDE Test Space]]
			* [[STRIDE Studio]]
	* [[Test Units]]		* [[Test Units]]
	* [[Test Scripts]]		* [[Test Scripts]]