Ir al contenido principal

Forward, Backward, Land in sight


Hello again everyone, on Friday, October 11, we continued working with the pending work, which was related to the correction of some details that the teacher had previously detected in our SRS document; in addition to continuing with the development of our design document. Despite the time that the teacher gave us to work with our project (basically most of Friday's class), as a team we felt a bit disappointed since we believed that the previous documents were well inspected, but thanks to the feedback from the teacher we realized that we passed some minimum details that we did not contemplate in the specification.

But that was not an obstacle, although we had to do a bit of rework regarding the modification of the SRS and the inspections of the whole document; we felt better at the end of these corrections and we also realized even more the importance of reviewing that important details are included and defined that contribute to the development of our project, however minimal they may be (sometimes due to pressure and work they can go unnoticed). That Friday we started a little pressured but throughout the day we managed to specify and carry out the activities and work necessary to make those corrections, in addition to continuing with the application design document as planned from days before. We realized again the importance that we are a good team and that together we can continue to achieve the goals we set ourselves despite the delays and falls we have as a team.



Then on Monday, October 14, the teacher gave us a review in class about the processes of the ISO 29110 standard related a bit with the PM and SR, how we were at that time, what we have to take into account in the work that we were doing and in the rest, in addition to some points that we should not overlook as in the importance of the requirements and the specifications or elements that at least must be present in our design documents such as: the justification of the architecture, definition of user interfaces and main components of the database. In addition, she also told us about the importance of having integration plans for the construction and verification of our product.

More than anything, the objective of the class was to see that we are making progress as planned and that there are no doubts about the work. The teacher asked each team how we were going about our plans and current work and apparently the whole group was late with a few hours or days regarding our plans. We realized time is progressing faster and there are still several tasks and activities to be done, but we always try to do our best to know what we are doing and thus avoid rework, although that is taking us a little more of time. In our case we continue working with the design document and review some aspects necessary to prepare the beginning of the implementation of our project.

On Tuesday we continue working as we have been doing and this time with the design of the application, we continue to complete it in order to finish it in the best possible way so that we are all clear about how the application will work in great aspects to continue with the development of it, correcting some details and adding new elements. In case we feel better because in spite of going back with respect to our plan we go a long way with respect to the design to the extent that we all knew more about how our product will work and define general characteristics; although we are still concerned about the fact of the remaining time and the tasks to be done, since we manage to identify more risks for teamwork and times that we must work; which makes us worry to make you want more, recover back times and move on with the project.



On Wednesday we continue working with the development of the project in its design phase; for which the teacher in her class explained general aspects about product implementation, system integration and testing and finally the postmortem (related to some of the processes handled by TSPi) to advance a bit with respect to the issues of the class and also to see that these are the activities that at some point in the development of the project we will have to perform step by step. This progress in class makes us think about the work we have to do, that as a team we must move forward as we commit ourselves to do it and we can achieve it. Something we liked and motivated the most was that the teacher believes in us and that we must learn to empathize with our team; which will sometimes mean clearing a little of the usual work routine and doing recreational activities as a team, since human resources (people) are the most important when we are talking about software development.
After class we were working on the pending work with respect to the design document already in its final stages and technical issues were also seen regarding the tool that we will be using for the development of the application: Flutter. Therefore we were seeing all those details to prepare each time for the development phase of the application once we finish the design phase. We are feeling again that we are moving forward despite all the setbacks, so the team's spirit is improving even if we have to work weekends to recover, we will do everything in our hands to move forward and not let the bad times surpass us.

Finally we will finish the design document, to continue with the inspections of the same. At last! At least this way we already feel that we are moving forward more and that we no longer have so much workload, although we know that there is still work at least it gives the feeling that we complete one more block of it. In this way we feel better as a team because the individual work of each participant is being reflected in a positive way in the advances the project.


“Do not study to earn money, study to learn. What you learn today is what you will be tomorrow.”

Bill Gates

Comentarios

Entradas populares de este blog

This is our solution, what do you think about it? 💡

Hello!👋 We are pleased that you are visiting our blog again. After validating our solutions with the users and obtaining the solution that we will be executing during the development of our project, it is necessary to communicate that solution to our classmates and the teacher. For this reason, during the session of Friday we exposed the solutions to each of our problems, it was a very interesting session, and we learned a lot, because after all the presentations, advice and feedback were given to each of the teams, which is very important, because we know that it is difficult to think about everything and with this type of sessions we can realize something that we had not contemplated. After our presentation we felt a little crestfallen because we realized that we had omitted something very important in our presentation, the prototype; we were talking a little and we reflected that it was a mistake don’t add it in the presentation, and the main reason for not adding it was t...

Yes we can, come on! 👌💪

Hello 🙌 On Friday we had a visit in the classroom, teacher Maria invited Professor Sodel Vásquez, the goal was for each team to expose again, but time only the problem, the solution and the prototype would be exposed, this in just 2 minutes; with the intention of being more concise and not talking so much because in the long term it only ends up being boring people, then Sodel would give his opinion about our exhibition, we honestly never imagined that he would say what he said since he concentrated more about the way the team representatives presented, since they told us that, in general, we did not take advantage of the time because some teams that do not exceed 2 minutes made it very fast and nervous. Something that he also told us is that if in the future the application we cultivate we had to learn to sell things, make commercial requirements known to be able to get the attention of entrepreneurs and be able to sell the idea, also something he told us and that other...