Software Development Life Cycle

1. What are the Disadvantages of Prototype Model?

Ans. Implementing the prototype model for creating the software has its disadvantages. Since it is being built out of concept, most of the models presented in early stage are not complete. They lack flaws that the developer still needs to work on them again and again. The Integration cannot be very difficult for prototype models. Hence this often happens when the other programs are already stable.

2. What is the difference between an Iterative model and the Waterfall model?

Ans. Waterfall Model is a flow based model, in which we pass every phase once, and can not go back to that phase again. Its most eminent drawback is that if there is any change in requirements, we cannot make any changes to the requirement section. Iterative Model is somewhat similar to waterfall model but herein we can always come back to previous phases, and make the changes accordingly.

3. Explain spiral model?

Ans. Spiral model is one of the different models implemented under Software Development life cycle. It is very easy to understand by both the developer and customer and react to the risk at each elementary level.It uses reduction of the mechanism. It is divided into number of framework.

4. What are the advantages of Prototype Model?

Ans. Creating software using the prototype model has its benefits. One of the key advantages prototype model software has is its time frame of the development period. Everyone works on the same module and at the same time, hence reducing work hours in creating the software. This work can be faster and more efficient if developers could collaborate more regarding the status of specific functions and thereby develop the necessary adjustments in timeline for the integration.

5. How many types of Prototype models are there?

Ans. There are four types of Prototype Models:

I. The Patch-Up Prototype
II. Nonoperational Prototype
III. First-of-a-Series Prototype
IV. Selected Features Prototype

6. What are the different phases in SDLC?

Ans. There are 5 phases in Software Development Life Cycle:

1. Requirement & analysis
2. Design
3. Coding
4. Testing
5. Maintenance

7. Explain the Difference between SDLC and STLC?

Ans. SDLC is a software development life Cycle model which is utilized for project management and involves processes from the feasibility Analysis to maintenance of the completed application. STLC is Software testing Life cycle and SDLC work closely together and are almost inseparable under some of the activities. However the stages are very different under sdlc and stlc.

8. What is SDLC.net?

Ans. When a person is utilizes the Dot Net library or Framework to create an application application,the process is termed SDLC.Net.

9. What are functional requirements?

Ans. Functional requirement is a document which contains what a certain system has to do to achieve a certain specific objective.This task is carried out during the preliminary stage of SDLC.

10. What are Non-functional requirements?

Ans. Without Non-functional, a software will never function or will have vital missing information in its output. Response time, security, reliability, accuracy, capacity and availability are examples of Non functional requirement for a software development process. Non functional requirements decides how the Program or the software will function in future.

11. What is Software Life Cycle?

Ans. Software life cycle comprise the total life of the software developed right from the time of initial development to the time it is scrapped out or terminated. This includes the development phases, revisions and upgrades and if necessary adding it up with another software project as well.

12. Is it mandatory to implement SDLC methods while developing any type of software project?

Ans. This is a tricky question and must be tackled smartly. Yes you can sure implement SDLC approaches for every type of software you want to develop. But it is not a cost effective solution for smaller projects. For every kind of software development needs different approach and solution and must not be considered to be developed under mandatory SDLC guidelines.

13. Are SDLC and STLC two different aspects of software development process?

Ans. No they are not different aspects of the development process. Rather they are closely related to each other and it is totally impossible for them to individually exist. If there is no software development process there cannot be a software testing phase and no software development process can be completed without testing the developed software.

14. Waterfall model is not suitable for?

Ans. Some of the suitable situations for using a Waterfall model are -

1. The software Project is limited to the development of a mainframe-based/transaction-oriented batch system.
2. The Complete Project is very large, costly and too much complicated.
3. The project objectives and solutions are clear.
4. There is no time frame pressure for quick project deployment.
5. The Project has stable and definite requirement which need not change in the future.
6. The project group (including project leader) is not very experienced.

15. What are some possible problems with waterfall model?

Ans. Some of the most common problems one might face while working with waterfall model are -

• Waterfall model is not suitable for multiple module projects.
• It does not support the feasibility of considering requirement specifications.
• It requires too much time to complete each stage.
• There can be a few bugs at the end which cannot be rectified as well.

16. What is the difference between Incremental model and Spiral model?

Ans. There is not much difference between these two sdlc models. Sdlc spiral Model includes the iterative nature of the prototyping model and the linear nature of the waterfall model. This approach is ideal for developing software that is revealed in various versions.

17. What is advanced sdlc waterfall methodology?

Ans. Any software development model that follows the basic linear flow of the waterfall model but has been modified to complete specific project types are called advanced sdlc methodology. Such models do not have name or either can be standardized to allow software developer to use them around other sdlc projects. Some sdlc interviewer however might claim Agile to be one of such models but it is not entirely true.

18. Give some practical real life examples of Spiral Model

Ans. The most popular real life examples for sdlc Spiral model are Microsoft Windows operating System, Visual Studio Manager, Adobe Photoshop, WordPress CMS and many more.

19. Why is Agile so popular?

Agile methodology is way too advanced and complex than the simple Waterfall model. The feasibility of agile to reshape the entire development structure to suit the most effective outcome is what makes Agile the number 1 choice of developers today.

20. Can I build a software project without sdlc models?

Ans. Of course. There is no hard and fast requirements for a developer to implement any sdlc model for developing a software project. The ability to simplify project into modules and ascertain correct progression for completion is the only reason for which sdlc models and methodology was designed in the first place. You can sure work without them but the challenges will be more and there won’t be any specific process to organize your work as a whole.