Studio:Folder Layout: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 21: | Line 21: | ||
== Documents == | == Documents == | ||
;Customer | |||
:<ul><li>customer-supplied documents that are not included or linked on the project portal wiki</li></ul> | |||
;S2 | |||
:<ul><li>S2-generated documents that are not included or linked in the project portal wiki</li><li>S2-generated documents that have been uploaded to the project portal wiki and embedded in a wiki page. (e.g. Visio drawings, screen shots, etc.)</li></ul> | |||
==Source== | ==Source== | ||
Customer source code required to build the target is stored here. This includes any makefiles, etc. | |||
Subfolder organization should follow that used by the customer. | |||
==Target== | ==Target== | ||
Target binaries | |||
Workspace database (.sidb) | |||
==TestAssets== | ==TestAssets== | ||
;TestWorkspace | |||
: Test workspace files go here | |||
:TestUnits | |||
: If the workspace has test units defined, source files go here | |||
;TestScripts | |||
: Test scripts | |||
;SCL | |||
: SCL | |||
;UtilityScripts | |||
: Utility scripts | |||
[[Category:STRIDE Workspace Best Practices]] | [[Category:STRIDE Workspace Best Practices]] |
Revision as of 18:39, 24 November 2008
This article outlines standards for placement of STRIDE solution files and folders.
Folder Overview
<Solution Root> Documents -- relevant documents Customer S2 Source -- customer target source Target -- instrumented target binary and STRIDE databse TestAssets -- test assets TestWorkspace TestUnits TestScripts SCL UtilityScripts
Documents
- Customer
- customer-supplied documents that are not included or linked on the project portal wiki
- S2
- S2-generated documents that are not included or linked in the project portal wiki
- S2-generated documents that have been uploaded to the project portal wiki and embedded in a wiki page. (e.g. Visio drawings, screen shots, etc.)
Source
Customer source code required to build the target is stored here. This includes any makefiles, etc.
Subfolder organization should follow that used by the customer.
Target
Target binaries Workspace database (.sidb)
TestAssets
- TestWorkspace
- Test workspace files go here
- TestUnits
- If the workspace has test units defined, source files go here
- TestScripts
- Test scripts
- SCL
- SCL
- UtilityScripts
- Utility scripts