Actors and Stakeholders in

the Requirements
Engineering Process
•Requirements engineering is a crucial phase
in software development that involves
gathering, documenting, and managing the
requirements for a system. Various actors
and stakeholders play essential roles in this
process, and there are established
processes and methodologies for effective
requirements engineering.
Actors & Stakeholders:
• Actors are persons, groups, or organisations acting within a system of
interest.
• Stakeholders, on the other hand, are persons, groups, or
organisations that are (1) affected by the project, (2) interested in the
project, and/or (3) able to affect the project
• Customer/Client:
• The primary source of requirements.
• Provides information about the needs and expectations of the system.
End Users:
• Individuals who will ultimately use the system.
• Contribute insights(‫ )آگاهی‬into usability and functionality requirements.
• Business Analysts:
• Analyze and document business processes.
• Act as a bridge between the business stakeholders and the development
team.
• System Analysts:
• Analyze technical aspects of the system.
• Collaborate with business analysts to create comprehensive requirements.
• Developers:
• Implement the system based on the specified requirements.
• May provide feedback on the feasibility and technical constraints.
• Testers:
• Validate that the implemented system meets the specified requirements.
• Identify and report defects.
• Project Managers:
• Oversee the requirements engineering process.
• Ensure that the project stays on schedule and within budget.
• Regulatory Authorities:
• Define legal and compliance requirements.
• Ensure that the system adheres to relevant standards and regulations.
• Domain Experts:
• Provide specialized knowledge about the industry or domain.
• Offer insights into specific domain requirements.
 Requirements Engineering Process:
• Elicitation(‫) نکالنا‬:
• Gathering requirements from stakeholders through interviews, surveys, and
workshops.
• Analysis:
• Analyzing and prioritizing requirements for feasibility and impact.
• Specification:
• Documenting requirements in a clear and unambiguous manner.
• Validation:
• Ensuring that the specified requirements meet the needs of the stakeholders.
• Management:
• Tracking changes, managing versions, and handling traceability of requirements.
Process Improvement for Requirements
Engineering:
• Continuous Feedback:
• Establish mechanisms for continuous feedback from stakeholders throughout the
development process.
• Traceability:
• Implement traceability matrices to trace requirements from their origin to the final
implementation.
• Change Control:
• Define a robust change control process to manage changes to requirements and
assess their impact.
• Prototyping:
• Use prototyping to validate and refine requirements before full-scale
implementation.
• Documentation Standards:
• Define and adhere to documentation standards to ensure clarity and consistency
in requirements.
• Automated Tools:
• Implement automated tools for requirements management and traceability.
• Training:
• Provide training for team members on effective requirements engineering
practices.
• Metrics and Measurement:
• Establish metrics to measure the effectiveness of the requirements engineering
process and identify areas for improvement.

(By involving the right stakeholders, following a structured process, and

continuously improving the process, organizations can enhance the success of their
requirements engineering efforts and ultimately deliver high-quality software that
meets stakeholder expectations.)
Social and Cultural Issues in Requirements
Engineering
• Social and cultural issues play a significant role in the success of
requirements engineering, influencing how stakeholders
communicate, collaborate, and understand the needs of a system.
Ignoring these factors can lead to misunderstandings, misalignments,
and project failures. Here are some key social and cultural issues in
requirements engineering:
• Communication Styles:
• Different stakeholders may have varying communication styles based on their cultural
background. Some cultures may be more direct, while others may prefer indirect
communication. Misinterpretations can occur if these differences are not understood
and managed.
• Language Barriers:
• When working in a multicultural environment, language differences can lead to
misunderstandings. Ambiguities in requirements documentation may arise if there is a
lack of clarity in communication.
• Cultural Norms and Values:
• Cultural norms and values influence the priorities and expectations of stakeholders. For
example, in some cultures, hierarchy and authority play a crucial role, while in others, a
more egalitarian approach may be favored. Understanding these differences is
essential for effective collaboration.
• Trust and Relationships:
• Building trust is vital in requirements engineering. Cultural differences can affect how
trust is established and maintained. Face-to-face interactions, relationship-building
activities, and understanding each other's backgrounds can contribute to building trust.
• Decision-Making Processes:
• Cultural differences can impact decision-making processes. In some cultures, decisions may
be made collectively, while in others, they may be more hierarchical. Understanding how
decisions are made is crucial for aligning requirements with the expectations of decision-
makers.
• Time Orientation:
• Different cultures have varying attitudes toward time. Some cultures emphasize punctuality
and adherence to schedules, while others may have a more relaxed approach. This can
impact deadlines and the overall project timeline.
• Individualism vs. Collectivism:
• Cultural orientations toward individualism or collectivism can influence how stakeholders
prioritize their needs. In individualistic cultures, individual goals and achievements may be
emphasized, while in collectivist cultures, group goals may take precedence.
• User Involvement:
• Cultural factors can affect the level of user involvement in the requirements engineering
process. In some cultures, end users may be more vocal and involved, while in others, they
may be more reserved. Understanding these dynamics is crucial for gathering accurate and
comprehensive requirements.
• Ethical Considerations:
• Cultural norms can influence ethical considerations and perceptions of what is
acceptable or unacceptable. This can impact the definition of requirements
and the expectations for system behavior.
• Documentation Preferences:
• Cultural preferences may influence the way stakeholders prefer requirements
to be documented. Some cultures may prefer detailed and formal
documentation, while others may favor more concise and informal
approaches.

(Addressing social and cultural issues in requirements engineering

requires a combination of cultural awareness, effective communication
strategies, and a willingness to adapt processes to accommodate diverse
perspectives. It's essential to create an inclusive and collaborative
environment that respects and embraces cultural differences, ultimately
enhancing the success of the requirements engineering process.)