They also perform several other activities like a senior developer reviewing the other developers code for any issues. Since the application is a banking application and security was a high priority in the application requirements, they implement several security checks, audit logging features in the application.
They take the design documents / artifacts and ensure that their solution follows the design finalized by the architect. The development team works on coding the project. The architect creates the Architecture diagrams and high level / low level design documents. It is decided that the banking application needs to have redundant backup and failover capabilities such that system is accessible at all times.
#WATERFALL METHODOLOGY DEFINITION SOFTWARE#
The architect and senior members of the team work on the software architecture, high level and low level design for the project. How many users are expected to use the application? etc.Do we have to support multiple languages?.Will the new banking application be used in more than one country?.Going through the requirements and analyzing them has revealed that the project team needs answers to the following questions which were not covered in the requirements document – The Business Analysts document the requirement based on their discussion with the customer.
Requirements are documented during this phase and clarifications can be sought. In this phase the requirements are gathered by the business analyst and they are analyzed by the team. Let us assume that the Citibank is planning to have a new banking application developed and they have approached your organization in the 1990’s. Let us understand the concept of Waterfall model with example of a banking application for illustrating the topic. There are several phases in the waterfall model. Phases of Waterfall Model in Software Engineering
0 kommentar(er)
