Appendix:
What did we learn working in team?
1. It is very important to have a reliable teammate. Not only reliable working on time but also to accomplish task and innovative to work on any task. The best of our team was that every team member works on the stuff which is pending, when others are trying to accomplish other tasks. All of us do their task voluntarily without actually assigning them. This helps us in order to split our job into pieces and simultaneously work on the single project. Overhead on every team member was zero.
2. We all participate in design and coding all together, this help us to understand the each and every step of progress in the project. It is important to understand the others opinion. This helps us to increase the productivity and efficiency of the project.
What did we learn working on others codebase?
1. When we scrutinize others codebase, we analyze what is good and what is bad in the programming styles, design, architecture.
2. Working on the others code base needs extra time to understand others ideas.
3. If documentations on codebase or comments provided on each and every files are insufficient and inadequate, it burdens on the programmers who are going to work on this codebase.
What did we learn from programming in A5?
1. It is important to have names of classes, methods etc to follow certain style guides.
2. It is important to keep it in mind whenever we program any code, that any other programmer can use this codebase to extend it. It is important to think of its future use not only by considering programmers in mind but program's extendibility and expandability.
3. While creating program, use of modularization is important so as to get each module or class have its own responsibility. It is isolated from others, and can be still linked with clear and clean code.
4. The module should have reusability in term of future implementation.
5. We need to understand what the basic purpose of each and every module. Such as in A5, each method has to be singleton. It is important to have data separate from the method. It shouldn't hold data inside it.
6. Duplication should be only on data such as clone or "new" an instance. Command, Executor, Action we used in A5 are based on this idea.