Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 11 Next »

All team members should provide their priorities, progress, and problems each day in this report.

Team name

Fudge

Direct supervisor

Table of contents

\uD83D\uDDD3 Thursday <03/03/2022>

Name

Priorities \uD83E\uDDD0

Progress \uD83D\uDE0A

Problems \uD83D\uDE10

1

Michelle

Refine requirements, based on new info

Added requirements on security and authentication

unsure on how secure our API should be, which makes it difficult to finalise requirements

2

Edward

Ticket - Get Email adress from xml invoice

basic functionality done, minor code revision needed

null.

3

Joshua

Setup github and base flask server

Finished setting up the github and created the basic flask server level. Was able to integrate the github into jira.

Integrating github into Jira required admin privileges in Jira and thus was done with the help of a tutor.

4

Tay

Try start code sometime soon!

Cloned git. Wrote more issues for the sprint (including more detail of task breakdown).

Have been vv busy! Not been able to do much oops.

5

Garvi

\uD83D\uDDD3 Saturday <05/03/2022>

Name

Priorities \uD83E\uDDD0

Progress \uD83D\uDE0A

Problems \uD83D\uDE10

1

Michelle

Think about tasks that need to be completed, when and by whom

not to much at this stage

thinking about all the tasks that are required to complete an issue

2

Edward

3

Joshua

Task allocation

Started working out the tasks that were needed for the sprint.

Still trying to understand the task fully.

4

Tay

5

Garvi

6

\uD83D\uDDD3 Monday <07/03/2022>

Name

Priorities \uD83E\uDDD0

Progress \uD83D\uDE0A

Problems \uD83D\uDE10

1

Michelle

Work on health check

pull github repo

start to think about potential implementation

not sure how to calculate the time the server has been running and how to access variables from other functions.

2

Edward

3

Joshua

Database design

Started working on how to design the database and what we needed for it.

Don’t quite understand the documentation required for DB design. Example given in lecture different to Tays understanding.

4

Tay

5

Garvi

\uD83D\uDDD3 Thursday <10/03/2022>

Name

Priorities \uD83E\uDDD0

Progress \uD83D\uDE0A

Problems \uD83D\uDE10

1

Michelle

Get health check finished

health check function is mostly completed

health check endpoint has been added

need to figure out how to write a test that tests time

can’t push to github

2

Edward

3

Joshua

Created database in sqlalchemy.

Took DB design and created the sqlalchemy classes to match.

Had to make adjustments to db.

4

Tay

5

Garvi

\uD83D\uDDD3 Saturday <12/03/2022>

Name

Priorities \uD83E\uDDD0

Progress \uD83D\uDE0A

Problems \uD83D\uDE10

1

Michelle

write tests for health check

figured out a way to test if time is working

got rid of the bugs

merged with main

2

Edward

3

Joshua

Added environment variables

Added pylint CI

Authenication

Was able to add environment variables to github and local file which distributed to group. Also added pylint github action to check pylint. Finished authentication for users.

Had difficult time adding pylint CI. Had to add file to tone down pylint.

4

Tay

5

Garvi

\uD83D\uDDD3 Monday <14/03/2022>

Name

Priorities \uD83E\uDDD0

Progress \uD83D\uDE0A

Problems \uD83D\uDE10

1

Michelle

2

Edward

3

Joshua

Integrated production DB.

Work on documentation.

Was able to get heroku DB working.

Finished up documentation related to development and deployment.

Had to add environment code to track if running on heroku or not and whether to use production DB.

4

Tay

5

Garvi

  • No labels