SLDC vs. JAD vs. RAD
Methodologies of Software Development
Kaplan University
IT460 – System Analysis and Design
From my reading I learned that Software Development Life Cycle (SDLC) follows a pretty general process that is used by a lot of project managers. The whole purpose of SDLC is to create a better product than is planned for while meeting time and cost figures (Tutorials Point). the Chief Information Officer (CIO) asked to look at a couple of methodologies. The two methodologies are JAD (Joint Application Development) and RAD (Rapid Application Development). JAD (Joint Application Development) is a methodology where you use the client and end users at different points during the project (Rouse, 2007). By using this methodology some of the advantages are that in a short time frame you can gather and consolidate a big amount of information. Another benefit is that you can look at many points of view on the project and can resolve discrepancies in a timely manner (n.d.). Some disadvantages of JAD (Joint Application Development) it takes a lot of planning and scheduling and this will also require a lot of time from the stakeholders. Another disadvantage is that people that are working on the project have to be trained and experienced with what the project requires. RAD (Rapid Application Development) is a methodology that is focused on producing software quickly. This is done by using prototypes that have been established before and uses tools that are specifically designed to produce software. The biggest thing is that this methodology is focused on producing a prototype and not a full application (Janssen). Some of the advantages of the RAD methodology are that it decreases the overall development time because you are integrating right from the beginning. You also get the advantage of being able to reuse a lot of the software components. Another advantage is that you can implement customer feedback quickly. Some of the disadvantages of the RAD methodology are that it requires an experienced and dedicated staff to accomplish the goal, the designers and developers need to be very experienced, and since it is can only handle modularized systems the cost of the project is very high (ISTQB Exam Certification, 2012). I think that overall it really boils down to the fact that SDLC has become outdated as the methodologies of JAD and RAD are more specialized specifically for Software Development. When choosing between the two I think that it comes down to whether or not the client has a lot of money for the project or if they are on a budget. Being that I am fairly experienced and if money wasn’t an issue I would probably go with the RAD methodology. From my own experience with website development clients like to get a picture of what the final project is going to be like. This keeps them invested with you and also eliminates a lot of misunderstandings when the project get finalized and signed off on.
Reference
Tutorials Point Simply Easy Learning. (n.d.). SDLC Overview. Retrieved July 5, 2014, from http://www.tutorialspoint.com/sdlc/sdlc_overview.htm
Rouse, M. (2007, March 1). JAD (Joint Application Development). What is ?. Retrieved July 5, 2014, from http://searchsoftwarequality.techtarget.com/definition/JAD
Story. (n.d.). Joint Application Development (JAD) Technique. Retrieved July 6, 2014, from http://www.directutor.com/content/joint-application-development-jad-technique
Janssen, C. (n.d.). What is Rapid Application Development (RAD)? - Definition from Techopedia. Techopedias. Retrieved July 6, 2014, from http://www.techopedia.com/definition/3982/rapid-application-development-rad
What is RAD model- advantages, disadvantages and when to use it? - ISTQB Exam Certification. (2012, January 13). ISTQB Exam Certification. Retrieved July 6, 2014, from http://istqbexamcertification.com/what-is-rad-model-advantages-disadvantages-and-when-to-use-it/ 