Project Semester 1 Group 3 Robert, Pavel, Ulfar, Svetomir Vestbjerg byggecenter DM69 - Group 3 (Robert, Pavel, Ulfar, Svetomir)

Group 3 presentation Project goals Brief description of the system and its functionalities Classes and use cases Diagrams Demonstration of the system

Goals Meet the software needs of the company Include new features and extensions Define work rules and split the workload in order to achieve efficiency To learn and understand how to design and implement a well working software system Successfully congregate and associate our strengths and weaknesses Design a fully integrated system capable of managing products, loans, sales and people (customers, contractors and employees) Apply a tool that is easy to work with and coherent with the needs of the company Last but not least to leave a good impression of our work as a group and pass the examination

Brief description of the system System requirements Store information about customers, products , contractors and employees Registering, making and confirming orders Adding a dispatch note, a delivery note and an invoce Using barcodes Managing the stock

System functionality Register function Remove function View function Register people , products and deals Remove function Remove people or products from the database View function View sales or lease deals stored in the database Purchase / lease list function List of items in the transaction

System functionality Search function Edit function Field validation Search for people , products or deals Edit function Edit information about people, products or deals Field validation Requires important fields to be filled in correctly, such as numbers only or email

The main classes in the domain model Person: The person class is a super class over 3 subclasses ( Employee, Customer and Contractor ). It contains the common information for persons who are connected to the company. The three subclasses hold information that make the difference between an employee , customer and a contractor. Deal: The deal class is a super class over four subclasses ( Sales, Loans, Offers and Orders ). It contains the common information for all types of deals. The four subclasses have their own attributes. Documentation: The documentation class is a super class over two subclasses ( DeliveryNote and Invoice ). They record information about delivery and Invoices. Product: The Product class holds all common information about all products available in the company. It is a super class over two subclasses ( SaleItem and LeaseItem ).

Use-case: Purchase Item Precondition: Customer has an account in the system Post condition: Purchase is successfully registered and a receipt, along with dispatch note is printed out. The customer arrives at a checkout with items to purchase. The cashier use the barcode scanner to record each purchased item and enters the number of item to be dispatched. The system presents a running total and line-item details. Cashier swipes customers account card. System returns updated total including discount. The customer asks for payment to be added to his account. A purchase is being registered in the system and an invoice is being printed and added to other invoices customer has on his account (if any). The system updates inventory. The customer receives a dispatch note and then leaves with it and items.

Use-case: Purchase Item (alternative scenario) Alternative situation: Account credit is maxed * From step six 7. System refuses to add the total amount to the account and for a cash payment. 8. Customer pays. * Go to step seven.

Use-case: Purchase Item (alternative scenario) Alternative situation: Customer forgot his account card * From step three 4. Customer provides a valid ID. 5. System searches for customer's account. * Go to step five.

Domain model

Design class diagram

Vestbjerg byggecenter system Demonstration