--Originally published at Computer Systems Engineering
Finally, we are at the last chapter of the book.
This is what we’ve been waiting for, the moment we put all those pices together to make it all part of a single thing. For this we have had followed this developing process:
- Make sure that your software does what the client wants: here we do the feature list, use cases diagrams, break up the project and list the requirements.
- Apply OOP principles to add flexibility: includes domain analysis, preliminary design, and everything to delimit the problem
- Strive for mantainable and reusable design: this is when we implement the solution and we have to make sure we have an order and clear documentation for when we want to add features, update or whatever we need.
When we were thinking about the project i have to admit that sometimes we were to caught up in what we wanted the program to be that we didn’t stop and think what a customer might want/expect from something like that, so we needed to step back and consider the design process, do it in order to have in mind the customer before the program (i think that’s why we had trouble with the use cases in the delivery of the first partial).
The thing that i learned is that we need to follow like a timeline process and, if it is needed, iterate though it to refine everything and define new things that we might have not considered before. So in conclusion it’s everything about ORDER.
