What is JRD in software engineering?

Question

What are Joint Requirements Development (JRD) Sessions? I know they are part of software engineering, but I didn’t understand this part:

Requirements usually have unknown interfunctional implications for individual stakeholders and often lost or incompletely defined during interviews with parties interested parties. These multifunctional implications can be achieved by holding JRD sessions in a controlled environment, facilitated by a trained facilitator (business analyst), in which stakeholders participate in discussions to meet requirements, analyze its details and discover interfunctional implications. A dedicated scribe must be present to document the discussion, freeing the Business Analyst to lead the discussion in a management that manages appropriate requirements that meet the objective of session.

JRD sessions are analogous to application design sessions sets . In the first, the sessions elicit requirements that guide the design, while the second outlines the specific features of the design be implemented in accordance with the elicited requirements.

Source: Wikipedia (English)

Answer 1

The process of identifying and analyzing requirements involves a number of stakeholders - people and organizations interested or affected by the developing system.

A recurring challenge in projects is to deal with conflicts between the views stakeholders have of the system and what it should do. Just as an illustration, in a transport management system, a request from a stakeholder A for the system to display a map with the current position of vehicles with a minimum accuracy of 5 meters may conflict with a request from another stakeholder B who set a limit on the price of the Gpss to be purchased, which may result in measurements of lower accuracy.

In this context, the JRD are sessions conducted with the presence of stakeholders from different areas and with different views, aiming to identify possible conflicts, contradictions, impacts and effects on the requirements - that would not be perceived if the analysis were made from the perspective of only one or a small group of stakeholders.