INTERNET APPLICATION DEVELOPMENT
MID MARKET ERP DEVELOPMENT
By Brian Terrell
How has CodePartners helped more than 500 companies in nine countries enhance their revenues or reduce their costs? We have a specific methodology to help our clients achieve these impressive results. Over the next several weeks, I’ll spend some time on each step of our process, which is illustrated here.
Today, I’ll discuss the first step of the process, which is gathering and organizing a prospect’s requirements into a Requirements Analysis document.
Always, our process starts by narrowing the gap between what we know and what the prospect knows. We call this process discovery. Our talented Business Analysts ask questions and review business workflows…but most importantly they listen. What does the client think the software automation requirements are? What does solving the problem look like? What will it mean to your company if this problem is solved by software automation?
A well written Requirements Analysis restates what the prospect understands about the issue requiring software automation. Sometimes, both parties realize the issue can be solved without software automation. An important byproduct of the Requirements Analysis should be a rough value proposition -- how we measure the success of the project. We must measure it to know if the automation was successful.
In summary, a Software Development Requirements Analysis states the case for the proposed software automation.
In the next article in this series, we’ll review an example of an actual Requirements Analysis document and show how this document provides much of the material required for a Software Design Document. In each step of our software development methodology, we continue to narrow the gap between what the software development team knows and what the prospect knows.