Requirements Gathering and Tracking

Capturing and communicating requirements can be key to ensuring that the deliverable is indeed what the customer, even internal customers, was expecting. The Achilles heel of LabVIEW is that it allows us to rapidly prototype and build small systems. As such it often lures the developer into thinking that it is safe to skip the process of gathering and managing requirements. However, regardless of your software process, you still must know what your customer expects you to deliver. Each of you will implement a unique process for your team and this section will provide some resources to guide you in that decision. We will be adding additional content in the coming months.



This is a quick guide to help you get started and identify considerations as you evolve this practice on your team.
"Joel on Software", a popular blog, shares a few stories on why you should have functional specifications
Having well-defined requirements at the beginning of a project can help pave the road to success. Stop trying to guess what you think your customer wants and start writing unambiguous requirements that are both verifiable and traceable.  Learn more about requirements traceability and how it helps project management, regulatory compliance and even improves software quality.  Explore an improved technique for requirements tracking through an OSLC layer for the LabVIEW IDE. 
How does one define a "good requirement"? Have you ever seen the following requirement: "The software should be easy to us"? How do you validate that requirement? This short and succinct book explains what a good requirement is and how to facilitates the conversation that extracts the requirements. It is a must read for any software project lead.
Now in its third edition, this classic guide to software requirements engineering has been fully updated with new topics, examples, and guidance. Two leaders in the requirements community have teamed up to deliver a contemporary set of practices covering the full range of requirements development and management activities on software projects.
Tecnova, an NI Alliance Partner, provides a free Requirements Specification Template for your use.
One of the most popular software tools that has been designed for requirements management is: IBM Rational Doors. This link will take you the page where you can evaluate the tool and determine whether it belongs in your workflow.
This blog post, kicked off by LabVIEW Champions Brian Hoover, explores many ways to use bookmarks in LabVIEW
This tutorial will show you how to implement requirements traceability with VeriStand.
Software engineering processes become even more important as you navigate the regulatory requirements and business demands when using LabVIEW for test and automation for medical devices. This course delivers best practices for design validation and manufacturing test using a fictional example of a medical device manufacturing test fixture throughout this course to illustrate concepts and provide a basis for discussion.
Log in to submit a comment.