Vefþróun@Tækniskóli

Product Development: Full stack web application

Competences

  • To be ready to collaborate effectively with peers in order to achieve a common goal
  • To be ready to learn and apply new technologies independently
  • To be ready to exhibit the results of a collaborative work
  • To be ready to create and deliver professional-grade web applications
  • To be ready to communicate and work independent of the technology stack involved
  • Coming up
  • Coming up

What to create

Full stack web application with Back-end (CMS & API) and Front-end (UI/UX & interactive application)

 

Description

It is possible and indeed quite common for front-end developers to never touch what is happening on the back-end. This makes sense because it often makes for an easier separation of roles and a more productive team. 

But being completely alienated from what makes up the back-end can also mean a front-end developer only sees a part of the picture they are trying to paint. Which is why in this Product Development Guide the students should create a back-end application from scratch and connect it to a (now familiar) front-end application.

The group must produce a written description of a product (briefing) which fits in this Guide’s requirements, and proceed to develop that product. The product can be fictitious or real, meaning the beneficiary can be the students or an external institution. Some theme ideas are listed in this Guide but do not represent, by any means, subject boundaries. The students are encouraged to use their imagination and networking to find interesting project ideas to work on and exercise the web development skills related to this Guide.

 

Group arrangement

Students must assemble in groups of 3-4.

Minimum requirements

  • Use Agile Development techniques (e.g. Scrum, Kanban, pair programming)
  • Creation of a back-end system which should:
    • Connect to a database
    • Do all CRUD operations
    • Expose an API so that front-end systems can use it
  • Creation of a Web Application, which should:
    • Consume the API created in the back-end
    • Count on an original design (i.e. created by the group)
    • Front-end can be on the simpler side
  • Final product must be available online (no need for a paid domain)

 

Deliverables

  • Link to project briefing
  • Link to design files
  • Link to repository containing the back-end code
  • Link to repository containing the front-end code
  • Link to access the project online
  • Group presentation about final result

 

Theme ideas

  • A lightweight CMS system (back-end) with an administration interface (front-end)
  • A streaming service
  • IFTTT-like application
  • URL-shortener with multiple options