CA FINAL ISCA | CH-5 | ADIS | RAD { RAPID ACCESS DEVELOPMENT MODEL } | MNEMONICS

Wrote by 2 Comments

CA FINAL ISCA
MNEMONICS

RAPID ACCESS DEVELOPMENT MODEL





RAD refers to a type a software development methodology; which uses minimal planning in favor of rapid prototyping. The planning of software developed using RAD is interleaved with writing the software itself. The lack of extensive pre-planning generally allows software to be written much faster and makes it easier to change requirements.

Mnemonics do not relate to Features (only Strengths & Weakness)

Features:
{Some of the features}


  • Key objective is fast development and delivery of a high-quality system at a relatively low investment cost.
  • Active user involvement is imperative.
  • Iteratively produces production software as opposed to a throwaway prototype.
  • Produces documentation necessary to facilitate future development and maintenance.
  • Key Emphasis is on fulfilling the business need while technological or engineering excellence is of lesser importance.


MNEMONICS STORY (IN हिन्दी )

If you haven't watched the Mnemonic video where the techniques are explained then watch it here.
DO watch the video to understand the linkage.

[ CLICK TO WATCH THE VIDEO]


  • TOP: TOP = दिमाग , Dimag से concentrate करते है। 


  • NOSE: लड़के/लड़की का nose देख के पता चल जाता है i.e Quick initial review {पहली नज़र मे देख के ही पसंद आ जाता/जाती है।}


  • MOUTH: आज कल के mouth बहुत Rapid चलते है। [Rapidly change system design]


  • RIBS: Ribs का Operation (version) करवाना पड़ा।  [रिब्स काम नहीं कर रही थी operation करवाना पड़ा ]


  • LIVER: आजकल Liver जल्दी ख़राब हो जाता है (Quickly)



  • JOINTS: जिनके joints atche है उनकी speed fast होती है 



  • KNEE: आजकल knees के operation के लिए new features आ गए है। 



  • FIBULA: अगर Fibula ख़राब हो जाये तो पूरी body एक Inconsistent system बन जाती है। 



  • BALL: ball को Goal तक पहुंचाने के लिए Well defined interface required होते है।  



  • SAND: दिल्ली/मुंबई मे जमीन की ज्यादा से ज्यादा Requirement है [more requirement]


Module reference:

Strengths:


  • The operational version of an application is available much earlier than with Waterfall, Incremental, or Spiral frameworks: Ribs का Operation (version) करवाना पड़ा।



  • Because RAD produces systems more quickly and to a business focus, this approach tends to produce systems at lower cost: आजकल Liver जल्दी ख़राब हो जाता है (Quickly)


  • Quick initial reviews are possible: लड़के/लड़की का nose देख के पता चल जाता है


  • Constant integration isolates problems and encourages customer feedback.


  • It holds a great level of commitment from stakeholders, both business and technical, than Waterfall, Incremental, or spiral frameworks. Users are seen as gaining more of a sense of ownership of a system, while developer are seen as gaining more satisfaction from producing successful systems quickly.


  • It concentrates on essential system elements from user viewpoint: TOP = दिमाग , Dimag से concentrate करते है।


  • It provides for the ability to rapidly change system design as demanded by users: आज कल के mouth बहुत Rapid चलते है।


  • It leads to a tighter fit between user requirements and system specifications




Weakness:

  • Fast speed and lower cost may affect adversely the system quality: जिनके joints atche है उनकी speed fast होती है। 


  • The project may end up with more requirements than needed (gold-plating): दिल्ली/मुंबई मे जमीन(SAND) की ज्यादा से ज्यादा Requirement है


  • Potential for feature creep where more and more features are added to the system over the course of development: आजकल knees के operation के लिए new features आ गए है। 


  • It may lead to inconsistent designs within and across systems: अगर Fibula ख़राब हो जाये तो पूरी body एक Inconsistent system बन जाती है। 


  • It may call for violation of programming standards related to inconsistent naming conventions and inconsistent documentation,


  • It may call for lack of attention to later system administration needs built into system


  • Formal reviews and audits are more difficult to implement than for a  complete system.


  • Tendency for difficult problems to be pushed to the future to demonstrate early sucess to management.


  • Since some modules will be completed much earlier than others, well-defined interfaces are required: ball को Goal तक पहुंचाने के लिए Well defined interface required होते है।  


YouTube: Video coming soon




Tags:

Share:

2 comments

  1. Swarnali Saha4 October 2017 at 22:23

    Hi, I would really love if could have provided the rest videos of sdlc sub parts

    ReplyDelete
  2. Unknown6 October 2017 at 12:20

    Please share videos on chapter 7. Much needed ..Please 🙏🙏🙏

    ReplyDelete