Alternative Methodologies Ken Peffers UNLV March 2004.

Slides:



Advertisements
Similar presentations
Prescriptive Process models
Advertisements

Systems Development Environment
1 Software Processes A Software process is a set of activities and associated results which lead to the production of a software product. Activities Common.
Systems Analysis and Design
Multimedia Specification Design and Production 2013 / Semester 1 / week 7 Lecturer: Dr. Nikos Gazepidis
1 Information Systems Development (ISD) Systems Development Life Cycle Overview of Analysis Phase Overview of Design Phase CP2236: Information Systems.
Systems Analysis & IT Project Management Pepper. System Life Cycle BirthDeathDevelopmentProduction.
CSE 470 : Software Engineering The Software Process.
The software process A software process is a set of activities and associated results which lead to the production of a software product. This may involve.
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.
© Prentice Hall CHAPTER 10 Alternative Approach: Purchasing Systems.
Pertemuan 4 Membangun Teknologi Informasi Matakuliah: H0402/PENGELOLAAN SISTEM KOMPUTER Tahun: 2005 Versi: 1/0.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Systems Development Life Cycles. The Traditional Systems Development Life Cycle.
Lesson-12 Information System Development-2
Chapter 8 Prototyping and Rapid Application Development
Slide 1 INTRODUCTION Chapter 1. Slide 2 Key Ideas Many failed systems were abandoned because analysts tried to build wonderful systems without understanding.
Contemporary Information Systems Development Chapter 10.
DECISION SUPPORT SYSTEM DEVELOPMENT
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
SDLC and alternative methodologies 1/14/2015 © Abdou Illia MIS Spring 2015.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Rapid software development.
Project phases and the life cycle
Chapter 3 Software Processes.
Systems Approach to Problem Solving
Chapter 14: Redesigning the Organization with Information Systems Instructor: Kevin Brabazon.
CSI315 Web Technology and Applications
S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
Laudon & Laudon: Canadian Edition
Objectives:  To define RAD  Describe RAD as a system development method  List the advantages of RAD as a method  List the disadvantages of RAD  State.
Prototyping. Introduction *Overview *What is the process *Changing roles of end users *What tools facilitate prototyping *Impact on traditional methodology.
Satzinger Chp. 2 Part Part 4 of 4 2 Object-Oriented Analysis and Design with the Unified Process Testing Testing is critical discipline Testing activities.
BUILDING INFORMATION SYSTEMS
The Systems Development Methodologies. Objectives  Describe the information Systems Development Life Cycle (SDLC)  Explain prototyping  Explain Rapid.
Development and Impact of Software Solutions Application of software development approaches.
Rapid Application Development. What is RAD……..?  Rapid Application Development (RAD) is a software development process.  first developed during the.
Software Development Cycle What is Software? Instructions (computer programs) that when executed provide desired function and performance Data structures.
Component 4: Introduction to Information and Computer Science Unit 9: Components and Development of Large Scale Systems Lecture 3 This material was developed.
14-1 Systems Development Concept of Systems Development Life Cycle (SDLC) Definition of SDLC Stages of SDLC Traditional versus modern SDLCs.
SDLC Class 4. SDLC Systems Development Life Cycle Traditional methodology used to develop, maintain, and replace information systems. Orderly set of activities.
Software Development Life Cycle by A.Surasit Samaisut Copyrights : All Rights Reserved.
Chapter 6 Prototyping, RAD, and Extreme Programming Systems Analysis and Design Kendall & Kendall Sixth Edition.
11.1 Copyright © 2011 Pearson Education, Inc. publishing as Prentice Hall 11 Chapter Building Information Systems.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
11.1 © 2007 by Prentice Hall 6 Chapter Building Information Systems.
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
Process Asad Ur Rehman Chief Technology Officer Feditec Enterprise.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Chapter 10 Information Systems Development. Learning Objectives Upon successful completion of this chapter, you will be able to: Explain the overall process.
Systems Development Life Cycle (SDLC)
CHAPTER 13 Acquiring Information Systems and Applications.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
A framework that describes the activities performed at each stage of a software development project. A life-cycle or a software process is the organisational.
Systems Development Life Cycle
3-1 Decision Analysis Phase Candidate solutions evaluated in terms of: Technical feasibility – Is the solution technically practical? Does our staff have.
Chapter 2: System Development Methodologies & Automated Systems 1.
C_ITIP211 LECTURER: E.DONDO. Unit 1 : The Systems Development Environment.
Building Information Systems
SOFTWARE DEVELOPMENT Presented By : Emporiumtech This presentation is brought you by
Systems Development Process and Methodologies Dr. T. Ravichandran.
Integrating Quality Activities in the Project Life Cycle
V-Shaped SDLC Model Lecture-6.
Systems Analysis and Design
Managing the development and purchase of information systems (Part 2)
CHAPTER 10 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
Rapid software development
Chapter 8 Prototyping and Rapid Application Development
Information Systems Development (ISD) Systems Development Life Cycle
Presentation transcript:

Alternative Methodologies Ken Peffers UNLV March 2004

Limitations of SDLC Expensive development Suited to in-house development Works poorly if problem not well structured Length of time

Alternative methodologies Prototyping Spiral Model Rapid Application Development (RAD) Phased Development Packages Sourcing

Prototyping Use To determine requirements –users may not know what they want or have trouble imagining what is possible To design user interface –in design phase To build the system

Prototyping 1. Define initial needs. 2. Create “quick and dirty” functionality. 3. User tests and comments. 4. Revise system 5. User tests and comments If satisfactory, step 6, otherwise step Incorporate into requirements or produce production system.

Prototyping Technology Application development environment –Access, Visual Basic Screens only –Storyboarding

Prototyping outcome Prototype may become final version Prototype may be used to define requirements. May be prototyped in one language and final version produced in another

The Spiral Model To reduce project risk –Iterative prototypes –Each iteration moves the project further along Cycle 1—feasibility study –Risk analysis What can go wrong How can the risk be managed –Prototype –Operation concept –Life cycle plan

Spiral Model Cycle 2—systems analysis –Risk analysis –Prototype –Models –Software requirements –Requirements validation –Development plan

Spiral Model Cycle 3—design –Risk analysis –Prototype –Models –Software product design –Design validation and verification –Integration and test plan

Spiral Model Cycle 4—testing, integration, and acceptance –Risk analysis –Operational prototype –Models –Detailed design –Code –Unit test –Integration test –Acceptance test –Implementation

Rapid application development (RAD) Purpose: faster development and higher quality system Heavy user involvement in project front end

RAD steps Investigate problem & develop workable solution Iterative steps with users: –Use application development tool to develop prototype –Put prototype into operation –Refine and modify prototype –Approve acceptable version Complete system Note: system developed with this method ought not be too complex; consider incremental development

Phased Development SDLC, but –JAD sessions –Prototyping –Use of tools to speed development CASE Quick development environments, e.g., VB, Access,

Application Packages Generic application functions –Office automation Industry generic function –Medical practitioner appointment and billing Custom developed application –written in 4th generation language

Package or Custom Development Package –economy –generic need Custom –unique need –performance requirements Customized package –tailor package to unique needs

Sourcing In House Outsource –development –development and operation –purchase service

Sourcing Considerations In House –Building IT capability critical to competitiveness –Low cost in-house development Outsource –Operations critical to competitiveness –Lower costs –Access IT resources unavailable in-house