INTRODUCTION n RAD has been demonstrate in many

INTRODUCTION n RAD has been demonstrate in many projects to be so superior to traditional development that it seems irresponsible to continue to development system. james Martin , 1991

? What is RAD n n “Rapid Application Development (RAD) is a development lifecycle designed to give much faster development and higher-quality results than those achieved with the traditional lifecycle. It is designed to take the maximum advantage of powerful development software that has evolved recently. ” james Martin

? What is RAD n “an approach to building computer systems which combines Computer. Assisted Software Engineering (CASE) tools and techniques, user-driven prototyping, and stringent project delivery time limits into a potent, tested, reliable formula for top-notch quality and productivity. ” Professor Clifford Kettemborough of Whitehead College,

? What is RAD n Online Knowledge defines Rapid Application Development as “a methodology that enables organizations to develop strategically important systems faster while reducing development costs and maintaining quality. ”

RAD v. TRAD Time Requirements fixed Resources DSDM waterfall Time variable Requirements Resources dynamic systems development method

Planning RAD SDLC Design Project identification & selection Development Project Initiation & planning cutover Analysis Design Standard SDLC Implementation Maintenance

Deliverable & Outcomes n n n Outcomes of RAD are the same as traditional SDLC : A system development plan Description of user & business process requirement for the application Logical & physical design for the application Application construction & implementation RAD puts a heavy emphasis on the use of computer_based to support as much of the development process as possible. tools

Software tools Visual. Age Generator Web. Sphere Studio Visual. Age for Java Web. Sphere Application Server

Martin’s 4 Pillars for RAD Power tools Design-automation technique Code generator Right skills People Tools Methodology Management Dedication Change in culture Pay attention to motivation Talent Train motivation

Methodology n n Combining the best technique & best sequence Using prototyping Using workshop instead of interview selecting a set of CASE tools to support modeling , code reusability…

Mac. Connell’s 4 necessary pillars for the RAD“ efficient approches development ” Mc. Connell Avoiding Applying Classic Development Mistakes Fundamentals Managing Risk Applying Schedule-Oriented Choosing the Practicesappropriated software tools & lifecycle approaches

Avoiding Classic Mistakes People. Related 1. Week personnel 2. Adding people To project late 3. Unrealistic expectations Process. Related Product- Technology. Related 1. Insufficient planning 1. Feature creep 1. Silver-bullet syndrome 2. Overly optimistic schedules 2. Requirements Gold-planning 3. Planning to catch up later 2. Overstimated saving from new tools or methods

Development Fundamental n n n Practices proper project estimating , scheduling , planning & tracking Measuring software quality & productivity Managing system requirements Engaging in good design techniques Assuring quality

Phases Requirements Planning JRP Workshop of RAD User Design Prototyping JAD Workshop CASE Construction Prototyping CASE Phases Cutover Techniques Tools

Requirements Planning n n n Concept definition stage Define the business functions & data subject areas Uses Joint Requirements Planning (JRP) workshop n n JRP attempts to identify the high level management requirements of the system at a strategic level, participants are senior managers. During this phase , high-level managers , executive & knowledgeable end user determine system requirement.

User Design n n Functional design stage Main technique is joint application development (JAD) workshops n n n End user &information system professionals participate in JAD workshops. Uses diagramming techniques of entity modeling, functional decomposition, data flow diagramming, and action diagrams. Users & analysts work closely & quickly to prototypes with CASE tools.

Construction n n Development stage Completes the construction of physical application system n Code generation using CASE tool n End users are participate & validating screens n Core of system developed in 4 -6 weeks

Cutover n n Cutover means delivery of the new system to its end users. Cutover involves many traditional activities of implementation : n including testing n training users n running new & old systems parallel

Structure of JAD/JRP Meeting : n n Intensive meeting of users and IT developers Defined length of meeting n n n Structured meeting room n n round table whiteboards & pin boards availability of technology tools Facilitator n n 1 -2 days, can be up to 5 away from interruptions leads and manages meeting independent of participants skilled in group dynamics, knowledge of tasks Scribe

Advantages n n Dramatic time saving during the system development effort. Tighter fit between user requirement & system specification. Works especially well where speed of development is important for changing business conditions. Ability to rapidly change system design as demanded by users.

Disadvantages n n More speed &lower cost may lead to lower quality. High cost of commitment on the part of key user personnel. May have inconsistent internal design within & across system. You cannot obtain three key characteristics of the development effort : speed , cost and quality.

What is rapid application development ? (article) n Modern system analysis & design methods (Jeffrey A. Hoofer) n WWW. Webopedia. com n WWW. IBM. COM n