ASWI - Pokročilé softwarové inženýrství » ASWI 2023 » Deformace svalů kombinací ARAP & PBD (Kohout) - Stark Industries

h1. Iterations

Summary of project work in interations.

h2. S01 ( 06.03.2023 - 19.03.2023 )

* selection of a suitable IDE - Visual Studio

* specification of requirements

* agreement that everyone has to learn c++ (nobody knows c++)

* introduction to cMake

* gitflow settings

* setting meeting times (Saturday 9:00 (planning + retrospective) + Wednesday 17:00)

h2. S02  ( 20.03.2023 - 26.03.2023 )

* getting the program up and running

* source code analysis

* workshop with the client about cMake and project requirements

* creation of a project plan

* configuration of Redmine and setting conventions

> h3. Retrospective

> 

> *GLAD:*

> * TK - Vasek made a nice plan

> * TK - Compared to the previous sprint we are more coordinated, more efficient

> * MJ - Better planning

> * JK - Clarifying the procedure with the mentor

> 

> *SAD:*

> * TK - I don't really understand the code

> * JK - The code is complicated

> 

> *MAD:*

> * VŠ - we are a little behind schedule

> * VŠ - we need to correctly specify the requirements for each task (optimizing is not a sufficient description)

h2. S03 ( 27.03.2023 - 02.04.2023 )

* workshop with the client about mathematical background of the project and source code structure

* risk analysis document prepared

* vision document prepared

* source code analysis of ARAP and PBD

h3. Retrospective

> *GLAD:*

> * JK - the meeting with the author of the project was very useful

> * TK - the meeting with the author helped me to get a better understanding of the code

> * VŠ - the meeting with the author was good

> * VŠ - we made up for the initial delay in the plan

> * TK - Vasek played nicely with the administration

> *SAD:*

> * TK - I analyzed a lot of things, but I still don't feel like I have a proper understanding of how everything works

> * JK - lots of work, little time

> * VŠ - Mathematically challenging project, big overhead for analysis

> * VŠ - We will descope cMake refactoring to the next sprint

> *MAD:*

> * VŠ - We still have a big slippage, we should escalate the situation better

> * VŠ - Tomas writes Czech in Redmine

> * VŠ - We need to improve communication in the team, we don't have a very good overview of the status of the individual tasks

h2. S04 ( 03.04.2023 - 09.04.2023 )

* consultations with client about PBD and ARAP merge

* architecture document first part prepared

* internal convention document prepared

* resolving super-build issue

h3. Retrospective

> *GLAD:*

> * JK - better understanding of the mathematical part of the method

> *SAD:*

> * JK - a team member couldn't handle the time pressure

> * JK - high mental load

> *MAD:*

> * TK - MJ left us

> * VŠ - basically zero progress on Cmake, I started implementing from scratch

> * VŠ - missing team member + delay on cMake will make big problems for on-time delivery

h2. S05 ( 10.04.2023 - 16.04.2023 )

* Setting new targets - removing a task for comparison of results

* Testing is unlikely to be as high quality due to time constraints

h3. Retrospective

> *GLAD:*

> * TK - The client is helpful and supportive

> * VŠ - We have the first implementation deliverable

> * VŠ - Improved team communication

> * VŠ - Moving the meeting to Sunday evening is better for closing tickets

> * TK - I better understand the connection of building c++ projects (Cmake etc.)

> * JK - positive feedbakc from ASWI mentor

> * TK - Vasek made nice documents => lots of points on ASWI evaluation

> * VŠ - team morale is not dropping (probably could now be less now)

> *SAD:*

> * JK - Mental state remains unchanged

> * VĚ - Every step of putting together a project results in a problem that blocks development

> *MAD:*

> * TK - I'm already on my second week of almost 0% progress and it's severely demoralizing (despite X hours spent on the task)

h3. Actionable points

* Trying to get the project to a state where we can start implementing as soon as possible

*   Help from the author + focus on the build process

*   Lunch together to boost team morale

* Incorporate deadlines from other coursework into deadline planning

h2. S06 ( 17.04.2023 - 23.04.2023 )

* oSim superbuild is working now on Win

* Fixing an unexpected bug that was in our project

* ARAP method - the project is in a state where we can address the combination of both methods

* We have received from the project author his proposal for a solution to the combination of methods

h3. Retrospective

> *GLAD:*

> * JK - quite a lot of implementation progress

> * JK - having lunch with the team was beneficial, I got motivated to continue my studies

> * TK - finally something is working -> big boost to morale

> * TK - Client satisfied with our bug fix

> * VŠ - One big feature was descoped, according to our new plan, we should be able to delivery everything on time

> *SAD:*

> * JK - time pres from other subjects

> * TK - I'm scared that we won't be able to get everything done in time

> * VŠ - In superbuild there is often a problem with external libraries (can't be translated, not compatible, other problems) - this creates blockers that prevent further progress and are time-consuming to resolve (hard to estimate time to resolve these kind of problems)

> *MAD:*

> * TK - I managed to forget about half of the mathematical background

h3. Previous actionable points outcomes

* Project is now in runnable state - perfect

* Lunch together to boost team morale was good

h3. Actionable points

* Create a prototype of the combination of PBD & ARAP methods

* Implement at least one of the two possible combinations (using scales or using a combination of kinetic forces)

* Would be helpufull to have one GIT repo for both features, current situation might lead in merge issues