1. a. Similarities between 'Context diagram' and 'Use case diagram': a. Both of these two diagrams identify participants who interact with a system. Context diagram demonstrate the constitutive relations between participants and the system. Use case diagram state who use the system and the functions of the system. b. They are described from users' perspective. c. They both indicate the boundary of the system, declare actor and internal system. Differences between 'Context diagram' and 'Use case diagram': a. Use case diagram illustrates logical relationships and dependencies between use cases in detail. b. Use case diagram provides a visibility into the system. Context diagram is a single process for summarizing the whole system. Use case diagram is a summary diagram as well. However, it contains details in actors and interactions. b. Similarities between 'Use case descriptions' and 'System narratives': a. They both demonstrate entities and how users interact with the system. b. Both of them are design from the users' perspective. Difference between 'Use case descriptions' and 'System narratives': a. They are difference on analyzing users' requirement. Use case description is comprehensive and step by step. 2. a.
<< extend>> Optimise itinerary Daily reconciliation Mary Deliver canister << include>> 0 Invoice canister << extend>> Client Monthly statement + Use case name: Monthly Statement Actor(s): Mary; Client Description: Generates a monthly statement to the clients who paid wrong Trigger event: < not needed for course> Trigger type: External Temporal <not needed for course> Steps: Collect data from invoice details Client name, receivables of each invoice Calculate batch receivable totals Batch receivables Collect invoice totals from Mary Batch real receipts Check if there is difference between batch receivables and batch real receipts If no difference, then quit Check if there is difference between receivable and real receipts on an invoice If no difference, then check next invoice If they are not matched, then generate a statement for the client on that invoice Send the statement to clients Pre-conditions: < not needed for course> Post-conditions: < not needed for course> Assumptions: < not needed for course> Information required [produced]: Receivable, real receipt, price difference, due date (for refilling the bill) Requirements met: < not needed for course> Outstanding issues: < not needed for course> Priority: < not needed for course> Risk: < not needed for course> b.
Itinerary Address: string Distance: string serial_num: int CustomerList Optimize() Delivery Slip Name: string Address: string Phone_number: string Canister_required: int Canister_empty: int Canister_retum: int Canister_damaged: int Invoice_id: int 1 ..* Mary Canister_onTruck: int CustomerList() DailyReconciliation() CalReceivable Canister_required: int Canister_empty: int Canister_return: int Canister_damaged: int Invoice_id: int Recivable: int Calculate() Daily Reconciliation Receivable: int real_receipt: int Invoice_id: int Check Balanced( 1 Invoice MonthlyReconciliation Receivable: int real_receipt: int Invoice_id: int Batch Receivable: int Batch_real_receipt: int Receivable: int real_receipt: int Invoice_id: int 1 Check Balanced( 1 1 .* Statement Price_difference: int DueDate: date Address: string Name: string Phone_number: string 1 Client Name: string Address: string Phone_number: string Send(Address, Name, Phone_number, Price_difference, DueDate) C. The differences between use case diagram and class