Introduction to requirement analysis

Requirements analysis is an important stage in the systems engineering & software development processes. Requirements analysis in both these mentioned case, looks at addressing those tasks that go into determining the needs or conditions to meet for a new or altered product, taking into account possible conflicting requirements coming from various stakeholders. Requirements analysis is crucial to the success of a development project. Requirements must be SMART (specific, measurable, actionable & testable) to an identified business need or opportunity. It defines to what levels of detail are to be made sufficient for system design. Requirements can be both functional and non-functional.

Overview about requirement analysis

If one were to conceptually look at requirements analysis it would include the following activities:

Requirements elicitation and collaboration:This involves making use of certain techniques to capture the stakeholder requirements that when ultimately addresses can lead to dissatisfaction, satisfaction or delightedness. As it involves more a single person working together to meeting a common objective it can be stated to being a collaborative effort.

Requirements analysis:Through this effort we can determine if the stated requirements are clear, non-ambiguous and non-contradicting.

Requirements analysis can be considered to be lengthy and strenuous process during which many psychological skills will be involved to develop a new system to change the environment and relationships that exist between people. The most important aspect shall be here to identify all relevant stakeholders, take their needs into account and finally ensure they the implications of the new system are clearly understood. For this various techniques are employed by the requirements engineer and requirement list then created. This can be through the use of techniques like brainstorming, brainstorming paradox, interviews, surveys, workshops, focus groups etc.

Requirements analysis as a part of requirement gathering

Requirements engineering refers to a systematic and a disciplined way of specifying and managing the requirements and has the following main goals:
·Knowing what the stakeholder’s desires and needs are, their relevance to the system to be developed, achieving consensus amongst these stakeholders, documenting the requirements and managing becomes requirements engineering aspects to be addressed.

In certain cases requirements engineering commences with feasibility study activity having been completed. This now means requirements analysis can now begin. If a feasibility study were to follow requirements analysis then feasibility shall be determined before finalisation of requirements.

Keys topics in requirements analysis

1.Identification of Stakeholder:
Stakeholders may be defined as anyone or any organisation that directly or indirectly influences the way in which the system requirements can be affected.

A few examples for stakeholders could include:
·System operators
·Beneficiaries of the system
·Procurers of system
·Regulatory bodies
·Someone who are likely to cause havoc to the system

Issues in requirements analysis