As Sandy indicated, the BABOK uses solution requirements as a generic term:
"Solution Requirements▶▶ describe the characteristics of a solution that meet business requirements and stakeholder requirements. They are developed and defined through requirements analysis. They are frequently divided into sub-categories, particularly when the requirements describe a software solution:
Functional Requirements▷▷ describe the behavior and information that the solution will manage. They describe capabilities the system will be able to perform in terms of behaviors or operations—specific information technology application actions or responses.
Non-functional Requirements▷▷ capture conditions that do not directly relate to the behavior or functionality of the solution, but rather describe environmental conditions under which the solution must remain effective or qualities that the systems must have. They are also known as quality or supplementary requirements. These can include requirements related to capacity, speed, security, availability and the information architecture and presentation of the user interface."
I think the term 'solution requirements' is appropriate, and haven't really run into too many issues when using it once my stakeholders understand what it means (although I haven't worked exclusively in an IT department for several years now; most of my work is for the business and only involves IT solutions on occasion).
As we've all noted Business Anaysis as a profession is still young, so Kimbo I think it would be great for you to read the BABOK and give feedback to the IIBA on its content. I am in a discussion group of BAs, executives, unit managers, and consulting business development managers that are reviewing the BABOK chapter by chapter bi-weekly. We've come up with areas that we think are well defined and areas where there could be improvement. It's helped everyone involved get a better handle on what is expected of BAs and how to develop better BA practices within our respective organizations. The disagreements over content in the BABOK have led to great discussions around what the central purpose of a BA is/could/should be and how to best go about doing the work that needs to be done.