I'm assuming BA means Bug Administrator (unlike M28 above I am a native speaker, but I've never seen the term except as shorthand for a college degree). In which case, I am one. In our case things are pretty informal, i.e. nobodies going to send a nasty note to the boss or HR saying X exceeded his bug quota and job action is requested. I think it is best to avoid an adversarial relationship between the BA and the developersirement. I take the attitude that we are all working towards the same goal, "providing the best possible service to our customers", and the BA and the developers are part of a team with this goal in mind.
In our case, we don't have formal requirements, but we do have a users manual, and maintaining consistency between the UM and the code is important. It is good to log a found bug, -even its already been fixed, as a customer who runs into the same bug because he's using an older version of the code (pre-bugfix) can see that a similar bug was found and fixed and that he should obtain a more recent code copy. So bug logging, is not to be considered to be a demerit system for developers. Also we recognize that some developers work with Beta customers, who to some extent are also feature testers, and bugs reprts/fixes are a normal part of this process.
We call feature requests, enhancement requests. We don't always implement them. Sometimes a request -or even a bugfix, runs into too much technical debt, and would require too much refactoring to be done in the desired timeframe -or at all. Communication with the customer as to the propects of their requests, and the reasons for the delay -or denial are important. Oftentimes we can suggest other ways for the customer to meet his needs, without changing the codes, i.e. use feature X in combination with feature Y like this, and you can accomplish the same result as wanna-have feature Z.
The important thing here is that respectful, and truthful communication among all parties is crucial. In our case that extends beyond the formal software company, and into the domain of our customers.