Study Guide

Objectives (course unit)

After completing the module, the student will have skills concerning techniques in the backend side. This module deepends the earlier professional know-how.

Content (course unit)

Databases,
version control,
cloud servicies,
backend technologies.

Prerequisites (course unit)

Courses Introduction to Programming, Databases and WWW Technologies or corresponding competencies.

Assessment criteria, satisfactory (1-2) (course unit)

The student knows the basics of Database servers.
The student knows the basics of version control.
The student understands the basic principles behind security, testing and cloud services.
The student knows the basics of backend application

Assessment criteria, good (3-4) (course unit)

The student can administer a database server.
The student knows how to use version control in projects and apply the release practises using it.
The student can write simple test cases and evaluate cloud services.
The student can write a simple backend application.

Assessment criteria, excellent (5) (course unit)

The student can use advanced features of database usage.
The student can use several version control softwares.
The student can design and build test sets and utilize cloud services.
The student can write powered backend application with robustness considering the information security.

Location and time

See timetable of semester and Moodle course homepage.

Exam schedules

No grade exam. See EVALUATING CRITERIAS

Assessment methods and criteria

VERSION CONTROL AND TESTING: homeworks of 30 % = 1, 60 % = 2, 90 % = 3. Optional projects increase greade by +1..+2
DATABASES:: returns: 50%: 1, 75%: 2, 90%: 3. Report: increases grade up to 2 grades.
BACKEND DEVELOPMENT: exercises (40%) and project work (60%)

Assessment scale

0-5

Teaching methods

lectures
homeworks
practical works or exams

Learning materials

Any relevant material concerning: databases, version control, testing, Nodejs and its related techniques.

Student workload

See Curriculum. The course consists of 3 parts. Parts 1-2 (first half of timetable): Databases and Version Control. Part 3: Nodejs (second half, after week 42).

Content scheduling

Timetable is announced at the beginning of course. Deadlines:
2023-11-30 part: Version Control and Testing. Exercises and projects. (week 48)
2023-11-03 part: Databses. Weekly and database evaluation report.
2023-12-31 part: Backend Development. Weekly exercises, project week 02/2024

NOTE: 2023-11-24 at 12:00 (week 47) version control Github team presentations for those who have worked in optional project. Mandatory for all members in http://bit.ly/jaalto-zoom

Completion alternatives

Case basis by contacting lecturers.

Assessment criteria - fail (0) (Not in use, Look at the Assessment criteria above)

Missing 30 % verified returns until deadline.

Assessment criteria - satisfactory (1-2) (Not in use, Look at the Assessment criteria above)

See previous topic: "Evaluating criterias"

Assessment criteria - good (3-4) (Not in use, Look at the Assessment criteria above)

See previous topic: "Evaluating criterias"

Assessment criteria - excellent (5) (Not in use, Look at the Assessment criteria above)

See previous topic: "Evaluating criterias"

Objectives (course unit)

After completing the module, the student will have skills concerning techniques in the backend side. This module deepends the earlier professional know-how.

Content (course unit)

Databases,
version control,
cloud servicies,
backend technologies.

Prerequisites (course unit)

Courses Introduction to Programming, Databases and WWW Technologies or corresponding competencies.

Assessment criteria, satisfactory (1-2) (course unit)

The student knows the basics of Database servers.
The student knows the basics of version control.
The student understands the basic principles behind security, testing and cloud services.
The student knows the basics of backend application

Assessment criteria, good (3-4) (course unit)

The student can administer a database server.
The student knows how to use version control in projects and apply the release practises using it.
The student can write simple test cases and evaluate cloud services.
The student can write a simple backend application.

Assessment criteria, excellent (5) (course unit)

The student can use advanced features of database usage.
The student can use several version control softwares.
The student can design and build test sets and utilize cloud services.
The student can write powered backend application with robustness considering the information security.

Location and time

See timetable of semester and Moodle course homepage.

Exam schedules

No grade exam. See EVALUATING CRITERIAS

Assessment methods and criteria

VERSION CONTROL AND TESTING: homeworks of 30 % = 1, 60 % = 2, 90 % = 3. Optional projects increase greade by +1..+2
DATABASES:: returns: 50%: 1, 75%: 2, 90%: 3. Report: increases grade up to 2 grades.
BACKEND DEVELOPMENT: exercises (40%) and project work (60%)

Assessment scale

0-5

Teaching methods

lectures
homeworks
practical works or exams

Learning materials

Any relevant material concerning: databases, version control, testing, Nodejs and its related techniques.

Student workload

See Curriculum. The course consists of 3 parts. Parts 1-2 (first half of timetable): Databases and Version Control. Part 3: Nodejs (second half, after week 42).

Content scheduling

Timetable is announced at the beginning of course. Deadlines:
2023-11-30 part: Version Control and Testing. Exercises and projects. (week 48)
2023-11-03 part: Databses. Weekly and database evaluation report.
2023-12-31 part: Backend Development. Weekly exercises, project (week 02/2024)

NOTE: 2023-11-29 at 12:00 (week 48) version control Github team presentations for those who have worked in optional project. Mandatory for all members in http://bit.ly/jaalto-zoom

Completion alternatives

Case basis by contacting lecturers.

Assessment criteria - fail (0) (Not in use, Look at the Assessment criteria above)

Missing 30 % verified returns until deadline.

Assessment criteria - satisfactory (1-2) (Not in use, Look at the Assessment criteria above)

See previous topic: "Evaluating criterias"

Assessment criteria - good (3-4) (Not in use, Look at the Assessment criteria above)

See previous topic: "Evaluating criterias"

Assessment criteria - excellent (5) (Not in use, Look at the Assessment criteria above)

See previous topic: "Evaluating criterias"

Objectives (course unit)

After completing the module, the student will have skills concerning techniques in the backend side. This module deepends the earlier professional know-how.

Content (course unit)

Databases,
version control,
cloud servicies,
backend technologies.

Prerequisites (course unit)

Courses Introduction to Programming, Databases and WWW Technologies or corresponding competencies.

Assessment criteria, satisfactory (1-2) (course unit)

The student knows the basics of Database servers.
The student knows the basics of version control.
The student understands the basic principles behind security, testing and cloud services.
The student knows the basics of backend application

Assessment criteria, good (3-4) (course unit)

The student can administer a database server.
The student knows how to use version control in projects and apply the release practises using it.
The student can write simple test cases and evaluate cloud services.
The student can write a simple backend application.

Assessment criteria, excellent (5) (course unit)

The student can use advanced features of database usage.
The student can use several version control softwares.
The student can design and build test sets and utilize cloud services.
The student can write powered backend application with robustness considering the information security.

Location and time

See course homepage

Exam schedules

No grade exam. See EVALUATING CRITERIAS

Assessment methods and criteria

VERSION CONTROL AND TESTING: homeworks of 30 % = 1, 60 % = 2, 90 % = 3. After 30 %, optional projects can increase greade by +1..+2
DATABASES:: returns: 50%: 1, 75%: 2, 90%: 3. Report: increases grade up to 2 grades.
BACKEND DEVELOPMENT: exercises (40%) and project work (60%)

Assessment scale

0-5

Teaching methods

lectures
homeworks
practical works or exams

Student workload

See Curriculum.

Content scheduling

Timetable is announced at the beginning of course. Deadlines:
2022-11-28 part: Version Control and Testing. Exercises and projects. (week 48)
2022-10-16 part: Databases. Weekly returns and database evaluation report.
2022-12-31 part: Backend Development. Projects.

NOTE: 2022-11-28 at 09:00 version control Github team presentations for those who have worked in optional project. Mandatory for all members in http://bit.ly/jaalto-zoom

Completion alternatives

Case basis by contacting lecturers.

Assessment criteria - fail (0) (Not in use, Look at the Assessment criteria above)

Missing 30 % verified returns until deadline.

Assessment criteria - satisfactory (1-2) (Not in use, Look at the Assessment criteria above)

See previous topic: "Evaluating criterias"

Assessment criteria - good (3-4) (Not in use, Look at the Assessment criteria above)

See previous topic: "Evaluating criterias"

Assessment criteria - excellent (5) (Not in use, Look at the Assessment criteria above)

See previous topic: "Evaluating criterias"

Objectives (course unit)

After completing the module, the student will have skills concerning techniques in the backend side. This module deepends the earlier professional know-how.

Content (course unit)

Databases,
version control,
cloud servicies,
backend technologies.

Prerequisites (course unit)

Courses Introduction to Programming, Databases and WWW Technologies or corresponding competencies.

Assessment criteria, satisfactory (1-2) (course unit)

The student knows the basics of Database servers.
The student knows the basics of version control.
The student understands the basic principles behind security, testing and cloud services.
The student knows the basics of backend application

Assessment criteria, good (3-4) (course unit)

The student can administer a database server.
The student knows how to use version control in projects and apply the release practises using it.
The student can write simple test cases and evaluate cloud services.
The student can write a simple backend application.

Assessment criteria, excellent (5) (course unit)

The student can use advanced features of database usage.
The student can use several version control softwares.
The student can design and build test sets and utilize cloud services.
The student can write powered backend application with robustness considering the information security.

Location and time

See course homepage

Exam schedules

No grade exam. See EVALUATING CRITERIAS

Assessment methods and criteria

VERSION CONTROL AND TESTING: homeworks of 30 % = 1, 60 % = 2, 90 % = 3. After 30 %, optional projects can increase greade by +1..+2
DATABASES:: returns: 50%: 1, 75%: 2, 90%: 3. Report: increases grade up to 2 grades.
BACKEND DEVELOPMENT: exercises (40%) and project work (60%)

Assessment scale

0-5

Teaching methods

lectures
homeworks
practical works or exams

Student workload

See Curriculum.

Content scheduling

Timetable is announced at the beginning of course. Deadlines:
2022-11-28 part: Version Control and Testing. Exercises and projects. (week 48)
2022-10-16 part: Databases. Weekly and database evaluation report.
2022-12-31 part: Backend Development. Projects.

NOTE: 2022-12-02 at +0:00 version control Github team presentations for those who have worked in optional project. Mandatory for all members in http://bit.ly/jaalto-zoom

Completion alternatives

Case basis by contacting lecturers.

Assessment criteria - fail (0) (Not in use, Look at the Assessment criteria above)

Missing 30 % verified returns until deadline.

Assessment criteria - satisfactory (1-2) (Not in use, Look at the Assessment criteria above)

See previous topic: "Evaluating criterias"

Assessment criteria - good (3-4) (Not in use, Look at the Assessment criteria above)

See previous topic: "Evaluating criterias"

Assessment criteria - excellent (5) (Not in use, Look at the Assessment criteria above)

See previous topic: "Evaluating criterias"