12.1. APPRAISE SYSTEM BUILDING ALTERNATIVESAPPRAISE SYSTEM BUILDING ALTERNATIVES COMPARE STRENGTHS, WEAKNESSES OF APPROACHESCOMPARE STRENGTHS, WEAKNESSES.

Slides:



Advertisements
Similar presentations
10.1 © 2002 by Prentice Hall c h a p t e r 10 REDESIGNING THE ORGANIZATION WITH INFORMATION SYSTEMS.
Advertisements

Systems Investigation and Analysis
DEVELOPMENT OF INFORMATION SYSTEM
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
Systems Analysis & IT Project Management Pepper. System Life Cycle BirthDeathDevelopmentProduction.
Ch 3 System Development Environment
© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Designing new systems or modifying existing ones should always be aimed at helping an organization achieve its goals State the purpose of systems design.
10.1 ALTERNATIVE SYSTEMS-DEVELOPMENT APPROACHES Traditional Systems Life Cycle –A phased approach, dividing development into formal stages –a formal division.
Chapter Twelve Approaches to Systems-Building. The Traditional Systems Lifestyle The systems lifecycle is a traditional methodology for developing an.
14.1 © 2006 by Prentice Hall 14 Chapter Redesigning the Organization with Information Systems.
Effective systems development requires a team effort from stakeholders, users, managers, systems development specialists, and various support personnel,
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
12 REDESIGNING THE ORGANIZATIONWITHINFORMATIONSYSTEMS Chapter.
Redesigning the Organization with Information Systems
Fundamentals of Information Systems, Second Edition
Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition.
12.1. APPRAISE SYSTEM BUILDING ALTERNATIVESAPPRAISE SYSTEM BUILDING ALTERNATIVES COMPARE STRENGTHS, WEAKNESSES OF APPROACHESCOMPARE STRENGTHS, WEAKNESSES.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
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.
Introduction to Systems Analysis and Design
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 1.1.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 1 The Systems.
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.
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.
Appendix 2 Automated Tools for Systems Development © 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 2 Slide 1.
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
1.1 © 2007 by Prentice Hall 11 Chapter Building Information Systems.
Laudon & Laudon: Canadian Edition
Managing the development and purchase of information systems (Part 1)
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
11. APPROACHES TO SYSTEM BUILDING SYSTEM LIFECYCLE PROJECT DEFINITION: Is There a Problem? Can it be Solved with a Project?PROJECT DEFINITION: Is.
11/26: How IS Systems Change the Organization, Systems-Building
Appraise system building alternativesAppraise system building alternatives Compare strengths, weaknesses of approachesCompare strengths, weaknesses of.
11.1 © 2007 by Prentice Hall 11 Chapter Building Information Systems.
10.1 CHAPTER 10. APPROACHES TO SYSTEM BUILDING APPRAISE SYSTEM BUILDING ALTERNATIVESAPPRAISE SYSTEM BUILDING ALTERNATIVES COMPARE STRENGTHS, WEAKNESSES.
Chapter 14 Information System Development
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
Chapter 10 Information Systems Analysis and Design
Copyright 2002 Prentice-Hall, Inc. 1.1 Modern Systems Analysis and Design Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 1 The Systems Development.
Systems Analysis and Design
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
14.1 © 2006 by Prentice Hall 13 Chapter Building Information Systems.
Systems Analysis and Design in a Changing World, Fourth Edition
Software Development Life Cycle by A.Surasit Samaisut Copyrights : All Rights Reserved.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
11.1 © 2007 by Prentice Hall 6 Chapter Building Information Systems.
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
CASE (Computer-Aided Software Engineering) Tools Software that is used to support software process activities. Provides software process support by:- –
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution Structured programming Product SW.
ANALISA & PERANCANGAN SISTEM Disusun Oleh : Dr. Lily Wulandari Program Pasca Sarjana Magister Sistem Informasi Universitas Gunadarma.
Final Review Systems Analysis and Design in a Changing World, 4th Edition 1 Final Review u Chapters 1-6, 8-10, 13, 14, 15 u Multiple choice, short answer,
C_ITIP211 LECTURER: E.DONDO. Unit 1 : The Systems Development Environment.
Building Information Systems
REDESIGNING THE ORGANIZATION WITH INFORMATION SYSTEMS
Building Information Systems
Fundamentals of Information Systems, Sixth Edition
Fundamentals of Information Systems, Sixth Edition
Building Information Systems
Approaches to Systems-Building
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
Chapter 13 Building Systems.
Presentation transcript:

12.1

APPRAISE SYSTEM BUILDING ALTERNATIVESAPPRAISE SYSTEM BUILDING ALTERNATIVES COMPARE STRENGTHS, WEAKNESSES OF APPROACHESCOMPARE STRENGTHS, WEAKNESSES OF APPROACHES ASSESS SOLUTIONS TO PROBLEMS CREATED BY APPROACHESASSESS SOLUTIONS TO PROBLEMS CREATED BY APPROACHES DESCRIBE TOOLS, METHODOLOGIES OF SYSTEMS DEVELOPMENTDESCRIBE TOOLS, METHODOLOGIES OF SYSTEMS DEVELOPMENT* LEARNING OBJECTIVES 12.2

MANAGEMENT CHALLENGES TRADITIONAL SYSTEMS LIFECYCLETRADITIONAL SYSTEMS LIFECYCLE ALTERNATIVE SYSTEM-BUILDING APPROACHESALTERNATIVE SYSTEM-BUILDING APPROACHES SYSTEM-BUILDING METHODOLOGIES & TOOLSSYSTEM-BUILDING METHODOLOGIES & TOOLS* 12.3

SYSTEM LIFECYCLE PROJECT DEFINITION: Is there a problem? Can it be solved with a project?PROJECT DEFINITION: Is there a problem? Can it be solved with a project? SYSTEM STUDY: Analyze problems in existing systems; define objectives evaluate alternativesSYSTEM STUDY: Analyze problems in existing systems; define objectives evaluate alternatives DESIGN: Logical & physical specifications for systems solutionDESIGN: Logical & physical specifications for systems solution PROGRAMMING: Develop software codePROGRAMMING: Develop software code* 12.4

SYSTEM LIFECYCLE INSTALLATION: Construct, test, train, convert to new systemINSTALLATION: Construct, test, train, convert to new system POSTINSTALLATION: On-going evaluation, modifications for improvement to meet new requirementsPOSTINSTALLATION: On-going evaluation, modifications for improvement to meet new requirements NECESSARY FOR LARGE, COMPLEX SYSTEMS & PROJECTS NECESSARY FOR LARGE, COMPLEX SYSTEMS & PROJECTS* 12.5

SYSTEM LIFECYCLE CAN BE COSTLY, TIME CONSUMINGCAN BE COSTLY, TIME CONSUMING MAY ENCOURAGE FREEZING SPECIFICATIONS EARLY IN DEVELOPMENTMAY ENCOURAGE FREEZING SPECIFICATIONS EARLY IN DEVELOPMENT MAY NOT BE SUITABLE FOR SMALL, LESS STRUCTURED SYSTEMSMAY NOT BE SUITABLE FOR SMALL, LESS STRUCTURED SYSTEMS* 12.6

ALTERNATIVE SYSTEM- BUILDING APPROACHES PROTOTYPINGPROTOTYPING APPLICATION SOFTWARE PACKAGESAPPLICATION SOFTWARE PACKAGES END-USER DEVELOPMENTEND-USER DEVELOPMENT OUTSOURCINGOUTSOURCING* 12.7

PROTOTYPING PROCESS OF BUILDING EXPERIMENTAL SYSTEM TO DEMONSTRATE, EVALUATE APPROACH; USERS REFINE NEEDS PROCESS OF BUILDING EXPERIMENTAL SYSTEM TO DEMONSTRATE, EVALUATE APPROACH; USERS REFINE NEEDS PROTOTYPE: Preliminary working version of information system for demonstration, evaluation purposesPROTOTYPE: Preliminary working version of information system for demonstration, evaluation purposes ITERATIVE PROCESSITERATIVE PROCESS* 12.8

STEPS IN PROTOTYPING 1. IDENTIFY USER’S REQUIREMENTS 2, DEVELOP PROTOTYPE 3, USE PROTOTYPE 4. REVISE & ENHANCE PROTOTYPE BEST FOR DESIGN OF END-USER INTERFACE: How end-user interacts with system BEST FOR DESIGN OF END-USER INTERFACE: How end-user interacts with system* 12.9

APPLICATION SOFTWARE PACKAGES PREWRITTEN, PRECODED APPLICATION SOFTWARE, COMMERCIALLY AVAILABLE FOR SALE OR LEASE PREWRITTEN, PRECODED APPLICATION SOFTWARE, COMMERCIALLY AVAILABLE FOR SALE OR LEASE GEARED TO COMMON REQUIREMENTSGEARED TO COMMON REQUIREMENTS CUSTOMIZATION: Modification of software to meet organization’s needsCUSTOMIZATION: Modification of software to meet organization’s needs MUST WEIGH COSTS / BENEFITSMUST WEIGH COSTS / BENEFITS* 12.10

SELECTED EXAMPLES OF APPLICATION PROGRAMS ACCOUNTS RECEIVABLE; BOND & STOCK MANAGEMENT; COMPUTER-AIDED DESIGN (CAD) ; DOCUMENT IMAGING; E- MAIL; ENTERPRISERESOURCE PLANNING (ERP); GROUPWARE; HEALTH CARE; HOTELMANAGEMENT; INTERNET TELEPHONE; INVENTORY CONTROL; JOB COSTING; LIBRARY SYSTEMS; LIFE INSURANCE; MAILING LABELS; MATHEMATICAL / STATISTICAL MODELING; ORDER PROCESSING; PAYROLL; PROCESS CONTROL;TAX ACCOUNTING; WEB BROWSER; WORD PROCESSING ACCOUNTS RECEIVABLE; BOND & STOCK MANAGEMENT; COMPUTER-AIDED DESIGN (CAD) ; DOCUMENT IMAGING; E- MAIL; ENTERPRISE.RESOURCE PLANNING (ERP); GROUPWARE; HEALTH CARE; HOTEL.MANAGEMENT; INTERNET TELEPHONE; INVENTORY CONTROL; JOB COSTING; LIBRARY SYSTEMS; LIFE INSURANCE; MAILING LABELS; MATHEMATICAL / STATISTICAL MODELING; ORDER PROCESSING; PAYROLL; PROCESS CONTROL;TAX ACCOUNTING; WEB BROWSER; WORD PROCESSING* 12.11

CUSTOMIZATION MODIFYING SOFTWARE PACKAGE TO MEET ORGANIZATION’S UNIQUE REQUIREMENTS WITHOUT DESTROYING INTEGRITY OF PACKAGE RAISES DEVELOPMENT COSTS * 12.12

% LINES OF CODE CONVERTED TOTAL IMPLEMENTATION COSTS EFFECTS OF CUSTOMIZING SOFTWARE ON TOTAL IMPLEMENTATION COSTS 12.13

DESCRIPTION (PRESENT, PROPOSED)DESCRIPTION (PRESENT, PROPOSED) RELIABILITYRELIABILITY BACKUPBACKUP SERVICESSERVICES SYSTEM SPECIFICATIONSSYSTEM SPECIFICATIONS CRITERIACRITERIA DEMONSTRATION (PROTOTYPE)DEMONSTRATION (PROTOTYPE) SCHEDULE (BENCH MARKS)SCHEDULE (BENCH MARKS) PRICE (PENALTIES)PRICE (PENALTIES) SPECIFIC QUESTIONSSPECIFIC QUESTIONS PROCEDURES FOR RESPONSEPROCEDURES FOR RESPONSE* REQUEST FOR PROPOSAL (RFP REQUEST FOR PROPOSAL (RFP) Source: Senn, Information Technology in Business (1995) 12.14

END-USER DEVELOPMENT END-USERS DEVELOP INFORMATION SYSTEM WITH LITTLE HELP FROM TECHNICAL SPECIALISTS USING 4th GENERATION TOOLS * 12.15

END-USER DEVELOPMENT STRENGTHS: IMPROVED REQUIREMENTS DETERMINATIONIMPROVED REQUIREMENTS DETERMINATION INCREASED USER INVOLVEMENT & SATISFACTIONINCREASED USER INVOLVEMENT & SATISFACTION REDUCED APPLICATION BACKLOGREDUCED APPLICATION BACKLOG* 12.16

END-USER DEVELOPMENT WEAKNESSES: RELATIVELY INEFFICIENTRELATIVELY INEFFICIENT SLOW TRANSACTION PROCESSINGSLOW TRANSACTION PROCESSING MAY CARRY HIGH COSTMAY CARRY HIGH COST LARGE FILES CAN DEGRADE PERFORMANCELARGE FILES CAN DEGRADE PERFORMANCE NONPROCEDURAL APPROACH MAY HAMPER LOGIC & UPDATING REQUIREMENTSNONPROCEDURAL APPROACH MAY HAMPER LOGIC & UPDATING REQUIREMENTS* 12.17

MANAGING END-USER DEVELOPMENT INFORMATION CENTER: SPECIAL FACILITY WITHIN ORGANIZATIONSPECIAL FACILITY WITHIN ORGANIZATION PROVIDES TRAINING, SUPPORT FOR END-USER-COMPUTINGPROVIDES TRAINING, SUPPORT FOR END-USER-COMPUTING* 12.18

OUTSOURCING CONTRACTING: COMPUTER CENTER OPERATIONSCOMPUTER CENTER OPERATIONS TELECOMMUNICATIONS NETWORKSTELECOMMUNICATIONS NETWORKS APPLICATION DEVELOPMENTAPPLICATION DEVELOPMENT TO EXTERNAL VENDORS TO EXTERNAL VENDORS* 12.19

OUTSOURCING WHEN TO OUTSOURCE: IF FIRM WON’T DISTINGUISH ITSELF BY DEVELOPING APPLICATIONIF FIRM WON’T DISTINGUISH ITSELF BY DEVELOPING APPLICATION PREDICTABILITY OF UNINTERRUPTED SERVICE NOT IMPORTANTPREDICTABILITY OF UNINTERRUPTED SERVICE NOT IMPORTANT IF EXISTING SYSTEM IS LIMITED, INEFFECTIVE, INFERIORIF EXISTING SYSTEM IS LIMITED, INEFFECTIVE, INFERIOR* 12.20

SYSTEM BUILDING METHODOLOGIES STRUCTURED METHODOLOGIESSTRUCTURED METHODOLOGIES OBJECT- ORIENTED SOFTWARE DEVELOPMENTOBJECT- ORIENTED SOFTWARE DEVELOPMENT COMPUTER AIDED SOFTWARE ENGINEERING (CASE)COMPUTER AIDED SOFTWARE ENGINEERING (CASE) SOFTWARE REENGINEERINGSOFTWARE REENGINEERING* 12.21

STRUCTURED METHODOLOGIES TOP DOWN, STEP BY STEP, EACH STEP BUILDS ON PREVIOUS STRUCTURED ANALYSISSTRUCTURED ANALYSIS STRUCTURED DESIGNSTRUCTURED DESIGN STRUCTURED PROGRAMMINGSTRUCTURED PROGRAMMING FLOWCHARTSFLOWCHARTS* 12.22

STRUCTURED ANALYSIS DEFINES SYSTEM INPUTS, PROCESSES, OUTPUTSDEFINES SYSTEM INPUTS, PROCESSES, OUTPUTS PARTITIONS SYSTEM INTO SUBSYSTEMS OR MODULESPARTITIONS SYSTEM INTO SUBSYSTEMS OR MODULES LOGICAL, GRAPHICAL MODEL OF INFORMATION FLOWLOGICAL, GRAPHICAL MODEL OF INFORMATION FLOW DATA FLOW DIAGRAM: Graphical display of component processes, flow of dataDATA FLOW DIAGRAM: Graphical display of component processes, flow of data* 12.23

STRUCTURED ANALYSIS DATA DICTIONARY: Controlled definitions of descriptions of all data, such as variable names & types of dataDATA DICTIONARY: Controlled definitions of descriptions of all data, such as variable names & types of data PROCESS SPECIFICATIONS: Describes logic of processes at module levelPROCESS SPECIFICATIONS: Describes logic of processes at module level* 12.26

STRUCTURED DESIGN DESIGN RULES / TECHNIQUES TO DESIGN SYSTEM, TOP DOWN IN HIERARCHICAL FASHION DESIGN RULES / TECHNIQUES TO DESIGN SYSTEM, TOP DOWN IN HIERARCHICAL FASHION STRUCTURE CHARTSTRUCTURE CHART STRUCTURED PROGRAMMINGSTRUCTURED PROGRAMMING MODULEMODULE SEQUENCE CONSTRUCTSEQUENCE CONSTRUCT SELECTION CONSTRUCTSELECTION CONSTRUCT* 12.27

STRUCTURED PROGRAMMING: DISCIPLINE TO ORGANIZE, CODE PROGRAMSDISCIPLINE TO ORGANIZE, CODE PROGRAMS SIMPLIFIES CONTROL PATHSSIMPLIFIES CONTROL PATHS EASY TO UNDERSTAND, MODIFYEASY TO UNDERSTAND, MODIFY MODULE HAS ONE INPUT, ONE OUTPUTMODULE HAS ONE INPUT, ONE OUTPUT* 12.29

STRUCTURED PROGRAMMING: MODULE: Logical unit of program. performs specific task(s)MODULE: Logical unit of program. performs specific task(s) SEQUENCE CONSTRUCT: Sequential steps or actions in program logic; streamlines flowSEQUENCE CONSTRUCT: Sequential steps or actions in program logic; streamlines flow SELECTION CONSTRUCT: IF Condition R is True THEN Action C ELSE Action DSELECTION CONSTRUCT: IF Condition R is True THEN Action C ELSE Action D ITERATION CONSTRUCT: WHILE Condition is True DO Action EITERATION CONSTRUCT: WHILE Condition is True DO Action E* 12.30

OBJECT - ORIENTED SOFTWARE DEVELOPMENT DE-EMPHASIZES PROCEDURESDE-EMPHASIZES PROCEDURES SHIFTS FOCUS FROM MODELS & DATASHIFTS FOCUS FROM MODELS & DATA TO OBJECTS, WHICH COMBINE DATA & PROCEDURESTO OBJECTS, WHICH COMBINE DATA & PROCEDURES OBJECTS REUSABLEOBJECTS REUSABLE SYSTEM: Classes; objects; relationshipsSYSTEM: Classes; objects; relationships REDUCES DEVELOPMENT TIME & COST * 12.36

COMPUTER AIDED SOFTWARE ENGINEERING (CASE) AUTOMATION OF SOFTWARE METHODOLOGIESAUTOMATION OF SOFTWARE METHODOLOGIES PRODUCES CHARTS; DIAGRAMS; SCREEN & REPORT GENERATORS; DATA DICTIONARIES; PROGRESS REPORTS; ANALYSIS; CHECKING TOOLS; CODE; DOCUMENTATIONPRODUCES CHARTS; DIAGRAMS; SCREEN & REPORT GENERATORS; DATA DICTIONARIES; PROGRESS REPORTS; ANALYSIS; CHECKING TOOLS; CODE; DOCUMENTATION* CASE 12.37

COMPUTER AIDED SOFTWARE ENGINEERING (CASE) INCREASES PRODUCTIVITY & QUALITY: ENFORCES DEVELOPMENT DISCIPLINEENFORCES DEVELOPMENT DISCIPLINE IMPROVES COMMUNICATIONIMPROVES COMMUNICATION DESIGN REPOSITORY FOR OBJECTSDESIGN REPOSITORY FOR OBJECTS AUTOMATES TEDIOUS TASKSAUTOMATES TEDIOUS TASKS AUTOMATES TESTING & CONTROLAUTOMATES TESTING & CONTROL REQUIRES ORGANIZATIONAL DISCIPLINEREQUIRES ORGANIZATIONAL DISCIPLINE* CASE 12.38

SOFTWARE REENGINEERING SALVAGES & UPGRADES AGING SOFTWARESALVAGES & UPGRADES AGING SOFTWARE DELAYS EXPENSIVE REPLACEMENTDELAYS EXPENSIVE REPLACEMENT REVERSE ENGINEERING: CONVERTING EXISTING PROGRAMS, FILES, DATABASE FOR USE IN NEW APPLICATIONSREVERSE ENGINEERING: CONVERTING EXISTING PROGRAMS, FILES, DATABASE FOR USE IN NEW APPLICATIONS* 12.39

SOFTWARE REENGINEERING REVISE DESIGN & PROGRAM SPECIFICATIONSREVISE DESIGN & PROGRAM SPECIFICATIONS FORWARD ENGINEERING: USE REVISED MATERIALS TO GENERATE NEW, STRUCTURED CODE; STRUCTURED & MAINTAINABLE SYSTEMFORWARD ENGINEERING: USE REVISED MATERIALS TO GENERATE NEW, STRUCTURED CODE; STRUCTURED & MAINTAINABLE SYSTEM* 12.40