Specification activities involve translating the collective requirements into written specifications that are in terms that can be understood by all stakeholders. Requirement specifications are elaborated from and linked to the scoping and analysis models, and structured into a logical framework providing a repository of requirements. Requirements are categorized into types, depending on their source and applicability. Understanding requirement types helps in the process of documenting and prioritizing them. It also enables the technical team to conduct a trade-offs analysis, estimate the system cost and schedule, and better assess the level of changes to be expected. Typically, requirements are broadly characterized as functional or supplemental (a.k.a. nonfunctional). In addition, constraints imposed upon the requirements and/or the solution are captured as part of the categorizing process. How would you define the different types of requirements? How are these used to help define a project