Chapter 8 Information Systems Development & Acquisition

Slides:



Advertisements
Similar presentations
Fundamentals of Information Systems, Sixth Edition
Advertisements

Copyright © 2014 Pearson Education, Inc. 1 Managers from across organizations are involved in developing and acquiring information systems Chapter 5 -
Acquiring Information Systems and Applications
Principles and Learning Objectives
8-1 Chapter 8 Information Systems Development and Acquisition Robert Riordan, Carleton University.
Chapter 8 Information Systems Development and Acquisition
DEVELOPING ENTERPRISE APPLICATIONS
© Prentice Hall CHAPTER 9 Application Development by Information Systems Professionals.
Chapter 8 Information Systems Development and Acquisition
1 California State University, Fullerton Chapter 13 Developing and Managing Information Systems.
The Information Systems Development Process Chapter 9.
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Fundamentals of Information Systems, Second Edition
Information Systems Development and Acquisition Chapter 8 Jessup & Valacich Instructor: Ramesh Sankaranarayanan.
“Get Bill to Fix it up for you!”. MIS 300, Chapter 82 Basic Concepts Developing and maintaining information systems requires cooperative efforts of users.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Lead Black Slide. © 2001 Business & Information Systems 2/e2 Chapter 13 Developing and Managing Information 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
Information Systems Development : Overview. Information systems development practice Concept and role of a systems development methodology Approaches.
Acquiring Information Systems and Applications
Acquiring Information Systems and Applications
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 1 The Systems.
Continuation From Chapter From Chapter 1
Chapter 8: Systems Development Please turn your cell phone off.
1 Information Systems Development and Acquisition J. S. Chou Assistant Professor.
Systems Analysis and Design: The Big Picture
SDLC: System Development Life Cycle Dr. Bilal IS 582 Spring 2006.
Succeeding with Technology Systems Development An Overview of Systems Development Tools and Techniques for Systems Development Systems Investigation Systems.
System design technique  System Development Life Cycle  Prototyping  Rapid Application Development.
Information Systems Planning
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
Computers Are Your Future Eleventh Edition Chapter 13: Systems Analysis & Design Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall1.
8-1 Chapter 8 Information Systems Development & Acquisition.
Module 4: Systems Development Chapter 13: Investigation and Analysis.
Alternatives to Systems Development Chapter 11. Chapter Objectives Understand the factors and situations where building a system in-house is not feasible.
© 2001 Business & Information Systems 2/e1 Chapter 13 Developing and Managing Information Systems.
Chapter 14 Information System Development
Computers Are Your Future © 2006 Prentice Hall, Inc.
SDLC: System Development Life Cycle Dr. Dania Bilal IS 582 Spring 2007.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
Alter – Information Systems © 2002 Prentice Hall 1 The Process of Information System Planning.
IS Today (Valacich & Schneider) Copyright © 2010 Pearson Education, Inc. Published as Prentice Hall 10/17/ Chapter 10 Developing and Acquiring.
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
Computers Are Your Future © 2008 Prentice Hall, Inc.
CHAPTER 13 Acquiring Information Systems and Applications.
1 Fundamentals of Information Systems, Sixth Edition Fundamentals of Information Systems, Sixth Edition Chapter 8 Systems Development.
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Fundamentals of Information Systems, Fifth Edition Chapter 8 Systems Development.
IS Today (Valacich & Schneider) Copyright © 2010 Pearson Education, Inc. Published as Prentice Hall 1/11/ Chapter 9 Information Systems Development.
PART 2 Information Systems Development. LEARNING OBJECTIVES Systems Development Life Cycle Application Development Methodologies Project Management Systems.
Chapter 6 SYSTEMS DEVELOPMENT Phases, Tools, and Techniques.
CHAPTER 13 Acquiring Information Systems and Applications.
Fundamentals of Information Systems, Third Edition2 An Overview of Systems Development: Participants in Systems Development Development team –Responsible.
Fundamentals of Information Systems, Third Edition2 Principles and Learning Objectives Effective systems development requires a team effort of stakeholders,
The Information Systems Development Processes Chapter 9.
Information Systems Development
Information Systems Development
Fundamentals of Information Systems, Sixth Edition
SDLC: System Development Life Cycle
Information Systems Development
CHAPTER 10 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
Chapter 8 Information Systems Development & Acquisition
Systems Development An Overview of Systems Development
Presentation transcript:

Chapter 8 Information Systems Development & Acquisition

Chapter 8 Objectives Understand the process of IS management Understand the system development life cycle (SDLC) Understand alternative approaches to system development Understand in-house system development Understand external acquisition, outsourcing, and end-user development

The Need for Structured Systems Development Systems analysis and design – the process of designing, building, and maintaining information systems The individual who performs this task is called Systems analyst Organization wants to hire System analyst because they have both technical and managerial expertise.

The Need for Structured Systems Development Evolution of IS development From “art” to a “discipline”: In the early days of computing it was considered an art that a very few people could master Standardized development methods: The techniques used to build an IS varies greatly from individual to individual. It was very difficult to integrate and maintain. To address this problem, info. Sys. professionals decided to use a disciplined approach of introducing common methods, techniques, and tools for building information systems Software engineering: This evolution led to the use of the term software engineering to define what system analyst & programmer do.

The Need for Structured Systems Development Options for Obtaining Information Systems Build your own Buy a prepackaged system from a software development company or consulting firm. Example: Payroll system. Outsource development to a 3rd party: outside organization custom build a system to an organization’s specifications. Good option when an organization does not have adequate resources or expertise. End user development: Individual users and departments build their own custom systems to support their individuals. Example MS. Excel.

The Need for Structured Systems Development

The Need for Structured Systems Development System Construction Process Identify a large IT problem to solve Break the large problem into several smaller, more manageable pieces Translate each “piece” (small problem) into computer programs Piece together each program into an overall comprehensive IS that solves the problem

The Need for Structured Systems Development The Role of Users in the Systems Development Process It is important for all members of the organization to understand what is meant by system development and what activities occur. Effective partnership: A close and mutually respectful working relationship between analysts and users is a key to project success.

Steps in the Systems Development Process

Steps in the Systems Development Process Systems Development Life Cycle (SDLC) - describes the life of an information system from conception to retirement. System identification, selection, and planning System analysis System design System implementation System maintenance

Steps in the Systems Development Process Phase 1: System Identification, Selection, and Planning Undertake only those projects critical to mission, goals, and objectives Select a development project from all possible projects that could be performed Different evaluation criteria used to rank potential projects An organization can only work on only a limited number of projects at a given time due to limited resources so care must be taken when selecting the projects to build. After all possible projects are identified, those deemed most likely to yield significant organizational benefits, given available resources, are selected for subsequent development. Some possible evaluation criteria for ranking potential projects are: strategic alignment, potential benefits, potential costs and resource availability, project size and duration, and technical difficulty.

Steps in the Systems Development Process Phase 1: System Identification, Selection, and Planning Evaluation criteria Strategic alignment: The extent to which the project is viewed as helping the organization achieve its strategic objectives an d long-term goal. Potential benefits: The extent to which the project is viewed as improving profits, customer service, and the duration of the benefits Potential costs and resource availability: The number and types of resources the project requires and their availability Project size / duration: The number of individuals and the length of time needed to complete the project Technical difficulty / risks: The level of technical difficulty involved to complete the project within a given time and resources An organization can only work on only a limited number of projects at a given time due to limited resources so care must be taken when selecting the projects to build. After all possible projects are identified, those deemed most likely to yield significant organizational benefits, given available resources, are selected for subsequent development. Some possible evaluation criteria for ranking potential projects are: strategic alignment, potential benefits, potential costs and resource availability, project size and duration, and technical difficulty.

Steps in the Systems Development Process Phase 2: System Analysis Collecting System Requirements: Requirement collection is process of gathering and organizing information from users, managers, business processes, an documents to understand how a proposed system should work System analysts use a variety of techniques to collect system requirements Interviews: analysts interview people Questionnaires: analysts design and administer surveys. Observations: analysts observe workers at selected times Document analysis: analysts study business documents Critical Success Factors (CSF): analysts ask each person to define her own personal CSFs. Joint Application Design (JAD): Special type of a group meeting where all users and analysts meet at the same time An organization can only work on only a limited number of projects at a given time due to limited resources so care must be taken when selecting the projects to build. After all possible projects are identified, those deemed most likely to yield significant organizational benefits, given available resources, are selected for subsequent development. Some possible evaluation criteria for ranking potential projects are: strategic alignment, potential benefits, potential costs and resource availability, project size and duration, and technical difficulty.

Steps in the Systems Development Process Phase 2: System Analysis Modeling Organizational Data: To construct an information system, systems analysts must understand what data the information system needs in order to accomplish the intended tasks. To do this they use data modeling tools to collect and describe data to users. Entity Relationship Diagram (ERD) Modeling Organizational Processes and Logic Data flows Processing logic An organization can only work on only a limited number of projects at a given time due to limited resources so care must be taken when selecting the projects to build. After all possible projects are identified, those deemed most likely to yield significant organizational benefits, given available resources, are selected for subsequent development. Some possible evaluation criteria for ranking potential projects are: strategic alignment, potential benefits, potential costs and resource availability, project size and duration, and technical difficulty.

A sample ERD for students

Steps in the Systems Development Process Phase 3: System Design Designing forms and reports Designing interfaces and dialogues Designing databases and files Designing processing and logic An organization can only work on only a limited number of projects at a given time due to limited resources so care must be taken when selecting the projects to build. After all possible projects are identified, those deemed most likely to yield significant organizational benefits, given available resources, are selected for subsequent development. Some possible evaluation criteria for ranking potential projects are: strategic alignment, potential benefits, potential costs and resource availability, project size and duration, and technical difficulty.

Steps in the Systems Development Process Phase 4: System Implementation Software programming Software testing Developmental: Programmers test the correctness of individual modules and the integration of multiple modules Alpha: Software tester tests whether it meets design specifications Beta: Actual system users test the capability of the system in the user environment with actual data An organization can only work on only a limited number of projects at a given time due to limited resources so care must be taken when selecting the projects to build. After all possible projects are identified, those deemed most likely to yield significant organizational benefits, given available resources, are selected for subsequent development. Some possible evaluation criteria for ranking potential projects are: strategic alignment, potential benefits, potential costs and resource availability, project size and duration, and technical difficulty.

Steps in the Systems Development Process Phase 4: System Implementation System conversion Parallel Direct Phased Pilot System documentation, training, and support User and reference guides Training and tutorials Installation procedures and troubleshooting guides An organization can only work on only a limited number of projects at a given time due to limited resources so care must be taken when selecting the projects to build. After all possible projects are identified, those deemed most likely to yield significant organizational benefits, given available resources, are selected for subsequent development. Some possible evaluation criteria for ranking potential projects are: strategic alignment, potential benefits, potential costs and resource availability, project size and duration, and technical difficulty.

Steps in the Systems Development Process Phase 5: System Maintenance Maintenance process steps: Obtain maintenance request Transform requests into changes Design changes Implement changes An organization can only work on only a limited number of projects at a given time due to limited resources so care must be taken when selecting the projects to build. After all possible projects are identified, those deemed most likely to yield significant organizational benefits, given available resources, are selected for subsequent development. Some possible evaluation criteria for ranking potential projects are: strategic alignment, potential benefits, potential costs and resource availability, project size and duration, and technical difficulty.

Steps in the Systems Development Process Phase 5: System Maintenance Maintenance types: Corrective maintenance Adaptive maintenance Perfective maintenance Preventive maintenance An organization can only work on only a limited number of projects at a given time due to limited resources so care must be taken when selecting the projects to build. After all possible projects are identified, those deemed most likely to yield significant organizational benefits, given available resources, are selected for subsequent development. Some possible evaluation criteria for ranking potential projects are: strategic alignment, potential benefits, potential costs and resource availability, project size and duration, and technical difficulty.

Other Approaches to Designing and Building Systems Prototyping Rapid Application Development (RAD) Object-Oriented Analysis & Design (OOA&D) An organization can only work on only a limited number of projects at a given time due to limited resources so care must be taken when selecting the projects to build. After all possible projects are identified, those deemed most likely to yield significant organizational benefits, given available resources, are selected for subsequent development. Some possible evaluation criteria for ranking potential projects are: strategic alignment, potential benefits, potential costs and resource availability, project size and duration, and technical difficulty.

Prototyping

Need for Alternatives to Building Systems Yourself Limited IS staff IS staff has limited skill set IS staff is overworked Problems with performance of IS staff An organization can only work on only a limited number of projects at a given time due to limited resources so care must be taken when selecting the projects to build. After all possible projects are identified, those deemed most likely to yield significant organizational benefits, given available resources, are selected for subsequent development. Some possible evaluation criteria for ranking potential projects are: strategic alignment, potential benefits, potential costs and resource availability, project size and duration, and technical difficulty.

Common Alternatives to In-house Systems Development External acquisition System identification, selection and planning Systems analysis Development of a request for proposal (RFP) Proposal evaluation Vendor selection An organization can only work on only a limited number of projects at a given time due to limited resources so care must be taken when selecting the projects to build. After all possible projects are identified, those deemed most likely to yield significant organizational benefits, given available resources, are selected for subsequent development. Some possible evaluation criteria for ranking potential projects are: strategic alignment, potential benefits, potential costs and resource availability, project size and duration, and technical difficulty.

Common Alternatives to In-house Systems Development Outsourcing – the practice of turning over responsibility of some to all of an organization’s information systems development and operations to an outside firm An organization can only work on only a limited number of projects at a given time due to limited resources so care must be taken when selecting the projects to build. After all possible projects are identified, those deemed most likely to yield significant organizational benefits, given available resources, are selected for subsequent development. Some possible evaluation criteria for ranking potential projects are: strategic alignment, potential benefits, potential costs and resource availability, project size and duration, and technical difficulty.

Common Alternatives to In-house Systems Development Why Outsource? Cost and quality concerns Problems in IS performance Supplier pressures Simplifying, downsizing, and reengineering Financial factors Organizational culture Internal irritants An organization can only work on only a limited number of projects at a given time due to limited resources so care must be taken when selecting the projects to build. After all possible projects are identified, those deemed most likely to yield significant organizational benefits, given available resources, are selected for subsequent development. Some possible evaluation criteria for ranking potential projects are: strategic alignment, potential benefits, potential costs and resource availability, project size and duration, and technical difficulty.

Common Alternatives to In-house Systems Development Managing the IS outsourcing relationship Strong CIO oversight Measurement of milestones, costs, and benefits Customer relationship management Not all outsourcing relationships are the same Basic relationship Preferred relationship Strategic relationship An organization can only work on only a limited number of projects at a given time due to limited resources so care must be taken when selecting the projects to build. After all possible projects are identified, those deemed most likely to yield significant organizational benefits, given available resources, are selected for subsequent development. Some possible evaluation criteria for ranking potential projects are: strategic alignment, potential benefits, potential costs and resource availability, project size and duration, and technical difficulty.

Common Alternatives to In-house Systems Development End-user development Benefits of end-user development Encouraging end-user development End-user development pitfalls An organization can only work on only a limited number of projects at a given time due to limited resources so care must be taken when selecting the projects to build. After all possible projects are identified, those deemed most likely to yield significant organizational benefits, given available resources, are selected for subsequent development. Some possible evaluation criteria for ranking potential projects are: strategic alignment, potential benefits, potential costs and resource availability, project size and duration, and technical difficulty.