Rapid Application Development (RAD)

-

RAD, or rapid application development, is an object-oriented approach to systems development that includes a method of development as well as software tools

•RAD is used when
–The team includes programmers and analysts who are experienced with it.
–Users are sophisticated and highly engaged with the goals of the company.

•Negative Aspect
- RAD is based on Object Oriented approach.
- If commitment is lacking RAD will fail.
- RAD is not appropriate when technical risks are high, e.g. this occurs when a new application makes heavy use of new technology.

You can also view:
1. Boehms Spiral Process Model
2. Rational Unified Process Model
3. Rapid Application Development-RAD
4. Prototyping Process Model
5. Incremental Process Model
6. Component Based Software Engineering
7. Evolutionary Process Development Model
8. Waterfall Process Model
9. Software Process Framework Activity

Comments

  1. Peter Smith3 July 2013 at 06:08

    Rapid Application Development (RAD) is Flexible and adaptable to changes, Can handle large projects without a doubt, RAD realizes an overall reduction in project risk.

    iPhone Application Development India

    ReplyDelete
  2. Joanna Zadrożna22 November 2019 at 12:52

    Great article...

    ReplyDelete

Post a Comment

i am running my new blog at Knowledge Sharing (https://ksharing.info). please subscribe my new blog

Popular posts from this blog

Component Based Software Engineering

-
Image
•Main characteristics –Makes intensive use of existing reusable components. –The focus is on integrating the components rather than on creating them from the scratch. •Advantages –Reduces considerably the software to be developed “in-house”. –Allows faster delivery. –In principle, more reliable systems, due to using previously tested components. •Disadvantages –agreement in requirements are needed. –Less control over the system’s evolution •Applicability: –When there is a pool of existing components that could satisfy the requirements of the new product. –Emerging trend: integration of web services from a range of suppliers. You can also view: 1. Boehms Spiral Process Model 2. Rational Unified Process Model 3. Rapid Application Development-RAD 4. Prototyping Process Model 5. Incremental Process Model 6. Component Based Software Engineering 7. Evolutionary Process Development Model 8. Waterfall Process Model 9. Software Process Framework Activity
Read more

What is software engineering

-
1.What is software? Ans:Computer programs and associated documentation. Software products may be developed for a particular customer or may be developed for a general market. 2.What is software engineering? Ans:Software engineering is an engineering discipline that is concerned with all aspects of software production. 3.What is the difference between software engineering and system engineering? Ans:System engineering is concerned with all aspects of computer-based systems development including hardware, software and process engineering. Software engineering is part of this more general process 4.What are the key challenges facing software engineering? Ans:Coping with increasing diversity, demands for reduced delivery times and developing trustworthy software. 5.What are the costs of software engineering? Ans:Roughly 60% of software costs are development costs, 40% are testing costs. For custom software, evolution costs often exceed development costs. 6.What are the best software engine
Read more

What is Non-functional requirements

-
Image
These define system properties and constraints e.g. reliability, response time and storage requirements. Constraints are I/O device capability, system representations, etc. i.e. Deactivate or delete record after 24 hrs Process requirements may also be specified mandating a particular programming language or development method. Non-functional requirements may be more critical than functional requirements. If these are not met, the system may be useless. Types of Nonfunctional requirement Product requirement: Examples The MHC-PMS shall be available to all clinics during normal working hours (Mon–Fri, 0830–17.30). Downtime within normal working hours shall not exceed five seconds in any one day. Organizational requirement:  Examples Users of the MHC-PMS system shall authenticate themselves using their health authority identity card. External requirement:  Examples The system shall implement patient privacy. Non-functional requirements implementation Non-functional requirements may affec
Read more