Explain the Principles of software development
models.
Introduction
These principles are a pack of instructions which help the developer during the process of
software development and after the development of software as it needs maintenance, so the
developers stay engaged. These principles play a vital role in the development of software
models as it gives developer a clear set of plan/instructions. Here are some software
development models:
● Waterfall model
● System life cycle
● Alternative models such as RAD model, agile model, prototyping.
Waterfall model
This is the model which is used in system development life cycle to produce a system with a
sequential procedure. This model is known as a waterfall because it evolves in an order which
moves downward in phases. Furthermore, waterfall is diverged into diverse phases & used as
inputs and inputs. As, input of a next phase comes from the output of previous phase.
Moreover, there is a rule for this process to be accomplished and that is all the phases must be
completed before the next phase begins. Also, there is no intersecting in waterfall model.
, Phases of waterfall model are shown in the image above. These phases are briefly explained below:
Requirement gathering and analysis
Requirement gathering is the phase where all the possible requirements are collected in the
documents of the product. Additionally, the development team analyses the requirement and
understands the issue entirely.
System design
Senior management and designer work on the organisation of system, levels of design for the
project. For example, high/low level of design.
Implementation
For implementation phase, coding is needed & development team has the responsibility to
code the project. The development team take the document where the design is made, and
they make sure that the solution they have is according to the design finalised by the designer.
The development team performs multiple other tasks such as a code of other developer gets
reviewed by a senior developer for any problems. Furthermore, there are also some other
developers who analyse the statistics of the code.
Testing
In the testing phase, there is a team who tests the entire application or a system and tries to
detect defects in the application. Furthermore, to fix these flaws there is a tea of developers
who fix them, and the testing team again tests the application to guarantee that the founded
flaws are fixed.
This testing team also performs retrogression testing of the application to see if there are any
new flaws in the system.
Deployment
Here is the triggering phase where the software gets installed and introduced to the real
environment after the previous phase of testing.
Maintenance
Last and final phase of the waterfall model known as maintenance. After some time, the
software might require you to update to avoid any sort of deficiency & to keep it working in the
real-world conditions. Furthermore, this phase (maintenance) maintains this activity by tuning
of the software as it requires.
models.
Introduction
These principles are a pack of instructions which help the developer during the process of
software development and after the development of software as it needs maintenance, so the
developers stay engaged. These principles play a vital role in the development of software
models as it gives developer a clear set of plan/instructions. Here are some software
development models:
● Waterfall model
● System life cycle
● Alternative models such as RAD model, agile model, prototyping.
Waterfall model
This is the model which is used in system development life cycle to produce a system with a
sequential procedure. This model is known as a waterfall because it evolves in an order which
moves downward in phases. Furthermore, waterfall is diverged into diverse phases & used as
inputs and inputs. As, input of a next phase comes from the output of previous phase.
Moreover, there is a rule for this process to be accomplished and that is all the phases must be
completed before the next phase begins. Also, there is no intersecting in waterfall model.
, Phases of waterfall model are shown in the image above. These phases are briefly explained below:
Requirement gathering and analysis
Requirement gathering is the phase where all the possible requirements are collected in the
documents of the product. Additionally, the development team analyses the requirement and
understands the issue entirely.
System design
Senior management and designer work on the organisation of system, levels of design for the
project. For example, high/low level of design.
Implementation
For implementation phase, coding is needed & development team has the responsibility to
code the project. The development team take the document where the design is made, and
they make sure that the solution they have is according to the design finalised by the designer.
The development team performs multiple other tasks such as a code of other developer gets
reviewed by a senior developer for any problems. Furthermore, there are also some other
developers who analyse the statistics of the code.
Testing
In the testing phase, there is a team who tests the entire application or a system and tries to
detect defects in the application. Furthermore, to fix these flaws there is a tea of developers
who fix them, and the testing team again tests the application to guarantee that the founded
flaws are fixed.
This testing team also performs retrogression testing of the application to see if there are any
new flaws in the system.
Deployment
Here is the triggering phase where the software gets installed and introduced to the real
environment after the previous phase of testing.
Maintenance
Last and final phase of the waterfall model known as maintenance. After some time, the
software might require you to update to avoid any sort of deficiency & to keep it working in the
real-world conditions. Furthermore, this phase (maintenance) maintains this activity by tuning
of the software as it requires.
