Software development process Model

A software development process, also known as

a software development life cycle (SDLC), is a structure imposed on the development of a softwareproduct. Similar terms include software life cycle and software process. It is often considered a subset of systems development life cycle. There are several models for such processes, each describing approaches to a variety of tasks or activities that take place during the process. Some people consider a lifecycle model a more general term and a software development process a more specific term. For example, there are many specific software development processes that 'fit' the spiral lifecycle model. Every software life cycle consist of the process started from taking the idea of the project to development and maintenance of the project. Every workflow during the creation of the software is divided into several aspects like eliciting requirements, analysis of requirement, planning, developing, testing etc. The large and growing body of software development organizations implement process methodologies. Many of them are in the defense industry, which in the U.S. requires a rating based on 'process models' to obtain contracts.

Types of process models

There are various types of software models used by the developers to make software feasibly and effectively. We can use any software process model which suits best to us. Below is the list of various process models used by developers to make softwares.

Water flow model. Spiral model Iterative and interactive model Incremental model Prototype model Con-current development model Chaos model

Spiral model

Wateflow model
The waterfall model is a sequential design process, often used in software development processes, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases e. In waterfall model, the following phases are followed in order:
1.

of

Conception,

Initiation, Analysis, Design,

Construction, Testing, Production/Implementation and Maintenanc

Requirements specification

2. 3. 4. 5. 6. 7.

Design Construction (AKA implementation or coding) Integration Testing and debugging (AKA Validation) Installation Maintenance

Thus the waterfall model maintains that one should move to a phase only when its preceding phase is completed and perfected. However, there are various modified waterfall models (including final model) that may include slight or major variations upon this process. We are going to use water-flow model in our perspective project which is Automated Intergroup Transaction.

Wateflow model

Why waterflow model??

Water-flow model is better option than any other model for the small projects. We find water-flow model as a best suitable model for our project. It is less time consuming and we can develop software threw sequential process very effectively. Moreover there are other benefits that can be counted to recommend this software models. Some other benefits of waterflow model are:
1. Progress can be conclusively identified (using milestones) by both vendor and client. 2. Ensures minimal wastage of time and effort 3. Reduce the risk of schedule slippage or of customers expectation not being met. 4. Easy to understand for low level software development. Because of these benefits, we find waterflow model is well suited model for our project. So we have decided to use it.