1 California State University, Fullerton Chapter 13 Developing and Managing Information Systems.

Slides:



Advertisements
Similar presentations
Lecture 3 Planning and Development Methodologies.
Advertisements

Pg. 1 Systems Development Life Cycle (SDLC) Systems Analyst – change agent Systems Analyst – change agent  coordination, communication, planning, design.
Chapter 8 Information Systems Development & Acquisition
1 IS 4420 Database Fundamentals Chapter 2: Database Development Process Leon Chen.
©2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart 18-1 Accounting Information Systems 9 th Edition Marshall.
Systems Development Life Cycle
7.2 System Development Life Cycle (SDLC)
Lead Black Slide. © 2001 Business & Information Systems 2/e2 Chapter 13 Developing and Managing Information Systems.
9 1 Chapter 9 Database Design Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
SDLC. Information Systems Development Terms SDLC - the development method used by most organizations today for large, complex systems Systems Analysts.
System Implementations American corporations spend about $300 Billion a year on software implementation/upgrade projects.
Information Systems Development : Overview. Information systems development practice Concept and role of a systems development methodology Approaches.
Building Information Systems lesson 26 This lesson includes the following sections: The Systems Development Life Cycle Phase 1: Needs Analysis Phase.
Welcome to CMPE003 Personal Computer Concepts: Hardware and Software Winter 2003 UC Santa Cruz Instructor: Guy Cox.
Acquiring Information Systems and Applications
Chapter 22 Systems Design, Implementation, and Operation Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 22-1.
Systems Analysis and Design: The Big Picture
1313 CHAPTER SYSTEMS ANALYSIS AND DESIGN. © 2005 The McGraw-Hill Companies, Inc. All Rights Reserved Competencies Describe the six phases of the.
Lecture Outline 11 The Development of Information Systems Chapter 8 page 390+
Chapter 2: Approaches to System Development
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.
Managing the development and purchase of information systems (Part 1)
8-1 Chapter 8 Information Systems Development & Acquisition.
Information Systems Analysis and Design
© 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.
Chapter 10 Information Systems Analysis and Design
Acquiring Information Systems and Applications
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
Systems Analysis and Design
Computers Are Your Future © 2008 Prentice Hall, Inc.
Computers Are Your Future Tenth Edition Chapter 13: Systems Analysis & Design Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall1.
System Implementation. © 2011 Pearson Education, Inc. Publishing as Prentice Hall 2 Chapter 13 FIGURE 13-1 Systems development life cycle with the implementation.
CISB113 Fundamentals of Information Systems IS Development.
第 11 組 MIS 報告. Phases of any information system ~ recognition of a business problem or opportunity ~ recognition of a business problem or opportunity.
Systems Development Life Cycle (SDLC)
ANALISA & PERANCANGAN SISTEM Disusun Oleh : Dr. Lily Wulandari Program Pasca Sarjana Magister Sistem Informasi Universitas Gunadarma.
Your Interactive Guide to the Digital World Discovering Computers 2012 Chapter 12 Exploring Information System Development.
Slide 10-1 Chapter 10 Systems Development Procedures Introduction to Information Systems Judith C. Simon.
The System Development Life Cycle
Systems Development Life Cycle
Information Systems Development
Systems Analysis and Design
Information Systems Development
Information Systems Development
Fundamentals of Information Systems, Sixth Edition
James A. Senn’s Information Technology, 3rd Edition
System Development Life Cycle (SDLC)
Developing Information Systems
System Development Life Cycle (SDLC)
Introduction to Computers
FORMAL SYSTEM DEVELOPMENT METHODOLOGIES
System Development Life Cycle (SDLC)
The Development of Information Systems Chapter 8 page 348+
Information Systems Development
Managing the development of information systems (Part 1)
The System Development Life Cycle
Systems Design, Implementation, and Operation
Chapter 13: Systems Analysis and Design
System Development Life Cycle (SDLC)
CHAPTER 10 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT
INFORMATION SYSTEMS PLAN
Building Information Systems
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
(System Development Life Cycle)
Systems Development Life Cycle
Building Information Systems
Presentation transcript:

1 California State University, Fullerton Chapter 13 Developing and Managing Information Systems

2 California State University, Fullerton People in Information Systems Development Systems analysts follow a step-by-step process to develop information systems. Information systems are usually developed by a group of people who form a project team.

3 California State University, Fullerton The Systems Development Process The system development process, which also called the System Development Life Cycle (SDLC) is divided into five main phases: 1.System planning 2.System analysis 3.System design 4.System implementation 5.System maintenance

4 California State University, Fullerton System Planning System planning is the phase in which the systems analyst decides whether a new information system should be developed. The systems analyst conducts a feasibility analysis. Technological feasibility Organizational feasibility A cost/benefit analysis (economic feasibility) is prepared.

5 California State University, Fullerton System Analysis During system analysis, the analyst studies the existing and determines what the new system must do. Studies the existing system Defines user requirements Develop a conceptual or general design Evaluate hardware and software alternatives Packaged software Custom software

6 California State University, Fullerton System Design During system design, the analyst specifies the detail of how the new system will function. Describing design details including layouts of screens, forms and reports; specifications for all hardware; descriptions of all programs.

7 California State University, Fullerton System Implementation During system implementation, the systems analyst acquires (purchase/build) the components of the system – such as: Hardware Acquisition Software acquisition or programming Testing Site preparation and installation Training System conversion

8 California State University, Fullerton System Implementation (cont’d.) Four methods of converting to the new system: Plunge – old system is turned off, new one is turned on. Phased – new system is divided into parts with one part phased in at a time. Pilot – new system is installed in a part of the organization. Parallel – old and new systems are used simultaneously for a period of time.

9 California State University, Fullerton System Maintenance System maintenance involves modifying the system during its life to meet new requirements. Maintenance is required for three reasons: 1.Errors found that were not detected in testing 2.A new function is to be added to the system 3.The requirements have changed

10 California State University, Fullerton System Development Tools Data Flow Diagrams (DFD) Entity-Relationship Diagram (ERD) Computer Aided Software Engineering (CASE) tools

11 California State University, Fullerton Data Flow Diagrams A tool many analysts use to show the flow of data in an information system. The diagram uses symbols with different shapes to indicate how data flows in the system. They are: Process – a rounded corner rectangle External entity – a rectangle Data store – an open rectangle Data flow – an arrow

12 California State University, Fullerton Entity-Relationship Diagram An entity is something about which data is stored in a database. A relationship is an association between entities. An entity-relationship diagram shows the entities and relationships between entities in a database.

13 California State University, Fullerton CASE Tools CASE – Computer Aided Software Engineering – tools are computer based tools such as those for system development.

14 California State University, Fullerton Prototyping Prototyping involves the systems analyst obtaining informal and incomplete requirements for the system and developing a prototype, which is a simplified version of the system that acts like the real system but may not perform all the required functions of the system.

15 California State University, Fullerton Individual Information System Development The five steps of the SDLC serve as a general guide. Individual information system planning starts when the user recognizes a problem or a need. Must consider whether personal technical skills are adequate.

16 California State University, Fullerton Electronic Commerce System Development While similar to the steps in the SDLC, there are notable differences: In e-commerce systems, the main user is the customer.

17 California State University, Fullerton Electronic Commerce System Development (cont’d.) Design of an e-commerce system involves two main parts: Front end – is what the customer sees when they use the system. Back end – provides the capabilities necessary for completing the customer’s order including inventory control and product distribution.

18 California State University, Fullerton Electronic Commerce System Development (cont’d.) Publishing the system is the process of setting up the system on a server and making it available through the Internet.

19 California State University, Fullerton Business Process Reengineering Business Process Reengineering (BPR) involves completely redesigning the business processes, which are groups of activities or tasks that accomplish things for a business. BPR is not gradual improvement, but rather radical redesign of business processes.