Introduction to Process of Formulating Products Requirements
Software project life cycle begins at the moment when the customer takes decision to replace the existing system or desires to acquire a completely new system. The customer can be any department of your company, a separate company or agency that enters into employment contract with you. A customer can be a mass production market selling active demand ready-made software products. Customer expectations can be represented by a set of requirements, where requirement means a description of what the system can to do, or a description of some operating conditions which need to be provided so that the system can perform its tasks. Requirements define what the system should perform, but not how it should perform it. The latter means that the focus of attention is the customer’s task and his business processes, but not how the solution is achieved. Outsourced software testing is what you really need to reduce development costs and mitigate the risks associated with unexpected project failures.
Formulating requirements for the software system. We analyze this process from the point of view of testing specialists who seek to obtain information that supports test planning activity in the early stages of development, strive to detect defects already in the requirements documents themselves, so that they can have minimum errors at later stages of development.
Identification of requirements is done in a question-answer format. Slides, mock-ups and prototypes are used to offer various options to the customer. To know what the customer expects from the product, namely to collect customer wishes, it is reasonable to hold interviews or use FAST(Facilitated Application Specification Techniques) that is a special type of customer interviews, which facilitates the identification of the requirements.
As requirements are defined by the user, they must be recorded into a document known as the requirements definition document. This document is drawn up in the form of listed requirements formulated during customer interviews. It is an agreement between the customer and the organization performing the development and design tasks, about what should be created. The requirements definition document is written in natural language, which is understandable to both the customer and the teams that develop and maintain the system.