This is an online, interactive lab powered by Thinkscape. Each lab contains instructions, multimedia, and assessments in an online environment where students can learn at their own pace. As an instructor, you can create and edit instances of this lab, assign them to students, and view student progress.
This is an online, interactive course powered by Thinkscape. Each included lab contains instructions, multimedia, and assessments in an online environment where students can learn at their own pace. As an instructor, you can create and edit instances of this course, assign them to students, and view student progress.
Incorporating code reviews into your software development process costs nothing, requires little research or effort, and provides a significant improvement in code quality. Of all the investments that your team could potentially make in your software development process, this one is reasonably easy with a very high ROI. Why isn't every team and individual engaging in code reviews? Because it requires humility to post code to a team for critique. Before embarking on integrating design and code reviews, read this classic blog series from LabVIEW Champion Brian Powell
VI Analyzer is an essential tool in the code review process. Developed by Darren Nattinger, VI Analyzer can find not just cosmetic issues, but issues that can degrade performance or cause bugs during operation. Many software teams require that code go through VI Analyzer before the team performs their review. Learn directly from Darren in his 2015 LabVIEW Developer Days Session.
Issue tracking is an important part of the overall code review process. The "Resources" tab includes a couple of lists of tools such as Mantis, Redmine, FobBugz, Trac, and Jira. For simple applications you may simply choose to track issues in a spreadsheet. You can begin by downloading the Issue Tracking spreadsheet. This will give you a general idea of the items that you want to capture and then resolve throughout the process. Then check the "Resources" tab to learn about a few tools used in the community. Finally, discuss with peers to determine the best tool for your team.