:TOO HIGH:

: HIGH: WD= WORKING DAYS:

: MEDIUM:

: AVERAGE:

: LOW:

NOTE: These values have been given to the module by the comparison within the model.

CLIENT SUPLEMENTR COMLEXIT COST TIME SUCCESS RISK

Y Y IN RATE INVOLVEMEN
INTERACTION
REQUIRMENT HANDLING WD T

WATERFALL WELL-DEFINED LOW 120-

MODEL 180

PROTOTYPE NOT MEDIUM 120-

MODEL WELL-DEFINED BUT 180 depends depends
CAN
GO
HIGH
LOOPY LINEAR
SEQUENTIAL WELL-DEFINED MEDIUM 120-
MODEL 180

RAD WELL-DEFINED MEDIUM 90-

MODEL 120 depends

INCREMENTAL NOT MEDIUM 120-

MODEL WELL-DEFINED 180
NOT
SPIRAL WELL-DEFINED MEDIUM 120-
METHOD AND HIGH 180

NOT WELL-DEFINED
AT THE START BUT ARE
WIN-WIN RESOLVED WHEN MEDIUM 120-
SPIRAL INTERACTION B/W AND HIGH 180
METHOD STOCK HOLDERS AND
DEVELOPER IS CARRIED
OUT
WATERFALL MODEL:

2*2: This model follows SDLC process. Client interaction in waterfall module is
very low as it follows sequential processing thus do not need client interaction in
the last 3 phases of SDLC.
2*3: Waterfall model requires both basic project requirement and supplementary
requirements as well.
2*4: It can only handle lower complex projects as it involves low client interaction
so uncertainty levels are higher in case of larger projects.
2*5: Since it follows SDLC process, so cost of the project will be higher than the
prototype model but is medium in comparison between other models.
2*6: It follows the default working time of SDLC process.
2*7:It has low success rate when it comes to higher projects but is OK for lower
complex projects.
2*8: It has high risk involvement as interaction and evaluating is very little or in
other words, not involved which increases uncertainty level.

PROTOTYPE MODEL:

3*2: Prototype module has an average client interaction as it involves evaluating

of the prototype from clients. It can have higher interaction depending on the client
(education) and the project itself.
3*3: It can work even when supplementary requirements are not defined.
3*4: It can handle medium size projects since it involves evaluating of prototypes
from client which lowers uncertainty.
3*5: Overall, the cost of this model is low but if the number of evaluation
increases, then cost of the model also increases.
3*6: It follows the standard working time to complete a project which is 120 days
to 180 days.
3*7: It has medium success rate but when evaluation goes higher than success rate
decreases.
3*8: It has some level of risk involved. That is if the initial prototype get accepted
by the client then its fine but if the evaluating phase goes too long than developer
always try to compromise with the info regarding the next prototypes.

LOOPY LINEAR SEQUENTIAL MODEL:

4*2: It also follows SDLC process steps so client interaction is low in it as well.
4*3: As it follows waterfall model so supplementary requirements are also needed.
4*4: It can cover medium sized projects as it involves iteration between phases.
4*5: Its cost is higher than the waterfall model, as it involves that looping function
of the model which will decrease the uncertainty level of the overall project.
4*6: It follows the standard time required to complete a project.
4*7:It has high success rate in case of lower projects as compared to waterfall
model but cannot cover complex level projects.
4*8: It has again medium risk involvement as interaction is very low in it but is
low than the waterfall model as it involves iteration.

RAD MODEL:

5*2: This model involves medium interaction of client and developer. The reason
is that the project is divided into small functions and evaluation of these functions
from client is also required.
5*3: Basic requirements must be defined but it is not supplementary requirement
dependent.
5*4: It also cover medium size projects as it involves group of experts.
5*5: Since it involves fast processing system, which requires experts so the cost of
this model is also high.
5*6:As it is fast in processing, so it has a working time of 90-120 days of time to
complete a project.
5*7: It has high success rate in case of medium complex projects but cannot handle
high level projects that requires low risk involvement.
5*8: It has low risk involvement but there is still a little bit of risk involved as due
to urgency some information may be left aside.

INCREMENTAL MODEL:

6*2: This module follows prototype like process but dividing the project in small
module which also involves evaluating of each module from client so it involves
medium type of interaction. It can also vary according to the complexity of the
project.
6*3: It does not depend on supplementary requirements whether provided or not.
2*4: Can cover up to medium size projects.
2*5: Its cost is high, as many modules are made and are evaluated through clients.
It can increase depending on the complexity of the project and clients (education
level).
6*6:follows standard working time but can be low than that depending on the
complexity of the project.
6*7: It has medium success rate which lower than spiral and win-win model.
6*8: It has an average risk involvement as each module made is evaluated through
client.

SPIRAL METHOD:

7*2: The main purpose of spiral module is to lower the risk in making the product
so for that reason interaction between client and developer becomes high.
7*3: Like most of the others model, it is also not supplementary requirement
dependent.
7*4: It can cover both medium and high-level projects as this model is all about
risk handling which is needed in high level projects.
7*5: Its cost is high as, it involves experts to lower risk involvement, which is
expensive.
7*6: It also follow the default working time of project handling.
7*7: It has high success rate which is lower that win-win model but higher than the
other given models.
7*8: It has low risk involvement as there is a team of experts to handle the risk that
will be encountered during the project.

WIN-WIN SPIRAL METHOD:

8*2: Client involvement is very high in win-win spiral method. The reason is that
in this module, we have to cover all the requirements of the stack holders to
remove risk involvements and thus to produce high quality product.
8*3: It do not depend on supplementary requirements. But get defined when
further time increases.
8*4: It also cover both high and medium complex projects as its success rate is
very high.
8*5: It is one of the highest resource consumption models since, it involves all the
requirements needed which are collected though the interaction between the stack
holders and developer which eventually becomes high.
8*6: Similarly, like spiral model, it has the same default working time but can go
higher depending on the size of the project.
8*7: It has the highest success rate as compared to the above given model due to
lower risk involvement.
8*8: It has very low risk involvement as it requires all the requirements of the
stack holders of that project which lowers the risk involvement.