Q1. SDLC stands for ASystem Development Life CycleBSystem Design Logical CycleCSoftware Design Life CycleDSoftware Development Logical Cycle Show answer Answer: A. System Development Life Cycle Report a mistake
Q2. A system is AOnly softwareBA single programCA set of interrelated components working togetherDOnly hardware Show answer Answer: C. A set of interrelated components working together Report a mistake
Q3. The importance of SDLC is ATo avoid planningBTo skip testingCTo develop systems systematically and efficientlyDTo increase errors Show answer Answer: C. To develop systems systematically and efficiently Report a mistake
Q4. The main objective of SDLC is ATo avoid documentationBTo ignore user needsCTo produce a high-quality system that meets user requirementsDTo finish quickly without quality Show answer Answer: C. To produce a high-quality system that meets user requirements Report a mistake
Q5. Stakeholders in SDLC include AOnly managersBOnly usersCUsers, developers, managers, clientsDOnly programmers Show answer Answer: C. Users, developers, managers, clients Report a mistake
Q6. The first phase of traditional SDLC is ACodingBTestingCPlanning / Requirement AnalysisDMaintenance Show answer Answer: C. Planning / Requirement Analysis Report a mistake
Q7. Feasibility study is done in ADesign phaseBPlanning phaseCMaintenance phaseDImplementation phase Show answer Answer: B. Planning phase Report a mistake
Q8. System design phase involves ADeploying the systemBCreating the architecture and detailed designCTesting onlyDWriting code only Show answer Answer: B. Creating the architecture and detailed design Report a mistake
Q9. Implementation phase includes AOnly requirement gatheringBOnly testingCCoding and installationDOnly planning Show answer Answer: C. Coding and installation Report a mistake
Q10. Testing is done to AFind and fix errorsBGather requirementsCDesign the systemDWrite more code Show answer Answer: A. Find and fix errors Report a mistake
Q11. Maintenance phase starts after ASystem is delivered and operationalBCoding onlyCDesignDPlanning Show answer Answer: A. System is delivered and operational Report a mistake
Q12. The role of a system analyst is AOnly to manage hardwareBOnly to testCTo study requirements and design the systemDOnly to write code Show answer Answer: C. To study requirements and design the system Report a mistake
Q13. Phases of classical SDLC (Waterfall) are AOnly Coding and TestingBPlanning, Analysis, Design, Implementation, Testing, MaintenanceCOnly PlanningDOnly Design Show answer Answer: B. Planning, Analysis, Design, Implementation, Testing, Maintenance Report a mistake
Q14. Waterfall model is ALinear sequential modelBSpiral modelCIterative modelDAgile only Show answer Answer: A. Linear sequential model Report a mistake
Q15. Advantage of Waterfall model is AHighly flexibleBContinuous user feedbackCNo documentation neededDSimple and easy to understand Show answer Answer: D. Simple and easy to understand Report a mistake
Q16. Disadvantage of Waterfall model is ANo documentationBDifficult to go back to previous phaseCToo much flexibilityDNo structure Show answer Answer: B. Difficult to go back to previous phase Report a mistake
Q17. Prototyping model is useful when ARequirements are not clear initiallyBOnly for small systemsCRequirements are fully clearDNo user involvement needed Show answer Answer: A. Requirements are not clear initially Report a mistake
Q18. Spiral model combines AOnly prototypingBOnly agileCIterative development with risk analysisDOnly waterfall Show answer Answer: C. Iterative development with risk analysis Report a mistake
Q19. Agile methodology focuses on ARigid documentation onlyBNo changes allowedCLong planning onlyDIterative development and customer collaboration Show answer Answer: D. Iterative development and customer collaboration Report a mistake
Q20. Requirement gathering techniques include AOnly testingBOnly codingCInterviews, questionnaires, observation, workshopsDOnly design Show answer Answer: C. Interviews, questionnaires, observation, workshops Report a mistake
Q21. Functional requirements describe AWhat the system should doBPerformance onlyCHardware onlyDHow the system looks Show answer Answer: A. What the system should do Report a mistake
Q22. Non-functional requirements include AOnly featuresBPerformance, security, usabilityCOnly outputsDOnly inputs Show answer Answer: B. Performance, security, usability Report a mistake
Q23. SRS stands for ASoftware Requirements SpecificationBNoneCSoftware Resource SystemDSystem Resource Specification Show answer Answer: A. Software Requirements Specification Report a mistake
Q24. Logical design focuses on AWhat the system will do (independent of technology)BHardware onlyCHow it will be implementedDCoding only Show answer Answer: A. What the system will do (independent of technology) Report a mistake
Q25. Physical design focuses on AOnly requirementsBHow the system will be implemented (technology specific)COnly testingDOnly planning Show answer Answer: B. How the system will be implemented (technology specific) Report a mistake
Q26. Data Flow Diagram (DFD) is used to AShow only codeBShow only usersCShow flow of data in the systemDShow only hardware Show answer Answer: C. Show flow of data in the system Report a mistake
Q27. Entity Relationship Diagram (ERD) is used for ADatabase designBProcess flow onlyCTestingDUser interface only Show answer Answer: A. Database design Report a mistake
Q28. Use Case diagram shows AOnly code structureBOnly hardwareCOnly databaseDInteraction between users and system Show answer Answer: D. Interaction between users and system Report a mistake
Q29. Coding phase converts ANoneBRequirements into designCTesting into maintenanceDDesign into actual programs Show answer Answer: D. Design into actual programs Report a mistake
Q30. Unit testing tests AEntire systemBOnly user interfaceCOnly databaseDIndividual modules/components Show answer Answer: D. Individual modules/components Report a mistake
Q31. Integration testing tests AInteraction between modulesBOnly designCOnly single moduleDOnly requirements Show answer Answer: A. Interaction between modules Report a mistake
Q32. System testing tests AThe complete system against requirementsBOnly one moduleCOnly code syntaxDOnly hardware Show answer Answer: A. The complete system against requirements Report a mistake
Q33. Acceptance testing is done by AOnly testers internallyBOnly developersCEnd users / clientsDOnly managers Show answer Answer: C. End users / clients Report a mistake
Q34. Black-box testing focuses on AFunctionality without knowing internal codeBOnly performanceCOnly securityDInternal code structure Show answer Answer: A. Functionality without knowing internal code Report a mistake
Q35. White-box testing focuses on AInternal code structure and logicBOnly databaseCOnly user interfaceDOnly external functionality Show answer Answer: A. Internal code structure and logic Report a mistake
Q36. Deployment means AOnly testingBOnly designingCInstalling and making the system operationalDOnly writing code Show answer Answer: C. Installing and making the system operational Report a mistake
Q37. Types of maintenance include ACorrective, Adaptive, Perfective, PreventiveBOnly correctiveCOnly perfectiveDOnly adaptive Show answer Answer: A. Corrective, Adaptive, Perfective, Preventive Report a mistake
Q38. Corrective maintenance is AAdapting to new environmentBFixing bugs and errorsCImproving performance onlyDAdding new features Show answer Answer: B. Fixing bugs and errors Report a mistake
Q39. Adaptive maintenance is AFixing bugs onlyBAdding features onlyCModifying system for new environment/platformDNone Show answer Answer: C. Modifying system for new environment/platform Report a mistake
Q40. Perfective maintenance is AImproving performance or adding enhancementsBNoneCOnly adaptingDFixing bugs only Show answer Answer: A. Improving performance or adding enhancements Report a mistake
Q41. Preventive maintenance is AFixing current bugs onlyBOnly adding featuresCNoneDMaking changes to prevent future problems Show answer Answer: D. Making changes to prevent future problems Report a mistake
Q42. Project manager is responsible for APlanning, monitoring and controlling the projectBOnly testingCOnly designing UIDOnly writing code Show answer Answer: A. Planning, monitoring and controlling the project Report a mistake
Q43. Programmer / Developer is responsible for AOnly managing budgetBWriting and testing codeCOnly user trainingDOnly gathering requirements Show answer Answer: B. Writing and testing code Report a mistake
Q44. Quality Assurance (QA) ensures AOnly speed of developmentBNoneCSystem meets quality standards and requirementsDOnly low cost Show answer Answer: C. System meets quality standards and requirements Report a mistake
Q45. Documentation is important because ANoneBIt is not neededCIt helps in maintenance, training and future developmentDIt slows down the project only Show answer Answer: C. It helps in maintenance, training and future development Report a mistake
Q46. CASE tools are AComputer-Aided Software Engineering toolsBNoneCOnly testing toolsDOnly hardware tools Show answer Answer: A. Computer-Aided Software Engineering tools Report a mistake
Q47. Feasibility types include AOnly economicBOnly technicalCTechnical, Economic, Operational, ScheduleDOnly operational Show answer Answer: C. Technical, Economic, Operational, Schedule Report a mistake
Q48. Economic feasibility checks AWhether the project is cost-effectiveBOnly timeCOnly user acceptanceDOnly technical possibility Show answer Answer: A. Whether the project is cost-effective Report a mistake
Q49. Technical feasibility checks AOnly costBWhether the technology is available and suitableCOnly scheduleDOnly user needs Show answer Answer: B. Whether the technology is available and suitable Report a mistake
Q50. The final output of SDLC is AA working, tested and documented system that meets requirementsBOnly test casesCOnly source codeDOnly design documents Show answer Answer: A. A working, tested and documented system that meets requirements Report a mistake