Design and Code Reviews

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
by Brian Powell | athenahealth

INCLUDED COURSE MODULES

This is a quick one-page overview to assist someone who is leading a team to integrate code reviews into their standard practices.
COMING SOON: Before wiring a single line of code, you want to review your design. This module will guide you through that process. (Content to be added June 2017)
This session is a great place to begin the conversation about code reviews. Consider your workflow, how the team shares code, and what structure you can implement now.
So what is the code review process. What is required? Who is involved? Brian Powell has shared his classic NIWeek session. Come learn from a veteran.
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.
This blog post, kicked off by LabVIEW Champions Brian Hoover, explores many ways to use bookmarks in LabVIEW

Related Resources

EXPLORE

These labs have related concepts that can expand student experience.

Log in to submit a comment.