database development ( mis 533 )

Database development(MIS 533)

MBS in Management Information Systems and Managerial Accounting Systems

(2007 / 2008)Fergal Carton

Business Information Systems

MBS (MIMAS) / MIS533 / Database development

Last week

• Cuisine de France– Table structure for bread products– Normalise by taking out type to another table– Database should be independent of application– Primary key = foreign key in related tables

• Normalisation: 1NF– One single data item at intersection of row and column– Use sample data to fill out tables to understand structure

• Requirements analysis: modelling– Goal is to uncover information flows, start at process level

• Modelling exercise – context level diagram for Cucina della Italia


This week

• Data flow diagrams– Cucina della Italia– Northwind?

• Normalisation• Process modelling

– Sales order process– Purchase order process

• Normalisation 2NF


Cucina della Italia

• Selling fresh bread to service stations

• Describe customer requirements

• How these requirements can be met?

• What processes will the business need?

• What information flows are required?


Your own examples

Student name System experience

1. Horgan, Shane Christopher Telesales system for Cuisine de France

2. Dillon, Damien

3. Creighton, Glenn Stock ordering for Chemist

4. Kenny, Clive EPOS and suppliers for StatOil

5. Crowley, Micheal

6. Hourigan, Brenda Quality control, Newmarket

7. Kavanagh, Fiona Marie Claire

8. Kearney, Tara Stationery ordering for Eason’s

9. Holland, Tadhg

10. REYHANI, PEYMAN Call center system for customers at RCI

11 FONZI, Kenneth Christopher Pledge customers for park

12 LI, Yan Purchasing for retail business


Call center customers

• Customer rings call center (timeshare sales)

• System recognises number, displays record

• Is there a database at work?


Normalisation• Process of simplifying the relationships amongst data

items as much as possible (see example provided - handout)

• Through an iterative process, structure of data is refined to 1NF, 2NF, 3NF etc.

• Reasons for normalisation:– to simplify retrieval (speed of response)– to simplify maintenance (updates, deletion, insertions)– to reduce the need to restructure the data for each new

application


Normalisation: 2NF

• A table already in 1NF

• A table with composite primary keys– A table with a single column primary key is

already in 2NF

• Values in each column can only be worked out from the values in all the columns that make up the primary key


Normalisation

ID Item1 Package2 Box3 Piece4 Pies5 Box of 2 pies6 Rounds7 Bottles8 J ar

Pro

duct

ID ProductNameSupplie

rID

Cat

egory

ID

Item Item

mea

sure

Item

siz

e

Qty

item

s / u

nit

51 Manjimup Dried Apples 24 7 Package g 300 5052 Filo Mix 24 5 Box g 2000 1653 Perth Pasties 24 6 Piece 4854 Tourtière 25 6 Pies 1655 Pâté chinois 25 6 Box of 2 pies 2456 Gnocchi di nonna Alice 26 5 Package g 250 2457 Ravioli Angelo 26 5 Package g 250 2458 Escargots de Bourgogne 27 8 Piece 2459 Raclette Courdavault 28 4 Package g 5000 160 Camembert Pierrot 28 4 Rounds g 300 1561 Sirop d'érable 29 2 Bottles ml 500 2462 Tarte au sucre 29 3 Pies 4863 Vegie-spread 7 2 J ar g 625 1564 Wimmers gute Semmelknödel12 5 Bag of 4 pieces 2065 Louisiana Fiery Hot Pepper Sauce2 2 Bottle oz 8 3266 Louisiana Hot Spiced Okra 2 2 J ar oz 8 32

ID Item measure1 Grammes g2 Millilitres ml3 Ounces Oz

Suppliers

Categories


Sales order process

• Provide price / quotation

• Give commit date for delivery

• Take order

• Dispatch goods and invoice

• Receive payment from customer


Sales order process

• PCB case study– Draw a process map of the sales order process– Show the information flows between stages in

the process


Purchase order process

• Obtain price / quotation

• Create purchase order

• Get approval for expenditure

• Receive goods and delivery note

• Receive invoice

• Make payment to supplier


Purchase request and payment• Departments make spending requests• Budget is checked in the allocated budget file• If budget exceeded, request is rejected• Approved requests are stored and used to create

Purhcase orders (PO’s) for suppliers• Goods received notes (GRN) are matched with

PO’s to identify any discrepancies• When supplier invoice is received, 3 way match is

made between PO, GRN and invoice prior to payment


Purchase request and payment• Draw a context level diagram for the

process

• Draw a Level 1 Data Flow Diagram

• What sort of analysis method would you use?

• What sort of output would you provide?

• Structure of User Requirements Report?


Example : Budget monitoring case• What analysis method would you use and why?

– Interviews• Management / Department interviews

– Describe the special approval process– What are the “tolerance levels” for overspending of budget– How many requests, how long to approve, backlog issues

– Documentation• Copies of current spending requests• List of departments and corresponding budgets• Print-out from allocated budget file• Copy of spending summary report• Process for order supply of parts (PO’s?)• Copy of delivery advice details

– Requirements report


Example : Budget monitoring case• What sort of output would you provide?

– Requirements report– Questionannaires– Functional Decomposition– Data Flow Diagrams– ERD– Etc.

• How would you validate requirements?– JRP– Prototype– Approving Requirements report– …


Make spending request

Budget is checked

[Request > Budget]Request rejected

Create Purchase Order

[Request < Budget]

GRN matched with PO

3 way match GRN / PO / Invoice

Invoice payment

Invoice received

[No discrepancy]

[Invoice on hold]


Budget monitoring case

Budget Monitoring

System

Department Management

Suppliers

Make Spending Request Check Budget

Respond To Special RequestSend Managements Response

Special Request Made

Provide Spending Summaries

SupplyDeliveryAdvice

Send Delivery Advice


CUSTOMER TABLE

PRODUCT TABLE

ITEM TABLE

SALES_ORDER TABLE

PRICE TABLE

Oracle Demo Set -Sales Order Processing


Production planning• Planning approaches (build to plan)

– Top down quarterly plan drives both Production (units) and Sales (€) targets

– Takes into account sales forecast, historical performance and market expectations

– Production plan must then be broken down into units, configurations, geograpahies

– Local production planners then turn this into:• an MRP plan to drive purchasing

• and a Master production schedule to drive manufacturing


Keeping tabs on Work-in-Progress (WIP)

• Inventory consumption

– Something must trigger inventory consumption as production proceeds (BO, WO, PO, SO, …)

– Visibility of inventory in Work-in-Progress (WIP) is low

– You can measure output / consumption at intermediate points but beware of disrupting process


Manufacturing modes and lead times

• Difference between process and discrete manufacturing

– Process manufacturing consumes inventory at a steady rate, but yield of finished goods may vary

– Discrete manufacturing consumes a predefined amount of inventory per article of finished goods

• Lead times:

– key to replenishment policy: what’s my buffer stock?

– Fiat Idea : re-uses previous model components to reduce cost & lead time

database development ( mis 533 )

Documents