Dear Jason,
Think of this as a piece of work that responds to one business event. The
business event is: Person Wants To Be A Member of Our Organisation
The input dataflow is everything that comes from the person when that event
takes place. I suggest that you call the input flow something like
Membership Application Details
Then you do a data dictionary definition
Membership Application Details = Application Form + Medical Information
+ Direct Debit Forms + Legal Documents.........
What are the output flows in response to this event? I envisage something
like
Accepted Membership
Refused Membership
Depending on whether the Membership Application Details conform with your
business rules for accepting a new member.
Hope this helps. Keep talking.
Regards
Suzanne Robertson
==============================================================
Suzanne Robertson
Principal of The Atlantic Systems Guild
suz...@systemsguild.net
www.systemsguild.com <
http://www.systemsguild.com>
www.volere.co.uk <
http://www.volere.co.uk>
Our new book "Adrenaline Junkies and Template Zombies - Understanding
Patterns of Project Behaviour" is the Jolt Award winner, Best General
Computing Book of 2008-2009.
http://www.dorsethouse.com/books/ajtz.html
==============================================================