To RAD or not to RAD? RAD is the relatively new kid on the block. You know the one. The one with all the flashy stuff and is practically the Usain Bolt.

Slides:



Advertisements
Similar presentations
kareRCIserIsviFIsaRsþGnuvtþKMerag
Advertisements

Prescriptive Process models
Lecture # 2 : Process Models
CS487 Software Engineering Omar Aldawud
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.
Alternate Software Development Methodologies
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix.
Chapter 6 SYSTEMS DEVELOPMENT Phases, Tools, and Techniques
Gu & Maher University of Sydney, October 2004 DECO2005 Monitoring Team Process.
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall Agile Modeling and Prototyping Systems Analysis and Design, 8e Kendall & Kendall 6.
Chapter 6 Prototyping, RAD, and Extreme Programming
Agile Modeling and Prototyping
Fundamentals of Information Systems, Second Edition
Xtreme Programming. Software Life Cycle The activities that take place between the time software program is first conceived and the time it is finally.
SE 555 Software Requirements & Specification 1 SE 555 Software Requirements & Specification Prototyping.
CHAPTER 19 Building Software.
Agile Modeling and Prototyping Systems Analysis and Design, 7e Kendall & Kendall 6 © 2008 Pearson Prentice Hall.
Chapter 15 Systems Development. 2 Learning Objectives When you finish this chapter, you will  Understand the systems development life cycle.  Be able.
Agile Modeling and Prototyping Systems Analysis and Design, 7e Kendall & Kendall 6 © 2008 Pearson Prentice Hall.
CSI315 Web Technology and Applications
RAD Model BY - Dhivakaran.JM.
Chapter 2 The process Process, Methods, and Tools
University of Palestine software engineering department Testing of Software Systems Testing throughout the software life cycle instructor: Tasneem.
Describing Methodologies PART II Rapid Application Development*
SOFTWARE ENGINEERING MCS-2 LECTURE # 5. RAD (RAPID APPLICATION DEVELOPMENT) MODEL  In RAD model the components or functions are developed in parallel.
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.
Lecture # 04 & 05 CS314 Introduction To Software Development Software Development Process (SDP) Instructor :Muhammad Janas khan
Prescriptive Process Models
Chapter 12: Systems Investigation and Analysis. Agenda  How to Develop a CBIS?  Systems Development Life Cycle (SDLC)  Prototyping  Join Application.
Rapid Application Development. What is RAD……..?  Rapid Application Development (RAD) is a software development process.  first developed during the.
1 Software Process Models-ii Presented By; Mehwish Shafiq.
Building Information Systems & Managing Projects.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix B Rapid Application.
Chapter 6 Prototyping, RAD, and Extreme Programming Systems Analysis and Design Kendall & Kendall Sixth Edition.
Prof. Aiken CS 169 Lecture 21 Software Process CS169 Lecture 2.
Lecture 19 Rapid Application Development 19.1 COSC4406: Software Engineering.
Copyright © 2011 Pearson Education Agile Modeling and Prototyping Systems Analysis and Design, 8e Kendall & Kendall Global Edition 6.
CS5103 Software Engineering Lecture 02 More on Software Process Models.
Engineering Design Process Brookville Intermediate School 7 th Grade.
Extreme programming (XP) Variant of agile Takes commonsense practices to extreme levels © 2012 by Václav Rajlich1.
Process Asad Ur Rehman Chief Technology Officer Feditec Enterprise.
Software Model Process
Agenda: Overview of Agile testing Difference between Agile and traditional Methodology Agile Development Methodologies Extreme Programming Test Driven.
Meghe Group of Institutions Department for Technology Enhanced Learning 1.
Software Development Life Cycle (SDLC)
Modern Approaches of Systems Development By: Hanouf AL-Monawer Sara Mohammed.
Systems Development Life Cycle
By: Amjad M. Omari 1.  Time is a competitive weapon. Even the best strategies, tactics, systems, and people will lose the battle if they arrive at the.
Layered Technology Software Process Framework Generic Process Framework Activities Process Models 6/14/20162.
Group 6 : - Yesika Kristina Dea Pradana D Sukianti Merianti Meshiya Caterlee
SOFTWARE DEVELOPMENT Presented By : Emporiumtech This presentation is brought you by
Chapter 2: The Process. What is Process? Software Engineering Process is the glue that holds the technology layers together and enables rational and timely.
PROJECT LIFE CYCLE AND EFFORT ESTIMATION
Software Engineering cosc 4359 Spring 2017.
Rapid Application Development
Methodologies and Algorithms
Rapid Application Development
INTRODUCTION TO SOFTWARE DEVELOPMENT
Methodologies By Akinola Soyinka.
Methodologies in Computing
Rapid Application Development Model
Software development life cycle models
Rapid Application Development
Software Life Cycle Models
Object Oriented Analysis and Design
Software life cycle models
Software Development Life Cycle:-
Rapid Application Development (JAD)
Presentation transcript:

To RAD or not to RAD? RAD is the relatively new kid on the block. You know the one. The one with all the flashy stuff and is practically the Usain Bolt at getting things done quickly. RAD or better know as the Rapid Application Design methodology was created to respond to the need of delivering systems really fast. And I mean really fast. RAD is easily the quickest type of development. The projects size, scope and circumference can heavily determine whether or not if RAD is the right method to use. For example RAD could be the right method to use if the project scope is narrow as it means you already has a very good idea of what you want to make

When should you choose RAD? The projects size, scope and circumference can heavily determine whether or not if RAD is the right method to use. For example RAD could be the right method to use if the project scope is narrow as it means you already has a very good idea of what you want to make. Other Variables that can effect if you use RAD or not are Project data Project decisions Project team Project technical architecture

Why is RAD fast ? When you breakdown the RADs structure you can see how it has speed in its blood. But why? I hear you ask. RAD has a set of management techniques that make sure that this method is as quick as possible. These include Prototyping- this is an important stage because with RAD you want to make the prototype as quickly as possible and then refine quickly over and over until you have what you want but there are dangers in starting it too early so a balance is needed to be found time management strategy that allocates a Iteration- is a commitment to incremental development based on refinement. This goes hand in hand with prototyping Time boxing- this is a time management strategy that allocates a set amount of time to each part of the process and for RAD to work these time schedules must be followed religiously.

RAD diagrams

Advantages of RAD Reduced development time. Increases reusability of components Quick initial reviews occur Encourages customer feedback Integration from very beginning solves a lot of integration issues.

Disadvantages of RAD Depends on strong team and individual performances for identifying business requirements. Only system that can be modularized can be built using RAD Requires highly skilled developers/designers. High dependency on modelling skills Inapplicable to cheaper projects as cost of modelling and automated code generation is very high.

Thanks for listening