mosser
commented
1 year ago - I cannot find things related to reporting in Appendix A (relation with client). It was part of the initial discussion, but after the ideation workshop, it looks like they have re-centred their expectations.
- I'm wondering about the scope of the system concerning some use cases.
- Is it part of ATCO to support food processing (e.g., line cook use cases)?
- Should Mosaic/Payment Gateway be considered as system actors?
- Citizen + community members could be abstracted as patrons to factorize the first relations
- I cannot find a relation to "order food" for the citizen persona description. Is it part of scope to order food for this actor? Same for payment (except to get some free food with points)
- (We really need to clarify with TheFirebird what are the perks associated to Loyalty points.)
- Is the process payment use case related to Manager rather than admin assistant? I'd guess the manager will send the invoice to Mac through ATCO, but based on the assistant description it should be transparent on their side.
t-chiang
Fundamental usage paths through the system. It presents the main scenarios (use cases) that the system should cover. The scenarios chosen for appearing here, in the Goals book, should only be the main usage patterns, without details such as special and erroneous cases; they should be stated in user terms only, independently of the system's structure. Detailed usage scenarios, taking into account system details and special cases, will appear in the System book (<>).