j****9
发帖数: 2295 | 1 The waterfall software development lifecycle consists of a sequence of steps
product maintenance. What are the issues with following such a model?
不知如何答起。谢谢。 |
s***e
发帖数: 122 | 2 Just for your information: the waterfall approach tries to express all the
requirements before the development, which usually evolves over time as the
development progresses. It tries to define the design and all technologies
in the development up front, therefore can hardly accommodate any change. It
lacks the capacity of mastering complexity. This approach is good only for
simple system of short development duration, with few unknowns and risks.
For a complex system of long duration, with a lo
【在 j****9 的大作中提到】
: The waterfall software development lifecycle consists of a sequence of steps
: product maintenance. What are the issues with following such a model?
: 不知如何答起。谢谢。
|
j****9
发帖数: 2295 | |
b***y
发帖数: 2799 | 4 My opinion is the opposite, and might be wrong.
Waterfall should be used for critical and large systems because these
systems have to be well planned. For simple and small systems, it's more
flexible and volatile, so XP is more suitable.
the
It
for
it
【在 s***e 的大作中提到】
: Just for your information: the waterfall approach tries to express all the
: requirements before the development, which usually evolves over time as the
: development progresses. It tries to define the design and all technologies
: in the development up front, therefore can hardly accommodate any change. It
: lacks the capacity of mastering complexity. This approach is good only for
: simple system of short development duration, with few unknowns and risks.
: For a complex system of long duration, with a lo
|
n****g
发帖数: 150 | 5 the issue is you can follow those steps and imagine you are performing an
artistic creation when there's no boss yelling behind you
steps
【在 j****9 的大作中提到】
: The waterfall software development lifecycle consists of a sequence of steps
: product maintenance. What are the issues with following such a model?
: 不知如何答起。谢谢。
|
F**********r
发帖数: 237 | 6 Design should come after requirement elicitation? I guess the major issue
is frequent changing requirement. Also late integration testing can be a
problem as well. |
