Computer Science Final Year Project

IN3007 / INM450
Closed
Main contact
City, University of London
London, England, United Kingdom
Head of Placements and Internships STEM
(1)
3
Timeline
  • February 1, 2022
    Experience start
  • October 6, 2020
    Semester 1 Mid-term Evaluation
  • December 5, 2020
    Semester 1 End-Term Evaluation
  • February 23, 2021
    Semester 2 Mid-term Evaluation
  • February 2, 2022
    Project Scope Meeting
  • March 17, 2022
    Spring Semester Project Restart
  • May 19, 2022
    Experience end
Experience
13/5 project matches
Dates set by experience
Preferred companies
Anywhere
Any
Any industries

Experience scope

Categories
Website development Mobile app development Security (cybersecurity and IT security) Information technology Software development
Skills
software engineering web development programming embedded systems mobile app development
Learner goals and capabilities

Is there a "nice-to-have" project that you never seem to have the time for?City, University of London are accepting proposals for Final Year Undergraduate Projects!Final year Computer Science students will work with you to complete your project from January 2022. Projects start after the January exams. However we need industry clients finalised by mid December at the latest.

Client-based projects

For a strong external client project, the ‘client owner’ will be able to provide some or many of the following resources:

· A project owner and stakeholders

· Well defined requirements and benefits

· An established SDLC and project management framework

· Established IT development standards

· Users to validate and test your application

· Test data

· IT literate staff to evaluate your application and maintain it after the project is finished

Learners

Learners
Undergraduate
Any level
5 learners
Project
450 hours per learner
Learners self-assign
Individual projects
Expected outcomes and deliverables

The final project deliverables will include:

  • Prototype and source code of your solution
  • User and Developer documentation


Project timeline
  • February 1, 2022
    Experience start
  • October 6, 2020
    Semester 1 Mid-term Evaluation
  • December 5, 2020
    Semester 1 End-Term Evaluation
  • February 23, 2021
    Semester 2 Mid-term Evaluation
  • February 2, 2022
    Project Scope Meeting
  • March 17, 2022
    Spring Semester Project Restart
  • May 19, 2022
    Experience end

Project examples

Based on your organisations goals, students will apply skills to build software and embedded systems to achieve your goals.

Students will work with you to:

  • Develop requirements, user stories and customer archetypes for your project.
  • Utilise a development method in order to deliver your work
  • Iterate and refine designs to meet your needs.
  • Test the system and create documentation for you to use the system on completion

Example projects include, but are not limited to:

  • Frontend and back-end website development
  • Application software development
  • Mobile Apps
  • Games programming projects (Unity, C++)

We are looking software development/programming challenges that meet the following criteria;

  • Must have a substantial programming element
  • The deadlines are dictated by the module calendar [Jan to April]. Projects must be defined by mid December
  • Students must have the project approved by an academic for us to check whether it is a valid project.
  • Project provider must provide feedback to the students on their work and respond to us at the end of the term about their involvement in the project.
  • Project provider can request for the projects to be kept confidential, in which case their contents will be seen by the module team, the corresponding project markers, moderators and external examiners. This includes the written report and the corresponding code generated.
  • Students are required to write a report according to the module requirements describing the project and the effort involved. They also record a video showing what they developed and discuss challenging parts of the code.
  • Students can work as a part of a team, but their task has to be self-contained and self-managed.
  • Intellectual property arrangements can be agreed between the client and the student using appropriate NDA agreements.


As a project owner you will be be required to give you formal consent to the project, state how tyou are going to use the application in your organisation, declare what resources you are making available to the student, and at the end sign off the project. In addition, markers will be looking for evidence in the project report students have complied with the organisation’s standards and practises.


Additional company criteria

Companies must answer the following questions to submit a match request to this experience:

  • Q1 - Checkbox
    If Intellectual property is a concern, provide an IP waiver and/or NDA agreement for the students to sign.
  • Q2 - Checkbox
    Be available for a quick phone call with the instructor to initiate your relationship and confirm your scope is an appropriate fit for the course.
  • Q3 - Checkbox
    Provide a dedicated contact who is available to answer periodic emails or phone calls over the duration of the project to address students' questions within 1 business day, and to meet with the individual for approximately 1 hour every 2 weeks (at least).
  • Q4 - Checkbox
    Provide any specialized resources (software, services, hardware) that are needed to complete the project (ASU provides basic development environments and tools).