FIND A SOLUTIONAT All A+ Essays

1CSE2DES/CSE5DES – Assignment (Part 1)Due Date: 10 am Monday 17th September 2018Assessment: This part is worth 15% of the final marks for CSE2DES/CSE5DES.This is an individual assignment. You are not permitted to work as a group.Assignment Submission: An electronic copy in PDF format, containing answers to bothTask 1 and Task 2, is to be submitted electronically via latcs8 using the submit command:submit DES <file name>For Students at Dandenong Campus: Please follow the instructions of your lecturerregarding assignment submission.Copying, Plagiarism: Plagiarism is the submission of somebody else’s work in a manner thatgives the impression that the work is your own. The Department of Computer Science andComputer Engineering treats plagiarism very seriously. When it is detected, penalties arestrictly imposed. Students are referred to the Department of Computer Science and ComputerEngineering’s Handbook and policy documents with regard to plagiarism.No extensions will be given: If there are circumstances that prevent the assignment beingsubmitted on time, an application for special consideration may be made. See thedepartmental Student Handbook for details. Note that delays caused by computer downtimecannot be accepted as a valid reason for a late submission without penalty. Students mustplan their work to allow for both scheduled and unscheduled downtime.Late Submission: Penalties will be applied to late assignments (5% of the total assignmentmark will be deducted per day and late submissions will be accepted only up to 5 days afterthe due date). Submissions more than 5 days late (i.e. after 10 am on Monday 24 September2018) will receive 0 mark.Return of Assignments: Assignments will be returned within three weeks from the last dayon which the assignment can be submitted.Objectives: To learn to identify the relevant use cases for a given application, describe theuse cases and develop an object-oriented domain model.2Problem Statement – Standing Orders Management SystemA distribution company supplies various kinds of products to customers on a daily basisaccording to the standing orders placed by the customers.The company wants to set up a system to maintain information about the products that thecompany can supply, its customers, the standing orders, together with information aboutdeliveries, invoices, and payments.ProductsProducts are identified by product ID. Each product has a short description which is to berecorded.CustomersCustomers are identified by customer ID. Each customer has a name and one or more deliveryaddresses. Each delivery address has a contact person, whose name and phone number arerecorded. Note that the names of the contact persons may not be unique. In addition, eachdelivery address is given a system-wide unique ID.Standing OrdersStanding orders are identified by standing order ID. Each standing order is for one product tobe supplied to one customer on an agreed price for the standing order. The standing orderstates the quantity required for each day of the week. Each standing order has a date initiatedand termination date. When a standing order is first created, it has the status of being “active”.The status is changed to “closed” when the termination date is past or when the customercancels the order.DeliveriesDeliveries are made on each day to satisfy orders for that day. Each delivery is identified by adelivery number, made to one particular delivery address of a customer, and can includeproducts from more than one standing order for the customer.A delivery docket (identified by the delivery number) is made out at each delivery. It containsdelivery date, the day of the week, the quantity delivered for each product, together with thestanding order number for that product. The quantity delivered for a standing order on aparticular day is usually equal to the quantity specified in the standing order, but occasionallyit may be different. In later case, a star (*) is marked against it.InvoicesEvery week an invoice is prepared and sent to the customers. The invoice consists of all thedeliveries made up to the Friday of the previous week to one customer. A sketch of theinvoice is given below.3Invoice Number: ____________Customer ID: _______________Week Ending: ______________Delivery St. Order Product. Qty Price CostNr. Nr. ID
_______________
_______________
_______________
Amount due: __________PaymentsCustomers pay by direct debit. Once the payment is made and confirmed, the date on whichthe direct debit is made is recorded against the invoice as payment date. A debit account hasan account number, the business name and the name of the authorization person.Results of an analysis of the required behaviour of the systemAn analysis of the behaviour of the system has been carried out. As a result, a number of usecases have been identified. More specifically, the following use cases, that need to besupported by the system.1. Add a new product.2. Remove a product – provided there are no standing orders for this product.3. Add a new customer. At least one delivery address and one standing order need to beadded for the new customer.4. Add a delivery address to an existing customer.5. Remove a delivery address, provided no deliveries have been made to this address.6. Add a standing order to an existing customer.7. Close a standing order – when the end-date is reached or when the customer cancelsthe order.8. List standing orders that need to be filled for a particular date, sorted by customername and, within a name, by id.9. Add a delivery.10. Generate a delivery docket.4Your Tasks (total 100 marks for Part 1 of the Assignment)For Part 1 of the assignment, you are required to do the tasks described below. Clearlystate any assumption you make. Your assumptions must not be inconsistent with what aregiven the description above.Task 1 (60 marks) – Use Case Modeling Describe each of the use cases in the list, using the Main Flow/Extensions format.Make sure you clearly number the use cases.Notes: You are not required to draw use case diagrams. You are required to describe all use cases given in the list above. As formarking, about 5 of those use cases will be marked. Your use case descriptions should capture the functional requirementsprecisely and concisely. Use case descriptions with superfluous details mayresult in marks being deducted.Task 2 (40 marks) – Domain Modeling Construct a domain class model, which may consist of one or more class diagrams. You should use enumerated types whenever appropriate (rather just using charactersor strings). You are required to use Enterprise Architect to draw the class diagrams. Diagrams thatare drawn by hand or with other software will have up to 50% of its marks deducted. You should include your class diagrams in your pdf document, not in separate files.What to submitAn electronic copy in PDF format, containing answers to both Task 1 and Task 2, is to besubmitted electronically via latcs8 using the submit command: submit DES <file name>Submission without any of surname, given name, student ID, subject code will have 5% ofthe mark deducted.Notes: You may need to know how to use WinSCP, for example, to transfer your file fromWindows to UNIX (so that you can submit your PDF file on latcs8). See a relevantdocument on LMS.

• Assignment status:Already Solved By Our Experts
• (USA, AUS, UK & CA PhD. Writers)

QUALITY: 100% ORIGINAL PAPER– NO PLAGIARISM– CUSTOM PAPER