Deploying IT resources MIS 533

1
Deploying IT resources(MIS 533)

• MBS in Management Information Systems and
  Managerial Accounting Systems
• (2006 / 2007)

Fergal Carton Business Information Systems
2
Last week

• Context level DFD
• DFD level 1 (7 processes) and level 2 (gt7
  processes)
• Distinction between ERD and data dictionary
• More system design examples
• Modelling
• Building a model RyanAir example
• DFDs naming conventions
• Planning approaches
• Build to Plan
• Build to Order
• Inventory consumption (Work Order, Process Order)
• Replenishment approach
• MRP
• Economic Order Quantity
• Depends on value / lead time of item
• Databases a trade-off between cost, accuracy
  and intrusiveness
• MusicMaestro narrative for assessment

3
This week

• Manufacturing data
• Data and normalisation
• Final system examples (Johanna, Kerrie, David,
  Michael)
• Associative entities (BOM, Sales orders, )
• Despatch link to SO and AR

4
More system examples

• Quality control for Guinness
• Test samples from franchised breweries
• Test data stored (ph, alcohol, colour, )
• Tolerance ranges
• Annual prize / discount for high achievers
• Interbank Accounts System for TSB
• Transactional screen, query screen
• Search limited to 3 chars (firstname, surname)
• SIFASoft for Electronic Point of Sale (EPOS)
• Response time on price for products with long
  history
• Sage Accounting package
• Entering transactions, coding of accounts
• Issue knowing which account to use

5
Data storage

• Series of ad-hoc systems manual and
  computer-based (spreadsheet, filed forms)
• Dedicated databases for manufacturing data (QC,
  shipping etc)
• Process Control Systems (technical parameters)
• Other specialised proprietary systems
  (integration may not be easy).
• ERP system with its own data structure or fed by
  existing systems

6
Using Manufacturing data

• Operational data
• volumes - schedule / re-schedule runs
• labour report - line up workers for next days
• quality of output
• Tactical data
• defect rates
• productivity
• Quality of RM
• Strategic data
• product mix information
• Market research
• turnover of staff

Some soft information is also required
7
Soft information

• Data collection -
• Grapevine
• factory tours (talking and observing)
• Data storage -
• managers minds
• special reports
• Data usage
• ad-hoc basis
• decision making

8
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

9
First Normal Form

• design record structure so that each record looks
  the same (same length, no repeating groups)
• repetition within a record means one relation was
  missed create new relation
• elements of repeating groups are stored as a
  separate entity, in a separate table
• normalised records have a fixed length and
  expanded primary key

10
Second Normal Form

• Record must be in first normal form first
• each item in the record must be fully dependent
  on the key for identification
• Functional dependency means a data items value
  is uniquely associated with anothers
• only on-to-one relationship between elements in
  the same file
• otherwise split into more tables

11
Third normal form

• to remove transitive dependencies
• when one item is dependent on an item which is
  dependent from the key in the file
• relationship is split to avoid data being lost
  inadvertently
• this will give greater flexibility for the design
  of the application eliminate deletion problems
• in practice, 3 NF not used all the time - speed
  of retrieval can be affected

12
Realistic constraints

• Users cannot cope with too many tables
• Too much development required in hiding complex
  data structure
• Too much administration
• Optimisation is impossible with too many tables
• Actually RDBs can be quite slow!

13
Oracle Demo Set - Sales Order Processing
CUSTOMER TABLE
SALES_ORDER TABLE
PRODUCT TABLE
ITEM TABLE
PRICE TABLE