A business analyst is required to document and represent all the attributes identified for a requirement as part of the elicitation results information.

All requirements must be documented in enough detail so that they exhibit the characteristics of the requirements and design quality. As part of specifying the requirements, they can also be categorized according to the schema described in an earlier section. Typically, elicitation results contain information about different types of requirements, which means different types of requirements are specified at the same time during an initiative. 

Let's imagine a real-world practical example scenario.

You are reviewing the elicitation results from a recent workshop and discover functional requirements describing the new online portal's required functional capabilities. You also find some non-functional requirements relating to the performance and security requirements for the online portal as part of the workshop output. You should document these requirements and clearly show which requirements are functional and non-functional in your documentation.