SDLC (Software Development Life Cycle), A structured "recipe" or process used by dev teams to design, build, test, and deploy high-quality software from start to finish., Planning (Initiation), The initial phase focused on scope, feasibility, timelines, and risks; compared to setting a budget and venue for a big wedding., Analysis (Requirements Gathering), The process of gathering every detail of what software needs to achieve; compared to writing a wish list to Santa Claus, Business Analyst (BA), A non-coding role mentioned in the video that champions the analysis phase by working with SMEs and developers., Design Phase, Creating blueprints, specifying the technology stack, user interfaces, and database structure., Development (Build Phase), The phase where developers turn requirements into actual code; described as intense, creative, and requiring "lots of coffee"., Testing Phase, Systematic quality checks to find bugs and errors before the application goes live., Deployment (Implementation), The big moment when software is released to end users, comparable to moving into a new house., Hypercare / ELS (Early Life Support), A temporary, high-attention phase immediately following release to handle initial hiccups, user queries, and early bugs., Post-Implementation Support (PIS), Broad term covering post-launch support activities carried out immediately after a project goes live., Maintenance, Ongoing software upkeep, bug fixing, and updating features over time to keep the app functional; compared to house maintenance., Subject Matter Experts (SME), High-level decision-makers and experts consulted during requirements gathering to define business needs., User Training, A step during deployment to ensure end users and support staff know how to navigate and operate the new system., Scrum Master / Project Manager, Non-coding leadership roles highlighted as needing SDLC knowledge to communicate effectively with devs and manage expectations.

SDLC Terms

만든이
인쇄
퍼가기

순위표

비주얼 스타일

옵션

템플릿 전환하기

자동 저장된 게임을 복구할까요?