CA FINAL ISCA | CH-5 | ADIS | SPIRAL MODEL | MNEMONICS

CA FINAL ISCA
CHAPTER 5

A D I S (Acquisition, Development & Implementation of Information systems)





SPIRAL MODEL


The Spiral model IS a software development process combining elements of both design and prototyping-in-stages. It tries to combine advantages of top-down and bottom-up concepts. It combines the features of the prototyping model and the waterfall model. The spiral model is intended for large, expensive and complicated projects. Game development is a main area where the spiral model is used and needed, that is because of the Size and the constantly shifting goals of those large projects. A list of pertinent characterizing features includes the following:

  • The new system requirements are defined n as much detail as possible. This usually involves interviewing a number of users representing all the external or internal users and other aspects of the existing system.


  • A preliminary design is created for the new system. This phase is the most important part of "Spiral Model" in which all possible alternatives that can help in developing a cost effective project are analyzed and strategies are decided to use them. This phase has been added specially in order to identify and resolve all the possible risks in the project development. If risks indicate any kind of uncertainty in requirements, prototyping may be used to proceed With the available data and find out a possible solution in order to deal with the potential changes in the requirements.


  • A first prototype of the new system in constructed from the preliminary design. This is usually a scaled-down system, and represents an approximation of the characteristics of the final product.


  • A second prototype is evolved by a fourfold procedure by evaluating the first prototype in terms of Its strengths, weaknesses, and risks; defining the requirements of the second prototype; planning and designing the second prototype; and constructing and testing the second prototype





Now, the MNEMONICS story/points in हिन्दी 
(for Strengths & Weakness)



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]


SPIRAL से याद रखना LADDER , जैसे SPIRAL zigzag होता है ना वैसे ही LADDER एकदम straight होती है। 
SPIRAL = LADDER i.e Ladder = 11 {Picture technique}


11 STAIRS/LADDER
12 RABBIT
13 BRAIN
14 HEART
15 FLAG

16 ELEPHANT
17 DOOR
18 SUMO RESTLER
19 TUMBLER
20 SNAKE

अब ये numerals इनके सामने लिखे words से कैसे relate होंगे वो मैं इस picture मैं draw कर के दिखाने की कोशिश करता हू। 

जब uper वाली picture समझ आ जाये तो अब इनकी linkage पे आते है। 
पहले मई सिर्फ linkage batyunga उसके बाद कोन सा point किस से link होना है वो Strenghts & Weakness मे dikhayunga. 


  • STAIRS: Using STAIRS/LADDER instead of escalator will ENHANCE RISK AVOIDANCE (Parents कभी escalator से नहीं जाते bcoz of this  reason) 



  • RABBIT: BLANK (n/a) 



  • BRAIN: BRAIN is always useful in selecting the Best Methodology 



  • HEART: SPIRAL(Model) ka Heart इतना बड़ा है कि वो WIP ko incorporate कर लेता है। W=Waterfall, I=Incremental & P= Prototype



  • FLAG: BLANK 




  • ELEPHANT: Elephant is an experienced project manager { हाथी जो है वो बहुत Experienced animal है  i.e Experienced project manager }



  • DOOR: Door की exact composition बना कर उसे एक जगह fit करना is a challenge



  • SUMO WRESTLER: Sumo wrestler की Body firm नहीं होती और वो किसी पे चढ़ जाये तो उसे इंसान की सारी Lifeline dead हो जाती है। 



  • TUMBLER: Tumbler की reusability होती है। 



  • SNAKE: N/A

Now, Strengths & Weakness Mnemonics linkage is shown below.

Strengths:


  • It enhances the risk avoidance. 11 = LADDER = Using STAIRS/LADDER instead of escalator will ENHANCE RISK AVOIDANCE (Parents कभी escalator से नहीं जाते bcoz of this  reason)


  • It is useful in helping for optimal development of a given software iteration based on project risk. 13 = BRAIN = BRAIN is always useful in selecting the Best Methodology 


  • It can incorporate Waterfall, Prototyping, and Incremental methodologies as special cases in the framework, and provide guidance as to which combination of these models best fits a given software iteration, based on the type of project risk. 14 = HEART = SPIRAL(Model) ka Heart इतना बड़ा है कि वो WIP ko incorporate कर लेता है। W=Waterfall, I=Incremental & P= Prototype



Weakness:


  • It is challenging to determine the exact composition of development methodologies to use for each iteration around the Spiral. 17 = DOOR = Door की exact composition बना कर उसे एक जगह fit करना is a challenge


  • It may prove highly customized to each project, and thus is quite complex and limits reusability. 19 = TUMBLER = Tumbler की reusability होती है।


  • A skilled and experienced project manager is required to determine how to apply it to any given project. 16 = ELEPHANT = Elephant is an experienced project manager { हाथी जो है वो बहुत Experienced animal है  i.e Experienced project manager }


  • No established controls exist for moving from one cycle to another cycle. Without controls, each cycle may generate more work for the next cycle.


  • There are no firm deadlines, cycles continue with no clear termination condition leading to, inherent risk of not meeting budget or schedule. 18 = SUMO WRESTLER = Sumo wrestler की Body firm नहीं होती और वो किसी पे चढ़ जाये तो उसे इंसान की सारी Lifeline dead हो जाती है। 


YouTube:

Video coming soon....

Share:

0 comments