Wednesday, January 3rd, 2018 / by Excel Champ
If you’re about to embark upon a software development engagement, you may be wondering about the best way to gather and communicate your requirements. Here are five tips that will help put everyone on the same page from the start:
At ExcelHelp.com, our team of expert Visual Basic for Applications (VBA) and Structured Query Language (SQL) developers can guide you through the requirements gathering process.
Provide a list of all the acronyms and industry specific terms that may be used during the project, along with their definitions. Include the names of any software products or databases that you are currently using, if they are related to the project. If your team refers to them with alternate names, then be sure to include those, as well. This relatively simple task can greatly accelerate the developer’s understanding of your project and avoid potentially costly misunderstandings.
A simple sketch of your current system can go a long way in helping communicate the problem you are trying to solve. This diagram should show where data is stored (database, cloud service, Excel file, etc.), where it is processed and how it is used (reports, quotes, input to another system, etc). If you envision a new configuration, then sketch that as well. Keep it simple to start with and add clarity later, as needed.
Ask each person on your team to write down what they need the software to do. Here are a few examples of user stories:
These user stories tell the developer what the software should do on a high level. You may have a very time-consuming, cumbersome process for doing these tasks now, but try to explain that in the diagram that you create in step 2.
At a high level, describe what the software needs to do. Include the overall objective of the project and any business rules that need to be incorporated. The overall project objective might be something like this:
“provide improved decision-making support by automating the integration of data from multiple systems and generating visualizations.”
Here is an example of a business rule:
“when the scrap generated by the production process is below 10%, highlight the cell green.”
Non-functional requirements clarify your expectations regarding a broad range of details concerning the application and how it will be used. Document each of the following items and review them with the developer early-on:
Let our expert VBA developers help you develop and implement your software solution. Contact our team to schedule a free consultation by calling 1-800-682-0882 or visit our website at ExcelHelp.com to submit an inquiry online.
I can not recommend ExcelHelp more highly. We had been struggling to complete a critical project and finding them was a lifesaver. Tom was knowledgable, professional, personable, patient and responsive. Look no further for your database programming needs. Thanks Tom and ExcelHelp.com!Randy Hartnell
We anticipate a long business partnership with ExcelHelp and look forward to working with them. I have been nothing but impressed with your firm’s services, your team members tenacity and the overall results. Sometimes you have to travel a bumpy road trying different firms until you find the one that fits.Posted By: Charlene Faber
Chief Operation Officer, Current Builders
I’d like to express my gratitude for the help and cooperation we’ve received from your entire organization during the development of our Modeling Utility. Over the past several weeks we’ve engaged key customers worldwide...We have confidence that this effort will add significant capability and value to the overall success of the program.Business Development Manager
Network Architecture and Strategy
Posted By: Marty M.