Conclusion and Acknowledgment

Conclusion

In this project, I iteractively develops a distributed, multi-user spreadsheet. I built 9 prototypes, each prototype is based on it ancestor prototype, and each prototype implements a new requirement. Each prototype modifies a minimum number of classes that are inherited from a previous prototype. So the effort to build the whole project is quite less than that tobuild a whole system in one time. From the UML classes diagram, we can see that each new diagram is obtained by adding some new classes, the whole frame or basic structure does not change during the iterative development. This is due to the following tow reasons:
  1. The main contribution is using design pattern. Since a design pattern clearly assigns different functions to different participants, any change to one participant will not affect the others. With the structure of a design pattern, we can easily add new stuff.
  2. Thanks for discussing with Professor Hans, we made a good plan. In this plan, we set which requirement should be fulfill in which prototypes.
  3. So always keep your final product requirments in mind when you implement every prototype.

Acknowledgment

Thanks Professor Hans Vangheluwe for giving a lot of indispensable suggestion and help.