Boiled water <czm***q.com> 11:07:15 In the
requirements specification, there is a data dictionary to write. For example, there is a dictionary item of the organization code
Bai Boishui <czm***q.com> 11:07:17 Bai Boishui 
<czm***q.com> 11:08:23
A function, such as ticket issuance , and ticket issuance Organization code of the person, the organization code of the
payee , I would like to ask: Do you want to include these two in the data dictionary?
Or just use one organization code for plain water <czm***q.com> 11:08:51 ?
Pan Jiayu (3504847) 11:11:51
(1) Parted . The input and output of the ticketing use case should be truthfully described, which has nothing to do with the internal design.
(2) In addition, do not need a data dictionary, but a list of fields for each use case. Different use cases have different input and output information. This use case requires seeing all the code, another use case may only need to see the last four digits of the code.
