2. 11.1

3. LEARNING OBJECTIVES EXPLAIN HOW ORGANIZATION CAN DEVELOP SUITABLE INFO SYSTEMSEXPLAIN HOW ORGANIZATION CAN DEVELOP SUITABLE INFO SYSTEMS IDENTIFY CORE ACTIVITIES IN SYSTEMS DEVELOPMENT PROCESSIDENTIFY CORE ACTIVITIES IN SYSTEMS DEVELOPMENT PROCESS* 11.3

4. MANAGEMENT CHALLENGES OVERVIEW OF SYSTEMS DEVELOPMENTOVERVIEW OF SYSTEMS DEVELOPMENT* 11.4

5. CHALLENGES: RISKS AND UNCERTAINTIES IN SYSTEMS DEVELOPMENTRISKS AND UNCERTAINTIES IN SYSTEMS DEVELOPMENT* INFORMATION SYSTEMS PLAN 11.5

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

7. INFORMATION SYSTEMS PLAN 1. PURPOSE OF THE PLAN: OVERVIEW OF PLAN CONTENTSOVERVIEW OF PLAN CONTENTS CHANGES IN CURRENT SITUATIONCHANGES IN CURRENT SITUATION FIRM’S STRATEGIC PLANFIRM’S STRATEGIC PLAN CURRENT ORGANIZATIONCURRENT ORGANIZATION MANAGEMENT STRATEGYMANAGEMENT STRATEGY* 11.7

8. INFORMATION SYSTEMS PLAN 2. STRATEGIC BUSINESS PLAN: CURRENT SITUATIONCURRENT SITUATION CURRENT ORGANIZATIONCURRENT ORGANIZATION CHANGING ENVIRONMENTCHANGING ENVIRONMENT MAJOR GOALS OF PLANMAJOR GOALS OF PLAN* 11.8

9. INFORMATION SYSTEMS PLAN 3. CURRENT SYSTEMS: MAJOR SYSTEMS SUPPORTING BUSINESS FUNCTIONSMAJOR SYSTEMS SUPPORTING BUSINESS FUNCTIONS MAJOR CURRENT CAPABILITIESMAJOR CURRENT CAPABILITIES –HARDWARE –SOFTWARE –DATABASE –TELECOMMUNICATIONS DIFFICULTIES MEETING REQUIREMENTSDIFFICULTIES MEETING REQUIREMENTS ANTICIPATED FUTURE DEMANDSANTICIPATED FUTURE DEMANDS* 11.9

10. INFORMATION SYSTEMS PLAN 4. NEW DEVELOPMENTS: NEW SYSTEM PROJECTSNEW SYSTEM PROJECTS –PROJECT DESCRIPTIONS –BUSINESS RATIONALE NEW CAPABILITIES REQUIREDNEW CAPABILITIES REQUIRED –HARDWARE –SOFTWARE –DATABASE –TELECOMMUNICATIONS* 11.10

11. INFORMATION SYSTEMS PLAN 5. MANAGEMENT STRATEGY ACQUISITION PLANSACQUISITION PLANS MILESTONES & TIMINGMILESTONES & TIMING ORGANIZATIONAL REALIGNMENTORGANIZATIONAL REALIGNMENT INTERNAL REORGANIZATIONINTERNAL REORGANIZATION MANAGEMENT CONTROLSMANAGEMENT CONTROLS MAJOR TRAINING INITIATIVESMAJOR TRAINING INITIATIVES PERSONNEL STRATEGYPERSONNEL STRATEGY* 11.11

12. IMPROVING INFORMATION TECHNOLOGY OUTCOMES Assessing Project RiskAssessing Project Risk Assessing Portfolio RiskAssessing Portfolio Risk Management of RiskManagement of Risk

13. FACTORS IN ASSESSING IT PROJECT RISK SizeSize StructureStructure Experience With TechnologyExperience With Technology –Within Company –Anywhere Commitment/CultureCommitment/Culture InterdependenceInterdependence Completion IntervalCompletion Interval

14. PORTFOLIO RISK Where Are You in Your Industry?Where Are You in Your Industry? –About To Go Under –Major Growth Opportunity Management ProfileManagement Profile –Risk Adverse (Willingness to Be Left Behind) –Risk Takers (Willingness to Be It All) Timing (How Much, How Fast)Timing (How Much, How Fast)

15. ENTERPRISE ANALYSIS (BUSINESS SYSTEMS PLANNING) 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* 11.12

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

17. 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?* SYSTEMS ANALYSIS 11.26

18. 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* 11.27

19. 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* 11.28

20. DESIGN SPECIFICATIONS OUTPUTOUTPUT –MEDIUM; CONTENT; TIMING INPUTINPUT –ORIGINS; FLOW; DATA ENTRY USER INTERFACEUSER INTERFACE –SIMPLICITY; EFFICIENCY; LOGIC –FEEDBACK; ERRORS DATABASE DESIGNDATABASE DESIGN –LOGICAL DATA RELATIONS –VOLUME, SPEED REQUIREMENTS –FILE ORGANIZATION & DESIGN –RECORD SPECIFICATIONS* 11.29

21. PROCESSINGPROCESSING –COMPUTATIONS –PROGRAM MODULES –REQUIRED REPORTS –TIMING OF OUTPUTS MANUAL PROCEDURESMANUAL PROCEDURES –WHAT ACTIVITIES –WHO PERFORMS THEM –HOW –WHERE* 11.30 DESIGN SPECIFICATIONS

22. CONTROLSCONTROLS –INPUT –PROCESSING –OUTPUT –PROCEDURAL SECURITYSECURITY –ACCESS CONTROLS –CATASTROPHE PLANS –AUDIT TRAILS* 11.31 DESIGN SPECIFICATIONS

23. CONVERSIONCONVERSION –TRANSFER FILES –INITIATE NEW PROCEDURES –SELECT TESTING MODULES –CUT OVER TO NEW SYSTEM TRAININGTRAINING –SELECT TRAINING TECHNIQUES –DEVELOP TRAINING MODULES –IDENTIFY TRAINING FACILITIES ORGANIZATIONAL CHANGESORGANIZATIONAL CHANGES –TASK REDESIGN –JOB DESIGN –PROCESS DESIGN –OFFICE / ORGANIZATION STRUCTURE DESIGN –REPORTING RELATIONSHIPS* 11.32 DESIGN SPECIFICATIONS

24. 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 11.33

25. 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?* 11.34

26. 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* 11.35

27. CONVERSION PARALLEL: Old & new run same problems. Give same results?PARALLEL: Old & new run same problems. Give same results? DIRECT CUTOVER: Risky conversion to new systemDIRECT CUTOVER: 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* 11.36

28. 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* 11.37

29. SYSTEMS DEVELOPMENT CORE ACTIVITY DESCRIPTION SYSTEMS ANALYSIS IDENTIFY PROBLEM(S) SPECIFY SOLUTIONS ESTABLISH INFORMATION REQUIREMENTS SYSTEMS DESIGN CREATE LOGICAL DESIGN SPECS CREATE PHYSICAL DESIGN SPECS MANAGE TECHNICAL REALIZATION OF SYSTEM PROGRAMMINGTRANSLATE DESIGN SPECS INTO PROGRAM CODE 11.38

30. SYSTEMS DEVELOPMENT CORE ACTIVITY DESCRIPTION TESTING UNIT TEST SYSTEMS TEST ACCEPTANCE TEST CONVERSION PLAN CONVERSION PREPARE DOCUMENTATION TRAIN USERS & TECHNICAL STAFF PRODUCTION & OPERATE SYSTEM MAINTENANCE EVALUATE SYSTEM MODIFY SYSTEM 11.39