How Do I Get My Hardware, Software and Systems Engineers to Agree on What They're Building When They Have Completely Different Perspectives?

Most organizations rely upon some documentation or drawing tool to capture system architecture. Keeping that document current is challenging - making it relevant to the software engineer is especially difficult. State modeling tools that are of interest to some systems engineers are only of incidental interest to the software engineer. Very few software engineers have the interest or the skills to read a schematic diagram or other hardware document to determine how to interface their software to the hardware. How then, can a team of engineers with different needs and perspectives collaborate on the development of a real-time embedded system and remain coordinated throughout the life of the project? This paper briefly describes how Real-time Studio provides a rich environment to ensure this team communication, coordination and collaboration.

View Entire Paper | Previous Page | White Papers Search

If you found this page useful, bookmark and share it on: