{"id":3476,"date":"2018-10-17T18:52:30","date_gmt":"2018-10-17T18:52:30","guid":{"rendered":"https:\/\/www.techuz.com\/blog\/?p=3476"},"modified":"2024-03-26T10:59:32","modified_gmt":"2024-03-26T10:59:32","slug":"top-12-sdlc-methodologies-with-pros-and-cons","status":"publish","type":"post","link":"https:\/\/www.techuz.com\/blog\/top-12-sdlc-methodologies-with-pros-and-cons\/","title":{"rendered":"Top 12 SDLC Methodologies with Pros and Cons"},"content":{"rendered":"<p><span style=\"font-weight: 400;\">As a developer, you might spit out few fancy SDLC Methodologies that are at the top of your mind.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Or as a client, you may recall some sweet-sounding terms &#8211; <\/span><i><span style=\"font-weight: 400;\">\u201cAgile&#8217;, \u201cLean&#8217;, \u201cDynamic System Development Model&#8217; (alright, this one\u2019s not so sweet)<\/span><\/i><span style=\"font-weight: 400;\"> or &#8216;<\/span><i><span style=\"font-weight: 400;\">Spiral&#8217;, <\/span><\/i><span style=\"font-weight: 400;\">because the <\/span><a href=\"https:\/\/techuz.com\/web-development\/\" target=\"_blank\" rel=\"noopener nofollow\"><span style=\"font-weight: 400;\">web development company<\/span><\/a><span style=\"font-weight: 400;\"> you hired practices it or at least claims to practice it. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">We all know that these SDLC methodologies are here for a while now and play a significant role in the success of your software or web application. They aim to provide the best quality product that meets or even transcends the client&#8217;s requirements. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">But the fact is, apart from the ones that frequently make headlines, there is a huge list of SDLC models that you ought to know. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">So in this blog, we have made a list of all those SDLC methodologies empowering you with the knowledge to apply them in your project. Here, take a look at the top SDLC methodologies with their pros and cons.<\/span><\/p>\n<div class=\"highlited-sec\">\n<h3><span>We answer all these <strong><i>questions and more<\/i><\/strong> in this blog:<\/span><\/h3>\n<ul>\n<li><a href=\"#section0\">Top SDLC Methodologies<\/a><\/li>\n<li><a href=\"#section1\">1. Waterfall Model<\/a><\/li>\n<li><a href=\"#section2\">2. Rational Unified Process<\/a><\/li>\n<li><a href=\"#section3\">3. Joint Application Development<\/a><\/li>\n<li><a href=\"#section4\">4. Spiral Model<\/a><\/li>\n<li><a href=\"#section5\">5. Prototype Methodology<\/a><\/li>\n<li><a href=\"#section6\">6. Agile Software Development Methodology<\/a><\/li>\n<li><a href=\"#section7\">7. Scrum Development Methodology<\/a><\/li>\n<li><a href=\"#section8\">8. Extreme Programming Methodology<\/a><\/li>\n<li><a href=\"#section9\">9. Feature Driven Development<\/a><\/li>\n<li><a href=\"#section10\">10. Rapid Application Development<\/a><\/li>\n<li><a href=\"#section11\">11. Dynamic System Development Model Methodology<\/a><\/li>\n<li><a href=\"#section12\">12. Lean<\/a><\/li>\n<li><a href=\"#section13\">Waterfall<\/a><\/li>\n<li><a href=\"#section14\">Rational Unified Process<\/a><\/li>\n<li><a href=\"#section15\">Joint Application Development<\/a><\/li>\n<li><a href=\"#section16\">Spiral Model<\/a><\/li>\n<li><a href=\"#section17\">Prototype Methodology<\/a><\/li>\n<li><a href=\"#section18\">Agile Software Development Methodology<\/a><\/li>\n<li><a href=\"#section19\">Scrum Development Methodology<\/a><\/li>\n<li><a href=\"#section20\">Extreme Programming Methodology<\/a><\/li>\n<li><a href=\"#section21\">Feature Driven Development<\/a><\/li>\n<li><a href=\"#section22\">Rapid Application Development<\/a><\/li>\n<li><a href=\"#section23\">Dynamic System Development Model Methodology<\/a><\/li>\n<li><a href=\"#section24\">\u00c2&nbsp;Lean<\/a><\/li>\n<li><a href=\"#section25\">Wrapping up<\/a><\/li>\n<\/ul>\n<\/div>\n<h2><b>Top SDLC Methodologies<\/b><\/h2>\n<h3><span>1. Waterfall Model<\/span><\/h3>\n<ul>\n<li><a href=\"#two\">Pros 1.0.1<\/a><\/li>\n<li><a href=\"#three\">Cons 1.0.2<\/a><\/li>\n<\/ul>\n<h3><span><a href=\"#four\">2. Rational Unified<\/a><a href=\"#four\"> Process<\/a><\/span><\/h3>\n<ul>\n<li><a href=\"#five\">Pros 2.0.1<\/a><\/li>\n<li><a href=\"#six\">Cons 2.0.2<\/a><\/li>\n<\/ul>\n<h3><span><a href=\"#seven\">3. Joint Application Development<\/a><\/span><\/h3>\n<ul>\n<li><a href=\"#eight\">Pros 3.0.1<\/a><\/li>\n<li><a href=\"#nine\">Cons 3.0.2<\/a><\/li>\n<\/ul>\n<h3><span><a href=\"#ten\">4. Spiral Model<\/a><\/span><\/h3>\n<ul>\n<li><a href=\"#eleven\">Pros 4.0.1<\/a><\/li>\n<li><a href=\"#twelve\">Cons 4.0.2<\/a><\/li>\n<\/ul>\n<h3><span><a href=\"#thirteen\">5. Prototype Methodology<\/a><\/span><\/h3>\n<ul>\n<li><a href=\"#fourteen\">Pros 5.0.1<\/a><\/li>\n<li><a href=\"#fifteen\">Cons 5.0.2<\/a><\/li>\n<\/ul>\n<h3><span><a href=\"#sixteen\">6. Agile Software Development Methodology<\/a><\/span><\/h3>\n<ul>\n<li><a href=\"#seventeen\">Pros 6.0.1<\/a><\/li>\n<li><a href=\"#eighteen\">Cons 6.0.2<\/a><\/li>\n<\/ul>\n<h3><span><a href=\"#nineteen\">7. Scrum Development Methodology<\/a><\/span><\/h3>\n<ul>\n<li><a href=\"#twenty\">Pros 7.0.1<\/a><\/li>\n<li><a href=\"#twenty-one\">Cons 7.0.2<\/a><\/li>\n<\/ul>\n<h3><span><a href=\"#twenty-two\">8. Extreme Programming Methodology<\/a><\/span><\/h3>\n<ul>\n<li><a href=\"#twenty-three\">Pros 8.0.1<\/a><\/li>\n<li><a href=\"#twenty-four\">Cons 8.0.2<\/a><\/li>\n<\/ul>\n<h3><span><a href=\"#twenty-five\">9. Feature Driven Development<\/a><\/span><\/h3>\n<ul>\n<li><a href=\"#twenty-six\">Pros 9.0.1<\/a><\/li>\n<li><a href=\"#twenty-seven\">Cons 9.0.2<\/a><\/li>\n<\/ul>\n<h3><span><a href=\"#twenty-eight\">10. Rapid Application Development<\/a><\/span><\/h3>\n<ul>\n<li><a href=\"#twenty-nine\">Pros 10.0.1<\/a><\/li>\n<li><a href=\"#thirty\">Cons 10.0.2<\/a><\/li>\n<\/ul>\n<h3><span><a href=\"#thirty-one\">11. Dynamic System Development Model Methodology<\/a><\/span><\/h3>\n<ul>\n<li><a href=\"#thirty-two\">Pros 11.0.1<\/a><\/li>\n<li><a href=\"#thirty-three\">Cons 11.0.2<\/a><\/li>\n<\/ul>\n<h3><span><a href=\"#thirty-four\">12. Lean<\/a><\/span><\/h3>\n<ul>\n<li><a href=\"#thirty-five\">Pros 12.0.1<\/a><\/li>\n<li><a href=\"#thirty-six\">Cons 12.0.2<\/a><\/li>\n<\/ul>\n<h2 id=\"one\"><b>Waterfall<\/b><\/h2>\n<p><img decoding=\"async\" class=\"alignnone wp-image-3493 size-full\" src=\"https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-Methodology_Waterfall.jpg\" alt=\"waterfall model\" width=\"100%\" srcset=\"https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-Methodology_Waterfall.jpg 1200w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-Methodology_Waterfall-300x170.jpg 300w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-Methodology_Waterfall-768x435.jpg 768w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-Methodology_Waterfall-1024x580.jpg 1024w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-Methodology_Waterfall-460x260.jpg 460w\" sizes=\"(max-width: 706px) 89vw, (max-width: 767px) 82vw, 740px\" \/><\/p>\n<p><span style=\"font-weight: 400;\">Waterfall Model is among the traditional SDLC methodologies. In fact, it is the oldest, most rigid and even easiest to understand. The idea here is quite simple: develop one phase of the project completely and move on to the next. Develop the new phase and advance to the next one. In this way, the project progresses and moves forward in a linear flow. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">And as per the <\/span><a href=\"https:\/\/searchsoftwarequality.techtarget.com\/definition\/waterfall-model\" target=\"_blank\" rel=\"nofollow noopener\"><span style=\"font-weight: 400;\">traditional waterfall model<\/span><\/a>,\u00a0<span style=\"font-weight: 400;\">any changes or modifications can\u2019t be performed<\/span>\u00a0<span style=\"font-weight: 400;\">once a phase of the project is developed completely. This SDLC methodology is best fitted for small projects where deliverables can be defined clearly.<\/span><\/p>\n<h3><b id=\"two\">Pros<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">1. Waterfall model is easy to understand due to its simple linear structure<\/span><\/p>\n<p><span style=\"font-weight: 400;\">2. It helps to define the goals and deliverables at the early stage of the project<\/span><\/p>\n<p><span style=\"font-weight: 400;\">3. Project management is simple and effective as there are no unnecessary changes<\/span><\/p>\n<p><span style=\"font-weight: 400;\">4. This model works effectively with smaller projects where the requirements are clearly<\/span><\/p>\n<p><span style=\"font-weight: 400;\">5. Each stage are clearly defined and understood<\/span><\/p>\n<h3><b id=\"three\">Cons<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">1. Definitely not a great choice complex and long-term project<\/span><\/p>\n<p><span style=\"font-weight: 400;\">2. Impossible to make changes at the later stage<\/span><\/p>\n<p><span style=\"font-weight: 400;\">3. This SDLC model doesn&#8217;t work for maintenance type project<\/span><\/p>\n<p><span style=\"font-weight: 400;\">4. Successful execution of the project depends on precise requirements<\/span><\/p>\n<p><span style=\"font-weight: 400;\">5. No working model of the software until the end of the life cycle<\/span><\/p>\n<h2 id=\"four\"><strong>Rational Unified Process<\/strong><\/h2>\n<p><img decoding=\"async\" class=\"alignnone wp-image-3492 size-full\" src=\"https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-methodologies_Rational-Unified-Process.jpg\" alt=\"Rational Unified Process\" width=\"100%\" srcset=\"https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-methodologies_Rational-Unified-Process.jpg 1116w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-methodologies_Rational-Unified-Process-300x192.jpg 300w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-methodologies_Rational-Unified-Process-768x491.jpg 768w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-methodologies_Rational-Unified-Process-1024x655.jpg 1024w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-methodologies_Rational-Unified-Process-406x260.jpg 406w\" sizes=\"(max-width: 706px) 89vw, (max-width: 767px) 82vw, 740px\" \/><\/p>\n<p><span style=\"font-weight: 400;\">Introduced by Rational Software, a subsidiary of IBM, Rational Unified Process \u00a0is one of the iterative SDLC methodologies<\/span><\/p>\n<p><a href=\"https:\/\/www.ibm.com\/developerworks\/rational\/library\/content\/03July\/1000\/1251\/1251_bestpractices_TP026B.pdf\" target=\"_blank\" rel=\"nofollow noopener\"><span style=\"font-weight: 400;\">IBM \u00a0defines<\/span><\/a><span style=\"font-weight: 400;\"> RUP &#8211; <em>\u201cThe Rational Unified Process\u00ae is a Software Engineering Process. It provides a disciplined approach to assigning tasks and responsibilities within a development organization. Its goal is to ensure the production of high-quality software that meets the needs of its end-users, within a predictable schedule and budget.\u201d<\/em><\/span><\/p>\n<p><span style=\"font-weight: 400;\">RUP divides the development process into four different phases namely <strong>Inception, Elaboration, Construction and Transition<\/strong>. Each of these phases goes through nine different stages shown in the figure above.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">By doing so it lays organized guidelines and structured templates to follow during the development process. Further, providing a specified plan at every phase helps in utilizing the available resources in an efficient and judiciously way. <\/span><\/p>\n<h3><b id=\"five\">Pros<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">1. This SDLC methodology puts emphasis on maintaining precise documentation<\/span><\/p>\n<p><span style=\"font-weight: 400;\">2. It reuses the components, thus saves the development time significantly<\/span><\/p>\n<p><span style=\"font-weight: 400;\">3. Ample amount of resources and literature is dispensed by its creators<\/span><\/p>\n<p><span style=\"font-weight: 400;\">4. The adaptive nature makes it easier to deal with changing customer needs and project requirements<\/span><\/p>\n<h3><b id=\"six\">Cons<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">1. For projects with new technology, the components can\u2019t be reused and hence time spends on development can&#8217;t be saved<\/span><\/p>\n<p><span style=\"font-weight: 400;\">2. It is a relatively complex methodology which requires expert developers<\/span><\/p>\n<p><span style=\"font-weight: 400;\">3. Despite the unfathomable resources available, RUP \u00a0is reasonably complicated model to understand<\/span><\/p>\n<h2 id=\"seven\"><b>Joint Application Development<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Joint Application Development was introduced in the early 70s as a software development methodology. However, due to its attribute to give more importance to business issues and solving them by involving the end user, instead of merely focusing on the technical aspects made it viable for any kind of projects.<\/span><\/p>\n<p><a href=\"https:\/\/en.wikipedia.org\/wiki\/Joint_application_design\" target=\"_blank\" rel=\"nofollow noopener\"><span style=\"font-weight: 400;\">This methodology<\/span><\/a><span style=\"font-weight: 400;\"> works on a simple philosophy &#8211; involving the client and end-user in the development process results in a project that is more aligned and suitable to their needs.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Joint Application Development Model brings the developers, clients and other stakeholders together through a series of meetings and called <em>JAD sessions.<\/em> These collaborative workshops help to define the requirements more clearly and from different viewpoints of business, end-user as well as developers.<\/span><\/p>\n<h3><b id=\"eight\">Pros<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">1. Identifies and lowers the risks through the collaboration of different parties<\/span><\/p>\n<p><span style=\"font-weight: 400;\">2. Requirements are well defined and clearly understood<\/span><\/p>\n<p><span style=\"font-weight: 400;\">3. Maintains continuous and proper communication between clients and developers<\/span><\/p>\n<p><span style=\"font-weight: 400;\">4. The open discussion with key members and customers also helps to diagnose any kind of errors at the initial stage. This results in quality and speedy development.<\/span><\/p>\n<h3><b id=\"nine\">Cons<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">1. This method is significantly time-consuming<\/span><\/p>\n<p><span style=\"font-weight: 400;\">2. Discussions and opinions among team members can also work as a distraction towards goal<\/span><\/p>\n<p><span style=\"font-weight: 400;\">3. Considerable investment in planning and requirements can increase the total cost<\/span><\/p>\n<h2 id=\"ten\"><b>Spiral Model<\/b><\/h2>\n<p><img decoding=\"async\" loading=\"lazy\" class=\"alignnone wp-image-3516 size-full\" src=\"https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-Model_Spiral.jpg\" alt=\"spiral model\" width=\"1597\" height=\"970\" srcset=\"https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-Model_Spiral.jpg 1597w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-Model_Spiral-300x182.jpg 300w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-Model_Spiral-768x466.jpg 768w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-Model_Spiral-1024x622.jpg 1024w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-Model_Spiral-428x260.jpg 428w\" sizes=\"(max-width: 706px) 89vw, (max-width: 767px) 82vw, 740px\" \/><\/p>\n<p>Spiral Model is<span style=\"font-weight: 400;\"> considered to be one of the best Software Development Life Cycle methodologies for a large and complex project.\u00a0<\/span><span style=\"font-weight: 400;\">It is an amalgamation of the two methodologies Waterfall Model and Prototyping Model.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">If you look at its diagram, you can see that the spiral has different loops known as phases.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Each phase passes through four different quadrants (stages) and keeps on repeating until the final product is developed.<\/span><\/p>\n<p><span style=\"font-weight: 400;\"> Each quadrant represents different tasks such as <strong>determination of requirement, analysing risks, engineering and planning<\/strong>. Thus, each phase of the project passes through.\u00a0<\/span><span style=\"font-weight: 400;\">The success of this model largely depends on the risk-analysis, so a high level of risk-analysing expertise is required.<\/span><\/p>\n<div class=\"suggested-read\">\n<h6><em><strong>Suggest read:\u00a0<a href=\"https:\/\/www.techuz.com\/blog\/what-is-sdlc-spiral-model\/\" target=\"_blank\" rel=\"noopener\">What is Spiral Model? A Simple Explanation of Spiral SDLC<\/a><\/strong><\/em><\/h6>\n<\/div>\n<h3><b id=\"eleven\"><br \/>\nPros<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">1. The spiral model is known for its flexibility as changes can be made on the later stage of the project<\/span><\/p>\n<p><span style=\"font-weight: 400;\">2. It is one the Software Development Life Cycle Methodologies that helps in mitigating the risk by analyzing and solving it beforehand <\/span><\/p>\n<p><span style=\"font-weight: 400;\">3. Clients are connected with the development team and project as they share the requirements and feedbacks of each phase<\/span><\/p>\n<p><span style=\"font-weight: 400;\">4. It is suitable for long-term and complex projects<\/span><\/p>\n<h3><b id=\"twelve\">Cons<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">1. Requires high risk-analysing expertise<\/span><\/p>\n<p><span style=\"font-weight: 400;\">2. The project takes a significantly long time to develop, increasing the overall expense of the project<\/span><\/p>\n<p><span style=\"font-weight: 400;\">3. It is complex to understand and implement<\/span><\/p>\n<p><span style=\"font-weight: 400;\">4. Since the number of iteration are unknown, the time required to complete the project remains a mystery<\/span><\/p>\n<h2><b>Prototype Methodology<\/b><\/h2>\n<p><img decoding=\"async\" class=\"alignnone wp-image-3495 size-full\" src=\"https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/Software-Development-Life-Cycle-Methodologies.jpg\" alt=\"prototyping model\" width=\"100%\" srcset=\"https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/Software-Development-Life-Cycle-Methodologies.jpg 1200w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/Software-Development-Life-Cycle-Methodologies-300x170.jpg 300w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/Software-Development-Life-Cycle-Methodologies-768x435.jpg 768w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/Software-Development-Life-Cycle-Methodologies-1024x579.jpg 1024w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/Software-Development-Life-Cycle-Methodologies-460x260.jpg 460w\" sizes=\"(max-width: 706px) 89vw, (max-width: 767px) 82vw, 740px\" \/><\/p>\n<p><a href=\"https:\/\/www.tutorialspoint.com\/sdlc\/sdlc_software_prototyping.htm\" target=\"_blank\" rel=\"nofollow noopener\"><span style=\"font-weight: 400;\">Prototyping model<\/span><\/a><span style=\"font-weight: 400;\"> is one of the most used Software Development Life Cycle Methodologies. As per the name suggests, prototypes are created to visualize the functionality and components of the software. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">In this methodology, a working prototype of the web application is created before initiating the actual development. These prototypes are sent to the customer for feedback and then necessary changes are made. This cycle of prototyping and updating as per customer&#8217;s feedback is repeated till the accurate prototype is achieved for the development. <\/span><\/p>\n<h3><b id=\"fourteen\">Pros<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">1. During the entire cycle, the clients stay in the loop. Thus, transparency during the development is maintained<\/span><\/p>\n<p><span style=\"font-weight: 400;\">2. Prototyping Methodology is quite adaptive as any updates or new requirements are accommodated<\/span><\/p>\n<p><span style=\"font-weight: 400;\">3. It mitigates or eliminates \u00a0the risks before the actual product is developed<\/span><\/p>\n<p><span style=\"font-weight: 400;\">4. One can expect quality results with this SDLC process as any flaws can be identified and refined before the development initiates<\/span><\/p>\n<h3><b id=\"fifteen\">Cons<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">1. It can be comparatively costly as more time and resources are required for prototyping<\/span><\/p>\n<p><span style=\"font-weight: 400;\">2. Revisions and updates affect the project workflow and duration<\/span><\/p>\n<h2 id=\"sixteen\"><b>Agile Software Development Methodology<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Agile is among the modern breeds of Software Development Life Cycle Methodologies introduced to developing the utmost quality software. It was created in 2001 by 17 technologists with <\/span><a href=\"http:\/\/agilemanifesto.org\/\" target=\"_blank\" rel=\"nofollow noopener\"><span style=\"font-weight: 400;\">four main principles<\/span><\/a><span style=\"font-weight: 400;\"> at its core:<\/span><\/p>\n<p><em>#1. Individuals and interactions over processes and tools<\/em><\/p>\n<p><em>#2. Working software over comprehensive documentation<\/em><\/p>\n<p><em>#3. Customer collaboration over contract negotiation<\/em><\/p>\n<p><em>#4. Responding to change over following a plan<\/em><\/p>\n<p><span style=\"font-weight: 400;\">Agile encourages building the project progressively rather than holistically. It follows the time-bound and iterative approach that builds software incrementally by updating and delivering small chunks instead of trying to deliver all at once. <\/span><span style=\"font-weight: 400;\">This incremental development is time-bound and the time period can be between a week to a month. <\/span><\/p>\n<h3><b id=\"seventeen\">Pros <\/b><\/h3>\n<p><span style=\"font-weight: 400;\">1. Highly adaptable to changes according to client and situation<\/span><\/p>\n<p><span style=\"font-weight: 400;\">2. Clients and customers are in direct communication providing transparency in the development process<\/span><\/p>\n<p><span style=\"font-weight: 400;\">3. Agile methodology mitigates the risks by updating the software with each iteration<\/span><\/p>\n<h3><b id=\"eighteen\">Cons<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">1. No adequate documentation as the methodology deals with the functionality of the software<\/span><\/p>\n<p><span style=\"font-weight: 400;\">2. At times, it can go off track due to less focus on planning<\/span><\/p>\n<h2 id=\"nineteen\"><b>Scrum Development Methodology<\/b><\/h2>\n<p><img decoding=\"async\" class=\"alignnone wp-image-3496 size-full\" src=\"https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/software-life-cycle_Scrum.jpg\" alt=\"Scrum Development Methodology\" width=\"100%\" srcset=\"https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/software-life-cycle_Scrum.jpg 1200w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/software-life-cycle_Scrum-300x170.jpg 300w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/software-life-cycle_Scrum-768x435.jpg 768w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/software-life-cycle_Scrum-1024x579.jpg 1024w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/software-life-cycle_Scrum-460x260.jpg 460w\" sizes=\"(max-width: 706px) 89vw, (max-width: 767px) 82vw, 740px\" \/><\/p>\n<p><span style=\"font-weight: 400;\">Scrum is another popular Agile SDLC framework widely used by the dev team. Usually people consider it as a methodology; however, <\/span><a href=\"https:\/\/en.wikipedia.org\/wiki\/Scrum_(software_development)\" target=\"_blank\" rel=\"nofollow noopener\"><span style=\"font-weight: 400;\">Scrum<\/span><\/a><span style=\"font-weight: 400;\"> is a framework that that uses Agile methodology for the project development. \u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The project is developed in series iterations and sprints which are time-bound between a week to a month. And its progress is gauged on daily basis.<\/span><\/p>\n<p><em><span style=\"font-weight: 400;\">(In Scrum, the term \u201csprint\u201d is used for one development cycle generally known as iteration.)<\/span><\/em><\/p>\n<p><span style=\"font-weight: 400;\">Each sprint initiates with a meeting that plans the list of tasks to execute. i.e deliverables. Then the team starts working on the plan starting from ideation, coding, testing, integration and so on until the product is developed. And at the end of each day, a Scrum Meeting is held between the client, team and Scrum Master updating about the progress of daily tasks. <\/span><\/p>\n<h3><b id=\"twenty\">Pros<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">1. Time and money are judicially and effectively utilized <\/span><\/p>\n<p><span style=\"font-weight: 400;\">2. Projects are managed effectively by dividing it into sprints<\/span><\/p>\n<p><span style=\"font-weight: 400;\">3. Daily scrum meetings help clients to stay updated about the progress and the team stays focused<\/span><\/p>\n<p><span style=\"font-weight: 400;\">4. As a part of the Agile methodology, it is quite flexible to changes <\/span><\/p>\n<p><span style=\"font-weight: 400;\">5. Scrum works extremely well with small teams<\/span><\/p>\n<h3><b id=\"twenty-one\">Cons<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">1. Using scrum with a large team can be a daunting task<\/span><\/p>\n<p><span style=\"font-weight: 400;\">2. Highly experienced and dedicated team members are quintessential<\/span><\/p>\n<p><span style=\"font-weight: 400;\">3. Daily meetings and updates can\u00a0sometimes\u00a0 get daunting\u00a0<\/span><\/p>\n<h2 id=\"twenty-two\"><b>Extreme Programming Methodology<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Extreme Programming Methodology accentuates on adaptability and customer satisfaction. The idea here is to adapt to the ever-changing requirements of the project during the life cycle rather than defining the requirements initially and resisting change at the later stage. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">This SDLC Methodology has gained significant favours from varied software and web development companies, as it provides high customer satisfaction and enables the developers to execute the required modifications, making the product impeccable. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">Apart from adaptability, the main goal of <\/span><a href=\"http:\/\/www.extremeprogramming.org\" target=\"_blank\" rel=\"nofollow noopener\"><span style=\"font-weight: 400;\">XP methodology<\/span><\/a><span style=\"font-weight: 400;\"> is to lower the cost incurred during the changes, which are generally quite high in case of traditional methodologies. \u00a0Even this methodology lives by a set of values and principles:<\/span><\/p>\n<p><em><span style=\"font-weight: 400;\">#1. Simplicity<\/span><\/em><\/p>\n<p><em><span style=\"font-weight: 400;\">#2. Streamlined Communication<\/span><\/em><\/p>\n<p><em><span style=\"font-weight: 400;\">#3. Feedback<\/span><\/em><\/p>\n<p><em><span style=\"font-weight: 400;\">#4. Respect<\/span><\/em><\/p>\n<p><em><span style=\"font-weight: 400;\">#5. Courage<\/span><\/em><\/p>\n<h3><b id=\"twenty-three\">Pros<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">1. Feedback from the client and flexibility to adapt the changes<\/span><\/p>\n<p><span style=\"font-weight: 400;\">2. Its core principles not only focuses on the client but also on employee satisfaction<\/span><\/p>\n<p><span style=\"font-weight: 400;\">3. The customer is constantly involved during the project and thus, can witness the progress<\/span><\/p>\n<p>4.\u00a0<span style=\"font-weight: 400;\">\u00a0Focuses on reducing the cost of the project<\/span><\/p>\n<div class=\"suggested-read\">\n<h6><em><strong>Suggested read:\u00a0<a href=\"https:\/\/www.techuz.com\/blog\/how-much-does-it-cost-to-develop-a-web-application\/\" target=\"_blank\" rel=\"noopener\">How Much Does it Cost to Develop a Web Application?<\/a><\/strong><\/em><\/h6>\n<\/div><br><\/br><h3><b id=\"twenty-four\">Cons<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">1. Many experts consider it to be a code-centric methodology and less of design-centric<\/span><\/p>\n<p><span style=\"font-weight: 400;\">2. Requires a highly disciplined team and frequent client feedback<\/span><\/p>\n<p><span style=\"font-weight: 400;\">3. Frequent meetings are essential as there is less documentation of the requirements during the initial stage. This arises the need of team member to be present together and may not be effective remote teams<\/span><\/p>\n<div class=\"suggested-read\">\n<h6><em><strong>Suggested Read:\u00a0<a href=\"https:\/\/www.techuz.com\/blog\/best-collaboration-tools-to-effectively-manage-a-remote-team\/\" target=\"_blank\" rel=\"noopener\">Best Collaboration Tools to Effectively Manage a Remote Team<\/a><\/strong><\/em><\/h6>\n<\/div>\n<h2 id=\"twenty-five\"><b>Feature Driven Development<\/b><\/h2>\n<p><img decoding=\"async\" class=\"alignnone wp-image-3494 size-full\" src=\"https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-model_Feature-Driven-Development.jpg\" alt=\"Feature Driven Development\" width=\"100%\" srcset=\"https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-model_Feature-Driven-Development.jpg 1200w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-model_Feature-Driven-Development-300x170.jpg 300w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-model_Feature-Driven-Development-768x435.jpg 768w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-model_Feature-Driven-Development-1024x580.jpg 1024w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-model_Feature-Driven-Development-460x260.jpg 460w\" sizes=\"(max-width: 706px) 89vw, (max-width: 767px) 82vw, 740px\" \/><\/p>\n<p><span style=\"font-weight: 400;\">The agile process we discussed previously &#8211;\u00a0<\/span><span style=\"font-size: 1rem;\"><em>Scrum and Extreme Programming<\/em> wo<\/span><span style=\"font-size: 1rem;\">rk great with small teams of skilled people. However, when it comes to implementing with a large team, they are not an ideal choice.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The reason being &#8211; large teams face challenges such as effective communication, frequent meetings and updates, identifying and gauging the skills of the members and more. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">Here, the <\/span><a href=\"https:\/\/en.wikipedia.org\/wiki\/Feature-driven_development\" target=\"_blank\" rel=\"nofollow noopener\"><span style=\"font-weight: 400;\">Feature Driven Development<\/span><\/a><span style=\"font-weight: 400;\"> or FDD comes into the picture as an SDLC methodology following Agile Manifesto that also works great with large teams.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">As the name suggests, \u201cFeatures\u201d play an important role in Feature Driven Development. The project is divided into chunks as per its features and functionalities. And then planning, design, development and testing are in accordance with these features. Moreover, it also follows the iterative and incremental process.<\/span><\/p>\n<h3><b id=\"twenty-six\">Pros<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">1. Feature Driven Development makes it easier to develop a large project effectively<\/span><\/p>\n<p><span style=\"font-weight: 400;\">2. It also offers the client to gauge the progress easily<\/span><\/p>\n<p><span style=\"font-weight: 400;\">3. FDD is built on industry standards and follows the best practices for Software Development<\/span><\/p>\n<p><span style=\"font-weight: 400;\">4. Can employ different-teams simultaneously working on different features on the same project<\/span><\/p>\n<h3><b id=\"twenty-seven\">Cons<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">1. It is built for larger projects and team. So, using this methodology for smaller projects is not suitable<\/span><\/p>\n<p><span style=\"font-weight: 400;\">2. The success is dependent on the leading developers; any kind of their inefficiency can lead to failure<\/span><\/p>\n<p><span style=\"font-weight: 400;\">3. Lack of proper written documents about the project and development<\/span><\/p>\n<h2 id=\"twenty-eight\"><strong>Rapid Application Development<\/strong><\/h2>\n<p><img decoding=\"async\" class=\"alignnone wp-image-3490 size-full\" src=\"https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/Rapid-Application-Development.jpg\" alt=\"Rapid Application Development\" width=\"100%\" srcset=\"https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/Rapid-Application-Development.jpg 1200w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/Rapid-Application-Development-300x170.jpg 300w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/Rapid-Application-Development-768x435.jpg 768w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/Rapid-Application-Development-1024x580.jpg 1024w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/Rapid-Application-Development-460x260.jpg 460w\" sizes=\"(max-width: 706px) 89vw, (max-width: 767px) 82vw, 740px\" \/><\/p>\n<p><a href=\"http:\/\/blog.capterra.com\/what-is-rapid-application-development\/\" target=\"_blank\" rel=\"nofollow noopener\"><span style=\"font-weight: 400;\">Rapid Application Development<\/span><\/a><span style=\"font-weight: 400;\"> is an SDLC methodology to accelerate the development with rapid prototyping of the product. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">It is an iterative model that focuses more on functional software and prototyping and less on planning. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">There are four main phases of RAD namely, <strong>requirement planning, user design, construction and cutover<\/strong>. The first two being the most important as they go through several iterations until the product is fully refined as per the user requirements. <\/span><\/p>\n<h3><b id=\"twenty-nine\">Pros<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">1. Tasks become easy and achievable by modularizing the project<\/span><\/p>\n<p><span style=\"font-weight: 400;\">2. The functional model of the \u00a0product can be reviewed at an early stage<\/span><\/p>\n<p><span style=\"font-weight: 400;\">3. The user remains in the loop while the development and provides feedback<\/span><\/p>\n<h3><b id=\"thirty\">Cons<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">1. Requires highly skilled designers and developers with forte in the application area<\/span><\/p>\n<p><span style=\"font-weight: 400;\">2. Highly dependent on a strong team.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">3. It would work best only with the systems and projects that can be divided into small chunks<\/span><\/p>\n<p><span style=\"font-weight: 400;\">4. RAD is highly expensive and is not recommended for small budget projects<\/span><\/p>\n<h2 id=\"thirty-one\"><strong>Dynamic System Development Model Methodology<\/strong><\/h2>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-3489\" src=\"https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/DSDM.jpg\" alt=\"\" width=\"100%\" srcset=\"https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/DSDM.jpg 1200w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/DSDM-300x170.jpg 300w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/DSDM-768x435.jpg 768w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/DSDM-1024x579.jpg 1024w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/DSDM-460x260.jpg 460w\" sizes=\"(max-width: 706px) 89vw, (max-width: 767px) 82vw, 740px\" \/><\/p>\n<p><span style=\"font-weight: 400;\">RAD methodology was quite swift but being unstructured it created chaos in development. This fueled the inception of a new Agile Methodology known as <\/span><a href=\"https:\/\/en.wikipedia.org\/wiki\/Dynamic_systems_development_method\" target=\"_blank\" rel=\"nofollow noopener\"><span style=\"font-weight: 400;\">Dynamic Systems Development Model<\/span><\/a><span style=\"font-weight: 400;\"> or feasible to say DSDM.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Developed by a group of project managers in 1994, DSDM is an iterative methodology that focuses on continuous user involvement along with developing it on budget and within the allotted time constraint. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">It provides a framework for software development that passes through 4 phases. They are:<\/span><\/p>\n<p><em><span style=\"font-weight: 400;\">#1. Feasibility and business study<\/span><\/em><\/p>\n<p><em><span style=\"font-weight: 400;\">#2. Functional model \/ prototype iteration<\/span><\/em><\/p>\n<p><em><span style=\"font-weight: 400;\">#3. Design and build iteration<\/span><\/em><\/p>\n<p><em><span style=\"font-weight: 400;\">#4. Implementation<\/span><\/em><\/p>\n<h3><b id=\"thirty-two\">Pros<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">1. Adheres to budget and time of the project<\/span><\/p>\n<p><span style=\"font-weight: 400;\">2. Clients and end-users stay updated with the development<\/span><\/p>\n<p><span style=\"font-weight: 400;\">3. It is quite flexible to the changes<\/span><\/p>\n<h3><b id=\"thirty-three\">Cons<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">1. Just like RAD, it requires high technical as well as business expertise <\/span><\/p>\n<p><span style=\"font-weight: 400;\">2. It is of no use without proper user involvement<\/span><\/p>\n<p><span style=\"font-weight: 400;\">3. This methodology is uncommon making it hard to understand and implement<\/span><\/p>\n<h2 id=\"thirty-four\"><b>\u00a0Lean<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Lean shares quite a few similarities with Agile. In fact, lean is considered to be the model under the umbrella of Agile principles; although, it was coined way before the Agile Manifesto was introduced. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">It is based on seven principles and values namely, <strong>eliminate waste, amplify learning, decide as late as possible, deliver as fast as possible, empower the team, build integrity in <\/strong>and <strong>see the whole. <\/strong><\/span><\/p>\n<p><span style=\"font-weight: 400;\">At its core, the main aim of <\/span><a href=\"https:\/\/en.wikipedia.org\/wiki\/Lean_software_development\" target=\"_blank\" rel=\"nofollow noopener\"><span style=\"font-weight: 400;\">this SDLC methodology<\/span><\/a><span style=\"font-weight: 400;\"> is to elevating the customer value and eliminating the wastage, i.e. the unproductive activities. This makes is a great choice for the projects with a tight budget. <\/span><\/p>\n<p><img decoding=\"async\" class=\"alignnone wp-image-3546 size-full\" src=\"https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-Methdodlogies_Lean-1.jpg\" alt=\"LEAN SDLC Methodology\" width=\"100%\" srcset=\"https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-Methdodlogies_Lean-1.jpg 1200w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-Methdodlogies_Lean-1-300x170.jpg 300w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-Methdodlogies_Lean-1-768x435.jpg 768w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-Methdodlogies_Lean-1-1024x580.jpg 1024w, https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-Methdodlogies_Lean-1-460x260.jpg 460w\" sizes=\"(max-width: 706px) 89vw, (max-width: 767px) 82vw, 740px\" \/><\/p>\n<h3><b id=\"thirty-five\">Pros<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">1. Saves time and money by eliminating wastage<\/span><\/p>\n<p><span style=\"font-weight: 400;\">2. Earlier product delivery to its value of \u201cDeliver as fast as possible\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">3. Lean can work great when the resources and time is scare<\/span><\/p>\n<h3><b id=\"thirty-six\">Cons<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">1. Requires proficient team that as the process is highly team-dependent<\/span><\/p>\n<p><span style=\"font-weight: 400;\">2. Decisions are to be made quickly during the process<\/span><\/p>\n<p><span style=\"font-weight: 400;\">3. There are chances that the team may get distracted due multi-tasking and varied responsibilities in small teams<\/span><\/p>\n<h2><b>Wrapping up<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Now you know a dozen SDLC Methodologies. Each has a different use case, peculiar traits, forte and of course weakness. Some focusing on the process while other have end-user at their core. Some are conventional and rigid while some have evolved over time to serve as per the changing requirements. Choosing the right methodology according to the project needs and the product will definitely elevate the success rate of your project. Or if you are still unsure which SDLC methodology will work for you, feel free to <\/span><a href=\"https:\/\/www.techuz.com\/contact-us\/\" target=\"_blank\" rel=\"nofollow noopener\"><span style=\"font-weight: 400;\">contact us<\/span><\/a><span style=\"font-weight: 400;\">. <\/span><\/p><br><\/br>","protected":false},"excerpt":{"rendered":"<p>As a developer, you might spit out few fancy SDLC Methodologies that are at the top of your mind. Or as a client, you may recall some sweet-sounding terms &#8211; \u201cAgile&#8217;, \u201cLean&#8217;, \u201cDynamic System Development Model&#8217; (alright, this one\u2019s not so sweet) or &#8216;Spiral&#8217;, because the web development company you hired practices it or at &hellip; <\/p>\n<p class=\"link-more\"><a href=\"https:\/\/www.techuz.com\/blog\/top-12-sdlc-methodologies-with-pros-and-cons\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Top 12 SDLC Methodologies with Pros and Cons&#8221;<\/span><\/a><\/p>\n","protected":false},"author":8,"featured_media":3515,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[13,14,5],"tags":[193,194],"better_featured_image":{"id":3515,"alt_text":"top SDLC Methdodlogies with pros and cons","caption":"","description":"","media_type":"image","media_details":{"width":1200,"height":680,"file":"2018\/10\/SDLC-Methdodlogies.jpg","sizes":{"thumbnail":{"file":"SDLC-Methdodlogies-150x150.jpg","width":150,"height":150,"mime-type":"image\/jpeg","source_url":"https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-Methdodlogies-150x150.jpg"},"medium":{"file":"SDLC-Methdodlogies-300x170.jpg","width":300,"height":170,"mime-type":"image\/jpeg","source_url":"https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-Methdodlogies-300x170.jpg"},"medium_large":{"file":"SDLC-Methdodlogies-768x435.jpg","width":768,"height":435,"mime-type":"image\/jpeg","source_url":"https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-Methdodlogies-768x435.jpg"},"large":{"file":"SDLC-Methdodlogies-1024x580.jpg","width":1024,"height":580,"mime-type":"image\/jpeg","source_url":"https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-Methdodlogies-1024x580.jpg"},"blog_list":{"file":"SDLC-Methdodlogies-460x260.jpg","width":460,"height":260,"mime-type":"image\/jpeg","source_url":"https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-Methdodlogies-460x260.jpg"},"alm-thumbnail":{"file":"SDLC-Methdodlogies-150x150.jpg","width":150,"height":150,"mime-type":"image\/jpeg","source_url":"https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-Methdodlogies-150x150.jpg"},"twentyseventeen-thumbnail-avatar":{"file":"SDLC-Methdodlogies-100x100.jpg","width":100,"height":100,"mime-type":"image\/jpeg","source_url":"https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-Methdodlogies-100x100.jpg"}},"image_meta":{"aperture":"0","credit":"","camera":"","caption":"","created_timestamp":"0","copyright":"","focal_length":"0","iso":"0","shutter_speed":"0","title":"","orientation":"0","keywords":[]}},"post":3476,"source_url":"https:\/\/www.techuz.com\/blog\/wp-content\/uploads\/2018\/10\/SDLC-Methdodlogies.jpg"},"_links":{"self":[{"href":"https:\/\/www.techuz.com\/blog\/wp-json\/wp\/v2\/posts\/3476"}],"collection":[{"href":"https:\/\/www.techuz.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.techuz.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.techuz.com\/blog\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/www.techuz.com\/blog\/wp-json\/wp\/v2\/comments?post=3476"}],"version-history":[{"count":79,"href":"https:\/\/www.techuz.com\/blog\/wp-json\/wp\/v2\/posts\/3476\/revisions"}],"predecessor-version":[{"id":7447,"href":"https:\/\/www.techuz.com\/blog\/wp-json\/wp\/v2\/posts\/3476\/revisions\/7447"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.techuz.com\/blog\/wp-json\/wp\/v2\/media\/3515"}],"wp:attachment":[{"href":"https:\/\/www.techuz.com\/blog\/wp-json\/wp\/v2\/media?parent=3476"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.techuz.com\/blog\/wp-json\/wp\/v2\/categories?post=3476"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.techuz.com\/blog\/wp-json\/wp\/v2\/tags?post=3476"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}