Waterfall model

Question 3:

1. Requirement characteristics:

·         Reliability:
…
With all the reliability, this project is suitable for the Waterfall model because:
+ The Waterfall model is one the easiest model to manage. Because of its nature,
each phase has specific deliverables and a review process.
+ It works well for smaller size projects where requirements are easily
understandable.
+ The Waterfall model faster delivery of the project.
+ The Waterfall model also has process well and the results are well documented.
+ Easily adaptable method for shifting teams and this project management
methodology is beneficial to manage dependencies.
+ The Waterfall model is very simple and easy to understand, each stage in the
model is clearly defined so the waterfall model is an idealistic model for this project.
+ This model also has good habits like: define-before-design because which is
considered one phase can be started after completion of the previous phase.
·         Types and number of requirements:
+ The number of requirements in this project are clearly defined and requirements
are well understood, this is an advantage of the Waterfall model. This model
assumes that all customer requirements can be completely and correctly defined at
the beginning of the project. 
+ Business analysis prepares requirements before the beginning of the project.
·         How often the requirements can change
+ In this project, the method is ideal for projects which have definite requirements
and changes not at all expected.
+ It is difficult for the test to initiate any change in requirements.
·         Can the requirements be defined at an early stage
+ Requirements in this project are very well documented, clear and fixed at an early
stage and no ambiguous requirements so Waterfall model is the best choice for this
project.

·    

2. Development team
…
3.                   User involvement in the project.
- At the time of development, user involvement is small because the system is based on
an older, existing one so it is not significantly necessary. However, after the first
deployment, user involvement can be considerably more important as it is needed in
improvement of later versions of the system. It is difficult to accommodate any change
requests after the requirements specification phase is complete.
4.                   Conclusion

·         Based on the above assessment, I believe that the Waterfall model is the best fit
for the case because the requirements are well defined and not likely to change. The
 team is relatively small so the team should have members focus on one stage at a
time. The requirements do not specify any important part of the system that can be
beneficial to be deployed first so development in increments is not necessary.

V-model
Question 3:

1. Requirement characteristics:

·         Reliability:
…
With all the reliability, this project is suitable for the V-model because:
+ The V-model is known as the Verification and Validation model. It is based on the
association of a testing phase for each corresponding development stage.
Development of each step directly associated with the testing phase.
+ The V-model is a highly disciplined model and phases are completed one at a
time, it also focuses on verification and validation activities early in the life cycle
thereby enhancing the probability of building an error-free and good quality product.
+  The V-model is used when ample technical resources are available with technical
expertise. The requirements are clearly defined and fixed.
+ The V-model avoids the downward flow of the defects and it also works well for
small projects where requirements are easily understood like this project.

·        Types and number of requirements

+ The number of requirements in this project are clearly defined and requirements
are well understood, this is an advantage of the V-model model because this model
works well for small projects where requirements are easily understood.
+ In the V-model, requirements identified by the project team create high-level
design, and detailed design phases of the project. As each of these phases is
completed the requirements become more and more refined and detailed.
·         How often the requirements can change
+ In this project, the requirements are clearly at the first stage because the V-model
is not suitable for the project where requirements are not clear and contains high risk
of changing.
+ If any changes happen in midway, then the test documents along with requirement
documents has to be updated.
·         Can the requirements be defined at an early stage
+ Requirements in this project are very well documented, clear and fixed at an early
stage and no ambiguous requirements so V-model model is the best choice for this
project.
2.                   Development team:
…
3.                   User involvement in the project
- At the time of development, user involvement is small because the system is based on
an older, existing one so it is not significantly necessary. However, after the first
deployment, user involvement can be considerably more important as it is needed in
improvement of later versions of the system. It is difficult to accommodate any change
requests after the requirements specification phase is complete.
4.                   Conclusion
·         Based on the above assessment, I believe that the V-model is the best fit for the
case because the requirements are well defined and not likely to change. The team
is relatively small so the team should have members focus on one stage at a time.
The requirements do not specify any important part of the system that can be
beneficial to be deployed first so development in increments is not necessary.

Agile model
 

Question 3:

a.       Requirement characteristics:
·         Reliability:
…

With all the reliability, this project is suitable for the Agile model because:

- The Agile model is focused client process. So, this project makes sure that the
client is continuously involved during every stage.

- The Agile teams are extremely motivated and self-organized so it likely to

provide a better result from this development project.

- The Agile software development method assures that quality of the

development is maintained.

- The process is completely based on the incremental progress. Therefore, the

client and team know exactly what is complete and what is not, this reduces risk
in the development process.

·         Types and number of requirements

-   The number of requirements in this project frequently changes. In the
Agile model, the highly qualified and experienced team is available so
sometimes a customer is ready to have a meeting with a software team
all the time. The project size is small and also needed in this Agile project.

How often the requirements can change

- The Agile model is quite a flexible method which allows changes to be
made in the project development requirements even if the initial planning
has been completed.
 - Products owner with team prepares requirements just about every day
during a project.
- The Agile development is a process in which the requirements are
expected to change and evolve.

- The Agile model is suitable for fixed or changing requirements so it

delivers early partial working solutions. The administration chooses a
good model for environments that can change steadily and are easy to
manage.
·         Can the requirements be defined at an early stage
-          The Agile model has minimal rules, documentation easily employed,
it also enables concurrent development and delivery within an overall
planned context.
- Requirements in this project are very well documented, clear and fixed
at an early stage and no ambiguous requirements so Waterfall model is
the best choice for this project.
b.      Development team
… 
c.       User involvement in the project
- Customers should be closely involved throughout the development process.
Their role is provided and prioritize new system requirements and to evaluate
the iterations of the system.
- The Agile model follows 6 steps: Requirements gathering, Design the
requirements, Construction/iteration, Testing/ Quality assurance,
Deployment, Feedback. So after releasing the product, the last step is
feedback. In this, the team receives feedback about the product and works
through the feedback. 
o Conclusion

-          Based on the above assessment, I believe that the Agile model is the
best fit for the case because the requirements are frequent delivery. The
requirements also known as face-to-face communication with clients and
its efficient design and fulfills the business requirements. The requirement
system can change anytime and it is acceptable so the system can be
beneficial to be deployed first so development in increments is not
necessary.