Code Rewrite Case Study

Problem
System was critically behind schedule
• Months of “one last bug”
• Lots of unexplained behaviors
• Nesting of deep sequence structures
• No use of data flow, nearly all code hidden, and lots of backward flows
• Hard to read code, lack of comments, hidden Wires, and little use of subVIs
Capabilities
• MS in Software Engineering
• Decades of Software Engineering experience
• Well-developed coding standards
• Flexible scheduling
• Worked 90-hour weeks to bring in schedule
Solution
Elimination of Stacked Sequence structures
• Replaced with a hierarchy of subVIs
• Each with extensive documentation
• Use of data flow, including universal error flow
Results
• Fixed all remaining bugs & got schedule back on track
• System paid for itself in six months
• Customer very happy; requesting new projects from us
Request a Free Consultation

Ready for a solution that fits? Get started with CSL today!