Deploying IT resources (MIS 533) MBS in Management Information Systems and Managerial Accounting Systems (2006 / 2007) Fergal Carton Business Information Systems

MBS (MIMAS) / MIS533 / Deploying IT Resources Last week Practicals: confirm groups and times –Tues Group B Visio and Access Run & Aoife –Tues – Group A Oracle and SQL Brian & Una –Wed Group A Visio and Access Run & Aoife –Tues – Group B Oracle and SQL Brian & Una More database examples Analysis & design = listening Narrative analysis rules Data tables (columns and rows) Relational model of linked tables (improve performance) Use data to test your design Applications: trade off design vs. resources Modelling (eg. architects models of buildings) communicates design

MBS (MIMAS) / MIS533 / Deploying IT Resources This week More system design examples Building models Abstract thinking User interface design rules Tutors Visio narratives RyanAir example

MBS (MIMAS) / MIS533 / Deploying IT Resources More systems design examples Quality Assurance database for cheese samples (volume) Gathering customer order details into one system: late changes! Survey questionnaire processing application: correlations Payroll application, dealing with events (emergency tax, P30, …) Supermarket point of sale system, activating new products (special offers)

MBS (MIMAS) / MIS533 / Deploying IT Resources Bad systems design SNCF : ticketing system Bank of Ireland on-line (what direct debits are on my account?) ERP systems: getting reports out Your own examples?

MBS (MIMAS) / MIS533 / Deploying IT Resources... The design of your software's interface, more than anything else, affects how a user interacts and therefore experiences your application. Tandy Trower, 1994

MBS (MIMAS) / MIS533 / Deploying IT Resources User Interface Design Rules Rule 1 –Making the Interface Simple Rule 2 –Allowing Users to Be in Control of the Software

MBS (MIMAS) / MIS533 / Deploying IT Resources Rule 1 : Making it simple Making the Interface Simple –KISS, Keep It Simple and Straightforward Are all fields or choices in your application necessary? –Making the Interface Transparent and Natural Don’t clutter the interface –Labels, static text, check boxes, and option buttons Can user look at screen and figure out what to do?

MBS (MIMAS) / MIS533 / Deploying IT Resources Rule 1 : Making it simple

MBS (MIMAS) / MIS533 / Deploying IT Resources Rule 2 : Users in control Some of the ways to put users in control are: Making the interface forgiving Making the interface visual Providing immediate feedback Avoiding “Modes” –A mode is something you must cancel before doing something else Making the interface consistent

MBS (MIMAS) / MIS533 / Deploying IT Resources Rule 2 : Users in control

MBS (MIMAS) / MIS533 / Deploying IT Resources Your tutors Visio – Access Run Zhang Aoife Mac Sharry SQL - Oracle Una Dunne Brian Cummins

MBS (MIMAS) / MIS533 / Deploying IT Resources Visio narratives Grocery Store ATM Budget monitoring RyanAir ticket purchase Purchase request and payment UCC travel requisition Film festival

MBS (MIMAS) / MIS533 / Deploying IT Resources Visio & database manuals Katie Dineen –Room 3818 ORB –By end of week

MBS (MIMAS) / MIS533 / Deploying IT Resources Building a model Process Flow Data Flow Diagram –Context diagram –Processes –Data Flow –Data store –External entities

MBS (MIMAS) / MIS533 / Deploying IT Resources Example :

MBS (MIMAS) / MIS533 / Deploying IT Resources Example : Input : –Flight details (eg. SNN-BVA, 8 Oct, 10.35) –Credit card details (eg. VISA no, Expiry date) Process : –Confirms price (eg. EUR 79) –Makes reservation & processes payment Output : –Reservation reference (eg.CGHKCA)

MBS (MIMAS) / MIS533 / Deploying IT Resources Process flow

MBS (MIMAS) / MIS533 / Deploying IT Resources Context diagram On-line reservation system Passengers Flight Operations Flight Schedule Flight reservation Reservation # Accounts Payment € Timetable Seat availability Reservations Seat prices

MBS (MIMAS) / MIS533 / Deploying IT Resources 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