M1:
Compare and contrast different application development models
Assessment Date:
M1:
Compare and contrast different application
development models
Draft Final
Introduction
What are the Software Development Models?
http://istqbexamcertification.com/what-are-the-software-development-models/
The software development models, also known as the software development life cycle models (SDLC), are a several different types of
processes that are used in developing different kind of projects. The type of development model is chosen depending on the aims,
requirements and budgets of the projects. Each type of the model has its own strengths/ weaknesses and its own processes that help with
certain types of projects. The common types of models use today are the waterfall model, the iterative model, the agile development model, the
rapid application development (RAD) model, the spiral model and the prototype model. Even though these models are used for different types
of projects, they all use similar stages throughout the development t process. These stages consist of the planning and requirement stage, the
designing stage, the development stage, the testing stage and finally the deployment stage.
What is this? Characteristics and features Advantages and disadvantages
Waterfall model https://www.tutorialspoint.com/sdlc/sdlc_waterfall_model.htm One advantage of using the waterfall
The waterfall model is a simple process that is used in software development with model is that you can understand it
a liner and sequential approach. This means that the stages are completed in easily as it is simple to use. This means
order so if you start any stage in the process must ensure that the previous stages that you don’t have to spend a great
are completed first. As I mentioned the waterfall model process is divided into amount of time learning it. Another
separate phases and it acts as a downwards mechanism resembling a real advantage is that the waterfall model is
waterfall. So as you go down the stages there is no going back, which means you easy to manage as you can organise
have to complete each stage accurately and with minimal mistakes. Altogether this deadlines for each stage in the model.
model consists of a total of 6 stages: the requirements stage, the design stage, the This is beneficial as you can manage
your time effectively and the stages will
implementation/coding stage, the deployment stage and finally the maintenance
get completed quicker.
stage. The requirement stage involves communication with the client, managers
One disadvantage is that once you’ve
and end users to create a criteria that you need to meet to be able to finish the completed the first few stages it is
project. The next stage is the design stage. This is where you use the look in to difficult to modify the requirements and
, the requirements further and plan out the design specification and technical design change ideas as you have to redo all
requirements. The next stage is the implementation/code stage. This is where you the stages that you have completed.
have to use the requirements from the previous stages and create source coding This can waste a lot of precious time
in small programs called units and implement them in the application. After this, that could have been used for
the next stage is the testing stage. This is where you use several methods to test something more useful. Another
the application and check for any bugs or flaws. This is where you use customer disadvantage is that this model is not
feedback to maintain your application and keep it running. suitable for complex projects. This is
because there would be a lot of risks
and uncertainty during the project, so a
different model would be suitable for
this project.
Appropriate for which types of project/s?
https://airbrake.io/blog/sdlc/waterfall-model
This model would be appropriate for short projects that may need to be done relatively quickly. However in the waterfall model quality is preferred over speed.
The requirements for this project should be fixed and clearly understood as it is really difficult to modify them so there should be little to no changes by you or
the client during the development of the process. For that reason if your requirements are well known by everyone you could consider using the waterfall
model.
Iterative model https://www.tutorialspoint.com/sdlc/sdlc_iterative_model.htm One advantage for the iterative model is
The Iterative model breakdown big applications into smaller chunks and uses that it is easier to find and manage any
the iterative process to further develop the product the product. . The iterative issues during the early stages of the
process is where the development procedure of the product is repeated, each project. This is because you constantly
time developing the previous version until you get the desired results. The repeat and evaluate the development of
model doesn’t start with fully defining the software requirements in detail but the software, each time finding ways to
instead starts developing and implementing part of the software. When further develop the product. Another
developing the software you have to pass through the designing phase, the advantage is that less time is spent on
coding phase and the testing phase to create your first prototype. Then this is documenting all the information and
reviewed and evaluated to identify any improvements and then this process is more time is spent on designing the
product. This is useful as you can start
repeated several times, each time enhancing the previous versions until the
developing prototypes at an early stage.
product bears a resemblance to the final product.
One disadvantage is that the iteration
process requires many resources and
people with a high level of skill for the
evaluation/analysis.
Appropriate for which types of project/s?
https://airbrake.io/blog/sdlc/iterative-model
This model is appropriative for projects that are complex where all the major requirements are clearly defined and understood by everyone. However some
minor details can be left out of this stage as they will later be noticed and then developed overtime. Also during the project the requirements may change so
Compare and contrast different application development models
Assessment Date:
M1:
Compare and contrast different application
development models
Draft Final
Introduction
What are the Software Development Models?
http://istqbexamcertification.com/what-are-the-software-development-models/
The software development models, also known as the software development life cycle models (SDLC), are a several different types of
processes that are used in developing different kind of projects. The type of development model is chosen depending on the aims,
requirements and budgets of the projects. Each type of the model has its own strengths/ weaknesses and its own processes that help with
certain types of projects. The common types of models use today are the waterfall model, the iterative model, the agile development model, the
rapid application development (RAD) model, the spiral model and the prototype model. Even though these models are used for different types
of projects, they all use similar stages throughout the development t process. These stages consist of the planning and requirement stage, the
designing stage, the development stage, the testing stage and finally the deployment stage.
What is this? Characteristics and features Advantages and disadvantages
Waterfall model https://www.tutorialspoint.com/sdlc/sdlc_waterfall_model.htm One advantage of using the waterfall
The waterfall model is a simple process that is used in software development with model is that you can understand it
a liner and sequential approach. This means that the stages are completed in easily as it is simple to use. This means
order so if you start any stage in the process must ensure that the previous stages that you don’t have to spend a great
are completed first. As I mentioned the waterfall model process is divided into amount of time learning it. Another
separate phases and it acts as a downwards mechanism resembling a real advantage is that the waterfall model is
waterfall. So as you go down the stages there is no going back, which means you easy to manage as you can organise
have to complete each stage accurately and with minimal mistakes. Altogether this deadlines for each stage in the model.
model consists of a total of 6 stages: the requirements stage, the design stage, the This is beneficial as you can manage
your time effectively and the stages will
implementation/coding stage, the deployment stage and finally the maintenance
get completed quicker.
stage. The requirement stage involves communication with the client, managers
One disadvantage is that once you’ve
and end users to create a criteria that you need to meet to be able to finish the completed the first few stages it is
project. The next stage is the design stage. This is where you use the look in to difficult to modify the requirements and
, the requirements further and plan out the design specification and technical design change ideas as you have to redo all
requirements. The next stage is the implementation/code stage. This is where you the stages that you have completed.
have to use the requirements from the previous stages and create source coding This can waste a lot of precious time
in small programs called units and implement them in the application. After this, that could have been used for
the next stage is the testing stage. This is where you use several methods to test something more useful. Another
the application and check for any bugs or flaws. This is where you use customer disadvantage is that this model is not
feedback to maintain your application and keep it running. suitable for complex projects. This is
because there would be a lot of risks
and uncertainty during the project, so a
different model would be suitable for
this project.
Appropriate for which types of project/s?
https://airbrake.io/blog/sdlc/waterfall-model
This model would be appropriate for short projects that may need to be done relatively quickly. However in the waterfall model quality is preferred over speed.
The requirements for this project should be fixed and clearly understood as it is really difficult to modify them so there should be little to no changes by you or
the client during the development of the process. For that reason if your requirements are well known by everyone you could consider using the waterfall
model.
Iterative model https://www.tutorialspoint.com/sdlc/sdlc_iterative_model.htm One advantage for the iterative model is
The Iterative model breakdown big applications into smaller chunks and uses that it is easier to find and manage any
the iterative process to further develop the product the product. . The iterative issues during the early stages of the
process is where the development procedure of the product is repeated, each project. This is because you constantly
time developing the previous version until you get the desired results. The repeat and evaluate the development of
model doesn’t start with fully defining the software requirements in detail but the software, each time finding ways to
instead starts developing and implementing part of the software. When further develop the product. Another
developing the software you have to pass through the designing phase, the advantage is that less time is spent on
coding phase and the testing phase to create your first prototype. Then this is documenting all the information and
reviewed and evaluated to identify any improvements and then this process is more time is spent on designing the
product. This is useful as you can start
repeated several times, each time enhancing the previous versions until the
developing prototypes at an early stage.
product bears a resemblance to the final product.
One disadvantage is that the iteration
process requires many resources and
people with a high level of skill for the
evaluation/analysis.
Appropriate for which types of project/s?
https://airbrake.io/blog/sdlc/iterative-model
This model is appropriative for projects that are complex where all the major requirements are clearly defined and understood by everyone. However some
minor details can be left out of this stage as they will later be noticed and then developed overtime. Also during the project the requirements may change so
