Guidlines for UX teams working from a use case document

I am trying to resolve an issue here:

The business analyst team here are adamant that the use case document that they write (including some wireframes that they've done) should be used as a template guide for the UX team - point by point (ie.1. user puts in phone number, address 2. user does this 3. user does that),in how to design the wireframes for a project i'm working on for a firm.

The UX team have the opinion that the use case document should be a document to be interpreted by the UX team to reach the desired solution. as apposed as being followed down to the letter. In other words, we feel that we are having our creativity and analysis skills squashed.

anyone have any thoughts on this?