Lab/Sessional -CSE-374. SYSTEM DEVELOPMENT LIFE CYCLE.

Slides:



Advertisements
Similar presentations
System Development Life Cycle (SDLC)
Advertisements

Pg. 1 Systems Development Life Cycle (SDLC) Systems Analyst – change agent Systems Analyst – change agent  coordination, communication, planning, design.
Discovering Computers Fundamentals, 2011 Edition Living in a Digital World.
© Prentice Hall CHAPTER 9 Application Development by Information Systems Professionals.
1 California State University, Fullerton Chapter 13 Developing and Managing Information Systems.
Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill Technology Education Copyright © 2006 by The McGraw-Hill Companies,
Chapter 8 Prototyping and Rapid Application Development
SYSTEMS DEVELOPMENT Phases, Tools, and Techniques
System Development Life Cycle (SDLC)
Professor Michael J. Losacco CIS 1150 – Introduction to Computer Information Systems Systems Analysis and Design Chapter 12.
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
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.
Systems Analysis and Design (Level 3)
Introduction to Systems Analysis and Design
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
Introduction to Computer Technology
CORE 1: PROJECT MANAGEMENT Overview TECHNIQUES FOR MANAGING A PROJECT Communication Skills Active Listening Mirroring Paraphrasing Summarizing Clarifying.
Copyright © 2003 by Prentice Hall Computers: Tools for an Information Age Chapter 14 Systems Analysis and Design: The Big Picture.
Chapter 22 Systems Design, Implementation, and Operation Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 22-1.
Introduction to Systems Analysis and Design Trisha Cummings.
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.
Succeeding with Technology Systems Development An Overview of Systems Development Tools and Techniques for Systems Development Systems Investigation Systems.
Chapter 10: Systems Development
Chapter 10.
System Implementation. System Implementation and Seven major activities Coding Testing Installation Documentation Training Support Purpose To convert.
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
Pertemuan 5 Pengembangan Teknologi Informasi Matakuliah: H0402/PENGELOLAAN SISTEM KOMPUTER Tahun: 2005 Versi: 1/0.
Computers Are Your Future Eleventh Edition Chapter 13: Systems Analysis & Design Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall1.
Transaction Processing Systems and System Development Life Cycle
SYSTEMS ANALYSIS FORM 4 Included in this topic: Information Systems Systems Analysts System Life Cycle (incl. Case Study) Documentation.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
Introduction to Information Technology Turban, Rainer and Potter John Wiley & Sons, Inc. Copyright 2005.
© 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.
Systems Development AIMS 2710 R. Nakatsu. Overview Why do IT projects succeed and fail? Two philosophies of systems development –Systems Development Life.
Systems Development MBAA 609 R. Nakatsu. Overview of Today’s Lecture Why do IT projects succeed and fail? Two philosophies of systems development –Systems.
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.
Topics Covered Phase 1: Preliminary investigation Phase 1: Preliminary investigation Phase 2: Feasibility Study Phase 2: Feasibility Study Phase 3: System.
Copyright © 2015 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent of McGraw-Hill Education.
Systems Development AIMS 2710 R. Nakatsu. Overview Two philosophies of systems development –Systems Development Life Cycle (SDLC) –Prototyping Alternative.
Systems Development Life Cycle (SDLC)
GCSE ICT 3 rd Edition The system life cycle 18 The system life cycle is a series of stages that are worked through during the development of a new information.
Your Interactive Guide to the Digital World Discovering Computers 2012 Chapter 12 Exploring Information System Development.
MANAGEMENT INFORMATION SYSTEM
© 2017 by McGraw-Hill Education. This proprietary material solely for authorized instructor use. Not authorized for sale or distribution in any manner.
Information Systems Development
Information Systems Development
Information Systems Development
Fundamentals of Information Systems, Sixth Edition
Fundamentals of Information Systems, Sixth Edition
System Development Life Cycle (SDLC)
Developing Information Systems
Introduction to Computers
System Development Life Cycle (SDLC)
Information Systems Development
Chapter 13: Systems Analysis and Design
Systems Analysis and Design
System Development Life Cycle (SDLC)
CHAPTER 10 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT
Building Information Systems
McGraw-Hill Technology Education
Building Information Systems
Presentation transcript:

Lab/Sessional -CSE-374

SYSTEM DEVELOPMENT LIFE CYCLE

Phase 2: Define New Systems Requirements:- In phase 2 of the SDLC, systems analyst defines the requirement of the new system in detail and evaluates alternative solutions to problems. In phase 2 the analyst focus attention on what they –and the user –want the new system to do. But before designing the new system, the analysts have to define the requirements that it must satisfy. And the requirements must be defined very carefully; otherwise the new system might not end up doing what the users hope it will do.

Purpose of Phase 2 In the second phase of the SDLC, the analyst defines the requirements for the new system in enough detail so both computer professionals and users know exactly what the new system is going to do and how the system is going to do it. Needless to say, these requirements should solve the problems identified in the first phase. Requirements That Affect Software Requirements That Affect Hardware Evaluating Alternative Solutions Systems Requirements Report

Phase 3: Design the new system In phase 3 of the SDLC, systems analyst and designers do the actual design work, often using computer-aided systems engineering tools to speed up the design process. Purpose of phase 3 Phase 3 involves two main objectives: (1) to design the new system and (2) to establish a sound framework of controls within the new system should operate. Tools used are, among others, data flow diagrams, systems flowcharts, program flowcharts (used by programmers writing software programs), structured design and programming, and prototyping.

-Computer –added systems engineering (CASE) tools -Project dictionary organization. -Among other outputs, CASE tools can generate: -Designing New Systems Controls and Security Functions Concluding the Design phase At the end of pahse3, the analyst / design complete, organize, and assemble the new systems design documentation by using a combination of the tools and techniques discussed earlier in the chapter. The documentation should include: A complete overview of the new system as a whole

Phase 4: Develop the new System and Have Users Test it:- In the fourth phase of the SDLC, hardware and software are obtained, and the new system is tested. Purpose of phase 4 During Phase 4, four major activities occur: Acquire software Acquire hardware Train the users Test the new system

Phase 5: Implement the New system:- In the fifth phase of the SDLC, final operating documentation and procedures are created, files are converted, and the new system is used. Conversion to the new system may proceed in four ways: direct, parallel, phased, or pilot. Purpose of Phase 5 The implementation phase, which gets the new system up and running, involves creating the final operating documentation and procedures, converting files, and using the new system.

New system Old system New system Old system New system 1. Direct-implementation : All- at-once change 2.Parallel implementation: run at the same time. 3.Phased implementation: step-by-step change. 4. Pilot implementation: tried first in only one part of the company

Phase 6: Post implementation Evaluation and Maintenance (Support):- The last phase of the SDLC consists of keeping the system running through system audits and periodic evaluations. When the time and money spent on maintaining and updating a system reach a critical point, its time to start planning a new systems development life cycle. Purpose of Phase 6 After a new system has been in operation for several months and any necessary systems maintenance has been done, a formal evaluation –called a post implementation evaluation –of the new system takes place. This evaluation determines either that the new system is meeting its objectives or that certain things need to be done so that it will meet these objectives.

What Skills does the User Need? Why do Some Systems Development Projects Fail? The chances are great that a system development project will fail if a clearly define SDLC isn’t followed. Sometimes, however, even when companies go to the trouble to establish a formal and comprehensive SDLC, projects still fail to achieve their objectives. Why? Most failures can be traced to a breakdown in communications between the users and the data processing group and information-specialists. The reasons for failure often include: --Inadequate user involvement: --Continuation of a project that should have been canceled: --The failure of two more portions of the new system to fit together properly (called system integration):