Intruduction

Chapter 3

The sashimi model (so called because it feature overlapping phases, like the overlapping fish of Japanese sashimi) was originated by DeGrace (2008). It is also referred to as the “waterfall model with overlapping phases “or” the waterfall model with feedback”. Since phases in the sashimi model overlap, information of then problem spots can be acted upon during phases of the waterfall model typically “precede” others in the waterfall model.

Sashimi process is a way of organizing a waterfall with feedback. The phases overlap to slow that requirements can’t be completed until architecture is at least partially explored, and architecture can’t be completed until module design is at least partially explored, and so on. The sashimi process is most appropriate for medium-sized projects for which the communication between phases can be handled in an improvised manner. For larger projects, high-risk, or projects in which few of the developers are experienced, a spiral approach may be better.

The developers used Sashimi Waterfall model. This 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. It will serve as a guide for the developers in developing project.

This method given a fair number of insights on each development phases, thus it is likely to be appropriate and absolutely suitable for the development of the project.

Figure 3.1 Sashimi Model

Software Concepts. In this phases, developers must understand and construct a generalized plan on how to develop good software,

In this phases, the developers conducted interviews with the stakeholders of New Star. Inc. to elicit data in development of then system....