Business Driven Technology Unit 5

Slides:



Advertisements
Similar presentations
Unified process(UP) UP is an OO system development methodology offered by Rational(Rational Rose) s/w, now a part of IBM Developed by Booach,Rambaugh,Jacobson--
Advertisements

Business Driven Technology Unit 5 Transforming Organizations Copyright © 2015 McGraw-Hill Education. All rights reserved. No reproduction or distribution.
National Association for Regulatory Administration September 13, 2011 IT’s NOT Like Building a House Mark Parker (800)
Enterprise Resource Planning
CS487 Software Engineering Omar Aldawud
THE SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC)
McGraw-Hill/Irwin © 2006 The McGraw-Hill Companies, Inc. All rights reserved BUSINESS DRIVEN TECHNOLOGY Chapter Nineteen: Building Software to Support.
BUSINESS DRIVEN TECHNOLOGY
CHAPTER TWO Object Oriented System Analysis and Design 1.
Transforming Organizations
Ch 3 System Development Environment
Slide 1 INTRODUCTION Chapter 1. Slide 2 Key Ideas The primarily goal of a system is to create value for the organization. Many failed systems were abandoned.
1 Prescriptive Process Models. 2 Prescriptive Models Prescriptive process models advocate an orderly approach to software engineering Prescriptive process.
Sharif University of Technology Session # 3.  Contents  Systems Analysis and Design Sharif University of Technology MIS (Management Information System),
COMPONENT-BASED DEVELOPMENT
CS 325: Software Engineering January 15, 2015 Software Process & Methodology Prototyping Process Model Evolutionary Process Model Spiral Process Model.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Chapter Extension 19 Alternative Development Techniques © 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke.
Slide 1 Systems Analysis & Design CS183 Spring Semester 2008 Dr. Jonathan Y. Clark Course Website:
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Introduction to Requirements (Chapters 1-3 of the requirements text) CSSE 371, Software Requirements and Specification Don Bagert, Rose-Hulman Institute.
Slide 1 INTRODUCTION Chapter 1. Slide 2 Key Ideas Many failed systems were abandoned because analysts tried to build wonderful systems without understanding.
Unit Five – Transforming Organizations
CHAPTER 9: LEARNING OUTCOMES
CHAPTER 17 Building Software to Support an Agile Organization
Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
CHAPTER 19 Building Software.
Chapter 1 The Systems Development Environment
Chapter 1 The Systems Development Environment
The Systems Development Environment. Learning Objectives Define information systems analysis and design. Describe the different types of information systems.
CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 1: Introduction to Systems Analysis and Design Alan.
SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT: CORPORATE RESPONSIBILITY
Transforming Organizations
Chapter 1 The Systems Development Environment
CHAPTER OVERVIEW SECTION 9.1 – Developing Enterprise Applications
Business Driven Technology Unit 5 Transforming Organizations McGraw-Hill/Irwin Copyright © 2013 by The McGraw-Hill Companies, Inc. All rights reserved.
Chapter 11 McGraw-Hill/Irwin Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved.
Chapter 1: Introduction to Systems Analysis and Design
Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Agile Methodologies: Comparative Study and Future Direction 林佳蓁 資工 4B.
Seminars in IT for Businesses Summary 1 By Dr Sadaf Sajjad.
Software development process ธนวัฒน์ แซ่ เอียบ. The development process Process –set of rules which define how a development project. Methodology and.
Information Systems Development
Systems Development and
Business Driven Technology Unit 5 Transforming Organizations Copyright © 2015 McGraw-Hill Education. All rights reserved. No reproduction or distribution.
Business Driven Technology Unit 5 Transforming Organizations Copyright © 2015 McGraw-Hill Education. All rights reserved. No reproduction or distribution.
McGraw-Hill/Irwin ©2009 The McGraw-Hill Companies, All Rights Reserved Business Driven Information Systems 2e CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 1: Introduction to Systems Analysis and Design Alan.
Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
The principles of an object oriented software development process Week 04 1.
The Systems Development Environment Systems Analysis and Design II.
CSPC 464 Fall 2014 Son Nguyen. 1. The Process of Software Architecting, Peter Eeles, Peter Cripss 2. Software Architecture for Developers, Simon Brown.
Teaching slides Chapter 2. Chapter 2 Software Engineering Methodologies Introduction Why a methodology? Agile methodologies Waterfall model Rational Unified.
11 ADM2372 Management Information Systems (MIS) Chapter 10 – Part I Systems Development Chapter 10 – Part I Systems Development.
McGraw-Hill/Irwin ©2009 The McGraw-Hill Companies, All Rights Reserved Business Driven Information Systems 2e CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT.
Software Development. The Software Life Cycle Encompasses all activities from initial analysis until obsolescence Analysis of problem or request Analysis.
CHAPTER 9: LEARNING OUTCOMES
Software Engineering cosc 4359 Spring 2017.
Software Development Methodologies
Chapter 4 & Chapter 5 Important Concepts
Software Development.
CHAPTER OVERVIEW SECTION 9.1 – Developing Enterprise Applications
Transforming Organizations
Software Process Models
Introduction to Software Engineering
Object Oriented Analysis and Design
Software Engineering: A Practitioner’s Approach, 6/e Chapter 3 Prescriptive Process Models copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Chapter 1: Introduction to Systems Analysis and Design
Systems Analysis and Design With UML 2
Presentation transcript:

Business Driven Technology Unit 5 Transforming Organizations Copyright © 2015 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent of McGraw-Hill Education.

Unit Five Chapter Seventeen – Developing Software to Streamline Operations Chapter Eighteen – Methodologies for Supporting Agile Organizations Chapter Nineteen - Managing Organizational Projects Chapter Twenty – Developing a 21st Century Organization

Methodologies for Supporting Agile Organizations Chapter 18 Methodologies for Supporting Agile Organizations

LEARNING OUTCOMES Summarize the different software development methodologies

SOFTWARE DEVELOPMENT METHODOLOGIES There are a number of different software development methodologies including Waterfall Agile Rapid application development (RAD) Extreme programming Rational unified process (RUP) Scrum

Waterfall Methodology Waterfall methodology – A sequence of phases in which the output of each phase becomes the input for the next

Agile Methodology Iterative development – Consists of a series of tiny projects Agile methodology – Aims for customer satisfaction through early and continuous delivery of useful software components developed by an iterative process using the bare minimum requirements

Rapid Application Development Methodology (RAD) Rapid application development methodology– Emphasizes extensive user involvement in the rapid and evolutionary construction of working prototypes of a system to accelerate the systems development process Prototype – A smaller-scale representation or working model of the users’ requirements or a proposed design for an information system The prototype is an essential part of the analysis phase when using a RAD methodology

Extreme Programming Methodology Extreme programming (XP) methodology – Breaks a project into tiny phases, and developers cannot continue on to the next phase until the first phase is complete

Rational Unified Process (RUP) Methodology Rational Unified Process (RUP) – Provides a framework for breaking down the development of software into four gates Gate One: Inception Gate Two: Elaboration Gate Three: Construction Gate Four: Transition

SCRUM Methodology SCRUM – Uses small teams to produce small pieces of deliverable software using sprints, or 30-day intervals, to achieve an appointed goal Under this methodology, each day ends or begins with a stand-up meeting to monitor and control the development effort

LEARNING OUTCOME REVIEW Now that you have finished the chapter please review the learning outcomes in your text