SDLC interview questions

1. What is Software life cycle? The life cycle begins when an application is first conceived and ends when it is no longer in use. It includes aspects such as initial concept, requirements analysis, functional design, internal design, documentation planning, test planning, coding, document preparation, integration, testing, maintenance, updates, retesting, phase-out, and other aspects.

2. Define SDLC as you would define it. Requirement Analysis: Feasibility study, outline requirements. Requirements Definition: Requirement specification. System specification: Functional specification, Acceptance test specification, Draft user Manual. Architectural Design: Design architecture specification, System test specification. Interface Design: Interface specification, integration test specification. Detailed design: Design specification, Unit test specification. Coding: Program code Unit Testing: Unit test result report. Module testing: Module test result report. Integration testing: Integration test report, final user manual. System Testing: System test report. Acceptance Testing: Final Report.
3. Describe your personnel Software Development process? 4. What is the Water Fall Development method and do you agree with all the Steps?

Ans: In a typical model, a project begins with feasibility analysis. On successfully demonstrating the feasibility of a project, the requirement analysis and project planning begins. The design starts after the requirements analysis is complete, and coding begins after the design is complete. Once the programming is completed, the code is integrated and testing is done. On successful completion of testing, the system is installed. After this, the regular operation and maintenance of the system takes place. 5. What is Prototyping Model of Software Developing? Ans: A prototype is a toy implementation of a system; usually exhibiting limited functional capabilities, low reliability, and inefficient performance. There are several reasons for developing a prototype. An important purpose is to illustrate the input data formats, messages, reports and the interactive dialogues to the customer. This a valuable mechanism for gaining better understanding of the customers needs. Another important use of the prototyping model is that it helps critically examine the technical issues associated with the product development 6. What is the V-Model? 7. What is Spiral model and its Life Cycle? Ans: It provides the potential for rapid development of the software. In the spiral model, software is developed in a series of incremental releases. During early iterations, the incremental release might be a paper model or prototype. Life cycle: Each iteration consists of Risk Analysis, Engineering, Construction, Release and Customer Evaluation. Customer Communication: Tasks required establishing effective communication between developer and customer. Planning: Tasks required defining resources, timelines, and other project related information. Risk Analysis: Tasks required to assess both technical and management risks.
Construction and Release: Tasks required to construct, test, install and provide user support. (e.g. documentation and Training) Customer Evaluation: Tasks required obtaining customer feedback based on evaluation of the software representations created during the engineering stage and implemented during the installation state. After accepting a software proposal, the corresponding project managers should one of the available 5 sdlc model to follow in the development cycle.

There are 5 SDLC models available currently. They are

1. Waterfall Model 2. Prototype Model 3. Incremental Model 4. Spiral Model 5. V-Model

Waterfall Model: When the customer requirements are clear and complete Requirements Gathering>Analysis & Planning> Design> Coding> Testing> Release & Maintenance Prototype Model: When the customer requirements are unclear and confusing Incremental Model: When the customer requirements are clear but not complete, because client is giving requirements in installment basis. Spiral Model: When the customer requirements are clear and complete but enhancing in future Note: In above 4 SDLC models the testing is available as one stage and the stage was also conducted by same developers. Due to this the organizations are concentrating on multiple stages of testing and separate testing teams for quality software development. V-Model: V- stands for Verification and Validation It is a recognized model by organizations This model defines the mapping in between multiple stages of development and multiple stages of testing

To decrease project cost,the organizations are maintaining the separate testing team only for system testing. Because the system testing stage is working as bottle neck stage in software development.