|
|
 |
|
| |
| The name "Sashimi" comes from
a Japanese hardware development model (from Fuji-Xerox)
and refers to the Japanese style of presenting overlapping
slices of raw fish. |
 |
The Sashimi Waterfall model
suggests a strong degree of overlap between the
phases of a software development life cycle. For
example, architectural design and detailed design
may be partially completed before requirement analysis
is considered complete. This approach is especially
suitable for projects requiring gainful insights
into each layer as they move through their development
life cycles.
Unlike the Pure Waterfall Model where complete documentation
is provided to the team handling the next phase,
Sashimi Waterfall Model suggests personnel continuity
between phases. |
|
|
|
|
|
|
|
