Stakeholder requirements are essentially the needs or expectations that stakeholders have for a particular system or project. They may come from various sources including customers, users, suppliers, partners, employees, or regulatory bodies. These requirements may be expressed in different ways such as specific functionality, performance levels, constraints, or other attributes. However, these stakeholder requirements often lack the precision and clarity of formal system requirements. They might not be testable in a straightforward way or they might be ambiguous in their wording or interpretation. This is why they are often referred to as "stakeholder wishes" or "requests". For example, a stakeholder might express a requirement like "The system should be user-friendly". This is not a clear requirement because it doesn't specify what exactly 'user-friendly' means – it could mean different things to different people. Therefore, it would need to be refined and clarified before it could be incorporated into the system design. To address this issue, business analysts and systems engineers work closely with stakeholders to understand their needs and translate them into clear, unambiguous and testable system requirements. This process may involve various activities such as interviews, workshops, surveys or use case analysis. In conclusion, while stakeholder requirements are critical inputs to any project or system development effort; they must be carefully managed and translated into formal system requirements that can guide the design and implementation process. --- ## Tags #StakeholderRequirements #SystemDesign #BusinessAnalysis #SystemsEngineering #ProjectManagement #UserFriendly #SystemRequirements #StakeholderManagement --- ## Parent Concepts - [[Stakeholder Management]]: Stakeholder requirements are a key aspect of stakeholder management, as they outline the needs and expectations of different stakeholders in a project or system. Understanding and managing these requirements is crucial for successful stakeholder relations. - [[System Design]]: The process of system design involves translating stakeholder requirements into clear, unambiguous and testable system requirements. These refined requirements then guide the design and implementation process. - [[Business Analysis]]: Business analysts play a critical role in deciphering stakeholder requirements, often working closely with stakeholders to understand their needs and translate them into clear system requirements. - [[Systems Engineering]]: Stakeholder requirements are an essential input in systems engineering, as they inform the development of formal system requirements that guide the design and implementation process. - [[Project Management]]: In project management, understanding and managing stakeholder requirements is vital for delivering a successful project that meets all stakeholders' expectations. --- ## Related Concepts - [[Stakeholder]]: Stakeholders are the source of stakeholder requirements. They can be anyone who has an interest in the project or system, including customers, users, suppliers, partners, employees, or regulatory bodies. - [[Requirement]]: Stakeholder requirements are a type of requirement that outlines the needs or expectations of stakeholders for a particular system or project. - [[Ambiguity]]: Stakeholder requirements often lack precision and clarity and may be ambiguous in their wording or interpretation. This ambiguity needs to be resolved for these requirements to be useful in system design. - [[User-friendly]]: This is an example of a vague stakeholder requirement that lacks specificity. What exactly 'user-friendly' means could vary between stakeholders and would need to be clarified before it could be used as a formal requirement. - [[Use Case Analysis]]: This is one method that can be used to understand stakeholder requirements. It involves creating detailed scenarios to capture how a system should behave from the user's perspective. - [[System Requirement]]: These are clear, unambiguous and testable requirements that guide the design and implementation process. Stakeholder requirements need to be translated into these formal system requirements.