Software Development Life Cycle (SDLC) -Planning- Lecture1.

Slides:



Advertisements
Similar presentations
Chapter 2 Analyzing the Business Case.
Advertisements

Chapter 3 Managing the Information Systems Project
© 2005 by Prentice Hall Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
© 2008 by Prentice Hall 3-1 ITCS311 Systems Analysis and Design Dr. Taher Homeed Feb 2010 Department of Computer Science College of IT University of Bahrain.
The System Development Life Cycle
E-Business Models. Learning Objectives  Identify the key components of e-commerce business models.  Describe the major B2C business models.  Describe.
What is a major cause of dissatisfaction with the sales job? Lack of training.
Systems Analysis and Design 9th Edition
Systems Development Life Cycle:
Modern Systems Analysis and Design Third Edition
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Discovering Computers Fundamentals, 2011 Edition Living in a Digital World.
Chapter 3 Managing the Information Systems Project
1 Info 1409 Systems Analysis & Design Module Lecture 5 - Feasibility HND Year /9 De Montfort University.
Fundamentals of Information Systems, Second Edition
Systems Development Life Cycle
L ECTURE 3 – P LANNING - P ROJECT I NITIATION Opportunity Identification System Request Feasibility Analysis Project Management The Project Plan Software.
Feasibility Analysis Chapter 3
SATERN for Supervisors May Session Objectives At the end of the session, participants will be able to:  Describe the benefits of SATERN.  Log.
Key questions answered in this chapter:  What are the four stages to the evolution of B2B capabilities?  What are the three categories of B2B?  Describe.
© 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 5 Slide 1 Chapter 3 Managing the Information Systems Project.
Chapter 3 : Managing the Information Systems Project.
Systems Analysis and Design in a Changing World, 6th Edition
© 2005 by Prentice Hall 3-1 Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Fourth Edition.
CIS 321—IS Analysis & Design Chapter 3: The Analyst as a Project Manager.
Managing the development and purchase of information systems (Part 1)
Software Project Management Introduction to Project Management.
Copyright 2010, The World Bank Group. All Rights Reserved. Statistical Work Plan Development Section B 1.
Business Case Justification System Planning
BUSINESS PLUG-IN B15 Project Management.
Chapter 14 Information System Development
Participation activity: form of ownership research/discussion buying an existing business (1) sole proprietorship (2) partnership (3) corporation (4) dealerships.
Chapter 12: Systems Investigation and Analysis. Agenda  How to Develop a CBIS?  Systems Development Life Cycle (SDLC)  Prototyping  Join Application.
Project Management. Lecture 5-2 Introduction This lecture discusses the key components of project management, role of project manager and techniques to.
SATERN for Supervisors Updated: January Session Objectives At the end of the session, participants will be able to:  Describe the benefits of SATERN.
SacProNet An Overview of Project Management Techniques.
INFO 638Lecture #21 Software Project Management WBS Approaches.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
Project Management Lecture 2/9/2015. Fundamental “Rules” of Project Engineering 1.While there is never enough time to do it right, there is always enough.
Small Business Information Systems Professor Barry Floyd
Chapter 3 Managing the Information Systems Project
5. Planning Phase System Analysis And Design Program: BSCS II (Advent Semester – 2014) Lecturer: Rebecca Asiimwe
KUFA UNIVERSITY Department of Computer Science. Fundamentals of Software Engineering Presented By Neamah Hassan Presented By Neamah Hassan.
Project Scheduling Class 7.
1: Idea of BTH EXPERTS BTH EXPERTS is a web based application for students, researchers and lecturers of the university. They can use it to come together.
Slide 1 Software Construction Software Construction Lecture 3.
Lecture 3 Part 1 Managing the Information Systems Project.
Get up and running quickly with common tasks. When you choose the Main Menu from the nav bar, you can access your work areas, records, or other items.
CHAPTER ELEVEN Information System Development and Programming Languages Copyright © Cengage Learning. All rights reserved.
Information Systems Development. Outline  Information System  Systems Development Project  Systems Development Life Cycle.
The System Development Life Cycle
Systems Development Life Cycle
Chapter 3 Managing the Information Systems Project
BUSINESS PLUG-IN B15 Project Management.
TIM 58 Continuing Ch 2: Project Management
Fundamentals of Information Systems, Sixth Edition
Systems Analysis and Design in a Changing World, 4th Edition
Principles of Information Systems Eighth Edition
Principles of Marketing - UNBSJ
Business System Development
INTRODUCTION OF PROPERTY MARKETING
System analysis and design
AUTOMOTIVE CRM SOFTWARE CRM FOR AUTOMOBILE INDUSTRY
The System Development Life Cycle
Gantt Chart.
Modern Systems Analysis and Design Third Edition
Lesson 10: IT Project and Program Management
Systems Development Life Cycle
UNIT No- III- Leverging Information System ( Investing strategy )
Modern Systems Analysis and Design Third Edition
Presentation transcript:

Software Development Life Cycle (SDLC) -Planning- Lecture1

2 Software Development Life Cycle (SDLC) Planning Analysis Design Development Implementation

3 Planning  The planning phase is the fundamental process of understanding why an information system should be built and determining how the project team will go about building it. It has two steps: 1. Project initiation: the system’s business value to the organization is identified, how will it lower costs or increase revenues? Most ideas for new systems come in the form of a system request. ² The IS department works together with the person or department that generated the request (called the project sponsor) to conduct a feasibility analysis. ² The system request and feasibility analysis are presented to an information systems approval committee, which decides whether the project should be undertaken. 2. Once the project is approved, it enters project management. During project management, the project manager creates a workplan, staffs the project.

4 Planning 1- Project initiation System request Feasibility analysis 2-project management Workplane Planning 1- Project initiation System request Feasibility analysis 2-project management Workplane

5 System Request A system request is a document that describes the business reasons for building a system and the value that the system is expected to provide.

6 System Request

7 System Request – Example

8 Planning 1- Project initiation System request Feasibility analysis 2- project management Workplane Planning 1- Project initiation System request Feasibility analysis 2- project management Workplane

9 Workplan  Workplan: is a schedule that records and keeps track of all the tasks that need to be accomplished over the course of the project.  To create a workplan, the project manager first identifies the tasks that need to be accomplished and determines how long they will take. Then the tasks are organized within a workplan and presented graphically using Gantt chart.  A Gantt chart: is a horizontal bar chart that shows the same task information as the project workplan but in a graphical way.  First, tasks are listed as rows in the chart, and time is listed across the top or bottom in increments based on the needs of the projects  Horizontal bars are drawn to represent the duration of each task; the bar’s beginning and end mark exactly when the task will begin and end.

10 Workplan

11 Gannt chart

12 EXERCISES  Car dealers have realized how profitable it can be to sell automobiles using the Web. Pretend you work for a local car dealership that is part of a large chain such as CarMax. Create a system request you might use to develop a Web-based sales system. Remember to list special issues that are relevant to the project.

13  System Request  Sponsor: Sales Manager.  Business Need: Increase sales, increase market share, broaden geographic reach to potential customers.  Business Requirements: Web-based access to vehicle inventory including pictures. Search capabilities.  Ability to process requests for more information about a vehicle.  Business Value: Increase sales by 4%;  increase market share by 1.5%;  broaden reach to customers within 250 mile radius of dealership.  Special Issues: Must have someone who will keep Web-site content up to date constantly. Who will handle customer inquiries? How will this person be compensated? Will the compensation of our current sales force be affected? How will the sales force feel about this new system? Will having our own Web-based sales system affect our participation in the CarMax chain? 13