Hi all,

I have a question about using swimlanes + UI + requirements  vs. using Use Cases + UI.   Can someone describe to me the pros and cons of these different strategies?

Background info:

We use Enterprise Architect to manage the requirements. When a swimlane/BPMN is created, all the related requirements information can be tied to each step of the process. This includes UI, external files, requirements, etc.

Goal of our application:

Allow a group of users to upload a transaction file (CSV format) via our web interface, then validate this information and enter it into the database tables of our ERP system.

The basic process is the following, which I did as a swimlane (about 10 steps, extensions/alternates are described via BPMN gateways/other symbols):

1. User uploads file.

2. System validates file. Input "correct" transactions into ERP. If any transactions fail validation, they are rejected and these transactions are stored in a CSV file on the network share for user to correct and re-submit.

Now, in Enterprise Architect, inside each process in the swimlane there are requirements, pre-conditions, acceptance criteria, links to external files (Excel/UI prototypes, etc).  I have not written any use cases because I feel that this visual description contains all the needed information to code the application.

Can someone tell me the pros and cons of doing it this way vs. using formal Use Cases + UI? In larger and more complex applications, wouldn't I be able to do this the same way by creating higher or lower level swimlanes as needed, and in some way convey their relationships?

Thanks for your input!