Specifying Business Requirements

[chanos]

Hi guys,

I'm wondering what techniques people are using to model data and field business requirements/rules in EA?

In the past we've used a combination of a use cases, business domain model, wireframes and supplmentary information (in a table) to indicate what fields are displayed on the screen, behaviour of these fields and any special rules. We then trace these wireframes to specific system interaction steps modelled in use cases.

I believe that this is perhaps too prescriptive and can limit creativity during the high level and detail design stages of a software development process.

Has anyone used any other artifacts to represent these requirements that are less prescriptive but still highlight specify business rule behaviour particularly identifying what fields are optional / mandatory?

If there is a more appropriate section to  post such a question please let me know.