├── 022152.ppm ├── 2115.jpeg ├── 2115.png ├── Book.jpg ├── LICENSE ├── README.md ├── SDLC.pdf ├── SDLC2 ├── SDLC-01.jpg ├── SDLC-02.jpg ├── SDLC-03.jpg ├── SDLC-04.jpg ├── SDLC-05.jpg ├── SDLC-06.jpg ├── SDLC-07.jpg ├── SDLC-08.jpg ├── SDLC-09.jpg ├── SDLC-10.jpg ├── SDLC-11.jpg ├── SDLC-12.jpg ├── SDLC-13.jpg ├── SDLC-14.jpg ├── SDLC-15.jpg ├── SDLC-16.jpg ├── SDLC-17.jpg ├── SDLC-18.jpg ├── SDLC-19.jpg ├── SDLC-20.jpg ├── SDLC-21.jpg ├── SDLC-22.jpg ├── SDLC-23.jpg ├── SDLC-24.jpg ├── SDLC-25.jpg ├── SDLC-26.jpg ├── SDLC-27.jpg └── SDLC-28.jpg ├── ghhggh.gif ├── mastering-the-7-stages-of-the-system-development-life-cycle-1.jpg └── sdlc-models.png /022152.ppm: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/022152.ppm -------------------------------------------------------------------------------- /2115.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/2115.jpeg -------------------------------------------------------------------------------- /2115.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/2115.png -------------------------------------------------------------------------------- /Book.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/Book.jpg -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "[]" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright [yyyy] [name of copyright owner] 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | ## SDLC Interview Question :) 🦖 2 | ## The Phases of the Software Development Lifecycle🚱 3 | Welcome images 4 | 5 | The software development lifecycle (SDLC) is a framework that development teams use to produce high-quality software in a systematic and cost-effective way. The SDLC methodology is used by both large and small software organizations. 6 | 7 | Developers often think that only one of the seven stages of the system development life cycle applies to them. But, to work at their best, everyone in a software development team should have a good working knowledge of all stages of the SDLC. 8 | 9 | Below, we discuss each stage and where it fits into the bigger picture. We also provide examples of expected output, describe team members needed, and share resources for individual learning. 10 | 11 | Welcome images 12 | 13 | ## 1. Planning Stage 🦖 14 | 15 | In any software development project, planning comes first. Before getting started, it is important to make sure the project has enough people and financial backing. You can have the best idea in the world, but if you don’t have people or money, moving forward will be a poor business decision. 16 | 17 | The planning phase involves the entire project team. The outputs from the planning stage include project plans, cost estimations, and procurement requirements. When you are finished, your plan should be something the entire team can understand. 18 | 19 | Here are resources for getting better at planning: 20 | 21 | Book: Software Estimation Without Guessing 22 | 23 | Course: Project Planning & Management 24 | 25 | Welcome images 26 | 27 | ## 2. Feasibility or Requirements Analysis Stage 🦖 28 | 29 | In feasibility analysis, your team ensures that the project requirements help the end-user of the system. 30 | 31 | Gathering requirements means talking to stakeholders and looking at as much relevant data as possible. At all times, you’ll want to consider the users and how workable the feature is. 32 | 33 | The outputs from the requirements analysis stage will vary depending on the methodology you are using. Regardless of whether your team is working with a formal requirements document or a list of tickets, everyone has to understand each need. 34 | 35 | At this stage, architects, developers, and product managers work together with relevant stakeholders. 36 | 37 | Resources for getting better at feasibility or requirements analysis include: 38 | 39 | Book: Mastering Software Project Requirements 40 | Blog: Seilevel on Requirements 41 | 42 | ## 3. Design and Prototyping Stage 🦖 43 | 44 | During the design phase, developers and designers prototype a feature or map out a solution. Prototyping is useful for getting early feedback and informing technical decisions. 45 | 46 | Without prototypes, there’s a risk that the team will waste time on production-ready solutions that don’t meet user needs. 47 | 48 | For some software development methodologies, the design phase needs specific output before a stakeholder can sign it off and more work can happen. 49 | 50 | When done well, the design and prototyping phase can produce tangible outputs that help drive decisions going forward. In web development teams, a prototype often serves to show that the functionality works, although it will still need polishing. 51 | 52 | The following are resources for getting better at design and prototyping: 53 | 54 | Video: Prototype Everything 55 | Book: Design Patterns 56 | 57 | ## 4. Software Development Stage 🦖 58 | 59 | Software development turns your project’s requirements and prototypes into working code. it’s the earliest phase in which you start to see something that resembles the final product. 60 | 61 | By the end of this stage, you will have a working feature to share with customers. 62 | 63 | Developers are the most involved during this phase. They will often need to confirm things with the product owner and the testers. 64 | 65 | Consider these resources for getting better at software development: 66 | 67 | Conferences: The Lead Developer 68 | Book: Adaptive Code 69 | Pro Tip: Code faster with TextExpander 70 | 71 | TextExpander makes it easy to save commonly-used code snippets, documentation comments, and more — then insert them anywhere you type with a simple shortcut or inline search. 72 | 73 | ## 5. Software Testing Stage 🦖 74 | 75 | During the software testing phase, testers put the code through its paces. 76 | 77 | Testers check for: 78 | 79 | Code quality 80 | That code meets the stated requirements 81 | That code is performant 82 | Evidence of secure development principals 83 | Some teams automate all their testing. Other teams test manually, but most do a combination of the two. 84 | 85 | The output of software testing is a better solution that meets edge cases and user needs. Developers can’t code for every eventuality; the fresh perspective that testing brings can help. 86 | 87 | Testers are the main people involved at this stage. They will often seek clarification from developers or product owners. 88 | 89 | Resources for getting better at software testing include: 90 | 91 | Book: Agile Testing 92 | Conference Videos: EuroSTAR Software Testing Conference 93 | 94 | ## 6. Implementation and Integration 🦖 95 | 96 | Often called ‘deployment’, the implementation phase takes code and puts it somewhere people can use. 97 | 98 | In simple projects, this will be as simple as deploying the code onto a web server. In large projects, this could involve integration with many different systems. 99 | 100 | The output from this stage is usable software. For some projects, this phase also encompasses the creation of documentation and marketing material. 101 | 102 | At this stage, the operations team focuses on deploying the software. The product owners work with content writers to produce documentation such as user manuals. 103 | 104 | Here are resources for getting better at implementation and integration: 105 | 106 | Book: The Phoenix Project 107 | Blog Post: How To Deploy Software 108 | 109 | ## 7. Operations and Maintenance 🦖 110 | 111 | In the operations and maintenance phase, developers watch software for bugs or defects. If they find one, they create a bug report. During maintenance, it is important to consider opportunities for when the development cycle starts over again. 112 | 113 | A sign that this phase is working well when developers are able to quickly identify and resolve problems. 114 | 115 | During this stage, support specialists will report issues, product owners will help prioritize them, and developers will work with testers to make improvements. 116 | 117 | Here are some resources for getting better at operations and maintenance: 118 | 119 | 120 | Welcome images 121 | 122 | Welcome images 123 | 124 | Welcome images 125 | 126 | Welcome images 127 | 128 | Welcome images 129 | 130 | Welcome images 131 | 132 | Welcome images 133 | 134 | Welcome images 135 | 136 | Welcome images 137 | 138 | Welcome images 139 | 140 | Welcome images 141 | 142 | Welcome images 143 | 144 | Welcome images 145 | 146 | Welcome images 147 | 148 | Welcome images 149 | 150 | Welcome images 151 | 152 | Welcome images 153 | 154 | Welcome images 155 | 156 | Welcome images 157 | 158 | Welcome images 159 | 160 | Welcome images 161 | 162 | Welcome images 163 | 164 | Welcome images 165 | 166 | Welcome images 167 | 168 | Welcome images 169 | 170 | Welcome images 171 | 172 | Welcome images 173 | 174 | Welcome images 175 | 176 | ## What is the Software Development Lifecycle? 177 | 178 | The software development lifecycle (SDLC) is a framework that development teams use to produce high-quality software in a systematic and cost-effective way. The SDLC methodology is used by both large and small software organizations. These teams follow development models ranging from agile to lean to waterfall and others. 179 | 180 | The software development lifecycle gives organizations a methodical, step-by-step approach to developing successful software. From gathering the initial requirements for a new product, through maintaining a mature product on the market, we’ll teach you how to employ SDLC. 181 | 182 | # Origins of the Software Development Lifecycle:- 183 | 184 | SDLC actually began as the “systems development lifecycle” in the 1960s. As Geoffrey Elliott explains in his book, Global Business Information Technology, large corporations developed the model to help manage complex business systems that required a lot of data processing and analysis. 185 | 186 | Over time, variations of the framework have been adopted for the development of hardware and software technology products and other complex projects. 187 | 188 | 189 | # The Phases of the Software Development Lifecycle:- 190 | 191 | Several versions of the software development lifecycle have evolved. Guru99, for example, uses a seven-phase SDLC framework that separates requirements collection and a feasibility study into two separate phases. Other organizations, such as Software Testing Help, combine these two steps into a single phase 1: “requirements gathering and analysis.” 192 | 193 | We’ve reviewed many variations of software development lifecycle models. The following six-phase framework seems to be the most straightforward. 194 | 195 | ## Phase 1: Plan 196 | The first stage of new software development will be to gather all relevant information from stakeholders and analyze this information to determine what will be feasible. 197 | 198 | This includes compiling requirements, studying user personas, and agreeing on the product’s purpose. During this phase, the team will also discuss the opportunities and risks of pursuing the project. This is why Software Testing Help refers to this phase as both requirements gathering and analysis. 199 | 200 | ## Phase 2: Design 201 | After the team has agreed on a broad set of requirements and goals for the product, the next step will be to create a design specification. This should answer the question, “How will we build this?” 202 | 203 | For a product team, this phase would include determining the priority order of the proposed work, building a product roadmap, and obtaining stakeholder agreement on it. This will help everyone on both the development and product teams get a clearer picture of what they are aiming for. 204 | 205 | ## Phase 3: Implement (or Code) 206 | This is the stage where the engineering team actually codes the product. At this stage, the development team translates the high-level overview communicated in the roadmap into a tactical set of assignments, due dates, and day-to-day work schedules. 207 | 208 | ## Phase 4: Test 209 | After the team has completed a version of the software, they will release it to a testing environment. Here, the QA team and the developers will test all areas of the application to spot any defects, bugs, or other problems. 210 | 211 | ## Phase 5: Deploy 212 | At this stage, the team is confident it has fixed all defects and that the software has been built to the agreed-upon goals and specifications. 213 | 214 | Now it’s time to release the software to the production environment. This means the product will be generally available for customers to buy and use. 215 | 216 | ## Phase 6: Maintain 217 | With the software now live and being used by customers, the development team’s focus will shift to maintaining it. 218 | 219 | The developers will need to be ready to address requests for enhancements, bug fixes, and new features. These requests will come from many sources—sales, executives, customers—but the product management team will determine which of these initiatives make it onto the product roadmap for developers to work on. 220 | 221 | ## What are the Benefits of the Software Development Lifecycle? 222 | 223 | Software development teams find many advantages from using the SDLC model, including: 224 | 225 | #Lowering the cost of software development. 226 | 227 | Improving the quality of the software that the organization delivers. 228 | Shortening development timelines by preventing after-the-fact fixes. 229 | Helping developers better understand what they are building and why. 230 | Ensuring all stakeholders have a chance to give their input in the early stages of development. 231 | Giving everyone on the cross-functional team an understanding of the costs and resources needed to complete the project. 232 | Because the software development lifecycle model requires the development team to complete each phase before moving on to the next, it helps ensure problems don’t become compounded during the process. Using this approach helps teams identify and deal with problems immediately. This minimizes their impact on both the cost of the project and the quality of the final software product that the developers deliver to the market. 233 | 234 | However, the software development lifecycle model also has potential downsides. These drawbacks can particularly affect agile and lean development organizations, but their risks are relevant to any software company using the SDLC framework. 235 | 236 | ## What are the Drawbacks of the Software Development Lifecycle? 237 | 238 | # It reduces communication and collaboration across departments. 239 | 240 | Because SDLC is a linear model, and the organization does not advance to the next step until the current step is complete, this approach can have the effect of creating information silos. 241 | 242 | The engineering team is the only team focused on the project, for example, during the implementation phase. That means the QA or UX team could miss out on important learning during this phase because they are not all part of a cross-functional team in constant communication throughout the development process. 243 | 244 | # It is process-heavy and does not allow much flexibility. 245 | 246 | Another complaint about the SDLC model is that it can make an organization overly dependent on the process. A key principle in agile development is “people over processes.” This empowers an agile team to make quick adjustments to its plan when needed 247 | 248 | With the SDLC framework, this is more difficult because the team agrees early on to follow a specific development plan. 249 | 250 | # It creates a single point of failure in the early stages. 251 | 252 | The team sets the entire product-development plan according to the initial requirements-gathering and analysis. However, this first phase can lead to a failed product if the team doesn’t properly assess the market’s needs. 253 | 254 | With an agile approach, by contrast, the organization continuously reviews its product’s progress and seeks regular feedback from users. As a result, the team is less likely to build an entire product or significant new functionality without knowing there is a market for it. 255 | 256 | From the drawbacks listed above, it might seem that agile development teams would find the SDLC framework ineffective. 257 | 258 | But the SDLC framework can and often is incorporated into the agile development methodology. Agile organizations break the proposed product into small development cycles called sprints. In each sprint, they will work through all of these phases quickly. 259 | 260 | # How Does the Software Development Lifecycle Work with Agile Sprints? 261 | 262 | The typical agile sprint is only two weeks or a month. The team will start each sprint with a sprint planning session. At this time, the cross-functional team reviews the backlog. Then, they determine a few strategically advantageous projects to work on and assign tasks. They will then focus only on those projects and test their work at the end of the sprint. Finally, they will move on to the next sprint. Breaking up the process this way allows agile organizations to quickly and frequently release new functionality to the market. This frees them from having to wait to build an entire product before releasing anything. 263 | 264 | In other words, an agile organization can successfully adapt the SDLC framework to its development model. 265 | 266 | This is why any software organization, using any development methodology, can benefit from using some form of the software development lifecycle model. 267 | 268 | For Book CLICK ME 269 | 270 | Buy this Book from Amazon.in :- 271 | The Complete Software Engineering from Basics to Advanced [Click For Book Purchage](https://www.amazon.in/Complete-Software-Engineering-Basics-Advanced/dp/B08NVJLGJ1 "The Complete Software Engineering from Basics to Advanced: Learn Software Engineering, SDLC, Software Project Management, Software requirements, Software Design Basics & more !"). 272 | 273 | ## Book: The DevOps Handbook 274 | ## Course: Software Maintenance 275 | -------------------------------------------------------------------------------- /SDLC.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/SDLC.pdf -------------------------------------------------------------------------------- /SDLC2/SDLC-01.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/SDLC2/SDLC-01.jpg -------------------------------------------------------------------------------- /SDLC2/SDLC-02.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/SDLC2/SDLC-02.jpg -------------------------------------------------------------------------------- /SDLC2/SDLC-03.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/SDLC2/SDLC-03.jpg -------------------------------------------------------------------------------- /SDLC2/SDLC-04.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/SDLC2/SDLC-04.jpg -------------------------------------------------------------------------------- /SDLC2/SDLC-05.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/SDLC2/SDLC-05.jpg -------------------------------------------------------------------------------- /SDLC2/SDLC-06.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/SDLC2/SDLC-06.jpg -------------------------------------------------------------------------------- /SDLC2/SDLC-07.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/SDLC2/SDLC-07.jpg -------------------------------------------------------------------------------- /SDLC2/SDLC-08.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/SDLC2/SDLC-08.jpg -------------------------------------------------------------------------------- /SDLC2/SDLC-09.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/SDLC2/SDLC-09.jpg -------------------------------------------------------------------------------- /SDLC2/SDLC-10.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/SDLC2/SDLC-10.jpg -------------------------------------------------------------------------------- /SDLC2/SDLC-11.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/SDLC2/SDLC-11.jpg -------------------------------------------------------------------------------- /SDLC2/SDLC-12.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/SDLC2/SDLC-12.jpg -------------------------------------------------------------------------------- /SDLC2/SDLC-13.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/SDLC2/SDLC-13.jpg -------------------------------------------------------------------------------- /SDLC2/SDLC-14.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/SDLC2/SDLC-14.jpg -------------------------------------------------------------------------------- /SDLC2/SDLC-15.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/SDLC2/SDLC-15.jpg -------------------------------------------------------------------------------- /SDLC2/SDLC-16.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/SDLC2/SDLC-16.jpg -------------------------------------------------------------------------------- /SDLC2/SDLC-17.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/SDLC2/SDLC-17.jpg -------------------------------------------------------------------------------- /SDLC2/SDLC-18.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/SDLC2/SDLC-18.jpg -------------------------------------------------------------------------------- /SDLC2/SDLC-19.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/SDLC2/SDLC-19.jpg -------------------------------------------------------------------------------- /SDLC2/SDLC-20.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/SDLC2/SDLC-20.jpg -------------------------------------------------------------------------------- /SDLC2/SDLC-21.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/SDLC2/SDLC-21.jpg -------------------------------------------------------------------------------- /SDLC2/SDLC-22.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/SDLC2/SDLC-22.jpg -------------------------------------------------------------------------------- /SDLC2/SDLC-23.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/SDLC2/SDLC-23.jpg -------------------------------------------------------------------------------- /SDLC2/SDLC-24.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/SDLC2/SDLC-24.jpg -------------------------------------------------------------------------------- /SDLC2/SDLC-25.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/SDLC2/SDLC-25.jpg -------------------------------------------------------------------------------- /SDLC2/SDLC-26.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/SDLC2/SDLC-26.jpg -------------------------------------------------------------------------------- /SDLC2/SDLC-27.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/SDLC2/SDLC-27.jpg -------------------------------------------------------------------------------- /SDLC2/SDLC-28.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/SDLC2/SDLC-28.jpg -------------------------------------------------------------------------------- /ghhggh.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/ghhggh.gif -------------------------------------------------------------------------------- /mastering-the-7-stages-of-the-system-development-life-cycle-1.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/mastering-the-7-stages-of-the-system-development-life-cycle-1.jpg -------------------------------------------------------------------------------- /sdlc-models.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rajeevranjancom/SDLC/2bbf460a47b96bab8b6c2f7d7e113fbaf5580525/sdlc-models.png --------------------------------------------------------------------------------