RAPID APPLICATION DEVELOPMENT باسمه تعالی دانشگاه الزهرا دانشکده علوم اجتماعی واقتصادی استاد : جناب آقای دکتر سلطانی تهیه و تنظیم : ارمغان خلیل زادگان اصل

INTRODUCTION 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 ? “ 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 ? “ 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 ? 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 Requirements ResourcesTime DSDM ResourcesTime Requirements fixed variable waterfall dynamic systems development method

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

Deliverable & Outcomes 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 tools to support as much of the development process as possible. computer_based tools

Software tools VisualAge GeneratorVisualAge for Java WebSphere Studio WebSphere Application Server

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

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

MacConnell ’ s 4 necessary pillars for the RAD approches Avoiding Classic Mistakes Applying Development Fundamentals Managing Risk Applying Schedule-Oriented Practices “ efficient development ” McConnell Choosing the appropriated software tools & lifecycle approaches

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

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

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

Requirements Planning Concept definition stage Define the business functions & data subject areas Uses Joint Requirements Planning (JRP) workshop 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 Functional design stage Main technique is joint application development (JAD) workshops 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 Development stage Completes the construction of physical application system Code generation using CASE tool End users are participate & validating screens Core of system developed in 4-6 weeks

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

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

Advantages 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 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) Modern system analysis & design methods (Jeffrey A.Hoofer)