 System Development Life Cycle System Development Life Cycle  SDLC Phases SDLC Phases Phase 1: Preliminary Investigation Phase 2: Feasibility Study.

Slides:



Advertisements
Similar presentations
Systems Analysis and Design Presented by Thakur Rai.
Advertisements

Systems Implementation and Operation
Software Quality Assurance Plan
Info1409 De Montfort University Lecture 3 The Systems Development Life Cycle Systems Analysis & Design Academic Year 2008/9.
The System Development Life Cycle
Software Quality Assurance Inspection by Ross Simmerman Software developers follow a method of software quality assurance and try to eliminate bugs prior.
Designing new systems or modifying existing ones should always be aimed at helping an organization achieve its goals State the purpose of systems design.
Systems Analysis and Design
McGraw-Hill Technology Education © 2006 by the McGraw-Hill Companies, Inc. All rights reserved CHAPTER SYSTEMS ANALYSIS AND DESIGN McGraw-Hill/Irwin.
Lecture 13 Revision IMS Systems Analysis and Design.
Computers: Tools for an Information Age
Systems Development Life Cycle
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)
System Implementations American corporations spend about $300 Billion a year on software implementation/upgrade projects.
The Agile vs. Waterfall Methodologies Systems Development:  the activity of creating new or modifying / enhancing existing business systems.  Objectives.
Welcome to CMPE003 Personal Computer Concepts: Hardware and Software Winter 2003 UC Santa Cruz Instructor: Guy Cox.
Chapter 17 Acquiring and Implementing Accounting Information Systems
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.
SYSTEM ANALYSIS AND DESIGN
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.
CCSB223/SAD/CHAPTER141 Chapter 14 Implementing and Maintaining the System.
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
Managing the development and purchase of information systems (Part 1)
Chapter 13: Developing and Implementing Effective Accounting Information Systems
Chapter 14 Information System Development
Information Systems Technology Ross Malaga "Part III - Building and Managing Information Systems" III 11 Copyright © 2005 Prentice Hall, Inc MANAGING.
Fundamentals of Information Systems, Third Edition1 Systems Design Answers the question “How will the information system do what it must do to solve a.
Advanced Higher Computing SOFTWARE DEVELOPMENT PROCESS.
Systems Analysis and Design
Computers Are Your Future © 2008 Prentice Hall, Inc.
Systems Life Cycle A2 Module Heathcote Ch.38.
Topics Covered Phase 1: Preliminary investigation Phase 1: Preliminary investigation Phase 2: Feasibility Study Phase 2: Feasibility Study Phase 3: System.
GCSE ICT Systems Analysis. Systems analysis Systems analysis is the application of analytical processes to the planning, design and implementation of.
A BRIEF LOOK AT THE COMPONENTS THAT MAKE UP THE SYSTEM LIFE CYCLE.
IS2210: Systems Analysis and Systems Design and Change Twitter:
A brief look at the components that make up the system life cycle.
10-1 McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved.
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.
The System Development Life Cycle
Systems Development Life Cycle
Information Systems Development
Systems Analysis and Design
Information Systems Development
Information Systems Development
System.
Principles of Information Systems Eighth Edition
Fundamentals of Information Systems, Sixth Edition
Systems Analysis and Design
System Development Life Cycle (SDLC)
System Development Life Cycle (SDLC)
System Development Life Cycle (SDLC)
Information Systems Development
The System Development Life Cycle
CLINICAL INFORMATION SYSTEM
Chapter 13: Systems Analysis and Design
Systems Analysis and Design
System Development Life Cycle (SDLC)
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
Chapter 13: Systems Analysis and Design
Systems Development Life Cycle
UNIT No- III- Leverging Information System ( Investing strategy )
System Analysis and Design:
Presentation transcript:

 System Development Life Cycle System Development Life Cycle  SDLC Phases SDLC Phases Phase 1: Preliminary Investigation Phase 2: Feasibility Study Phase 3: System Analysis Phase 4: System Design Phase 5: System Development Phase 6: System Testing Phase 7: System Implementation and Evaluation Phase 8: Operations & Maintenance  Deliverables of the SDLC Deliverables of the SDLC

 System Development Life Cycle(SDLC) is a well defined process by which a System is conceived, developed and implemented. BACK

Preliminary Investigation System Operation & Maintenance System Analysis System Implementation and Evaluation System Design System Development System Testing Feasibility Study BACK

 Determine if a new system is needed  Three primary tasks: ◦ Define the problem  By observation and interview, determine what information is needed by whom, when, where and why ◦ Suggest alternative solutions ◦ Prepare a short report BACK

 Evaluate alternatives based upon: ◦ Economic feasibility – Cost benefit analysis is performed to determine the benefits and servings that are expected. ◦ Technical feasibility – It decides whether the technical resources are sufficient for the proposed system or not. ◦ Operational feasibility – It is determined whether the system will operate in the way that users want or not. BACK

 This Phase includes studying of existing system in details and collecting data in order to find out the requirements of the user. ◦ The system analyst must consult a variety of persons to understand the whole details,processes involved in it and problems faced by staff and should identify the reasons for the problems that have occurred and the preventive measures to avoid them  In addition to observation and interviews, examine: ◦ Formal lines of authority (org chart) ◦ Standard operating procedures ◦ How information flows ◦ Reasons for any inefficiencies

 Checklists - list of questions  Top-down analysis - start with top level components, break down into smaller parts through each successive level  Grid charts - to show relationship between inputs and outputs  System flowcharts - charts flow of input data, processing, and output which show system elements and interactions

 Complete description of current system and its problems  Requirements for for new system including: ◦ Subject ◦ Scope ◦ Objectives ◦ Benefits  Possible development schedule BACK

 In System Design phase,the primary objective is to identify user requirements and to build a system that satisfies these requirements, system specialists often refer to this stage as logical design and the process of developing program software,which is referred to as Physical Design.  Uses specifications from the systems analysis to design alternative systems BACK

 Build the system to the design specifications. ◦ Develop the software  Purchase off-the-shelf software OR  Write custom software ◦ Acquire the hardware BACK

◦ The main purpose of this phase is to test the new system and find the errors and correct them.  Module (unit) test - tests each part of system  Integration testing - tests system as one unit ◦ The main objective of system testing is to make sure that the system during operation will perform as per the specification laid down initially at the time of system analysis. ◦ To ensure that during the operation, incorrect inputted data and processing will be detected. ◦ The system is tested with special test data and the results are examined for the validity so that the analyst can ascertain that the system can work in the specified environment. BACK

 Convert from old system to new system  Train users  Compile final documentation  Once the system is implemented,then evaluate the new system

 Direct/plunge/crash approach – entire new system completely replaces entire old system, in one step  Parallel approach - both systems are operated side by side until the new system proves itself  Pilot approach - launched new system for only one group within the business -- once new system is operating smoothly, implementation goes company-wide  Phased/incremental approach - individual parts of new system are gradually phased-in over time, using either crash or parallel for each piece.

 Evaluation of the system is performed to identify its strength and weakness.the actual evaluation can occur alomg any of the following dimensions: a) Operational Evaluation : Assesment of the manner in which the sytsem functions including response time,overall reliability and the level of utilization b) Organisational impact:Identification and measurement of benefits to the organisation in such areas as financial concerns,operational efficiency and competitive impact c) User Manager Assesment : Judge the Attitudes of senior and user manager within the organisation as well as end users. d) Development Performance : Evaluation of cost,time and effort taken for the overall project.

 User Training ◦ Ease into system, make them comfortable, and gain their support ◦ Most commonly overlooked ◦ Can be commenced before equipment delivery ◦ Outside trainers sometimes used BACK

 Maintenance is actually improvement and updation of software in response to the changes in the organisation.  Types of changes: ◦ Physical repair of the system ◦ Correction of new bugs found (corrective) ◦ System adjustments to environmental changes ◦ Adjustments for users’ changing needs (adaptive) ◦ Changes to user better techniques when they become available (perfective)

 Evaluation Methods ◦ Systems audit - performance compared to original specifications ◦ Periodic evaluation - “checkups” from time to time, modifications if necessary BACK

Begin building new system System converted Users trained Coded and Tested System Design Specifications Preliminary Investigation System Analysis System Design System Implementation System Development System Maintenance Approved Feasibility Study Operational System Documentation completed Abort Project Goto next phase Goto Previous phase Problem Specifications BACK