Michael, We should be asking the **real** users how they want to conduct business (= requirements!!!) Then the software developers should provide solutions to enable the business requirements. Software developers should not/are not capable of determining the business requirements and the business process requirements. They only provide solutions that enable the process to execute to the determined/expected outcome or deal appropriately with exceptions.
Rachel -----Original Message----- From: Michael Mattias/Tal Systems [mailto:[EMAIL PROTECTED]] Sent: Monday, May 06, 2002 6:18 PM To: WEDI/SNIP Listserve Subject: Re: CPP Data elements draft for comment ----- Original Message ----- From: Rachel Foerster <[EMAIL PROTECTED]> > Developing a requirements document....how novel! What is really novel here is asking USERS (in this case, user=software developer) what they need. And since it's my turn to be the user, I am going to enjoy every last minute of it! MCM (No more of those "control total *precedes* item detail" implementations the ivory-tower academic snobs...er, make that, "our distinguished educational-institution-based colleagues"... seem to invent from time to time.) > -----Original Message----- > From: Ajay K sanghi [mailto:[EMAIL PROTECTED]] > Subject: RE: CPP Data elements draft for comment > > Michael Mattias wrote: > <snip> > >(A DOCUMENT section in addition to CONNECTION would be just fine). > <snip> > > > It's absolutely necessary and many fields (18-27) in RECEIVER section needs > to be "generic" and moved to DOCUMENT section (line items type). > Michael Mattias Tal Systems, Inc. Racine WI [EMAIL PROTECTED]
