Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Rapid application development

U will learn one or two useful information about RAD model from this presentation
by

Hung Luu

on 16 March 2012

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Rapid application development

Rapid Application Development (RAP)
model Practical implications Thank you for spending approx. 5 minutes reading my presentation !!! Steve McConnell (1996). Rapid Development: Taming Wild Software Schedules, Microsoft Press Books, ISBN 978-1556159008
Kerr, James M.; Hunter, Richard (1993). Inside RAD: How to Build a Fully-Functional System in 90 Days or Less. McGraw-Hill. ISBN 0070342237.
Ellen Gottesdiener (1995). "RAD Realities: Beyond the Hype to How RAD Really Works" Application Development Trends
Ken Schwaber (1996). Agile Project Management with Scrum, Microsoft Press Books, ISBN 978-0735619937
Steve McConnell (2003). Professional Software Development: Shorter Schedules, Higher Quality Products, More Successful Projects, Enhanced Careers, Microsoft Prese s Books, ISBN 978-0321193674
Dean Leffingwell (2007). Scaling Software Agility: Best Practices for Large Enterprises, Addison-Wesley Professional, ISBN 978-0321458193
Further reading When organizations adopt rapid development methodologies, care must be taken to avoid role and responsibility confusion and communication breakdown within a development team, and between team and client.

In addition, especially in cases where the client is absent or not able to participate with authority in the development process, the system analyst should be endowed with this authority on behalf of the client to ensure appropriate prioritisation of non-functional requirements.

Furthermore, no increment of the system should be developed without a thorough and formally documented design phase. Rapid application development (RAD) is a software development methodology that uses minimal planning in favor of rapid prototyping, allowing usable systems to be built in short development cycle (anywhere from 60-90 days), often with some compromises.

The RAD model is a high-speed adaptation of the linear sequential model / Waterfall model.



Definition Promotes strong collaborative atmosphere and dynamic gathering of requirements.

Business owner actively participates in prototyping, writing test cases and performing unit testing.

Quick initial reviews are possible.

Constant integration isolate problems and encourage customer feedback.

omg I did it :)) Testing and Turn over

Process Modeling 1.Requirements Planning phase – combines elements of the system planning and systems analysis phases of the System Development Life Cycle (SDLC). Users, managers, and IT staff members discuss and agree on business needs, project scope, constraints, and system requirements. It ends when the team agrees on the key issues and obtains management authorization to continue.

2.User design phase – during this phase, users interact with systems analysts and develop models and prototypes that represent all system processes, inputs, and outputs. The RAD groups or subgroups typically use a combination of Joint Application Development (JAD) techniques and CASE tools to translate user needs into working models. User Design is a continuous interactive process that allows users to understand, modify, and eventually approve a working model of the system that meets their needs.

3.Construction phase – focuses on program and application development task similar to the SDLC. In RAD, however, users continue to participate and can still suggest changes or improvements as actual screens or reports are developed. Its tasks are programming and application development, coding, unit-integration and system testing.

4.Cutover phase – resembles the final tasks in the SDLC implementation phase, including data conversion, testing, changeover to the new system, and user training. Compared with traditional methods, the entire process is compressed. As a result, the new system is built, delivered, and placed in operation much sooner. Its tasks are data conversion, full-scale testing, system changeover, user training.
RAD assumes the use of fourth generation techniques. Rather than creating software using conventional third generation programming languages,

RAD process works to use the automated tools to facilitate the construction of the software.


The information flow among business functions is defined by answering questions like what information drives the business process, what information is generated, who generates it, where does the information go, who process it and so on.



The RAD approach encompasses 4 phases:

Business Modeling

Data Modeling


The information collected from business modeling is refined into a set of data objects (entities) that are needed to support the business. The attributes (character of each entity) are identified and the relation between these data objects (entities) is defined.

1 2 3
The data object defined in the data modeling phase are transformed to achieve the information flow necessary to implement a business function. Processing descriptions are created for adding, modifying, deleting or retrieving a data object.
Application Generation

4 Since the RAD processes emphasize reuse, many of the program components have already been tested. This saves time, money and the overall time to test an application also reduces considerably.

5 Another version of RAD phases Another Version
What are the advantages and disadvantages of RAD
???
Advantages Disadvantages Dependence on strong cohesive teams and individual commitment to the project.

Decision-making relies on the feature functionality team and a communal decision-making process with lesser degree of centralized project management and engineering authority.

Requires a system that can be modularized

Requires highly skilled and well-trained developers
Full transcript