In my previous blogs Requirements Part 1 and Part 2, I discussed how the requirements fit into the overall project and the specific language that is used in the requirements process. This time we are going to look at the technical aspects of the requirements process. The requirements process is a part of the overall systems engineering process. These technical requirements flow down to the engineers, designers, programmers, suppliers and subcontractors. Problems managing these requirements will most definitely contribute significantly to project failures. This includes not only managing the requirements, but also in the definition of the requirements themselves. Defining the requirements includes two major functions; defining the problem and defining the solution.
Defining the problem is the task of translating the needs of the sponsor into the requirements for the product, service or system. Defining the solution is the task of specifying the components that will meet those needs by becoming accepted deliverables.