10.REDESIGNING THE ORGANIZATION WITH INFORMATION SYSTEMS 10.REDESIGNING THE ORGANIZATION WITH INFORMATION SYSTEMS.

Slides:



Advertisements
Similar presentations
Module N° 4 – ICAO SSP framework
Advertisements

Information Systems Systems Development Chapter 6.
10.1 © 2002 by Prentice Hall c h a p t e r 10 REDESIGNING THE ORGANIZATION WITH INFORMATION SYSTEMS.
REDESIGNING THE ORGANIZATION WITH INFORMATION SYSTEMS
DEVELOPMENT OF INFORMATION SYSTEM
Sixth Edition 1 M a n a g e m e n t I n f o r m a t i o n S y s t e m s M a n a g I n g I n f o r m a t i o n T e c h n o l o g y i n t h e E – B u s i.
Acquiring Information Systems and Applications
Redesigning the Organization with Information Systems Soetam Rizky.
6.1 Copyright © 2014 Pearson Education, Inc. publishing as Prentice Hall Building Information Systems Chapter 13 VIDEO CASES Video Case 1: IBM: Business.
Redesigning the Organization with Information System
14.1 © 2006 by Prentice Hall 14 Chapter Redesigning the Organization with Information Systems.
Sheu 1 n Spectrum of Organizational Changes (& Impacts) –Paradigm shift / Reengineering / Rationalization /Automation n IS as Planned Org. Change Information.
Eleventh Edition 1 Introduction to Information Systems Essentials for the Internetworked E-Business Enterprise Irwin/McGraw-Hill Copyright © 2002, The.
12 REDESIGNING THE ORGANIZATIONWITHINFORMATIONSYSTEMS Chapter.
Redesigning the Organization with Information Systems
Fundamentals of Information Systems, Second Edition
Prof. Yuan-Shyi Peter Chiu
14 Lecture Redesigning the Organization with Information Systems.
CHAPTER 9 DEVELOPING BUSINESS/IT STRATEGIES. IT Planning Planning an information system doesn’t start with bits, and bytes, or a Web site. It starts with.
13.1 © 2007 by Prentice Hall 13 Chapter Building Systems.
SDLC. Information Systems Development Terms SDLC - the development method used by most organizations today for large, complex systems Systems Analysts.
Lecture Nine Database Planning, Design, and Administration
Database System Development Lifecycle Transparencies
Acquiring Information Systems and Applications
Introduction to Computer Technology
Picture 1 model: ICT lifecycle in a company 1. business needs & business strategy 2. ICT strategy - ICT assessment - ICT strategic plan - ICT implementation/tactical.
Redesigning The Organization With Information Systems
1.Database plan 2.Information systems plan 3.Technology plan 4.Business strategy plan 5.Enterprise analysis Which of the following serves as a road map.
Chapter 14: Redesigning the Organization with Information Systems Instructor: Kevin Brabazon.
Chapter 9 Database Planning, Design, and Administration Sungchul Hong.
Database Planning, Design, and Administration Transparencies
Database System Development Lifecycle © Pearson Education Limited 1995, 2005.
Design Completion A Major Milestone System is Presented to Users and Management for Approval.
Information Systems Planning
14 REDESIGNING THE ORGANIZATION WITH INFORMATION SYSTEMS.
4/8: Systems Analysis & Development Systems change affecting organizations Systems development Influences on & challenges to implementation Systems development.
9.1 CHAPTER 9. REDESIGNING THE ORGANIZATION WITH INFORMATION SYSTEMS.
Laudon & Laudon: Canadian Edition
SYSTEMS ANALYSIS FORM 4 Included in this topic: Information Systems Systems Analysts System Life Cycle (incl. Case Study) Documentation.
Building and Managing Systems Chapter Thirteen (10E)
REDESIGNING THE ORGANIZATION WITH INFORMATION SYSTEMS
11/26: How IS Systems Change the Organization, Systems-Building
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
11. BUILDING INFORMATION SYSTEMS: CONTEMPORARY APPROACHES 11.1.
Module 4: Systems Development Chapter 12: (IS) Project Management.
Alter – Information Systems © 2002 Prentice Hall 1 The Process of Information System Planning.
Fundamentals of Information Systems, Third Edition1 Systems Design Answers the question “How will the information system do what it must do to solve a.
Acquiring Information Systems and Applications
Systems Analysis and Design
CHAPTER 13 Acquiring Information Systems and Applications.
INFORMATION SYSTEMS IN THE ENTERPRISE ENTERPRISE.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
SYSTEM INTERDEPENDENCE BUSINESS Strategy Strategy Rules Rules Procedures Procedures ORGANIZATION INFORMATION SYSTEM HARDWARE SOFTWAREDATABASE TELE- COMMUNICATIONS.
10.1 Copyright © 2005 Pearson Education Canada Inc. Management Information Systems, Second Canadian Edition Chapter 10: Systems Development SYSTEMS DEVELOPMENT.
1.Upgrade bandwidth 2.Upgrade desktop operating systems 3.Increase the number of servers 4.Determine industry standards 5.Convert to VoIP Which of the.
11.1 LEARNING OBJECTIVES EXPLAIN HOW ORGANIZATION CAN DEVELOP SUITABLE INFO SYSTEMSEXPLAIN HOW ORGANIZATION CAN DEVELOP SUITABLE INFO SYSTEMS IDENTIFY.
ISMS Implementation Workshop Adaptive Processes Consulting Pvt. Ltd.
第 11 組 MIS 報告. Phases of any information system ~ recognition of a business problem or opportunity ~ recognition of a business problem or opportunity.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
MANAGEMENT INFORMATION SYSTEM
The Information Systems Development Processes Chapter 9.
REDESIGNING THE ORGANIZATION WITH INFORMATION SYSTEMS
Information Systems Development
Principles of Information Systems Eighth Edition
Fundamentals of Information Systems, Sixth Edition
Why can a new information system be considered planned organizational change? An information system is a sociotechnical entity, an arrangement of both.
CLINICAL INFORMATION SYSTEM
INFORMATION SYSTEMS PLAN
(System Development Life Cycle)
Chapter 13 Building Systems.
Presentation transcript:

10.REDESIGNING THE ORGANIZATION WITH INFORMATION SYSTEMS 10.REDESIGNING THE ORGANIZATION WITH INFORMATION SYSTEMS

INFORMATION SYSTEMS PLAN DIRECTION OF SYSTEM DEVELOPMENT: RATIONALERATIONALE CURRENT SITUATIONCURRENT SITUATION MANAGEMENT STRATEGYMANAGEMENT STRATEGY IMPLEMENTATION PLANIMPLEMENTATION PLAN BUDGETBUDGET* 10.2

ENTERPRISE ANALYSIS ORGANIZATION-WIDE INFORMATION NEEDS IN TERMS OF: ORGANIZATION-WIDE INFORMATION NEEDS IN TERMS OF: ORGANIZATIONAL UNITSORGANIZATIONAL UNITS FUNCTIONSFUNCTIONS PROCESSESPROCESSES DATA ELEMENTSDATA ELEMENTS HELPS IDENTIFY KEY ENTITIES & ATTRIBUTES IN ORGANIZATION’S DATA HELPS IDENTIFY KEY ENTITIES & ATTRIBUTES IN ORGANIZATION’S DATA* 10.3

CRITICAL SUCCESS FACTORS SMALL NUMBER, EASILY IDENTIFIABLE OPERATIONAL GOALS SHAPED BY INDUSTRY, MANAGER, ENVIRONMENT BELIEVED TO ASSURE FIRM’S SUCCESS. USED TO DETERMINE ORGANIZATION’S INFORMATION REQUIREMENTS * 10.4

EXAMPLE EXAMPLE GOALS GOALS CRITICAL SUCCESS FACTOR PROFIT CONCERN PROFIT CONCERN EARNINGS/SHARE EARNINGS/SHARE AUTOMOBILE INDUSTRY AUTOMOBILE INDUSTRY RETURN ON INVESTMENT STYLING STYLING MARKET SHARE MARKET SHARE QUALITY DEALER SYSTEM QUALITY DEALER SYSTEM NEW PRODUCT NEW PRODUCT COST CONTROL COST CONTROL ENERGY STANDARDS ENERGY STANDARDS NONPROFIT NONPROFIT EXCELLENT HEALTH CARE EXCELLENT HEALTH CARE REGIONAL INTEGRATION OF HOSPITALS REGIONAL INTEGRATION OF HOSPITALS MEETING GOVERNMENT REGULATIONS MEETING GOVERNMENT REGULATIONS EFFICIENT USE OF RESOURCES EFFICIENT USE OF RESOURCES FUTURE HEALTH NEEDS FUTURE HEALTH NEEDS IMPROVED MONITORING OF REGULATIONS IMPROVED MONITORING OF REGULATIONS Source: Rockart “Chief Executives Define Their Own Data Needs” (1979) CRITICAL SUCCESS FACTORS & GOALS 10.5

USING CSFs TO DEVELOP SYSTEMS COLLECT MANAGERS’ CSFsCOLLECT MANAGERS’ CSFs AGGREGATE, ANALYZE INDIVIDUALS’ CSFsAGGREGATE, ANALYZE INDIVIDUALS’ CSFs DEVELOP AGREEMENT ON COMPANY CSFsDEVELOP AGREEMENT ON COMPANY CSFs DEFINE COMPANY CSFsDEFINE COMPANY CSFs USE CSFs TO DEVELOP INFORMATION SYSTEM PRIORITIESUSE CSFs TO DEVELOP INFORMATION SYSTEM PRIORITIES DEFINE DSS & DATABASESDEFINE DSS & DATABASES* 10.6

SPECTRUM OF ORGANIZATIONAL CHANGE AUTOMATION: Using Technology to Perform Tasks Efficiently / EffectivelyAUTOMATION: Using Technology to Perform Tasks Efficiently / Effectively RATIONALIZATION OF PROCEDURES: Streamline SOPs; Eliminate BottlenecksRATIONALIZATION OF PROCEDURES: Streamline SOPs; Eliminate Bottlenecks BUSINESS REENGINEERING: Radical Redesign of Processes to Improve Cost, Quality, Service; Maximize Benefits of TechnologyBUSINESS REENGINEERING: Radical Redesign of Processes to Improve Cost, Quality, Service; Maximize Benefits of Technology PARADIGM SHIFTPARADIGM SHIFT* 10.7

PARADIGM SHIFT PARADIGM IS A COMPLETE MENTAL MODEL OF HOW A COMPLEX SYSTEM FUNCTIONSPARADIGM IS A COMPLETE MENTAL MODEL OF HOW A COMPLEX SYSTEM FUNCTIONS A PARADIGM SHIFT INVOLVES RETHINKING THE NATURE OF THE BUSINESS, THE ORGANIZATION; A COMPLETE RECONCEPTION OF HOW THE SYSTEM SHOULD FUNCTIONA PARADIGM SHIFT INVOLVES RETHINKING THE NATURE OF THE BUSINESS, THE ORGANIZATION; A COMPLETE RECONCEPTION OF HOW THE SYSTEM SHOULD FUNCTION* 10.8

RISKS & REWARDS RISK RETURN Low LowHigh High 10.9

BUSINESS REENGINEERING WORKFLOW MANAGEMENT: Streamlining Procedures to Move Documents Easily, Efficiently from One Location to AnotherWORKFLOW MANAGEMENT: Streamlining Procedures to Move Documents Easily, Efficiently from One Location to Another MEASURE EXISTING PROCESSES AS BASELINEMEASURE EXISTING PROCESSES AS BASELINE USE INFORMATION TECHNOLOGY TO CREATE NEW DESIGN OPTIONSUSE INFORMATION TECHNOLOGY TO CREATE NEW DESIGN OPTIONS* 10.10

SYSTEM DEVELOPMENT PROCESS SYSTEMS ANALYSISSYSTEMS ANALYSIS SYSTEM DESIGNSYSTEM DESIGN PROGRAMMINGPROGRAMMING TESTINGTESTING CONVERSIONCONVERSION PRODUCTION & MAINTENANCEPRODUCTION & MAINTENANCE*

SYSTEMS ANALYSIS ANALYSIS OF PROBLEM TO BE SOLVED WITH AN INFORMATION SYSTEM ANALYSIS OF PROBLEM TO BE SOLVED WITH AN INFORMATION SYSTEM FEASIBILITY STUDY: CAN PROBLEM BE SOLVED WITHIN CONSTRAINTS? FEASIBILITY STUDY: CAN PROBLEM BE SOLVED WITHIN CONSTRAINTS?*

FEASIBILITY TECHNICAL: Assess Hardware, Software, Technical ResourcesTECHNICAL: Assess Hardware, Software, Technical Resources ECONOMIC: Will Benefits Outweigh CostsECONOMIC: Will Benefits Outweigh Costs OPERATIONAL: Is Solution Desirable Within Existing Conditions?OPERATIONAL: Is Solution Desirable Within Existing Conditions? INFORMATION REQUIREMENTS: Detailed Statement of New System NeedsINFORMATION REQUIREMENTS: Detailed Statement of New System Needs*

SYSTEM DESIGN DETAILS HOW SYSTEM WILL MEET NEEDS: DETAILS HOW SYSTEM WILL MEET NEEDS: LOGICAL DESIGN: Components, Data as Needed by ApplicationsLOGICAL DESIGN: Components, Data as Needed by Applications PHYSICAL DESIGN: Physical Location of Components and DataPHYSICAL DESIGN: Physical Location of Components and Data END USERS: Needs Drive Design; Must Have Input, Understand How Solution Meets Their Needs END USERS: Needs Drive Design; Must Have Input, Understand How Solution Meets Their Needs OUTPUTOUTPUT –MEDIUM –CONTENT –TIMING *

ROLE OF END USERS USERS DRIVE SYSTEMS EFFORTUSERS DRIVE SYSTEMS EFFORT MUST HAVE SUFFICIENT CONTROL TO ENSURE SYSTEM REFLECTS BUSINESS PRIORITIES, NEEDSMUST HAVE SUFFICIENT CONTROL TO ENSURE SYSTEM REFLECTS BUSINESS PRIORITIES, NEEDS FUNCTIONAL USERS DRIVE SYSTEM NEEDSFUNCTIONAL USERS DRIVE SYSTEM NEEDS

COMPLETING SYSTEM DEVELOPMENT PROCESS PROGRAMMING: Translating needs to Program CodePROGRAMMING: Translating needs to Program Code TESTING: Does System Produce Desired Results?TESTING: Does System Produce Desired Results?*

TESTING UNIT TESTING: Tests Each Unit SeparatelyUNIT TESTING: Tests Each Unit Separately SYSTEM TESTING: Do Modules Function as planned?SYSTEM TESTING: Do Modules Function as planned? ACCEPTANCE TESTING: Final CertificationACCEPTANCE TESTING: Final Certification TEST PLAN: Preparations for Tests to be PerformedTEST PLAN: Preparations for Tests to be Performed*

CONVERSION PARALLEL: Old & New Run Same Problems. Give Same Results?PARALLEL: Old & New Run Same Problems. Give Same Results? DIRECT: Risky Conversion to New SystemDIRECT: Risky Conversion to New System PILOT: Introduce Into One Area. Does it Work? Yes: Introduce into Other AreaPILOT: Introduce Into One Area. Does it Work? Yes: Introduce into Other Area PHASED: Introduce in StagesPHASED: Introduce in Stages CONVERSION PLAN: Schedule for ConversionCONVERSION PLAN: Schedule for Conversion DOCUMENTATION: Description of How System WorksDOCUMENTATION: Description of How System Works*

PRODUCTION & MAINTENANCE PRODUCTION: Constant Review by Users & Operators. Does it Meet Goals?PRODUCTION: Constant Review by Users & Operators. Does it Meet Goals? MAINTENANCE: Upkeep; Update; Corrections Over TimeMAINTENANCE: Upkeep; Update; Corrections Over Time*

SYSTEMS DEVELOPMENT CORE ACTIVITY CORE ACTIVITY DESCRIPTION DESCRIPTION SYSTEMS ANALYSIS SYSTEMS ANALYSIS IDENTIFY PROBLEM(S) IDENTIFY PROBLEM(S) SPECIFY PROBLEM SPECIFY PROBLEM ESTABLISH INFORMATION REQUIREMENTS ESTABLISH INFORMATION REQUIREMENTS SYSTEMS DESIGN SYSTEMS DESIGN CREATE LOGICAL DESIGN SPECIFICATIONS CREATE LOGICAL DESIGN SPECIFICATIONS CREATE PHYSICAL DESIGN SPECIFICATIONS CREATE PHYSICAL DESIGN SPECIFICATIONS MANAGE TECHNICAL REALIZATION OF SYSTEM MANAGE TECHNICAL REALIZATION OF SYSTEM PROGRAMMING PROGRAMMING TRANSLATE DESIGN INTO CODE TRANSLATE DESIGN INTO CODE TESTING TESTING UNIT UNIT SYSTEMS SYSTEMS ACCEPTANCE ACCEPTANCE CONVERSION CONVERSION PLAN PLAN PREPARE DOCUMENTATION PREPARE DOCUMENTATION TRAIN USERS & TECHNICAL STAFF TRAIN USERS & TECHNICAL STAFF PRODUCTION & PRODUCTION &MAINTENANCE OPERATE OPERATE EVALUATE EVALUATE MODIFY MODIFY

IMPLEMENTING CHANGE ALL ACTIVITIES WORK TOWARD ADOPTING, MANAGING, ROUTINIZING INNOVATION ALL ACTIVITIES WORK TOWARD ADOPTING, MANAGING, ROUTINIZING INNOVATION CHANGE AGENT: Individual Acting as Catalyst to Insure Success in Adapting to New SystemCHANGE AGENT: Individual Acting as Catalyst to Insure Success in Adapting to New System USER-DESIGNER COMMUNICATIONS GAP : Differences in Backgrounds, Interests, Priorities that Impede Communications & Problem Solving Between End-users & SpecialistsUSER-DESIGNER COMMUNICATIONS GAP : Differences in Backgrounds, Interests, Priorities that Impede Communications & Problem Solving Between End-users & Specialists*

Factors Critical For Success User InvolvementUser Involvement Management SupportManagement Support Level of Complexity and RiskLevel of Complexity and Risk Management of Implementation ProcessManagement of Implementation Process

DESIGNING FOR THE ORGANIZATION JOB DESIGN STRATEGIC PEOPLE- TECHNOLOGY PLANNING WORK STANDARDS & PERFORMANCE MONITORING TRAINING & PILOTING ERGONOMICS: *HARDWARE * WORKSTATIONS *SOFTWARE * WORK ENVIRONMENT HEALTH & SAFETY HEALTH & SAFETY EMPLOYEE COMMUNICATIONS MECHANISMS LEGAL/REGULATORY COMPLIANCE EMPLOYEE PARTICIPATION

MANAGEMENT CHALLENGES MAJOR RISKS/UNCERTAINTIES IN SYSTEM DEVELOPMENTMAJOR RISKS/UNCERTAINTIES IN SYSTEM DEVELOPMENT DIFFICULT TO DETERMINE BENEFITSDIFFICULT TO DETERMINE BENEFITS MANAGING CHANGEMANAGING CHANGE*