Blog Post #3 

How is the journey so far?

The journey of my capstone project has been challenging yet rewarding. From the beginning, I faced numerous obstacles and had to overcome various hurdles to achieve my goals. However, with the guidance of my mentors and the support of my peers, I was able to make steady progress and accomplish key milestones. One of the biggest challenges I faced was understand how to parse the user input and then create a docker image but I overcame this obstacle by learning online tutorial and discussion with my teammates.

What communication tools is your team using, and how well is this going?

We used discord as the primary tool for communication and used zoom for the weekly meeting. Everyone on the team is comfortable with these tools.

What Project Management tools is your team using, and how well is that going?

We don’t use any specific tools like Jira. Teammates thought the project is not too complex and thus we just use Word as tool for project management.

How often does your team commit their code? Is code integrating easily?

We commit our codes once a week. But we are still struggling with coding integration because some of the pull request are still under review.

How about pull-requests or code reviews? Is this too much overhead or is it useful to your team?

There is some overhead involved in the pull-request and code review process, By having multiple team members review each other’s code, we catched errors and identified areas for improvement early on.

What about your build/debug/deployment? Is this going well, or are you spending a lot of time debugging?

Overall, our team’s build/debug/deployment process is going well. However, we have encountered some challenges and spent some time debugging certain aspects of the project.To address these issues, we have implemented regular testing and quality assurance processes

How well is your team following your original Team Standards?

W regularly reviewed and evaluated how well the team is following the standards. This has helped us identify areas for improvement and ensure that the team is on track to meet its goals. 

Do you feel your project is on-track to succeed? If not, what do you plan to do to help the team get back on track?

I feel like we are on-track overall. However, there would be some unexpected factors and bugs can arise during the development process.

Do you personally feel your part of the project will succeed? If not, what do you plan to do to get back on track?

I think the project will be succeed because we are on the track and build each features based on needs from development of the sponsor companies.

What one thing would really help your team succeed?

Effective communication helps us to share ideas, provide feedback, and coordinate the efforts towards achieving the project’s goals. To promote our effective communication, we established regular check-ins and meetings, using a communication tool that everyone is comfortable with.

Plans and thoughts about Custom Scripts Containerization project

This project will allow users to save their custom data analysis scripts in the Docker. So the main technologies will be used is Docker.

  • Why did you and your team choose the technologies you did?

Not all users are comfortable to code in Jupiter Notebook or having the programming skills required to work with it. Docker serve such purpose that package the applications and their dependencies into a portable containerm so that the application can be run the same way across different environments.

  • How will your project use them?

We plan to convert Jupiter Notebook codes inputted by users to Python scripts, and then pack Python scripts and its dependencis into Docker container image.

  • What are their pros and cons?

Docker containers provide a consistent environment for applications to run in different environments, although they do have a learning curve and can be complex to configure.

  • What were the alternatives?

Kubernetes may be an alternative tool to managing containerized applications, but Kubernetes containers are larger and consume more resources when deployed.

  • What do you like or dislike about your system UI/UX?

We will be following the same UI style for the software. which is simple and clean. However, we will highlight important elements using color.

  • What do you like or dislike about your server/backend system/API?

A button to trigger the Docker image will be added to UI. Backend includes a function to validate the .ipynb file. I think it will be proper meet the requimrent of this project.

  • What do you like or dislike about your design modularity? Does it enable each of your to work independently?

The current modular design includes all necessary tasks that follow the flowchart as the users. Each of the team members has picked some individual tasks, so we can work independently and test integration at the end,

  • Anything else

The marketing team from the sponsor company will be sending us the Docker image.