projects
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
projects [2020/08/17 17:27] – aan | projects [2021/09/02 14:02] (current) – aan | ||
---|---|---|---|
Line 3: | Line 3: | ||
====== Proposed Projects | ====== Proposed Projects | ||
- | Below is a list of 4080/4088 projects proposed by faculty members. More projects may be added once they come in (normally in August). Please contact the supervisor directly you are in interested in a project. You can also contact faculty members individually to discuss possible projects. Click [[http:// | + | Below is a list of 4080/4088/4480 projects proposed by faculty members. More projects may be added once they come in (normally in August). Please contact the supervisor directly you are in interested in a project. You can also contact faculty members individually to discuss possible projects. Click [[http:// |
+ | ====== Full-Stack Developer(s) ====== | ||
+ | **Course:** EECS4080/ | ||
+ | |||
+ | **Supervisor: | ||
+ | |||
+ | **Contact: | ||
+ | |||
+ | **Project Description and Responsibilities: | ||
+ | The student(s) will be responsible for developing a web application. The primary focus will be the development of the user interface, web services, API and database interactions, | ||
+ | |||
+ | **Responsibilities: | ||
+ | * Development of a modern web application with a responsible user interface, and a back-end responsible with processing user input and interacting with various API end points and database engines | ||
+ | * Building reusable code and libraries for future use | ||
+ | * Design and implementation of data storage solutions | ||
+ | * Collaborate with other team members | ||
+ | |||
+ | ** Required Skills:** | ||
+ | * Good knowledge of a back-end programming language such as Python or Java EE | ||
+ | * Good understanding of front-end technologies and platforms, such as Javascript, HTML5, Angular or React | ||
+ | * Good knowledge of RESTFul web API concept and architecture | ||
+ | * Good knowledge of database concepts such as SQL and NoSQL | ||
+ | * Good knowledge of JSON or XML formats and libraries to produce them | ||
+ | * Some understanding of code versioning tools, such as Git | ||
+ | * Implementing automated testing platforms and unit tests | ||
+ | |||
+ | ** Good to Have: | ||
+ | * Understanding differences between multiple delivery platforms such as mobile vs desktop, and optimizing output to match the specific platform | ||
+ | * Understanding of secure coding practices, and latest web development standards | ||
+ | * Recommended education level: 3rd year undergraduate or higher in Computer Science or equivalent program | ||
+ | |||
+ | **Notes:** | ||
+ | * Email Prof. Uyen T. Nguyen (utn@eecs.yorku.ca) a copy of your resume listing courses, projects and prior experience relevant to the project. | ||
+ | * A student completing this project successfully may be hired (paid) as a research assistant after the course is over to continue the next step of the project. | ||
+ | |||
+ | |||
+ | ====== Building a Database of Dark Webpages ====== | ||
+ | **Course:** EECS4080/ | ||
+ | |||
+ | **Supervisor: | ||
+ | |||
+ | **Contact: | ||
+ | |||
+ | **Project Description and Responsibilities: | ||
+ | * Searching internet resources (google, reddit, dark web link archives, etc.) for links to dark websites of interest | ||
+ | * Grouping and categorizing web pages | ||
+ | * Developing graphs representing the data present on the found dark websites | ||
+ | * Assist in the development of a dark web crawler | ||
+ | * Assist in the development of information retrieval systems | ||
+ | |||
+ | **Required Technical Skills:** | ||
+ | * Experience building programs in Python | ||
+ | * Good understanding of object-oriented design | ||
+ | * Experience with Windows and Linux environments | ||
+ | * Experience with Excel and/or a commonly used graph generation program | ||
+ | **Required Non-Technical Skills:** | ||
+ | * Strong teamwork skills | ||
+ | * High organizational skills | ||
+ | * Good time management skills (there will be weekly check-ins) | ||
+ | **Non-required Asset Skills:** | ||
+ | * Knowledge of information retrieval methods | ||
+ | **Notes:** | ||
+ | * Email Prof. Uyen T. Nguyen (utn@eecs.yorku.ca) a copy of your resume listing courses, projects and prior experience relevant to the project. | ||
+ | * A student completing this project successfully may be hired (paid) as a research assistant after the course is over to continue the next step of the project. | ||
+ | |||
+ | ====== Automation of Copyright Takedowns ====== | ||
+ | **Course:** EECS4070/ | ||
+ | |||
+ | **Supervisor: | ||
+ | |||
+ | **Contact: | ||
+ | |||
+ | COVID has accelerated the trend for delivering university courses online. This has been a boon to providing accessible learning modes to students. | ||
+ | |||
+ | A copyright takedown process (e.g. DMCA) is in place on these commercial sites but it is cumbersome to use. The objective of this project is to semi-automate the take-down process in one of two ways: | ||
+ | |||
+ | 1. Allow a copyright holder to identify a category of course material (e.g. a course name and number) a priori and engage a scheduled process which regularly scans a commercial site (e.g. Course Hero) and automatically submits takedowns on behalf of the copyright holder | ||
+ | |||
+ | 2. Submit reports to the copyright holder when an identified category of course material is found on a commercial site (e.g. Course Hero) and asks the copyright holder whether a takedown request should be made on the holder' | ||
+ | |||
+ | **Required skills:** General programming skills | ||
+ | |||
+ | **Recommended skills:** Experience in Python (and perhaps Beautiful Soup) and/or Java and/or equivalent | ||
+ | |||
+ | ====== Visualization of Course Maps at YorkU ====== | ||
+ | |||
+ | **Course:** EECS4070/ | ||
+ | |||
+ | **Supervisor: | ||
+ | |||
+ | **Contact: | ||
+ | |||
+ | Students at York have long been missing the ability to visualize the connections between courses when planning or reviewing their progress through their program. | ||
+ | |||
+ | This is a continuation of an existing open-source project written in Python. | ||
+ | |||
+ | 1. A visualization can be produced and displayed on the web | ||
+ | |||
+ | 2. Corrections to the existing data set (the University' | ||
+ | |||
+ | Students involved in the project will be required to maintain public-facing documentation. The result of this project will remain open source for further development by students, staff and faculty. | ||
+ | |||
+ | **Required skills:** General programming skills | ||
+ | |||
+ | **Recommended skills:** Experience in Python (and perhaps Beautiful Soup) and web-centric tools | ||
+ | |||
+ | /* | ||
====== Characterizing, | ====== Characterizing, | ||
**Course:** EECS4080 | **Course:** EECS4080 | ||
Line 38: | Line 144: | ||
====== Release Management for Mobile Apps ====== | ====== Release Management for Mobile Apps ====== | ||
- | **Course: | + | **Course: |
**Supervisor: | **Supervisor: | ||
Line 103: | Line 209: | ||
**Required skills:** General EECS408x prerequisites. Good knowledge of C#. Ability to work independently. | **Required skills:** General EECS408x prerequisites. Good knowledge of C#. Ability to work independently. | ||
+ | |||
+ | */ | ||
/* | /* |
projects.1597685235.txt.gz · Last modified: 2020/08/17 17:27 by aan