SDLC "A5" 1 / 50 SDLC का primary goal है – Fast coding Quality software delivery Less testing Hardware use 2 / 50 SDLC का पहला phase है – Design Requirement Analysis Testing Coding 3 / 50 Requirement Analysis का output होता है – Code SRS Test cases UI 4 / 50 Feasibility study में शामिल नहीं है – Technical Economic Compilation Operational 5 / 50 SRS document किसके बीच agreement होता है? Developer–Tester Client–Developer User–Tester Manager–Coder 6 / 50 Design phase का focus है – Bug fixing Architecture & modules User training Deployment 7 / 50 HLD दर्शाता है – Algorithms Overall system design Source code Test data 8 / 50 LLD दर्शाता है – Database only Release plan User needs Module logic & flow 9 / 50 Coding phase का main output – SRS Design Executable code Report 10 / 50 Testing phase का उद्देश्य – Improve UI Defect detection Speed Documentation 11 / 50 Black box testing based है – Code structure Functional requirements Loops Logic paths 12 / 50 White box testing based है – UI Output Internal logic Requirements 13 / 50 Unit testing करता है – Individual module Complete system User acceptance Database 14 / 50 Integration testing होता है – Requirement phase में Modules combine होने पर Deployment में Maintenance में 15 / 50 System testing verify करता है – Code syntax End-to-end behavior Algorithm UI only 16 / 50 Acceptance testing करता है – Manager Developer Client/User Tester 17 / 50 Regression testing किया जाता है – New feature के लिए Changes के बाद First build Deployment के बाद 18 / 50 Alpha testing होती है – User site पर Developer site पर Production में Maintenance में 19 / 50 Beta testing होती है – Design phase में Real users के साथ Lab में Coding में 20 / 50 Validation का अर्थ – Product सही बना? Code check Right product बना? Debug 21 / 50 Maintenance phase में cost होती है – Lowest Highest Zero Fixed 22 / 50 Corrective maintenance – Bug fixing Environment change Performance tuning Future prevention 23 / 50 Adaptive maintenance – Error removal OS/Environment change Feature add Refactoring 24 / 50 Perfective maintenance – Bug fix Environment Performance/Feature improvement Security 25 / 50 Preventive maintenance – Current error Future fault prevention New requirement Migration 26 / 50 Waterfall model nature – Iterative Sequential Cyclic Agile 27 / 50 Waterfall model drawback – Simple No flexibility Documentation Easy management 28 / 50 Iterative model advantage – No planning Early feedback High risk No testing 29 / 50 Prototype model suitable है – Clear requirement Unclear requirement Safety critical Fixed scope 30 / 50 Prototype model risk – No UI Poor documentation High cost No feedback 31 / 50 Spiral model focus करता है – Speed Risk analysis Coding UI 32 / 50 Spiral model combination है – Waterfall + RAD Iterative + Risk Agile + DevOps Big-Bang + Waterfall 33 / 50 RAD model suitable है – Large critical systems Short duration projects Military software OS development 34 / 50 RAD model drawback – Fast Skilled team required Reusable components User involvement 35 / 50 Big-Bang model risk – Structured No planning Documentation Controlled 36 / 50 Agile manifesto focus करता है – Tools Individuals & interaction Documentation Fixed plan 37 / 50 Agile development में requirement होती है – Fixed Changing Locked Frozen 38 / 50 Sprint होता है – Long phase Short iteration Testing phase Deployment 39 / 50 Scrum में sprint duration – 6–12 months 1–4 weeks 1 year Undefined 40 / 50 Product owner का role – Coding Requirement prioritization Testing Deployment 41 / 50 DevOps integrate करता है – Design + Testing Development + Operations Planning + Coding UI + DB 42 / 50 DevOps goal – Manual deployment More documentation Faster & reliable delivery Less testing 43 / 50 CI/CD का अर्थ – Code Integration Continuous Integration / Deployment Code Inspection Central Integration 44 / 50 Agile disadvantage – User involvement Difficult cost estimation Fast delivery Flexibility 45 / 50 Waterfall suitable है – Changing requirement Stable requirement Startup projects UI heavy apps 46 / 50 V-Model based है – Iteration Verification & Validation Risk Prototype 47 / 50 V-Model advantage – Late testing Early test planning No documentation High risk 48 / 50 V-Model drawback – Structured Rigid Clear mapping Quality 49 / 50 Verification का अर्थ – Are we building product right? Right product? Testing Validation 50 / 50 Validation का अर्थ – Syntax Build right product Code correct Build right Your score isThe average score is 0% 0% Restart quiz
