|
|
Software Requirement Specifications
W. L. Reid & Associates knows the importance of developing a system correctly and that cannot happen without defining accurate, precise, and valid requirements. Requirements must be accurate and must capture the actual meaning of customer inputs and not attempt to interpret or embellish those inputs. Requirements are the raw material from which design documents, implementation code, and test designs / implementations are derived and so it is critical that requirements are correct. A requirement should first be specified in the language of the customer so that concurrence with the customer is assured. That form of the requirement is the written version of the requirement. An essential property of all software requirements is that they are verifiable and our software requirement specifications adhere to this property. We use the techniques of conducting interviews, facilitating meetings, and observation with all relevant sources to ensure all requirements are gathered. The specifications are written in accordance to industry standard and our requirements elicitation clearly captures expected variations over the software lifecycle. Failure to capture the right requirements is a major risk. Inadequate generalization in the requirements leads to a design that is too fragile and cannot deal with the changes that happen over the lifecycle of the software. Over generalization leads to excessive efforts in the development cycle which must account for the generality by developing too many specific products. Our specifications are written to withstand a thorough requirements assessment before design can begin and reduces the chance of a later re-design. Because of our software engineering background, we are capable of producing a document that provides a realistic basis for estimating development costs, risks, and schedules.
|
