Beruflich Dokumente
Kultur Dokumente
E-Hospital
MMRUMY
EHospital HospitalInformationSystems
2. Rationalizationofprocedures
Streamlinesstandardoperatingprocedures Oftenfoundinprogramsformakingcontinuousquality improvements
Totalqualitymanagement(TQM) Sixsigma
4. Paradigmshifts
Rethinknatureofbusiness Definenewbusinessmodel Changenatureoforganization
MMRUMY
EHospital HospitalInformationSystems
FIGURE131
StepsinBPM
1. Identifyprocessesforchange 2 Analyze 2. A l existing i ti processes 3. Designthenewprocess 4. Implementthenewprocess 5. Continuousmeasurement
MMRUMY
EHospital HospitalInformationSystems
ASISBUSINESSPROCESSFORPURCHASINGABOOKFROMAPHYSICALBOOKSTORE
FIGURE132
Purchasingabookfromaphysicalbookstorerequiresmanystepstobeperformedby boththesellerandthecustomer.
REDESIGNEDPROCESSFORPURCHASINGABOOKONLINE
FIGURE133
UsingInternettechnologymakesitpossibletoredesigntheprocessforpurchasinga booksothatitrequiresfewerstepsandconsumesfewerresources.
MMRUMY
EHospital HospitalInformationSystems
Review:
ITvs.OrganizationalChange
GlobalNetwork Internationaldivisionoflabor Enterprisenetworks collaborativeworkandteamwork Distributedcomputing Empowerment P t bl computing Portable ti Virtual Vi t lorganizations i ti GraphicalUserInterface Accessibility
ITCapabilitiesthathasorganizationalimpacts
Transactional,geographical,automation,analytical, informational,sequential,knowledgemanagement,tracking, disintermediation
MMRUMY
EHospital HospitalInformationSystems
MMRUMY
EHospital HospitalInformationSystems
Systemsdevelopment:
Activitiesthatgointoproducinganinformation systemsolutiontoanorganizationalproblemor opportunity 1. Systemsanalysis 2. Systemsdesign 3 Programming 3. 4. Testing 5. Conversion 6. Productionandmaintenance
FIGURE134
MMRUMY
EHospital HospitalInformationSystems
Systems Analysis
Analysisofproblemtobesolvedbynewsystem
Definingtheproblemandidentifyingcauses Specifyingsolutions
Systemsproposalreportidentifiesandexaminesalternative solutions
Identifyinginformationrequirements
Includesfeasibilitystudy
Issolutionfeasibleandgoodinvestment? Isrequiredtechnology,skillavailable?
MMRUMY
EHospital HospitalInformationSystems
Systems Design
Describessystemspecificationsthatwilldeliver functionsidentifiedduringsystemsanalysis Shouldaddressallmanagerial,organizational,and technologicalcomponentsofsystemsolution Roleofendusers
Userinformationrequirementsdrivesystembuilding Usersmusthavesufficientcontroloverdesignprocesstoensure systemreflectstheirbusinessprioritiesandinformationneeds Insufficientuserinvolvementindesigneffortismajorcauseofsystem failure
MMRUMY
EHospital HospitalInformationSystems
Testing
Ensuressystemproducesrightresults Unittesting:Testseachprograminsystemseparately S t testing: System t ti Test T tfunctioning f ti i of fsystem t asawhole h l Acceptancetesting:Makessuresystemisreadytobe usedinproductionsetting Testplan:Allpreparationsforseriesoftests
MMRUMY
10
EHospital HospitalInformationSystems
Conversion
Processofchangingfromoldsystemtonewsystem Fourmainstrategies
1. 2. 3. 4. Parallelstrategy Directcutover Pilotstudy Phasedapproach
MMRUMY
11
EHospital HospitalInformationSystems
DESCRIPTION
Identify problem(s) Specify solutions Establish information requirements Create design specifications
Systems design
Programming
Translate design specifications into code Unit test Systems test A Acceptance t t test t Plan conversion Prepare documentation Train users and technical staff Operate the system Evaluate the system Modify the system
Testing
Conversion
IT Project Management
MMRUMY
12
EHospital HospitalInformationSystems
CURRENT SITUATION
GOALS
New Developments
NOW
New Developments
THEFUTURE
MMRUMY
13
EHospital HospitalInformationSystems
Typesofsystemfailure
Failtocaptureessentialbusinessrequirements Failtoprovideorganizationalbenefits Complicated,poorlyorganizeduserinterface Inaccurateorinconsistentdata
MMRUMY
14
EHospital HospitalInformationSystems
Project Management
Activitiesincludeplanningwork,assessingrisk, estimatingresourcesrequired,organizingthe work,assigningtasks,controllingproject execution,reportingprogress,analyzingresults Fivemajorvariables
1. 2. 3. 4. 5. Scope Time Cost Quality Risk
Constrain
Accept
X X
MMRUMY
15
EHospital HospitalInformationSystems
PurposeofthePlan
Overview, ,strategic g &management g p plan Currentsituation&organization,changingenvironment,major goals Systems~businessfunction,capabilities,system~business requirements,futuredemands Newsystemsprojects,newcapabilitiesrequirement Acquisition,schedule, realignment,reorganization,controls, training,personnel Anticipateddifficultiesinimplementation,progressreport Requirements,potentialsavings,financing,acquisitioncycle
StrategicBusinessPlan CurrentSystems
NewDevelopments ManagementStrategy
ImplementationPlan
BudgetRequirements
StrategicContext
3.
SystemDescription
4.
ImplementationPlan
MMRUMY
16
EHospital HospitalInformationSystems
SystemsDesign
Createlogical&physicaldesignspecs,managetechnical realization Programming(daesign specs programcode)
Testing
Unittest, test systemstest, test acceptancetest
Conversion
Planconversion,preparedocs,trainusersandtechnicalstaff
Production&Maintenance
Operatesystem,evaluatesystem,modifysystem
StrategicAnalysis:CriticalSuccessFactors
Smallnumberofeasilyidentifiableorganizationalgoals Shapedbytheindustry,firm,manager,&environment Believedtoensurethesuccessofanorganization
MMRUMY
17
EHospital HospitalInformationSystems
Systems-Development Approaches
1. 2. 3. 4 4. 5. SystemsDevelopmentLifecycle Prototyping Applicationsoftwarepackage Enduserdevelopment Outsourcing
SystemsDevelopmentApproaches(1/5)
MMRUMY
18
EHospital HospitalInformationSystems
Year 1
Year 1
SystemsDevelopmentApproaches(2/5)
Prototyping
Characteristics Dynamic requirements by experiment Rapid, informal, iterative Continuous user-prototype interaction Advantages Rapid & inexpensive For uncertain requirements or end end-user user interface focus Promotes user participation Disadvantages Not for large, complex systems Can gloss over analysis, documentation, & testing
MMRUMY
19
EHospital HospitalInformationSystems
SystemsDevelopmentApproaches
Prototyping
Identify y basic req.
Develop prototype
User satisfied?
SystemsDevelopmentApproaches(3/5)
MMRUMY
20
EHospital HospitalInformationSystems
SystemsDevelopmentApproaches
SystemsDevelopmentApproaches(4/5)
End-User Development
Characteristics Created by end-users with software tools Rapid & informal Minimum system specialist role Advantages y development p Users control system Saves development time & cost Reduce applications backlog Disadvantages Can proliferate uncontrolled IS and data Not always meet Quality Assurance
MMRUMY
21
EHospital HospitalInformationSystems
SystemsDevelopmentApproaches(5/5)
Outsourcing
Characteristics Built (& operated) by ext. vendor Advantages Can reduce/control cost When internal resources are limited Disadvantages Losses control over IS functions Dependence on external vendors
Systems-Development Approaches
A Approach h Systems Lifecycle Ch Characteristics t i ti Sequential, formal Written specs and approvals Limited user role Dynamic reqs by experiment Rapid, informal, iterative Cont. userprototype interaction Ad Advantages t Necessary for large complex systems and projects Rapid & inexpensive For uncertain reqs or end-user interface focus Promotes user part.
(1/2)
Di d Disadvantages t Slow & expensive Discourages changes Massive paperwork Not for large, complex systems Can gloss over analysis, documentation, & testing
Prototyping
MMRUMY
22
EHospital HospitalInformationSystems
Systems-Development Approaches
Approach
Application software package
(2/2)
Characteristics
Eliminates needs for internally dev. s/w
Advantages
Reduces design, prog., install., and maint. Can save time & cost (for common bus.apps) Reduces int. IS resource Users control sys.dev. Saves dev. time & cost Reduce apps backlog
Disadvantages
May not meet org orgs s req. May not perform bus.functions well Extensive customization raises cost Can proliferate uncontrolled IS and data Not always meet Quality Assurance Losses control over IS functions Dependence on external vendors
End-user development
Created by end-users w/ 4G s/w tools Rapid p & informal Min. sys.spec. role Built (& operated) by ext. vendor
Out-sourcin
IS Stakeholders
MMRUMY
23
EHospital HospitalInformationSystems
INFORMATIONSYSTEMBUILDINGBLOCKS
Systems Development
Stakeholders
S Y S T E M S A N A L Y S T S
System Owner
ANINFORMATIONSYSTEM
Activities
ISSCOPE
Purpose&vision Goalsandobjectives Costsandbenefits
System Users
ISREQUIREMENTS
Whatthesystemis:andmustdoindependentof technology
System Designers
ISDESIGN
Howthesystemwillbeimplementedusingtechnology
System Builders
ISCOMPONENTS
Actual,technicalimplementationofthesystem
INFORMATION TECHNOLOGY & ARCHITECTURE
SystemOwners
ISsponsorsandchiefadvocates Fundingtodevelop,operate,andmaintaintheIS
SystemUsers/Clients
RegularlyuseoraffectedbytheIS Capture,validate,enter,respond,store,exchangeData &Information Alwaysright,andultimatelypaysfortheIS 1)Internal lusers:clerical l i l&service i workers; k technical h i l& professionalstaff;knowledgeworkers;supervisors, middlemanagers,andexecutivemanagers. 2)Remoteandmobileusers 3)Externalusers
MMRUMY
24
EHospital HospitalInformationSystems
SystemDesigners
Translatessystemusersbusinessrequirementsand constraintsintotechnicalsolutions. Designscomputerfiles,databases,inputs,outputs, screen,networks,andprograms
SystemBuilders
ConstructsIScomponentsbasedondesign specifications
SystemsAnalysts
Facilitates thedevelopmentofISandcomputer applications
System Owner System Users System Designers System Builders
SYSTEMS ANALYSTS
MMRUMY
25
EHospital HospitalInformationSystems
Interpersonalskills
Effectivewrittenandoralcommunicationskills
Helpyouworkwithenduseraswellasothersystemanalysts andprogrammers
MMRUMY
26