<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Sri Sai Charan on Medium]]></title>
        <description><![CDATA[Stories by Sri Sai Charan on Medium]]></description>
        <link>https://medium.com/@srisaicharan?source=rss-41b677a11fad------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ZROe7v3mTUgw67rJTQ4XUg.jpeg</url>
            <title>Stories by Sri Sai Charan on Medium</title>
            <link>https://medium.com/@srisaicharan?source=rss-41b677a11fad------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 09:45:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@srisaicharan/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What is SDLC? The 7 Phases of Software Development]]></title>
            <link>https://srisaicharan.medium.com/what-is-sdlc-the-7-phases-of-software-development-210d47527b7d?source=rss-41b677a11fad------2</link>
            <guid isPermaLink="false">https://medium.com/p/210d47527b7d</guid>
            <category><![CDATA[sdlc-methodologies]]></category>
            <category><![CDATA[sdlc]]></category>
            <category><![CDATA[sdlc-process]]></category>
            <category><![CDATA[stlc]]></category>
            <category><![CDATA[sdlc-model]]></category>
            <dc:creator><![CDATA[Sri Sai Charan]]></dc:creator>
            <pubDate>Sun, 18 Jan 2026 10:19:04 GMT</pubDate>
            <atom:updated>2026-01-18T10:19:04.093Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><strong><em>For hands-on practice quizzes and visual diagrams, check out my free learning platform</em></strong><em>: </em><a href="https://software-methodologies.netlify.app/"><em>Agile Mastery Hub</em></a></blockquote><h3>Software Development Life Cycle (SDLC)</h3><p>The foundation that all methodologies are built upon</p><h3>What is SDLC?</h3><p>The <strong>Software Development Life Cycle (SDLC)</strong> is a systematic process for building software that ensures quality and correctness. It defines the tasks to be performed at each step of the software development process.</p><p>Think of SDLC as the “what” (what phases need to happen), while methodologies define the “how” (how those phases are organized and executed).</p><p>example :<strong>The Scenario: Custom House vs. Food Delivery App</strong></p><p>To understand the SDLC phases, we will follow two parallel projects throughout this guide:</p><p><strong>Project A: Building a Custom House </strong>A tangible, physical project where mistakes are costly and changes are difficult.</p><p><strong>Project B: Food Delivery App </strong>A digital software project where iteration is easier but complexity is invisible</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w55hcnVAC4EydcIjB0H9RA.png" /><figcaption>SDLC Flowchart</figcaption></figure><h3>Phase 1: Planning &amp; Analysis</h3><p><strong>Key Question:</strong> “Should we build this?”</p><h4>Purpose</h4><p>This phase determines the project’s viability, scope, and approach. It’s the foundation that guides all subsequent phases.</p><h4>Key Activities</h4><ul><li><strong>Feasibility Study:</strong> Assess technical, economic, legal, operational, and scheduling feasibility (TELOS)</li><li><strong>Stakeholder Identification:</strong> Identify all parties affected by or interested in the project</li><li><strong>Scope Definition:</strong> Define what’s included and excluded from the project</li><li><strong>Resource Planning:</strong> Estimate budget, timeline, team size, and infrastructure needs</li><li><strong>Risk Assessment:</strong> Identify potential risks and mitigation strategies</li><li><strong>Project Charter:</strong> Create formal document authorizing the project</li></ul><h4>Types of Feasibility</h4><h4>Economic</h4><p>Cost-benefit analysis. Will ROI justify the investment? Calculate TCO (Total Cost of Ownership).</p><h4>Technical</h4><p>Can it be built with current technology? Does the team have required skills?</p><h4>Legal</h4><p>Compliance with regulations (GDPR, HIPAA, etc.), licensing, and intellectual property.</p><h4>Operational</h4><p>Will users accept it? Does it fit organizational culture and processes?</p><h4>Deliverables</h4><ul><li>Feasibility Study Report</li><li>Project Charter / Project Initiation Document (PID)</li><li>High-level Project Plan</li><li>Risk Register</li><li>Stakeholder Analysis Matrix</li></ul><h4>Applying the Scenario: The Dream &amp; The Budget</h4><p><strong>🏗️ Building a House</strong></p><p>You look at your savings ($500k), scout locations, and decide: “I want a 4-bedroom house near the park.” You ensure you can afford it.</p><p><strong>📱 Food Delivery App</strong></p><p>Business team allocates budget ($50k), researches competitors (UberEats), and decides: “We will build a localized food delivery app.”</p><h3>Phase 2: Requirements Gathering</h3><p><strong>Key Question:</strong> “What should we build?”</p><h4>Purpose</h4><p>Capture and document exactly what the system needs to do. Poor requirements are the #1 cause of project failure.</p><h4>Types of Requirements</h4><h4>Functional Requirements</h4><p>What the system should DO. Example: “Users can reset their password via email.”</p><h4>Non-Functional Requirements (NFRs)</h4><p>How the system should PERFORM. Example: “Page load time under 3 seconds.”</p><h4>Non-Functional Requirements Categories</h4><ul><li><strong>Performance:</strong> Response time, throughput, resource utilization</li><li><strong>Scalability:</strong> Handle growth in users, data, transactions</li><li><strong>Security:</strong> Authentication, authorization, encryption, audit trails</li><li><strong>Reliability:</strong> Uptime (99.9%), mean time between failures (MTBF)</li><li><strong>Availability:</strong> System accessible when needed</li><li><strong>Maintainability:</strong> Easy to update, fix, and enhance</li><li><strong>Usability:</strong> User-friendly, accessible (WCAG compliance)</li><li><strong>Compatibility:</strong> Browsers, devices, operating systems</li></ul><h4>Requirements Gathering Techniques</h4><ul><li><strong>Interviews:</strong> One-on-one with stakeholders</li><li><strong>Workshops/JAD Sessions:</strong> Joint Application Development with groups</li><li><strong>Questionnaires/Surveys:</strong> Collect data from many users</li><li><strong>Observation:</strong> Watch users perform current tasks</li><li><strong>Document Analysis:</strong> Review existing documentation</li><li><strong>Prototyping:</strong> Build mockups to validate understanding</li><li><strong>Use Cases/User Stories:</strong> Describe functionality from user perspective</li></ul><h4>Deliverables</h4><ul><li>Software Requirements Specification (SRS)</li><li>Use Case Diagrams</li><li>User Stories with Acceptance Criteria</li><li>Requirements Traceability Matrix (RTM)</li><li>Prototypes/Wireframes</li></ul><h4>Applying the Scenario: The Checklist</h4><p><strong>🏗️ Building a House</strong></p><p>You list specifics: “Master bedroom must have a walk-in closet. Kitchen needs a gas stove. Garage must fit 2 cars.”</p><p><strong>📱 Food Delivery App</strong></p><p>Product Owner lists features: “Users can filter by ‘Vegan’. Payment via Credit Card &amp; PayPal. App must load in under 2 seconds.”</p><h3>Phase 3: Design</h3><p><strong>Key Question:</strong> “How should we build it?”</p><h4>Purpose</h4><p>Transform requirements into a blueprint for development. Define the architecture, components, interfaces, and data structures.</p><h4>Types of Design</h4><h4>High-Level Design (HLD)</h4><p>System architecture, modules, technology stack, data flow between components.</p><h4>Low-Level Design (LLD)</h4><p>Detailed design of each module, class diagrams, database schemas, algorithms.</p><h4>Design Components</h4><ul><li><strong>System Architecture:</strong> Monolithic, Microservices, SOA, Serverless, Event-Driven</li><li><strong>Database Design:</strong> Schema, tables, relationships, normalization, indexing</li><li><strong>UI/UX Design:</strong> Wireframes, mockups, style guides, user flows</li><li><strong>API Design:</strong> RESTful endpoints, GraphQL schema, request/response formats</li><li><strong>Security Design:</strong> Authentication flows, encryption methods, access control</li><li><strong>Integration Design:</strong> Third-party APIs, legacy system connections</li></ul><h4>Design Patterns</h4><ul><li><strong>Creational:</strong> Singleton, Factory, Builder, Prototype</li><li><strong>Structural:</strong> Adapter, Facade, Decorator, Proxy</li><li><strong>Behavioral:</strong> Observer, Strategy, Command, State</li><li><strong>Architectural:</strong> MVC, MVVM, Clean Architecture, Hexagonal</li></ul><h4>Deliverables</h4><ul><li>System Architecture Document</li><li>Database Design Document (ERD)</li><li>Class Diagrams, Sequence Diagrams</li><li>API Specifications (OpenAPI/Swagger)</li><li>UI/UX Mockups and Style Guides</li><li>Technical Design Document (TDD)</li></ul><h4>Applying the Scenario: The Blueprints</h4><p><strong>🏗️ Building a House</strong></p><p>Architect draws the floor plan, electrical wiring diagrams, and plumbing layout. No bricks are laid yet.</p><p><strong>📱 Food Delivery App</strong></p><p>Designers create UI Wireframes (How it looks). Architects create Database Schema &amp; API Documents (How it works).</p><h3>Phase 4: Development (Coding)</h3><p><strong>Key Activity:</strong> Build the actual software</p><h4>Purpose</h4><p>Transform designs into working code. This is where the product actually gets built.</p><h4>Key Activities</h4><ul><li><strong>Environment Setup:</strong> Development, staging, production environments</li><li><strong>Coding:</strong> Write source code following design documents</li><li><strong>Code Reviews:</strong> Peer review for quality and knowledge sharing</li><li><strong>Version Control:</strong> Git branching strategies (GitFlow, Trunk-Based)</li><li><strong>Continuous Integration:</strong> Automated builds and early testing</li><li><strong>Documentation:</strong> Code comments, README files, API docs</li></ul><h4>Coding Best Practices</h4><ul><li><strong>Clean Code:</strong> Readable, maintainable, self-documenting</li><li><strong>SOLID Principles:</strong> Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion</li><li><strong>DRY:</strong> Don’t Repeat Yourself</li><li><strong>KISS:</strong> Keep It Simple, Stupid</li><li><strong>YAGNI:</strong> You Aren’t Gonna Need It</li><li><strong>Code Standards:</strong> Consistent formatting, naming conventions</li><li><strong>Error Handling:</strong> Graceful error handling and logging</li></ul><h4>Development Approaches</h4><h4>TDD (Test-Driven Development)</h4><p>Write tests BEFORE code. Red → Green → Refactor cycle.</p><h4>BDD (Behavior-Driven Development)</h4><p>Write tests in business language. Given-When-Then format.</p><h4>Pair Programming</h4><p>Two developers work together on one computer. Driver + Navigator.</p><h4>Mob Programming</h4><p>Entire team works on one task together. Good for complex problems.</p><h4>Deliverables</h4><ul><li>Source Code in Version Control</li><li>Unit Tests</li><li>Build Scripts / CI/CD Pipeline</li><li>Code Review Records</li><li>Technical Documentation</li></ul><h4>Applying the Scenario: Breaking Ground</h4><p><strong>🏗️ Building a House</strong></p><p>Workers pour the concrete foundation, frame the walls, install the roof, and connect the plumbing.</p><p><strong>📱 Food Delivery App</strong></p><p>Frontend Developers write React code. Backend Developers write Node.js APIs. The app is actually built.</p><h3>Phase 5: Testing</h3><p><strong>Key Activity:</strong> Verify it works correctly</p><h4>Purpose</h4><p>Verify the software meets requirements and works as expected. Testing is NOT just finding bugs — it’s about <strong>building confidence</strong> in the software.</p><h4>Testing Principles (ISTQB)</h4><ol><li><strong>Testing shows presence of defects:</strong> Testing can prove bugs exist, not that they don’t</li><li><strong>Exhaustive testing is impossible:</strong> Test based on risk and priority</li><li><strong>Early testing:</strong> Start testing activities early (Shift Left)</li><li><strong>Defect clustering:</strong> A small number of modules contain most defects</li><li><strong>Pesticide paradox:</strong> Running same tests repeatedly won’t find new bugs</li><li><strong>Testing is context-dependent:</strong> Testing approach depends on the context</li><li><strong>Absence-of-errors fallacy:</strong> Finding and fixing bugs is useless if system is unusable</li></ol><h4>Software Testing Life Cycle (STLC)</h4><p>STLC is a sequence of specific activities conducted during testing to ensure software quality goals are met. It defines WHAT testing activities to do and WHEN to perform them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lwoUWGTJ6DFy1UZOTRyliw.png" /><figcaption>STLC</figcaption></figure><p>Phase 1: Requirement Analysis</p><ul><li><strong>Entry Criteria:</strong> Requirements documents available (BRS, SRS, FRS)</li><li><strong>Activities:</strong></li><li>Identify testable requirements</li><li>Analyze requirements for testability</li><li>Identify gaps, ambiguities, and conflicts</li><li>Create Requirement Traceability Matrix (RTM)</li><li>Identify test types needed (functional, performance, security)</li><li><strong>Exit Criteria:</strong> RTM signed off, automation feasibility documented</li><li><strong>Deliverables:</strong> RTM, Automation Feasibility Report</li></ul><p>Phase 2: Test Planning</p><ul><li><strong>Entry Criteria:</strong> Requirements analyzed, RTM ready</li><li><strong>Activities:</strong></li><li>Define test strategy (manual vs automated)</li><li>Estimate effort and cost</li><li>Define resources, roles, and responsibilities</li><li>Identify training needs</li><li>Define test scope (in-scope/out-of-scope)</li><li>Identify risks and mitigation plans</li><li>Define entry and exit criteria for each phase</li><li><strong>Exit Criteria:</strong> Test Plan approved by stakeholders</li><li><strong>Deliverables:</strong> Test Plan, Test Estimation Document</li></ul><p>Phase 3: Test Case Design/Development</p><ul><li><strong>Entry Criteria:</strong> Test Plan approved</li><li><strong>Activities:</strong></li><li>Create detailed test cases with steps</li><li>Define test data requirements</li><li>Create test scenarios</li><li>Write automation scripts (if applicable)</li><li>Review and baseline test cases</li><li>Update RTM with test case IDs</li><li><strong>Exit Criteria:</strong> Test cases reviewed and approved</li><li><strong>Deliverables:</strong> Test Cases, Test Scripts, Test Data</li></ul><p>Phase 4: Test Environment Setup</p><ul><li><strong>Entry Criteria:</strong> Test plan and test data ready</li><li><strong>Activities:</strong></li><li>Set up hardware and software environment</li><li>Configure test tools and frameworks</li><li>Perform smoke test on environment</li><li>Prepare test data and database</li><li>Verify network configurations</li><li><strong>Exit Criteria:</strong> Environment ready, smoke test passed</li><li><strong>Deliverables:</strong> Environment Setup Report, Smoke Test Results</li></ul><p>Phase 5: Test Execution</p><ul><li><strong>Entry Criteria:</strong> Test cases ready, environment set up, build deployed</li><li><strong>Activities:</strong></li><li>Execute test cases as per plan</li><li>Log defects for failed tests</li><li>Map defects to test cases in RTM</li><li>Retest fixed defects</li><li>Perform regression testing</li><li>Track test execution status</li><li><strong>Exit Criteria:</strong> All tests executed, defects logged and tracked</li><li><strong>Deliverables:</strong> Test Execution Report, Defect Report, Updated RTM</li></ul><p>Phase 6: Test Closure</p><ul><li><strong>Entry Criteria:</strong> Testing complete, all defects closed/deferred</li><li><strong>Activities:</strong></li><li>Evaluate exit criteria completion</li><li>Analyze test metrics (pass %, defect density)</li><li>Document lessons learned</li><li>Archive test artifacts</li><li>Prepare test summary report</li><li>Send test completion sign-off</li><li><strong>Exit Criteria:</strong> Test completion report approved, sign-off received</li><li><strong>Deliverables:</strong> Test Summary Report, Test Metrics, Lessons Learned</li></ul><h4>STLC vs SDLC</h4><h4>SDLC</h4><p>Focuses on the entire software development process from planning to maintenance.</p><h4>STLC</h4><p>Focuses specifically on testing phase within SDLC, with detailed testing activities.</p><h4>Unit Testing</h4><p><strong>What:</strong> Test individual functions/methods in isolation</p><p><strong>Who:</strong> Developers</p><p><strong>Tools:</strong> JUnit, pytest, Jest, NUnit, xUnit</p><p><strong>Goal:</strong> Verify each unit works correctly on its own</p><h4>Integration Testing</h4><p><strong>What:</strong> Test how components work together</p><p><strong>Who:</strong> Developers/QA</p><p><strong>Types:</strong> Big Bang, Top-Down, Bottom-Up, Sandwich</p><p><strong>Goal:</strong> Find interface defects between modules</p><h4>System Testing</h4><p><strong>What:</strong> Test complete integrated system</p><p><strong>Who:</strong> QA Team</p><p><strong>Environment:</strong> Production-like environment</p><p><strong>Goal:</strong> Verify system meets requirements</p><h4>User Acceptance Testing (UAT)</h4><p><strong>What:</strong> End users test the system</p><p><strong>Who:</strong> Business users/stakeholders</p><p><strong>Types:</strong> Alpha, Beta, Contract, Regulation</p><p><strong>Goal:</strong> Validate system meets business needs</p><h4>Testing Types by Category</h4><p>Functional Testing</p><ul><li><strong>Smoke Testing:</strong> Quick check that critical functionality works (Build Verification Test)</li><li><strong>Sanity Testing:</strong> Focused testing after minor changes</li><li><strong>Regression Testing:</strong> Ensure new changes don’t break existing functionality</li><li><strong>Retesting:</strong> Verify fixed defects are actually fixed</li><li><strong>Exploratory Testing:</strong> Unscripted testing based on tester’s experience</li><li><strong>Ad-hoc Testing:</strong> Informal testing without planning</li></ul><p>Non-Functional Testing</p><ul><li><strong>Performance Testing:</strong> Response time, throughput under normal load</li><li><strong>Load Testing:</strong> Behavior under expected peak load</li><li><strong>Stress Testing:</strong> Behavior beyond normal capacity (breaking point)</li><li><strong>Volume Testing:</strong> Large amounts of data</li><li><strong>Endurance/Soak Testing:</strong> Sustained load over extended period (memory leaks)</li><li><strong>Spike Testing:</strong> Sudden increase in users</li><li><strong>Scalability Testing:</strong> Can system scale up/down?</li><li><strong>Security Testing:</strong> Vulnerabilities, penetration testing, OWASP Top 10</li><li><strong>Usability Testing:</strong> User experience, ease of use</li><li><strong>Accessibility Testing:</strong> WCAG compliance (screen readers, keyboard navigation)</li><li><strong>Compatibility Testing:</strong> Different browsers, devices, OS</li><li><strong>Localization Testing:</strong> Different languages, regions, currencies</li></ul><h4>Testing Techniques</h4><h4>Black Box Testing</h4><p>Test without knowing internal code. Focus on inputs and outputs.</p><p><strong>Techniques:</strong> Equivalence Partitioning, Boundary Value Analysis, Decision Tables, State Transition, Use Case Testing</p><h4>White Box Testing</h4><p>Test with knowledge of internal code structure.</p><p><strong>Techniques:</strong> Statement Coverage, Branch Coverage, Path Coverage, Condition Coverage</p><h4>Gray Box Testing</h4><p>Partial knowledge of internal structure. Combines black and white box.</p><p><strong>Used for:</strong> Integration testing, web application testing</p><h4>Test Design Techniques (Black Box)</h4><ul><li><strong>Equivalence Partitioning:</strong> Divide inputs into groups that should behave the same. Test one from each partition.</li><li><strong>Boundary Value Analysis:</strong> Test at the boundaries of input ranges (min, max, just above, just below)</li><li><strong>Decision Table Testing:</strong> Test combinations of conditions and actions</li><li><strong>State Transition Testing:</strong> Test different states and transitions between them</li><li><strong>Use Case Testing:</strong> Test based on user scenarios</li><li><strong>Error Guessing:</strong> Based on tester’s experience and intuition</li></ul><h4>Test Coverage Metrics (White Box)</h4><ul><li><strong>Statement Coverage:</strong> % of code statements executed</li><li><strong>Branch Coverage:</strong> % of branches (if/else) executed</li><li><strong>Condition Coverage:</strong> % of boolean sub-expressions evaluated</li><li><strong>Path Coverage:</strong> % of possible paths through code</li><li><strong>MC/DC (Modified Condition/Decision Coverage):</strong> Each condition independently affects outcome</li></ul><h4>Q1: Unit Tests</h4><p>Technology facing, guides development</p><h4>Q2: Functional Tests</h4><p>Business facing, guides development</p><h4>Q3: Exploratory Testing</h4><p>Business facing, critiques product</p><h4>Q4: Performance Tests</h4><p>Technology facing, critiques product</p><h4>Automation Testing</h4><ul><li><strong>When to Automate:</strong> Repetitive tests, regression tests, data-driven tests, cross-browser tests</li><li><strong>When NOT to Automate:</strong> One-time tests, exploratory testing, tests that change frequently, UX testing</li><li><strong>UI Automation Tools:</strong> Selenium, Cypress, Playwright, TestCafe, Appium (mobile)</li><li><strong>API Testing Tools:</strong> Postman, REST Assured, Karate, SoapUI</li><li><strong>Unit Testing Frameworks:</strong> JUnit, TestNG, pytest, Jest, Mocha, xUnit</li><li><strong>BDD Frameworks:</strong> Cucumber, SpecFlow, Behave, JBehave</li><li><strong>Performance Tools:</strong> JMeter, Gatling, k6, LoadRunner, Locust</li><li><strong>Security Tools:</strong> OWASP ZAP, Burp Suite, Nmap, SQLMap</li></ul><h4>Test Documentation</h4><ul><li><strong>Test Plan:</strong> What, when, how, who will test</li><li><strong>Test Cases:</strong> Steps, expected results, preconditions</li><li><strong>Test Scenarios:</strong> High-level what to test</li><li><strong>Test Data:</strong> Input data for tests</li><li><strong>Traceability Matrix:</strong> Map requirements to test cases</li><li><strong>Defect Reports:</strong> Bug details (steps to reproduce, severity, priority)</li><li><strong>Test Summary Report:</strong> Results, metrics, recommendations</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rMvdMjUPWD_thaNTobe3vA.png" /></figure><h4>Defect Severity vs Priority</h4><h4>Severity (Technical Impact)</h4><ul><li><strong>Critical:</strong> System crash, data loss</li><li><strong>Major:</strong> Major feature broken</li><li><strong>Minor:</strong> Minor feature issue</li><li><strong>Trivial:</strong> Cosmetic issues</li></ul><h4>Priority (Business Impact)</h4><ul><li><strong>P1 — Critical:</strong> Fix immediately</li><li><strong>P2 — High:</strong> Fix in current sprint</li><li><strong>P3 — Medium:</strong> Fix soon</li><li><strong>P4 — Low:</strong> Fix when time permits</li></ul><h4>Testing Deliverables</h4><ul><li>Test Plan</li><li>Test Cases and Test Scripts</li><li>Test Data</li><li>Defect Reports</li><li>Test Execution Results</li><li>Test Coverage Reports</li><li>Test Summary Report</li><li>Requirements Traceability Matrix</li></ul><h4>Applying the Scenario: The Inspection</h4><p><strong>🏗️ Building a House</strong></p><p>Inspector checks if the switches turn on lights, if the toilet flushes, and if the roof leaks during rain.</p><p><strong>📱 Food Delivery App</strong></p><p>QA Team tests: “Does the app crash when I order 100 pizzas?” “Is credit card data secure?” (Security Testing).</p><h3>Phase 6: Deployment</h3><p><strong>Key Activity:</strong> Release software to production</p><h4>Purpose</h4><p>Make the software available to end users in the production environment.</p><h4>Deployment Strategies</h4><h4>Blue-Green Deployment</h4><p>Two identical environments. Switch traffic instantly. Easy rollback.</p><h4>Canary Deployment</h4><p>Release to small % of users first. Monitor, then expand gradually.</p><h4>Rolling Deployment</h4><p>Update instances one at a time. No downtime but slower.</p><h4>Feature Flags</h4><p>Deploy code but toggle features on/off. A/B testing support.</p><h4>Deployment Activities</h4><ul><li><strong>Environment Preparation:</strong> Configure production servers, databases, networking</li><li><strong>Data Migration:</strong> Move/transform data from old system</li><li><strong>Release Execution:</strong> Deploy code, run migrations, update configs</li><li><strong>Smoke Testing:</strong> Quick verification that critical features work</li><li><strong>User Training:</strong> Train end users on new system</li><li><strong>Documentation:</strong> User manuals, admin guides, runbooks</li><li><strong>Monitoring Setup:</strong> Alerts, dashboards, logging</li><li><strong>Rollback Plan:</strong> How to revert if something goes wrong</li></ul><h4>CI/CD Pipeline</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/942/1*WFlAkQ-fyCpSSoOQqPnB5w.png" /></figure><h4>Deliverables</h4><ul><li>Deployment Plan and Runbook</li><li>Release Notes</li><li>User Documentation/Training Materials</li><li>Rollback Procedures</li><li>Monitoring and Alerting Configuration</li></ul><h4>Applying the Scenario: Moving In</h4><p><strong>🏗️ Building a House</strong></p><p>You get the keys, movers bring furniture, and you sleep there for the first time.</p><p><strong>📱 Food Delivery App</strong></p><p>App is published to App Store and users start downloading it.</p><h3>Phase 7: Maintenance</h3><p><strong>Key Activity:</strong> Updates and fixes</p><h4>Purpose</h4><p>Keep the software running, fix issues, and add enhancements. This phase often takes 60–80% of the total software lifecycle cost!</p><h4>Types of Maintenance</h4><h4>Corrective</h4><p>Fix bugs and defects discovered after deployment.</p><h4>Adaptive</h4><p>Adapt to changes in environment (OS updates, new browsers, regulations).</p><h4>Perfective</h4><p>Add new features, improve performance, enhance usability.</p><h4>Preventive</h4><p>Refactoring, updating dependencies, improving maintainability.</p><h4>Maintenance Activities</h4><ul><li><strong>Bug Tracking:</strong> Log, prioritize, and manage reported issues</li><li><strong>Hotfixes:</strong> Emergency fixes for critical production issues</li><li><strong>Security Patches:</strong> Update for newly discovered vulnerabilities</li><li><strong>Performance Tuning:</strong> Optimize slow queries, cache, etc.</li><li><strong>Capacity Planning:</strong> Scale infrastructure as usage grows</li><li><strong>Technical Debt:</strong> Pay down accumulated shortcuts</li><li><strong>Documentation Updates:</strong> Keep docs current with changes</li><li><strong>Monitoring &amp; Alerting:</strong> Watch for issues proactively</li></ul><h4>Key Metrics to Monitor</h4><ul><li><strong>MTTR (Mean Time To Recovery):</strong> How fast can you recover from failures?</li><li><strong>MTBF (Mean Time Between Failures):</strong> How reliable is the system?</li><li><strong>Error Rates:</strong> % of requests failing</li><li><strong>Response Time:</strong> P50, P95, P99 latencies</li><li><strong>Availability:</strong> Uptime percentage (99.9% = 8.76 hrs downtime/year)</li><li><strong>User Satisfaction:</strong> NPS, support ticket volume</li></ul><h4>Deliverables</h4><ul><li>Incident Reports</li><li>Change Requests</li><li>Updated Documentation</li><li>Performance Reports</li><li>Security Audit Results</li></ul><h4>Applying the Scenario: Upkeep &amp; Renovations</h4><p><strong>🏗️ Building a House</strong></p><p>Fixing a leaky faucet (Bug fix). Painting the nursery for a new baby (New Feature).</p><p><strong>📱 Food Delivery App</strong></p><p>Fixing login errors (Bug Fix). Adding a “Grocery Delivery” option (New Feature/Update).</p><blockquote><em>What’s Next?</em></blockquote><blockquote><em>Now you understand the phases of building software, but there are many ways to organize these phases — some are sequential (Waterfall), some are iterative (Agile), and some blend both (Scrumban).</em></blockquote><blockquote><em>In Part 2, we’ll explore the most popular methodologies: Waterfall, Agile, Scrum, Kanban, DevOps, and more.</em></blockquote><blockquote><strong><em>Want to Practice &amp; Learn More?</em></strong></blockquote><blockquote><strong><em>I’ve built a free interactive website with quizzes, diagrams, and detailed explanations for SDLC, Agile, Scrum, and Kanban.</em></strong></blockquote><blockquote><em>👉 </em><a href="https://software-methodologies.netlify.app/"><em>Explore Agile Mastery Hub</em></a></blockquote><blockquote><a href="https://www.linkedin.com/in/srisaicharan/">— Sri Sai charan</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=210d47527b7d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>