Software Development Life Cycle (SDLC) Questions and Answers for Viva

Answer-1: SDLC (Software Development Life Cycle) is a process used by software engineers and developers to design, develop, test, and maintain software applications.

Answer-2: The main stages are: Requirement Analysis, Design, Implementation, Testing, Deployment, and Maintenance.

Answer-3: The Waterfall model is a linear and sequential approach where each phase must be completed before the next one begins.

Answer-4: Agile is an iterative and incremental approach to software development that emphasizes flexibility, collaboration, and customer feedback.

Answer-5: Agile is more flexible, allows for frequent changes, and focuses on customer feedback and quick delivery of working software.

Answer-6: Scrum is an Agile framework that uses sprints (short, time-boxed periods) to build and deliver software incrementally.

Answer-7: The V-Model is an extension of the Waterfall model where each development phase corresponds to a testing phase, emphasizing verification and validation.

Answer-8: The Spiral model combines iterative development with systematic aspects of the Waterfall model and emphasizes risk management.

Answer-9: The Incremental model breaks down the system into smaller, manageable parts, where each part is developed and delivered incrementally.

Answer-10: RAD (Rapid Application Development) is an SDLC model focused on fast development using prototypes and minimal planning.

Answer-11: A prototype is an early, simplified version of a system that helps stakeholders understand the functionality before the final product is built.

Answer-12: Functional requirements describe system behavior, such as features, while non-functional requirements define system attributes, such as performance, security, and usability.

Answer-13: A business analyst gathers and analyzes requirements, ensures communication between stakeholders, and ensures the system meets business needs.

Answer-14: The SRS is a document that defines the software?s functional and non-functional requirements, helping developers understand the project?s scope.

Answer-15: Alpha testing is performed by the internal team, while Beta testing involves end-users to validate the system before full deployment.

Answer-16: A Use Case describes how a user interacts with the system to achieve a specific goal, helping in both requirements gathering and testing.

Answer-17: Version control is the practice of tracking and managing changes to software code, allowing multiple developers to collaborate efficiently.

Answer-18: A bug is an issue found in the code, while a defect refers to a deviation from the expected behavior or requirement.

Answer-19: A project manager oversees the project, manages resources, timelines, risks, and ensures that the project meets the defined objectives.

Answer-20: CI is the practice of automatically integrating code changes into a shared repository multiple times a day to detect issues early.

Answer-21: Agile is iterative and flexible, focusing on collaboration and continuous improvement, while Waterfall is linear, with a rigid sequence of stages.

Answer-22: Requirement gathering is critical for understanding the needs of the client, ensuring the software meets expectations, and defining the project scope.

Answer-23: Testing ensures the software works as intended, meets requirements, and is free of defects, ensuring quality and user satisfaction.

Answer-24: A Change Request is a formal proposal to modify the system?s requirements, design, or functionality during or after the development phase.

Answer-25: A system design document outlines the architecture and detailed design of the system, including components, interfaces, and data flow.

Answer-26: Coding standards ensure consistency, readability, maintainability, and quality across the codebase, facilitating collaboration and reducing errors.

Answer-27: Automated testing increases efficiency, repeatability, and coverage, reducing manual effort and errors, especially for regression testing.

Answer-28: User feedback helps refine the product to meet user expectations, identify issues early, and enhance usability and functionality.

Answer-29: Challenges include managing changing requirements, communication gaps, scope creep, and ensuring quality throughout all stages.

Answer-30: A milestone in SDLC represents a significant event or phase completion that marks progress in the project?s development.

Answer-31: Regression testing ensures that new code changes do not negatively affect the existing functionality of the system.

Answer-32: A test case is a set of conditions and inputs used to verify whether a system functions as expected.

Answer-33: Configuration management tracks and controls changes to the software?s components, ensuring consistency and preventing errors.

Answer-34: The deployment phase involves releasing the software into a production environment for use by end-users.

Answer-35: Functional testing checks the system?s functionality against requirements, while non-functional testing assesses performance, usability, and other attributes.

Answer-36: A tester is responsible for ensuring the system is bug-free, meets requirements, and functions as expected through various testing techniques.

Answer-37: Acceptance testing verifies whether the system meets the user?s needs and business requirements before final approval.

Answer-38: A software release refers to making the software available to users or customers, often involving version control and patching.

Answer-39: Key deliverables include requirements documents, design documents, source code, test plans, test cases, and user manuals.

Answer-40: The prototype model builds a working model early for feedback, while the Waterfall model progresses through each stage linearly and sequentially.

Answer-41: System maintenance involves updating the software after deployment to fix defects, improve performance, or adapt to changing requirements.

Answer-42: Project estimation helps predict the time, cost, and resources needed, helping plan and allocate effectively for the entire SDLC process.

Answer-43: Types include unit testing, integration testing, system testing, acceptance testing, and performance testing.

Answer-44: A milestone review is a formal assessment of the project?s progress at key points to ensure the project is on track and meets objectives.

Answer-45: Changes are managed through a formal change request process. This involves assessing the impact of the changes, revising project documents, updating timelines, and re-approving the modified scope. Effective communication with stakeholders and ensuring that the changes align with business goals are also crucial for smooth management.

Answer-46: Changes are managed through a formal change request process, ensuring proper assessment, impact analysis, and approval before implementation.

Answer-47: A software architect defines the high-level structure of the system, ensuring it meets technical and business requirements while maintaining scalability and performance.

Answer-48: UML (Unified Modeling Language) is a standardized visual language used to represent system designs, including class diagrams, sequence diagrams, and use case diagrams.

Answer-49: Black-box testing focuses on the system's functionality without knowledge of the internal code, while white-box testing involves testing internal logic and structure.

Answer-50: RTM is a document that maps and traces user requirements with test cases, ensuring all requirements are validated and met during testing.