Today we begin the work tracking in the wiki by explaining all our previous work.

The 10/04/2019 we had our first meeting. Highlights include the selection of the working day and a work-distribution for this first week. Anyway, if you want to see more about it check it out this link: Meeting Report 1

Several days later we created the webpage, google groups and google docs on our weekly workday. Here are the links: Webpage Google Group Google Docs

The 10/11/19 we had our second meeting, this one was far more adequate and professional due to our growth as a company. The group came into contact with Github and all its features. For more info check this link: Meeting Report 2

The next weekly workday we proceeded to have a very frustrating and unsuccessful session but failing to achive the github configuration.

The 10/18/19 we had our third meeting. As always, you can check all the info in this link: Meeting Report 3

Despite the problems we had last week, we manage to solve Github configuration and finally conquer it. Thanks to our github workers that have been fast and we have finally been able to solve the problems.

People in charge of learning about Maven had their first touch with it. They realize that its going to be hard, but sooner or later Maven will bend the knee. We will keep updating.

Besides our Github conquer, last weekly workday we also extracted requirements. Check it out in this link: Requirements

The 10/30/19 we had our fourth meeting. We have planned to finish with iteration 0 this week in order to keep on working in the project. You can check all the info aboute the minute here: Meeting Report 4

Last weekly workday we created a Business processes file to better specify how we do the things in our company. Today 11/04/19 we have approved it.Check it out in this link: Business Processes v1.0

We realised our requirements document was not according to our new Business Processes so we made it right, here’s the link: Software Requirements v1.0

Today, 11/08/19 we had our fifth meeting. It is important to highlight the change we made on the way of working for the following weeks. Check it out on the next link: Meeting Report 5

Yesterday, 11/10/19 the planification was finished. Everything about it is contained on this 2 files: Project Planification v1.0 Agenda & Costs

Yesterday, 11/10/19 the apropiate github branched were created and today 11/11/19 the iterations 1 & 2 have begun.

Today, 11/15/19 with the corresponding improvements to the several iteration 2 steps, by means of the VP code generation feature, the pull request has been generated. you can see both the commit and the push request here: commit pull request

Today, 11/16/19 after checking the code generated with VP tools, we have uploaded a new version that solve errors: commit

On Sunday 11/17/19 Iteration 1 pull request was done along with the merge of both pull request. You can see all the information here: iteration 1 iteration 2

The 11/13/19 an important meeting was held with the stakeholder. This specific meeting did not provide a minute or a file for us to share with you, but it gave us a lot of internal knowledge and inspiration to improve. Those said changes will be added below in this section.

As a result of the previously mentioned meeting we have modified our Business processes file to better specify how we do the things in our company, thus creating a new version. The 11/15/19 we have approved it.Check it out in this link: Business Processes v1.1

The 11/22/19, as a result of the previously mentioned meeting we have modified our Agenda file to include iterations 0 & 6 which had not been included before. But we did not remember to create a new version of the file, and as a result losing the version 1.0. Check it out in this link: Agenda

Last week, iteration 1 and iteration 2 were developed in parallel as there are no dependencies between them. Everything went as planned so I would like to thank the team for their dedicated work. Now its time to begin with iterations 3 and 4.

Iteration 4 branch’s creation suffers a delay of 1 day due to the appearance of a problem that prevented it4 branch from updating, this problem was solved (God bless Stackoverflow) and therefore the branch was created at 11/18/2019 instead of 11/17/2019 , as stated in the project planification.

On *11/18/2019* while the team was working in Iteration 3 and Iteration 4 we detect that one of the last week diagrams was missing.

On Sunday 11/24/19 Both iterations were merged from their respective pull requests. You can see all the information here: iteration 3 iteration 4

Last week, iteration 3 and iteration 4 were developed in parallel as there are no dependencies between them. Everything went as planned so I would like to thank the team for their dedicated work. Now its time to begin with iteration 5.

Iteration 5 pull request’s creation was not done by the iteration 5 manager, but instead was done by another group member delegated by the iteration 5 manager himself in order to help that person al levelize the number of tasks. Said pull request was created at 11/29/2019 as stated in the project planification. You can see the pull request in the next section.

On Friday 11/29/19 Iteration 5 has been merged from its respective pull request. You can see all the information here: iteration 5

Today, 11/29/19 we had our sixth and final meeting. Check it out on the next link: Meeting Report 6

After several hard working sessions by our Maven delegation members it finally has been completed just at the deadline ( 11/29/19 ). Check it out in the next link: Maven

Now that the project is finished ( 11/29/19 ) no more adjustments are needed in visual paradigm, so we uploaded it. Check it out in the next link: Visual Paradigm