Use Case Scenario Example
Windchill Integrations for Embedded Software supports numerous use case scenarios. Contact your PTC representative for further information about use case scenarios for this product.
The following use case provides an example of how this product supports the integration of the software deliverables within the overall product development. In this example, a consumer product includes a part that contains firmware designed to control a particular function of the product.
1. Product Manager creates a product structure in Windchill, which includes a software part for the firmware.
2. Software Project Manager created folders for software artifacts in Windchill, and assigns the development of the firmware to a Software Engineer.
3. Software Engineer sets up the build environment for the project, and defines a step in the build process to upload the build artifacts and other attributes, such as build number and label, to the central build repository in Windchill Integrations for Embedded Software.
4. Software Engineer begins the development of the firmware. A continuous build process creates new builds of the firmware, and each build is uploaded to the software build object in Windchill Integrations for Embedded Software.
5. If one of the components of the firmware was previously developed and can be reused in this project, Software Engineer can update the build script to download this component from Windchill Integrations for Embedded Software, and use it as part of the build process.
6. The source code associated with the software build for the firmware can be stored in the designated location in Windchill Integrations for Embedded Software using software document objects.
7. Once the firmware is completed and ready for testing, Software Project Manager can start the promotion process.
8. During the testing process, defects can be created in Windchill Integrations for Embedded Software against a specific software build and associated with the corresponding defects in the remote defect tracking system.
9. Defects can be assigned to Software Engineers using Windchill assignments that are added as tasks to the Eclipse task list.
10. As the defects are fixed and closed, a new version of the software build is uploaded. Software Project Manager can review the defects that were reported and submitted against the software build.
11. After the review and testing are completed, the firmware can be approved by the Software Project Manager.
12. As the final step in the promotion process, an association is made between the software build object in Windchill Integrations for Embedded Software and the software part in Windchill.
13. The firmware is now available through the associated software part in the product configuration, integrating the correct version of the firmware with the released version of the product.