SEN Practical no 3
SEN Practical No 3
Select the process model to define activity and related task for assign project. In bank management System we have used waterfall model.
Select the process model to define activity and related task for assign project.
In bank management System we have used waterfall model.
waterfall model
The waterfall model is a classical model used in system development life cycle to create a system with a linear and sequential approach. It is termed as waterfall because the model develops systematically from one phase to another in a downward fashion.This model is divided into different phases and the output of one phase is used as the input of the next phase. Every phase has to be completed before the next phase starts and there is no overlapping of the phases.
The sequential phases described in the Waterfall model are:
1. Requirement Gathering- All possible requirements are captured in product requirement documents.
2. Analysis Read - the requirement and based on analysis define the schemas, models and business rules.
3. System Design -- Based on analysis design the software architecture.
4. Implementation Development of the software in the small units with functional testing.
5. Integration and Testing Integrating of each unit developed in previous phase and post integration test the entire system for any faults.
6. Deployment of system - Make the product live on production environment after all functional and nonfunctional testing completed.
7. Maintenance Fixing issues and release new version with the issue patches as required.
The waterfall model is a classical model used in system development life cycle to create a system with a linear and sequential approach. It is termed as waterfall because the model develops systematically from one phase to another in a downward fashion.This model is divided into different phases and the output of one phase is used as the input of the next phase. Every phase has to be completed before the next phase starts and there is no overlapping of the phases.
The sequential phases described in the Waterfall model are:
1. Requirement Gathering- All possible requirements are captured in product requirement documents.
2. Analysis Read - the requirement and based on analysis define the schemas, models and business rules.
3. System Design -- Based on analysis design the software architecture.
4. Implementation Development of the software in the small units with functional testing.
5. Integration and Testing Integrating of each unit developed in previous phase and post integration test the entire system for any faults.
6. Deployment of system - Make the product live on production environment after all functional and nonfunctional testing completed.
7. Maintenance Fixing issues and release new version with the issue patches as required.
When Should you use it?
Requirements are clear and fixed that may not change.There are no ambiguous requirements (no confusion).It is good to use this model when the technology is well understood.The project is short and cast is low.Risk is zero or minimum.
Requirements are clear and fixed that may not change.
There are no ambiguous requirements (no confusion).
It is good to use this model when the technology is well understood.
The project is short and cast is low.
Risk is zero or minimum.
Advantages of waterfall model.
This model is simple and easy to understand and use. It is easy to manage due to the rigidity of the model – each phase has specific deliverables and a review process. In this model phases are processed and completed one at a time. Phases do not overlap.
This model is simple and easy to understand and use. It is easy to manage due to the rigidity of the model – each phase has specific deliverables and a review process. In this model phases are processed and completed one at a time. Phases do not overlap.
