Mail Order.

Slides:



Advertisements
Similar presentations
Databases Using Information. What is a Database? A database package allows the user to organise and store information. This information can be sorted,
Advertisements

09/04/2015Unit 2 (b) Back-Office processes Unit 2 Assessment Criteria (b) 10 marks.
Employee database: Conceptual Schema in ERD Chapter 3, page 62.
The Database Approach u Emphasizes the integration of data across the organization.
Database Introduction
- 1 - Tables Query (View) FormReport Database Application Basic Database Objects Relationships among Access Database Objects A saved SELECT query is officially.
Data Model Examples USER SPECIFICATIONS.
Data Access Patterns. Motivation Most software systems require persistent data (i.e. data that persists between program executions). In general, distributing.
CIS 270—App Dev II Big Java Chapter 22 Relational Databases.
NMS1.0(c) Copyright Final Year Project Demonstration Dublin City University 29 th May 2003 Team Members : David ReadeTimothy Kelly
C H A P T E R 4 Designing Database E-Commerce Hassanin M. Al-Barhamtoshy
MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management Dave Salisbury ( )
Your Name Here See Page Notes for Info about Hyperlinks.
MIS 301 Information Systems in Organizations Dave Salisbury ( )
MIS 301 Information Systems in Organizations Dave Salisbury ( )
IT354 Database Design Seminar 5: May 19, 2011 Physical Database Design Entity-Relationship Diagrams.
ORDER ENTRY ORDER ENTRY SYSTEM O/E DAILY PROCESSING MENU ORDER ENTRY.
IMS 4212: Introduction to Data Modeling 1 Dr. Lawrence West, Management Dept., University of Central Florida Introduction to Data Modeling—Topics.
Welcome! User Conference 2010 Presenter: Nick Cascone.
INFO1408 Database Design Concepts Week 15: Introduction to Database Management Systems.
1 ICOM 5016 – Introduction to Database System Project # 1 Dr. Manuel Rodriguez-Martinez Department of Electrical and Computer Engineering University of.
Mcommerce app Small and Medium Business. Home Screen Retrieve products from Database for Viewing product Users can view the Best Deal of the week/Current.
DESIGN PART 2: OBJECT-LEVEL SEQUENCE DIAGRAMS WITH AN EXAMPLE OF COMPOSITION BTS430 Systems Analysis and Design using UML.
Exam 1 Review. Bureau of Labor Statistics, U.S. Department of Labor, Occupational Outlook Handbook, Edition, Computer and Information Systems.
Introduction Database integral part of our day to day life Collection of related database Database Management System : software managing and controlling.
How I spend my money Software architecture course Mohan, Maxim.
How to Enter a Requisition for Goods and Services in Owl Link Updated March 15, 2013.
Group Booking : Reserve Multiple Rooms In Single entry Book Multiple Rooms in Single Entry.
CSE300 EAIusing EJB & XML CSE Enterprise Application Integration Using EJB and XML by Prithwis Sett Mumtaz Lohawala Nayana Paranjape.
The Business of IT ® Austin Code Camp ‘08 Prescriptive Data Access Development in.NET 3.5 Austin, TX May 17, 2008 Brian Orrell.
Chapter 4 © 2013 Pearson Education, Inc. Publishing as Prentice Hall Chapter 4: Logical Database Design and the Relational Model Modern Database Management.
Business Analyst Web App and ArcGIS Online Anna Hou Julia Holtzclaw.
DEVRY CIS 336 W EEK 7 G ROUP P ROJECT T ASK 5 Check this A+ tutorial guideline at
Databases and DBMSs Todd S. Bacastow January 2005.
CompSci 280 S Introduction to Software Development
Order Database – ER Diagram
Database Development Lifecycle
Chapter 1 Introduction.
Component and Deployment Diagrams
Order Database – ER Diagram
MIS2502: Data Analytics Relational Data Modeling
Database Requirements and Design
Chapter 12 Information Systems.
Information Systems Database Management
CMPE 280 Web UI Design and Development October 24 Class Meeting
Order Database – ER Diagram
Order Database – ER Diagram
Example Question–Is this relation Well Structured? Student
Relationships among Access Database Objects
How to Modify a Requisition Using Owl Link
Data Solutions- Karm Upadhyay Zoheb Khan Swati Shukla
SE-565 Software System Requirements IV. Use Cases
Use Case Modeling - techniques for detailing use cases
Data Solutions- Karm Upadhyay Zoheb Khan Swati Shukla
MIS2502: Data Analytics Converting ERDs to Schemas
POINT OF SALE.
Customer Order Entry Database Version: 1.1 by: R. Holowczak
Order Database – ER Diagram
Accessing Your MySQL Database from the Web with PHP (Ch 11)
CHAPTER 4: LOGICAL DATABASE DESIGN AND THE RELATIONAL MODEL
CHAPTER 1: THE DATABASE ENVIRONMENT AND DEVELOPMENT PROCESS
Order Database – ER Diagram
Database Management Systems
Topic 12 Lesson 1 – Data and databases
SALES RECEIPT Downloaded from
Grocery Store Outline csc242 – web programming.
Data Access Layer (Con’t) (Overview)
Information Systems in Organizations 2. 1
MIS2502: Data Analytics Relational Data Modeling 3
Order Processing.
Presentation transcript:

Mail Order

Requirements An employee takes orders from customers Each purchase may contain multiple products System maintains customer information System maintains product information

Use Cases Add/delete/update/view customers Add/delete/update/view products Take purchase orders View purchase orders Delete purchase orders Update purchase orders

The Database - ERD Name Address Name Description Id Id Product Customer M 1 Price contains Places Quantity N N Purchase Order Order_date PO Id

The Database - Schema customer customer_id name address purchase_order po_id Customer_id order_date order_item id po_id product_id quantity product product_id name description price

System Architecture Database Take purchase order Delete purchase order OrderManagement Take purchase order Delete purchase order Update purchase order View purchase order CustomerManagement ProductManagement Add customer Delete customer Update customer View customer Add product Delete product Update product View product Database

System Architecture Each package is responsible for CRUD on a set of tightly related business entities E.g., Customers, customer groups (VIP, etc), and customer credit card info as a package Use cases are allocated to packages and each package contains related use cases E.g., Add customer including his group and credit card info, update customer, delete customer, and query customer in CustomerManagemant Each package has a Manager which takes cares of the business logic of the use cases. E.g., OrderManager would check if an order contains more than the limit of the number of items or not. A Design Pattern called Service Layer may be used to package managers’ operations as one class – ServiceLayer MailOrder sample app employs this approach.

System Architecture Each use case is mapped to a Presenter which is responsible for the presentation logic of the use case. E.g., TakeOrderPresenter is responsible for creating a new purchase order and saving the order in the DB Each Presenter may employ multiple Views each of which is a UI. E.g., TakeOrderPresenter uses SelectCustomerView to select a customer for the order, SelectOrderItemsView to collect order items, finally ConfirmOrderView to display the order info to the user.

System Architecture Database entity OrderManagement Customer Product PuchaseOrder OrderItem ui SelectCustomerView SelectOrderItemsView ConfirmOrderView TakeOrderPresenter db CustomerDao ProductDao PuchaseOrderDao OrderItemDao MailOrderDatabase ViewOrderPresenter PurchaseOrderManager Depends on A B Database

Architecture – Service Layer OrderManagement CustomerManagement ui SelectCustomerView ConfirmOrderView ProductManagement TakeOrderPresenter ViewOrderPresenter server ServiceLayer (Façade) db CustomerDao PurchaseOrderDao OrderItemDao ProductDao MailOrderDatabase Database

Detailed Design: db & entity Customer Product Purchase Order Order Item Customer_id Name Address Product_id Name Description Price Po_id Customer_id Order_date Po_id Product_id Quantity CustomerDao ProductDao PurchaseOrderDao OrderItemDao Insert() Delete() Update() getCustomerById() getAllCustomers() Insert() Delete() Update() getProductById() getAllProducts() Insert() Delete() Update() getPOById() getAllPOs() Insert() Delete() Update() getItemByItemId() getItemsByOrderId() MailOrderDatabase getConnection() Close()

Detailed Design: OrderManagement ui 1. Customers = ServiceLayer#getAllCustomers(); 2. Display SelectCustomerView(customers) 3. products = ServiceLayer#getAllProducts() 4. Display SelectOrderItemsView(products) 5. Display ConfirmOrderView() SelectCustomerView SelectOrderItemsView ConfirmOrderView TakeOrderPresenter begin() ServiceLayer getAllCustomers() AllProducts() CustomerDao.getAllCustomers() ProductDao.getAllProducts() db CustomerDao ProductDao PuchaseOrderDao OrderItemDao MailOrderDatabase Code segment

Detailed Design: Startup AppController Main() HomeView.instance().display() OrderManagement HomeView Display() Start Take Order use case TakeOrderPresenter Start ViewOrder use case ViewOrderPresenter CustomerManagement AppContext Static getInstance() getDbConnection() ProductManagement