Final answer:
Requirements elicitation for an Embedded software project usually uses workshops, interviews, and observations. System Interface Analysis, on the other hand, is more suitable for later stages after design decisions have been made and is generally not used early in requirements elicitation.
Step-by-step explanation:
The techniques that should be used for requirements elicitation in an Embedded software project are critical to ensure that the developed system meets all the needs and constraints of the project. Techniques such as workshops, interviews, and observations are typically quite effective. Workshops involve group discussions and brainstorming which can generate a broad range of ideas and requirements. Interviews allow for detailed insights from individual stakeholders, reflecting their specific concerns and needs regarding the embedded software. Observations involve watching end-users interact with the current system, which can reveal implicit requirements and actual usage patterns that may not be captured through discussion alone.
However, System Interface Analysis might not typically be used in the early stages of requirements elicitation for an Embedded software project. This technique is more appropriate for analyzing interactions between different systems once some requirements have already been established and design decisions have been made. Requirement elicitation is about understanding the needs before designing a solution, whereas system interface analysis is about understanding how different systems will interact after some design decisions have already been made.