Rapid application development & win win spiral approach.
Introduction :
The software development models are the different procedures or philosophies that are being chosen for the improvement of the venture contingent upon the venture’s points and objectives. There are numerous improvement life cycle models that have been produced with a specific end goal to accomplish diverse required destinations. The models determine the different phases of the procedure and the request in which they are completed.
The determination of model has high effect on the testing that is completed. It will characterize the what, where and when of our arranged testing, impact relapse testing and to a great extent figures out which test strategies to utilize.
There are different Software improvement models or approach. They are as per the following:
- Waterfall model
- V model
- Incremental model
- RAD model
- Agile model
- Iterative model
- Spiral model
- Prototype model
(RAD) is a software development methodology, which favors iterative improvement and the fast development of models rather than a lot of in advance arranging. The “arranging” of programming created utilizing RAD is interleaved with composing the product itself. The absence of broad pre-arranging by and large permits programming to be composed much speedier, and rolls out it less demanding to improvement necessities.
The fast advancement handle begins with the improvement of preparatory information models and business handle models utilizing organized methods. In the following stage, prerequisites are confirmed utilizing prototyping, in the long run to refine the information and process models. These stages are rehashed iteratively; assist advancement brings about “a joined business necessities and specialized plan proclamation to be utilized for building new systems”.[1]
The term was initially used to depict a product advancement prepare presented by James Martin in 1991. As indicated by Whitten (2003), it is a merger of different organized methods, particularly information driven Information Engineering, with prototyping strategies to quicken programming frameworks development.[1]
- win win spiral approach:
The win win spiral approach is the enhanced version of Spiral Approach. The phase in this is same as of Spiral Approrach while as the only difference is the time of identifying the requirements, the delevelopment team and customer hold discussions. This approach is called win win because of its winning situation for development team as well as the customer. The customer wins by getting the product that fills his most of the requirements and the delevoplment team wins by deleviring the software which is create by getting the all requirements after negotiations with the customer. This approach is only used when we have time bound releases.
Spiral model has four phases Planning,risk analysis,engineering and evaluation But the more focus is on Risk Analysis.
This project undergoes each phase repeatedly which are called Spirals Planning phase is the baseline and each subsequent part is build on that spiral model. The advantage if this project is that more emphasis is put on risk analysis and software is produced at early stage but its very costly model. [3]
Conclusion :
The rapid development process starts with the improvement of preparatory information models and business handle models utilizing organized methods. In the following stage, prerequisites are checked utilizing prototyping, in the long run to refine the information and process models. These stages are rehashed iteratively; promote advancement brings about “a consolidated business necessities and specialized outline explanation to be utilized for building new systems”.c
The Win-Win Spiral Model propsed by Barry Boehm is another interpretation of a customary programming process. While keeping up large portions of the conventional components of the winding model, the Win-Win variant endeavors to include all partners in the advancement procedure. It includes a community motor that sets up “win” conditions set by clients, clients, designers, and framework builds to develop and reprioritze necessities all through the procedure. Customary practices, for example, prerequisites building, plan, code, and test, are still present amid every emphasis of the winding, yet the collective stride all through the improvement procedure makes it unmistakably versatile. This cooperation conveys programming all the more rapidly, with higher quality, and less expensive due to the in advance fulfillment of client prerequisites and decreased measure of upkeep. [3]
References:
- Whitten, Jeffrey L.; Lonnie D. Bentley, Kevin C. Dittman. (2003). Systems Analysis and Design Methods. 6th edition. ISBN 0-256-19906-X.
- Centers for Medicare & Medicaid Services (CMS) Office of Information Service (2008). Selecting a development approach. Webarticle. United States Department of Health and Human Services (HHS). Re-validated: March 27, 2008. Retrieved 27 Oct 2008.
Boehm, B., A. Egyed, J. Kwan, D. Port, A. Shah, R. Madachy, Using the Win-Win Spiral Model: A Case Study,IEEE Computer, July
