Different Sources of Understanding Software Requirements
The requirements specifications of the software provides a base for developing the system and this is one the most crucial steps in SDLC. Although the stakeholder is the ultimate source of the requirements, you cannot depend on the specification stated by a single source.
For single source requirements, there will be almost no possible verification of specifications because no comparable checks will exist for the prescribed specialties from a variety of sources including customers, consumers, problem domain experts, connected domain experts, potential users, operators, experienced developers, and even critics of the system. A set of knowledge data is produced from the execution of an existing manual or semi-automatic system.
Feedback from owner, user, operator, other workers. and the beneficiaries are also gathered and their suggestions and expectations about the new system are recorded. The data collected is evaluated and refined collectively and in consultation with the people involved.
- Stakeholders/Buyers :
They are the persons responsible for accepting and executing the software. They can be individual individuals, organizations, trusts or even the government or public of a country.
- User/Beneficiaries :
These are the users of the product for which the product is intended.
- Operators :
They are the persons who work on the software to make the services of the software available to its beneficiaries or the end users.
- Domain experts :
They are professionals with experience and expertise of the domain in which the software provides its services, viz. insurance, financials, banking, communication, data transfer, networking, etc. Domain experts unwind the hidden or unseen probable requirements or risks involved in product development.
- Developer :
The software engineering responsible for developing the software to make it provide the expected services. They are responsible for software design, prototype development, and technical feasibility. They work closely with the end-users, buyers, and application experts.
- Automated Tools :
In the new generation of information technology and software development paradigm, many automated and semi-automated tools are available that allow for the affirmation and management of the need for building the system. such software also provides input. System/software requirements.
- Past Experience/Case Studies :
An organization working in the similar or same domain may provide its past experience or even documented case studies. This helps have a clearer picture of the requirements, which may otherwise be left hidden.
- Connected People/Machine/Environment :
People associated with software or environmental factors and IT domain may give a lot of provide information about constraints involved in development, development, its and environment implications on software.
- Tester :
Testers are a good source of information about the user’s behavior or the predictive behavior of the system’s condition. continuous contact with real users for their input. In such cases, examiners may use their experiences and analytical skills to provide input.