1. i. 1.
The inception of the project, team collaboration and when you
present it.
ii. The rules are rigidly defined so there is no room for human error
especially when you’re dealing with such a complex OS system.
iii. Not very efficient.
2. Extreme programming is when the programmer and the client are
together while the programmer is creating the software, in this case,
the anti-virus software. It is suitable since there is no ambiguity
between the client and the programmer, as while the programmer is
coding, the client can give suggestions and make sure the program
is what they envisioned. As the company continually needs to
update their software, the client can inform the programmer of the
major viruses, and make sure the system is even more robust by
making sure there are no loopholes.
3. Rapid application development is when you create many prototypes
(in this case for mobile phones) of an application and present it to
the client. This is advantageous as the client can model and critique
the prototypes, as necessary. However, this can be quite onerous, as
it will be time consuming and expensive to create many prototypes.
There is a waterfall cycle in which the entire team follow a set
structure. This is good as it is rigid, and all the rules are defined.
However, if the rules are rigidly defined, if an error occurs, you
cannot improvise, however, you could just make a contingency plan.
In conclusion, I believe that rapid application development is the
best, as there is no ambiguity between the client and programmer
and the programmer will know of their expectations for their designs
and code.
4. The team members may consider extreme programming, as
extreme programming is when the programmer and the client are
together while the programmer is creating the software, in this case,
the “De-Duplicator.” It is suitable since there is no ambiguity
between the client and the programmer, as while the programmer is
coding, the client can give suggestions and make sure the program
is what they envisioned. This would be beneficial as the process
would be quick and fast, however this would be quite stressful to the
programmer, as they may need to program the entire project all in
one go. Also, the client may not have a lot of time to look at the
programmer coding, and they may lose money by doting on the
programmer.
There is a waterfall cycle in which the entire team follow a set
structure. This is good as it is rigid, and all the rules are defined.
However, if the rules are rigidly defined, if an error occurs, you
cannot improvise, however, you could just make a contingency plan.
In conclusion, I believe that extreme programming is the best, as
there is no ambiguity between the client and programmer and the
programmer will know of their expectations for their designs and
code.
19/31 = 61.29%
