Beruflich Dokumente
Kultur Dokumente
MANAGINGTHEDIGITALFIRM,12TH EDITION
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
LearningObjectives
Chapter13
BUILDINGINFORMATIONSYSTEMS
VIDEOCASES
Case1:IBM:BusinessProcessManagementinaServiceOrientedArchitecture andManagingProjects Case2:RapidApplicationDevelopmentWithAppcelerator InstructionalVideo1:SalesforceandGoogle:DevelopingSalesSupportSystemswith OnlineApps
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
CIMBGroupRedesignsItsAccountOpeningProcess
SystemsasPlannedOrganizationalChange
Problem: FinancialservicesproviderCIMBgroup wantedtoimproveefficiencyinbusinessprocesses, specificallyprocessofopeningaccountsatbranch Solutions:ARISBPMtoolused toidentify25areas p gefficiency. y UtilizedMalaysias y forimproving governmentIDsmartcardtoautomateinputting customerdata,reducingtimespentby50% Demonstratestheuseofinformationsystemsto streamlineandredesignbusinessprocesses Illustratesfirstkeystepinbuildingnewsystem analysis l i
3 Prentice Hall 2011
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
SystemsasPlannedOrganizationalChange
SystemsasPlannedOrganizationalChange
ORGANIZATIONAL CHANGECARRIES RISKSAND REWARDS
Themostcommonformsof organizationalchangeare automationandrationalization. Theserelativelyslowmoving and dslow l changing h i strategies t t i presentmodestreturnsbut littlerisk.Fasterandmore comprehensivechangesuch asredesignandparadigm shiftscarrieshighrewards butofferssubstantialchances offailure. FIGURE131
StructuralorganizationalchangesenabledbyIT 3. Businessprocessredesign Analyze, Analyze simplify simplify,andredesignbusiness processes Reorganize R i workflow, kfl combine bi steps,eliminate li i repetition 4. Paradigmshifts Rethinknatureofbusiness Definenewbusinessmodel Change Ch natureof forganization i i
5 Prentice Hall 2011
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
SystemsasPlannedOrganizationalChange
SystemsasPlannedOrganizationalChange
ASISBUSINESSPROCESSFORPURCHASINGABOOKFROMAPHYSICALBOOKSTORE
Businessprocessmanagement(BPM)
Varietyoftools,methodologiestoanalyze,design, optimizeprocesses Usedbyfirmstomanagebusinessprocessredesign
StepsinBPM
1.Identifyprocessesforchange 2.Analyzeexistingprocesses 3 Designthenewprocess 3.Design 4.Implementthenewprocess 5.Continuousmeasurement
7 Prentice Hall 2011
FIGURE132
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
SystemsasPlannedOrganizationalChange
REDESIGNEDPROCESSFORPURCHASINGABOOKONLINE
SystemsasPlannedOrganizationalChange
VarietyoftoolsforBPM,to
Identifyanddocumentexistingprocesses
Identifyinefficiencies
FIGURE133
Createmodelsofimprovedprocesses Captureandenforcebusinessrulesforperforming processes Integrateexistingsystemstosupportprocess improvements Verify V if that th tnewprocessesh haveimproved i d Measureimpactofprocesschangesonkeybusiness performance f i indicators di
10 Prentice Hall 2011
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
SystemsasPlannedOrganizationalChange
OverviewofSystemsDevelopment
CANBUSINESSPROCESSMANAGEMENTMAKEADIFFERENCE?
ReadtheInteractiveSessionanddiscussthefollowingquestions
Systemsdevelopment:
Activitiesthatgointoproducinganinformation y solutiontoanorganizational g problem p or system opportunity 1 Systemsanalysis 1.Systems 2.Systemsdesign 3.Programming 4.Testing . est g 5.Conversion 6 P d i and 6.Production dmaintenance i
12 Prentice Hall 2011
WhyarelargecompaniessuchasAmerisourceBergenand Di b ldgood Diebold dcandidates did t for f b business i processmanagement? t? Whatwerethebusinessbenefitsforeachcompanyfrom redesigningandmanagingtheirbusinessprocesses? HowdidBPMchangethewaythesecompaniesrantheir businesses? WhatmightbesomeoftheproblemswithextendingBPM softwareacrossalargenumberofbusinessprocesses? p standtog gainthemostby yimplementing p g Whatcompanies BPM?
11 Prentice Hall 2011
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
OverviewofSystemsDevelopment
THESYSTEMS DEVELOPMENT PROCESS
Buildingasystemcanbe brokendownintosixcore activities. FIGURE134
OverviewofSystemsDevelopment
Systemsanalysis
Analysisofproblemtobesolvedbynewsystem
Definingtheproblemandidentifyingcauses Specifyingsolutions
Systemsproposalreportidentifiesandexaminesalternative solutions
Identifyinginformationrequirements
Includesfeasibilitystudy
I Issolution l ti f feasible ibl and dgood di investment? t t? Isrequiredtechnology,skillavailable?
13 Prentice Hall 2011 14 Prentice Hall 2011
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
OverviewofSystemsDevelopment
OverviewofSystemsDevelopment
Systemanalysis(cont.)
Establishinginformationrequirements Who Wh needs d what h ti information, f ti where, h when, h andhow Defineobjectivesofnew/modifiedsystem Detailthefunctionsnewsystem y mustperform p Faultyrequirementsanalysisisleadingcauseof systemsfailureandhighsystemsdevelopment cost
15 Prentice Hall 2011
Systemsdesign
Describessystemspecificationsthatwilldeliver functionsidentifiedduringsystemsanalysis Shouldaddressallmanagerial,organizational,and g components p ofsystem y solution technological Roleofendusers
Userinformationreq requirements irementsdri drive es system stemb building ildin Usersmusthavesufficientcontroloverdesignprocessto ensuresystemreflectstheirbusinessprioritiesand informationneeds g effortismajor j cause Insufficientuserinvolvementindesign ofsystemfailure
16 Prentice Hall 2011
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
OverviewofSystemsDevelopment
OverviewofSystemsDevelopment
OUTPUT Medium Content Timing INPUT Origins Flow Data entry USER INTERFACE Simplicity Efficiency Logic Feedback Errors DATABASE DESIGN Logical data model Volume and speed requirements File organization and design Record specifications
PROCESSING Computations Program modules Required reports Timing of outputs MANUAL PROCEDURES What activities Who performs them When H How Where CONTROLS Input p controls ( (characters, , limit, , reasonableness) ) Processing controls (consistency, record counts) Output controls (totals, samples of output) Procedural controls (passwords, special forms) SECURITY Access controls Catastrophe plans Audit trails
DOCUMENTATION Operations documentation Systems documents User documentation CONVERSION Transfer files Initiate new procedures Select testing method Cut over to new system TRAINING Select training techniques Develop training modules Identify y training g facilities ORGANIZATIONAL CHANGES Task redesign Job redesign Process design Organization structure design Reporting relationships
Programming:
Systemspecificationsfromdesignstageare translatedintosoftwareprogramcode
Testing
Ensuressystemproducesrightresults Unittesting:Testseachprograminsystemseparately Systemtesting:Testfunctioningofsystemasawhole Acceptancetesting:Makessuresystemisreadytobe usedinproductionsetting Testplan:Allpreparationsforseriesoftests
18 Prentice Hall 2011
17
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
OverviewofSystemsDevelopment
ASAMPLETESTPLANTOTESTARECORDCHANGE
OverviewofSystemsDevelopment
Conversion
Processofchangingfromoldsystemtonewsystem Fourmainstrategies
1. 2. 3. 4. Parallelstrategy Directcutover Pilotstudy Phasedapproach
FIGURE135
19
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
OverviewofSystemsDevelopment
OverviewofSystemsDevelopment
SUMMARY OF SYSTEMS DEVELOPMENT ACTIVITIES CORE ACTIVITY
Systems analysis
Productionandmaintenance
Systemreviewedtodetermineifrevisionsneeded Mayincludepostimplementationauditdocument Maintenance
Changes h inh hardware, d software, f d documentation,or procedurestoaproductionsystemtocorrecterrors, meetnewrequirements requirements,orimproveprocessing efficiency
20%debugging,emergencywork 20%changestohardware,software,data,reporting 60%ofwork:Userenhancements,improvingdocumentation, recodingforgreaterprocessingefficiency
21 Prentice Hall 2011 22
DESCRIPTION
Identify problem(s) Specify solutions Establish information requirements Create design specifications
Systems design
Programming
Translate design specifications into code d Unit test Systems test Acceptance test Plan conversion Prepare documentation Train users and technical staff Operate the system Evaluate the system Modify the system
Testing
Conversion
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
OverviewofSystemsDevelopment
OverviewofSystemsDevelopment
Mostprominentmethodologiesformodelingand designingsystems:
1. Structuredmethodologies 2. Objectorienteddevelopment
Dataflowdiagram:
Primarytoolforrepresentingsystemscomponent processesandflowofdatabetweenthem Offerslogicalgraphicmodelofinformationflow High g levelandlowerleveldiagrams g canbeusedtobreak processesdownintosuccessivelayersofdetail Datadictionary:Definescontentsofdataflowsanddatastores Processspecifications:Describetransformationoccurring withinlowestlevelofdataflowdiagrams Structurechart:Topdownchart,showingeachlevelofdesign, relationshiptootherlevels levels,andplaceinoveralldesignstructure
24 Prentice Hall 2011
Structuredmethodologies
23
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
OverviewofSystemsDevelopment
DATAFLOWDIAGRAMFORMAILINUNIVERSITYREGISTRATIONSYSTEM
OverviewofSystemsDevelopment
HIGHLEVELSTRUCTURECHARTFORAPAYROLLSYSTEM
FIGURE136
FIGURE137
25
26
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
OverviewofSystemsDevelopment
OverviewofSystemsDevelopment
CLASSAND INHERITANCE
Thisfigureillustrateshow classesinheritthecommon featuresoftheirsuperclass. superclass FIGURE138
Objectorienteddevelopment
Objectisbasicunitofsystemsanalysisanddesign
Object:
Combinesdataandtheprocessesthatoperateonthosedata Dataencapsulatedinobjectcanbeaccessedandmodified onlybyoperations,ormethods,associatedwiththatobject
Objectorientedmodelingbasedonconceptsofclass andinheritance
Objectsbelongtoacertainclassandhavefeaturesofthat class ayinherit e tstructures st uctu esand a dbehaviors be a o sof o amore o egeneral, ge e a , May ancestorclass
27 Prentice Hall 2011 28 Prentice Hall 2011
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
OverviewofSystemsDevelopment
OverviewofSystemsDevelopment
Objectorienteddevelopment
Moreiterativeandincrementalthantraditional p structureddevelopment
Systemsanalysis:Interactionsbetweensystemandusers analyzedtoidentifyobjects Designphase:Describeshowobjectswillbehaveand interact;groupedintoclasses,subclassesandhierarchies Implementation: Someclassesmaybereusedfromexisting libraryofclasses,otherscreatedorinherited
Computeraidedsoftwareengineering(CASE)
Softwaretoolstoautomatedevelopmentandreduce p work, ,including g repetitive
Graphicsfacilitiesforproducingchartsanddiagrams p g generators,reporting p gfacilities Screenandreport Analysisandcheckingtools Datadictionaries Codeanddocumentationgenerators
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
AlternativeSystemsBuildingApproaches
AlternativeSystemsBuildingApproaches
Traditionalsystemslifecycle:
Oldestmethodforbuildinginformationsystems Phasedapproachdividesdevelopmentintoformal stages
Followswaterfall waterfall approach:Tasksinonestagefinish beforeanotherstagebegins
31
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
AlternativeSystemsBuildingApproaches
AlternativeSystemsBuildingApproaches
THEPROTOTYPING PROCESS
Theprocessofdevelopingaprototype canbebrokendownintofoursteps. Becauseaprototypecanbedeveloped quicklyandinexpensively,systems builderscangothroughseveral iterations,repeatingsteps3and4,to prototype yp before refineandenhancethep arrivingatthefinaloperationalone. FIGURE139
Prototyping
Buildingexperimentalsystemrapidlyand p yforenduserstoevaluate inexpensively Prototype:Workingbutpreliminaryversionof informationsystem
Approvedprototypeservesastemplateforfinalsystem
Steps S in i prototyping i
1. 2. 3. 4.
33
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
AlternativeSystemsBuildingApproaches
AlternativeSystemsBuildingApproaches
Advantagesofprototyping
Usefulifsomeuncertaintyinrequirementsordesign solutions Oftenusedforenduserinterfacedesign More M lik likely l tof fulfill lfillend duserrequirements i
Enduserdevelopment:
Usesfourthgenerationlanguagestoallowendusers psystems y withlittleornohelp pfrom todevelop technicalspecialists Fourthgenerationlanguages:Lessproceduralthan conventionalprogramminglanguages
36
Disadvantages g
Mayglossoveressentialsteps Maynotaccommodatelargequantitiesofdataor largenumberofusers
Maynotundergofulltestingordocumentation
35 Prentice Hall 2011
PCsoftwaretools Querylanguages Reportgenerators G hi l Graphics languages Applicationgenerators Application pp softwarep packages g Veryhighlevelprogramminglanguages
Prentice Hall 2011
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
AlternativeSystemsBuildingApproaches
AlternativeSystemsBuildingApproaches
Enduserdevelopment(cont.):
Advantages:
Morerapid p completion p ofprojects p j Highlevelofuserinvolvementandsatisfaction
Applicationsoftwarepackages
Savetimeandmoney Manyoffercustomizationfeatures:
Softwarecanbemodifiedtomeetuniquerequirementswithout destroyingintegrityofpackagesoftware
Disadvantages:
Notdesignedforprocessingintensiveapplications q management g andcontrol, ,testing, g, Inadequate documentation Lossofcontroloverdata
Evaluationcriteriaforsystemsanalysisinclude:
Functionsprovidedbythepackage,flexibility,userfriendliness, hardwareandsoftwareresources, resources databaserequirements, requirements installationandmaintenanceefforts,documentation,vendor quality,andcost
Managingenduserdevelopment
Require q costj justificationofendusersystem y projects p j Establishhardware,software,andqualitystandards
37 Prentice Hall 2011 38
RequestforProposal(RFP)
Detailedlistofquestionssubmittedtopackagedsoftwarevendors Used U dtoevaluate l alternative l i software f packages k
Prentice Hall 2011
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
AlternativeSystemsBuildingApproaches
AlternativeSystemsBuildingApproaches
Outsourcing
Severaltypes
CloudandSaaSproviders
Subscribingcompaniesusesoftwareandcomputerhardware providedby p yvendors
Outsourcing(cont.)
Advantages Allows All organization i ti fl flexibility ibilit i inITneeds d Disadvantages Hiddencosts,e.g.
Identifyingandselectingvendor Transitioningtovendor
Externalvendors
Hiredtodesign, g ,createsoftware Domesticoutsourcing Drivenbyfirmsneedforadditionalskills,resources, assets Offshoreoutsourcing Drivenbycostsavings
39 Prentice Hall 2011 40
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
AlternativeSystemsBuildingApproaches
TOTALCOSTOFOFFSHOREOUTSOURCING
ApplicationDevelopmentfortheDigitalFirm
Rapidapplicationdevelopment(RAD)
Processofcreatingworkablesystemsinaveryshort periodoftime p Utilizestechniquessuchas: Visualprogrammingandothertoolsforbuilding graphicaluserinterfaces Iterativeprototypingofkeysystemelements program g codegeneration g Automationofp Closeteamworkamongendusersandinformation systemsspecialists
42 Prentice Hall 2011
FIGURE1310
41
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
ApplicationDevelopmentfortheDigitalFirm
ApplicationDevelopmentfortheDigitalFirm
Jointapplicationdesign(JAD)
Usedtoaccelerategenerationofinformation requirementsandtodevelopinitialsystems design Brings i end dusersand di information f i systems specialiststogetherininteractivesessionto di discuss systems d design i Cansignificantly g yspeed p up pdesign g p phaseand involveusersatintenselevel
43 Prentice Hall 2011
Agiledevelopment
Focusesonrapiddeliveryofworkingsoftwareby glarge g p project j intoseveralsmallsubp projects j breaking Subprojects
T Treated t dasseparate, t complete l t projects j t Completedinshortperiodsoftimeusingiterationand continuousfeedback
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
ManagementInformationSystems
CHAPTER13:BUILDINGINFORMATIONSYSTEMS
ApplicationDevelopmentfortheDigitalFirm
Componentbaseddevelopment
Groupsofobjectsthatprovidesoftwareforcommon (e.g., g ,onlineordering) g)andcanbecombinedto functions( createlargescalebusinessapplications Webservices
ReusablesoftwarecomponentsthatuseXMLandopenInternet standards(platform p independent) p Enableapplicationstocommunicatewithnocustom programmingrequiredtosharedataandservices Can C engageother th W Web bservices i f formorecomplex l t transactions ti Usingplatformanddeviceindependentstandardscanresultin significantcostsavingsandopportunitiesforcollaborationwith othercompanies
45 Prentice Hall 2011 46
All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of the publisher.
Pi t di Printed in th the U United it d St States t of fA America. i Copyright 2011 Pearson Education, Inc. P bli hi as Prentice Publishing P ti Hall H ll
Prentice Hall 2011