Hi Francis,
Batch processes are difficult because they are typically non-OO. At an analysis level, to draw a sequence diagram for a batch process, I would do the following. >From reading your description below, it sounds like receiving the file is the first step in the process. I would show this interaction by having an actor for the system that produces the file, and a message like "send file x" going from the actor to the first object in the batch process. If different types of transactions are treated differently, then I would define the different types of transactions and their attributes elsewhere (could create a class for each, and possibly use inheritance) or define them in a document. Then, produce one sequence diagram for each type of transaction. The sequence diagrams should be different if the transactions are treated differently. You can link sequence diagrams by using notes. I hope I haven't totally missed your point. Thanks, Tara. > -----Original Message----- > From: Law, Francis [IBM GSA] [SMTP:[EMAIL PROTECTED]] > Sent: Friday, May 17, 2002 9:25 AM > To: [EMAIL PROTECTED] > Subject: (ROSE) Sequence Diagram > > > Dear all, > > I have problem in drawing sequence diagram for batch processes. I have > read > a number of reference and still couldn't get it. Therefore, I hope some > of > the kind people can give me some advise. > > Most of the time, example in reference use interactive process such as > order > entry process that involve dialogue between the process and human. > However, > in case of a batch process, i.e. individual transaction data is batched in > a > file. What the process received is a file instead of individual data. > How > could we present the scenarios of each type of transaction in the sequence > diagram? > > Thanks in advance for all advise! > > Regards, > Francis Law > > ************************************************************************ > * Rose Forum is a public venue for ideas and discussions. > * For technical support, visit http://www.rational.com/support > * > * Post or Reply to: [EMAIL PROTECTED] > * Subscription Requests: [EMAIL PROTECTED] > * Archive of messages: > * http://www.rational.com/support/usergroups/rose/rose_forum.jsp > * Other Requests: [EMAIL PROTECTED] > * > * To unsubscribe from the list, please send email > * To: [EMAIL PROTECTED] > * Subject: <BLANK> > * Body: unsubscribe rose_forum > ************************************************************************* JBWERE LIMITED DISCLAIMER JBWere Limited and its related entities distributing this document and each of their respective directors, officers and agents ("the Were Group") believe that the information contained in this document is correct and that any estimates, opinions, conclusions or recommendations contained in this document are reasonably held or made as at the time of compilation. However, no warranty is made as to the accuracy or reliability of any estimates, opinions, conclusions, recommendations which may change without notice) or other information contained in this document and, to the maximum extent permitted by law, the Were Group disclaims all liability and responsibility for any direct or indirect loss or damage which may be suffered by any recipient through relying on anything contained in or omitted from this document. ************************************************************************ * Rose Forum is a public venue for ideas and discussions. * For technical support, visit http://www.rational.com/support * * Post or Reply to: [EMAIL PROTECTED] * Subscription Requests: [EMAIL PROTECTED] * Archive of messages: * http://www.rational.com/support/usergroups/rose/rose_forum.jsp * Other Requests: [EMAIL PROTECTED] * * To unsubscribe from the list, please send email * To: [EMAIL PROTECTED] * Subject: <BLANK> * Body: unsubscribe rose_forum *************************************************************************
