Final Project

Python Programming M2 203

Project Description

The final project of the course consists of developing a complete Python application aimed to solve a current problem in Finance.

Students will work in groups of 3 or 4 students, and autonomously choose a relevant topic and apply libraries either seen in class or learned by the students. The project should demonstrate the ability to use GitHub for version control and collaboration, and high coding standards. Students should also prepare a pitch proposal to present its results to a non technical audience.

Deliverables

Technical

  • GitHub repository containing well-structured code. The repository should show the history of commits by EACH one of the team members.
  • The repository should contain all the required files and instructions to be replicated. Only leave out confidential information such as API keys.
  • README.md file with description, setup instructions, usage instructions, project summary, and an overview of results.
  • An User Interface is not required if the target audience is highly technical, otherwise it is important.

Non Technical

  • A Business Plan document outlining the project's goals, target audience, pricing strategy, and funding requirements. E.g. What do you need to start a company to commercialize the application.
  • A short professional presentation (e.g. 15 minutes) to myself and a Private Equity investor scheduled for November 14th (last session).

Use of AI coding tools

  • AI assistants and the use of LLMs for coding is not prohibited but encouraged. However, you should disclose their use.
  • You are responsible for verifying the correctness of any code generated by AI tools.
  • Since using AI makes you more productive, the bar is higher for your contributions.

Timeline

November 12 - Business Plan and GitHub Repository Snapshot of the working application.

November 14 - Presentation

December 7 - Final Github Repository Snapshot

Evaluation Criteria

  • Originality and value of the project idea.
  • Functionality and usability of the application.
  • Code quality, including readability, organization, and documentation.
  • Both Github snapshots will be evaluated, you need to specify the commit hashes. Anything outside these two snapshots will not be graded.
  • Collaboration among the group members.
  • Proper use of Git and GitHub for version control.
  • Development of the Business Plan
  • Quality of the presentation to a non technical audience.
  • Willingness of the PE investor to (hypothetically) invest in the idea.

For questions, email juan.imbet@dauphine.psl.eu