Elicitation Notes - AutoRepair7/MarketProject GitHub Wiki

Link to User Characteristics

General Techniques

Interviews: A traditional form of requirement elicitation in which you meet with an individual or a group of experts to learn more about their business, needs, requirements, etc...

Workshops: A *structured *meeting with the stakeholders in which everyone collaborates to define, create, refine, and reach closure on deliverables.

Focus Groups: A representative group of users who come together to work in an activity specifically made to facilitate requirement elicitation.

Observations: Observing the users go about their workday, seeing how they interact with the product, etc...

Questionnaires: Surveys given to large groups of users to understand what they need.

System interface analysis: technique that works for examining the systems to which your system connects. It helps reveal functional requirements.

User interface analysis: technique in which you study existing systems to discover user and functional requirements.

Document analysis: examines any existing documentation for potential software requirements.

Examples of Stakeholders

Examples of related stakeholders:

  • Engineering: Acquirer, panel of potential users, marketing division, research and development department, standardization body, suppliers, verification and validation team, production system, regulator/certification authorities, etc.
  • Development: Acquirer, suppliers (technical domains for components realization), design engineers, integration team, etc.
  • Transfer for Production or for Use: Quality control, production system, operators, etc.
  • Logistics and Maintenance: Supply chain, support services, trainers, etc.
  • Operation: Normal users, unexpected users, etc.
  • Disposal: Operators, certifying body, etc.

More stakeholders:

  • Boss
  • Senior executives
  • Co-workers
  • Team
  • Customers
  • Prospective Customers

Identifying stakeholders

When you are working on a new project and need to find the stakeholders:

Brainstorm who the stakeholders might be. A stakeholder is a person who is affected by the work you are doing, who can have influence over it, or have an interest in it being successful or unsuccessful. Find and identify who the project head, key sponsors, clients, and influencers are. You can find this information by reviewing charter documents, enterprise environmental factors, interviews, focus groups, etc. Communicate with the people around you and ask questions to find their place in the project.


  • Goals: The larger, broader objectives of the software/project.
  • Domain Knowledge: knowledge about the domain. It provides knowledge about the environment in which the software will operate.
  • Stakeholders: To have a successful project, we need to identify the needs and viewpoints of many different types of stakeholders.
  • Business rules: statements that constraint or define some part of the structure or behavior of the business, and the way that the business is run.
  • Operational Environment: Requirements elicited from the environment in which the software will operate.
  • Organizational Environment: making sure that the software can support the business process, structure, culture, internal politics of the organization.