Skip to main content

Low-Code Software Development BasicsLaajuus (5 cr)

Code: TE00CQ20

Credits

5 op

Objective

By the end of this course, students can:

understand the role of no-code and low-code tools in design processes.
design basic solutions in NCLC platforms.
collaborate in teams on an NCLC project.
consider NCLC implementation constraints and opportunities.
evaluate their NCLC-implemented projects.
reflect on the entire process.

Content

This course delves into the "Implement" and "Operate" stages of the CDIO framework using low-code/no-code tools. The students will complete a NCLC project including the following steps:
*Introduction to Software Development and No-Code/Low-Code Platforms
*Implementation with No-Code/Low-Code Platform
*Testing, Feedback, and Iteration

Enrollment

01.06.2025 - 02.09.2025

Timing

02.09.2025 - 21.12.2025

Number of ECTS credits allocated

5 op

Mode of delivery

Contact teaching

Campus

Kupittaa Campus

Teaching languages
  • Finnish
  • English
Seats

70 - 90

Degree programmes
  • Degree Programme in Information and Communication Technology
  • Degree Programme in Business Information Technology
  • Degree Programme in Information and Communications Technology
Teachers
  • Tiina Tolmunen
  • Laura Järvenpää
Groups
  • PTIETS25B
    PTIETS25B
  • PTIETS25A
    PTIETS25A

Objective

By the end of this course, students can:

understand the role of no-code and low-code tools in design processes.
design basic solutions in NCLC platforms.
collaborate in teams on an NCLC project.
consider NCLC implementation constraints and opportunities.
evaluate their NCLC-implemented projects.
reflect on the entire process.

Content

This course delves into the "Implement" and "Operate" stages of the CDIO framework using low-code/no-code tools. The students will complete a NCLC project including the following steps:
*Introduction to Software Development and No-Code/Low-Code Platforms
*Implementation with No-Code/Low-Code Platform
*Testing, Feedback, and Iteration

Materials

Material provided by the teacher and shared in learning environment (ITS).

Teaching methods

This course consists of:
- lectures: theoretical background and demonstrating the use of various low code/ no-code frameworks and environments that can be used for example in software / game / web development.
- practice sessions: practicing the use of LCNC tools introduced in lecture, learning project working skills
- group work: students will complete a LCNC project where they use the tools and skills learned in lectures and practice

Exam schedules

-

International connections

In the course, skills are learned through exercises and practical project work.

Only electronic materials are used in the implementation.

Completion alternatives

-

Student workload

The student completes tasks related to the course, with an estimated workload:
- Theory lessons: 9 x 2h = 18h
- Practical lessons: 10 x 2h = 20h
- Group work: 2 x 2h = 4h
- Final event: 4h
- Other independent/group work: approximately 90h
TOTAL: approximately 135h

Content scheduling

This course delves into the "Implement" and "Operate" stages of the CDIO framework using Low-Code/No Code (LCNC) tools. The students will complete a LCNC project including the following steps:
- Introduction to Software Development and LCNC Platforms
- Implementation with LCNC Platform
- Testing, Feedback, and Iteration

The course is implemented during weeks 38 - 50 as follows:
- Theory, weeks 38 - 47: 2h contact session for 9 weeks
- Practice, weeks 39 - 49: 2h contact session with your own tutor
- Group work, weeks 48-49: 2h independent working
- Final event, week 50

Further information

Available in ITS.

Evaluation scale

H-5

Assessment methods and criteria

The course assessment is based on:
1. Active participation
2. Timely submission of weekly exercises
3. The final LCNC project outcome

Each section (1-3) receives its own grade, and to pass the course, each section must be approved.

The final grade is calculated based on the weighted scores from each section:
1. Attendance 25%
2. Weekly assignments 50%
3. Final project 25%

Section 1: Attendance
Attendance fewer than 13 times: Fail
Attendance 13 times: Grade 1
Attendance 14 times: Grade 2
Attendance 15 times: Grade 3
Attendance 16 times: Grade 4
Attendance more than 16 times: Grade 5

Section 2: Weekly Assignments

There are 9 weekly assignments, each graded from 0 to 3 points as follows:

0 points: Assignment not submitted on time OR Submission is incomplete and does not match instructions OR Submission shows signs of cheating, e.g., identical to another student's work.

1 point: Assignment submitted on time AND submission is incomplete or partially matches instructions.

2 points: Assignment submitted on time AND submission mostly matches instructions but contains minor shortcomings.

3 points: Assignment submitted on time AND submission fully matches instructions.

Grading scale based on total points:
Fewer than 13 points: Fail
13–15 points: Grade 1
16–18 points: Grade 2
19–21 points: Grade 3
22–24 points: Grade 4
25–27 points: Grade 5

NOTE: Passing the course requires submission of at least 50% of the assignments. Only assignments submitted on time will be evaluated.

Section 3: Final Project

No final project produced and presented at the final event OR the project submission includes cheating (e.g., the final product is clearly not the group's own work) OR the application is significantly unfinished, non-functional, or incomprehensible: FAIL

Application partially functions but has significant issues affecting usability or functionality. Issues may relate to the user interface, operational logic, or feature performance: Grade 1

Application meets minimum requirements but clearly needs improvement in technical aspects and usability. It is very basic, with minimal additional features or enhancements beyond essential functions: Grade 2

Application is functional and usable but lacks significant innovation. Well-executed and meets course requirements, but not notably innovative or distinctive: Grade 3

Application is technically high-quality and includes thoughtful additional features. Good consideration of user interface and user experience. Tools and techniques are used effectively, and the application stands out positively (additional features should be purposeful rather than merely decorative): Grade 4

Application is innovative, exceptionally well-executed, and provides users with something new and significant. It creatively and effectively utilizes course tools. Technically flawless, highly user-friendly, and offers an outstanding user experience. Demonstrates a clear understanding of leveraging low-code platforms for broader application development opportunities: Grade 5

Assessment criteria, fail (0)

See the evaluation criteria above

Assessment criteria, satisfactory (1-2)

See the evaluation criteria above

Assessment criteria, good (3-4)

See the evaluation criteria above

Assessment criteria, excellent (5)

See the evaluation criteria above

Enrollment

30.05.2025 - 15.09.2025

Timing

02.09.2025 - 21.12.2025

Number of ECTS credits allocated

5 op

Mode of delivery

Contact teaching

Campus

Kupittaa Campus

Teaching languages
  • Finnish
Seats

90 - 120

Degree programmes
  • Degree Programme in Information and Communication Technology
Teachers
  • Juha Saarinen
  • Noora Maritta Nieminen
  • Virtuaalihenkilö3 IECS
Groups
  • PTIVIS25A
    PTIVIS25A
  • PTIVIS25B
    PTIVIS25B
  • PTIVIS25C
    PTIVIS25C

Objective

By the end of this course, students can:

understand the role of no-code and low-code tools in design processes.
design basic solutions in NCLC platforms.
collaborate in teams on an NCLC project.
consider NCLC implementation constraints and opportunities.
evaluate their NCLC-implemented projects.
reflect on the entire process.

Content

This course delves into the "Implement" and "Operate" stages of the CDIO framework using low-code/no-code tools. The students will complete a NCLC project including the following steps:
*Introduction to Software Development and No-Code/Low-Code Platforms
*Implementation with No-Code/Low-Code Platform
*Testing, Feedback, and Iteration

Materials

Material provided by the teacher and shared in learning environment (ITS).

Teaching methods

This course consists of:
- lectures: theoretical background and demonstrating the use of various low code/ no-code frameworks and environments that can be used for example in software / game / web development.
- practice sessions: practicing the use of LCNC tools introduced in lecture, learning project working skills
- group work: students will complete a LCNC project where they use the tools and skills learned in lectures and practice

Exam schedules

-

International connections

In the course, skills are learned through exercises and practical project work.

Only electronic materials are used in the implementation.

Completion alternatives

-

Student workload

The student completes tasks related to the course, with an estimated workload:
- Theory lessons: 9 x 2h = 18h
- Practical lessons: 10 x 2h = 20h
- Group work: 2 x 2h = 4h
- Final event: 4h
- Other independent/group work: approximately 90h
TOTAL: approximately 135h

Content scheduling

This course delves into the "Implement" and "Operate" stages of the CDIO framework using Low-Code/No Code (LCNC) tools. The students will complete a LCNC project including the following steps:
- Introduction to Software Development and LCNC Platforms
- Implementation with LCNC Platform
- Testing, Feedback, and Iteration

The course is implemented during weeks 38 - 50 as follows:
- Theory, weeks 38 - 47: 2h contact session for 9 weeks
- Practice, weeks 39 - 49: 2h contact session with your own tutor
- Group work, weeks 48-49: 2h independent working
- Final event, week 50

Further information

Available in ITS.

Evaluation scale

H-5

Assessment methods and criteria

The course assessment is based on:
1. Active participation
2. Timely submission of weekly exercises
3. The final LCNC project outcome

Each section (1-3) receives its own grade, and to pass the course, each section must be approved.

The final grade is calculated based on the weighted scores from each section:
1. Attendance 25%
2. Weekly assignments 50%
3. Final project 25%

Section 1: Attendance
Attendance fewer than 13 times: Fail
Attendance 13 times: Grade 1
Attendance 14 times: Grade 2
Attendance 15 times: Grade 3
Attendance 16 times: Grade 4
Attendance more than 16 times: Grade 5

Section 2: Weekly Assignments

There are 9 weekly assignments, each graded from 0 to 3 points as follows:

0 points: Assignment not submitted on time OR Submission is incomplete and does not match instructions OR Submission shows signs of cheating, e.g., identical to another student's work.

1 point: Assignment submitted on time AND submission is incomplete or partially matches instructions.

2 points: Assignment submitted on time AND submission mostly matches instructions but contains minor shortcomings.

3 points: Assignment submitted on time AND submission fully matches instructions.

Grading scale based on total points:
Fewer than 13 points: Fail
13–15 points: Grade 1
16–18 points: Grade 2
19–21 points: Grade 3
22–24 points: Grade 4
25–27 points: Grade 5

NOTE: Passing the course requires submission of at least 50% of the assignments. Only assignments submitted on time will be evaluated.

Section 3: Final Project

No final project produced and presented at the final event OR the project submission includes cheating (e.g., the final product is clearly not the group's own work) OR the application is significantly unfinished, non-functional, or incomprehensible: FAIL

Application partially functions but has significant issues affecting usability or functionality. Issues may relate to the user interface, operational logic, or feature performance: Grade 1

Application meets minimum requirements but clearly needs improvement in technical aspects and usability. It is very basic, with minimal additional features or enhancements beyond essential functions: Grade 2

Application is functional and usable but lacks significant innovation. Well-executed and meets course requirements, but not notably innovative or distinctive: Grade 3

Application is technically high-quality and includes thoughtful additional features. Good consideration of user interface and user experience. Tools and techniques are used effectively, and the application stands out positively (additional features should be purposeful rather than merely decorative): Grade 4

Application is innovative, exceptionally well-executed, and provides users with something new and significant. It creatively and effectively utilizes course tools. Technically flawless, highly user-friendly, and offers an outstanding user experience. Demonstrates a clear understanding of leveraging low-code platforms for broader application development opportunities: Grade 5

Assessment criteria, fail (0)

See the evaluation criteria above

Assessment criteria, satisfactory (1-2)

See the evaluation criteria above

Assessment criteria, good (3-4)

See the evaluation criteria above

Assessment criteria, excellent (5)

See the evaluation criteria above

Enrollment

30.05.2025 - 15.09.2025

Timing

02.09.2025 - 21.12.2025

Number of ECTS credits allocated

5 op

Mode of delivery

Contact teaching

Campus

Kupittaa Campus

Teaching languages
  • Finnish
  • English
Seats

90 - 120

Degree programmes
  • Degree Programme in Information and Communication Technology
Teachers
  • Annukka Kinnari
  • Jetro Vesti
  • Tiina Ferm
  • Laura Järvenpää
Groups
  • PTIVIS25D
    PTIVIS25D
  • PTIVIS25E
    PTIVIS25E
  • PTIVIS25F
    PTIVIS25F

Objective

By the end of this course, students can:

understand the role of no-code and low-code tools in design processes.
design basic solutions in NCLC platforms.
collaborate in teams on an NCLC project.
consider NCLC implementation constraints and opportunities.
evaluate their NCLC-implemented projects.
reflect on the entire process.

Content

This course delves into the "Implement" and "Operate" stages of the CDIO framework using low-code/no-code tools. The students will complete a NCLC project including the following steps:
*Introduction to Software Development and No-Code/Low-Code Platforms
*Implementation with No-Code/Low-Code Platform
*Testing, Feedback, and Iteration

Materials

Material provided by the teacher and shared in learning environment (ITS).

Teaching methods

This course consists of:
- lectures: theoretical background and demonstrating the use of various low code/ no-code frameworks and environments that can be used for example in software / game / web development.
- practice sessions: practicing the use of LCNC tools introduced in lecture, learning project working skills
- group work: students will complete a LCNC project where they use the tools and skills learned in lectures and practice

Exam schedules

-

International connections

In the course, skills are learned through exercises and practical project work.

Only electronic materials are used in the implementation.

Completion alternatives

-

Student workload

The student completes tasks related to the course, with an estimated workload:
- Theory lessons: 9 x 2h = 18h
- Practical lessons: 10 x 2h = 20h
- Group work: 2 x 2h = 4h
- Final event: 4h
- Other independent/group work: approximately 90h
TOTAL: approximately 135h

Content scheduling

This course delves into the "Implement" and "Operate" stages of the CDIO framework using Low-Code/No Code (LCNC) tools. The students will complete a LCNC project including the following steps:
- Introduction to Software Development and LCNC Platforms
- Implementation with LCNC Platform
- Testing, Feedback, and Iteration

The course is implemented during weeks 38 - 50 as follows:
- Theory, weeks 38 - 47: 2h contact session for 9 weeks
- Practice, weeks 39 - 49: 2h contact session with your own tutor
- Group work, weeks 48-49: 2h independent working
- Final event, week 50

Further information

Available in ITS.

Evaluation scale

H-5

Assessment methods and criteria

The course assessment is based on:
1. Active participation
2. Timely submission of weekly exercises
3. The final LCNC project outcome

Each section (1-3) receives its own grade, and to pass the course, each section must be approved.

The final grade is calculated based on the weighted scores from each section:
1. Attendance 25%
2. Weekly assignments 50%
3. Final project 25%

Section 1: Attendance
Attendance fewer than 13 times: Fail
Attendance 13 times: Grade 1
Attendance 14 times: Grade 2
Attendance 15 times: Grade 3
Attendance 16 times: Grade 4
Attendance more than 16 times: Grade 5

Section 2: Weekly Assignments

There are 9 weekly assignments, each graded from 0 to 3 points as follows:

0 points: Assignment not submitted on time OR Submission is incomplete and does not match instructions OR Submission shows signs of cheating, e.g., identical to another student's work.

1 point: Assignment submitted on time AND submission is incomplete or partially matches instructions.

2 points: Assignment submitted on time AND submission mostly matches instructions but contains minor shortcomings.

3 points: Assignment submitted on time AND submission fully matches instructions.

Grading scale based on total points:
Fewer than 13 points: Fail
13–15 points: Grade 1
16–18 points: Grade 2
19–21 points: Grade 3
22–24 points: Grade 4
25–27 points: Grade 5

NOTE: Passing the course requires submission of at least 50% of the assignments. Only assignments submitted on time will be evaluated.

Section 3: Final Project

No final project produced and presented at the final event OR the project submission includes cheating (e.g., the final product is clearly not the group's own work) OR the application is significantly unfinished, non-functional, or incomprehensible: FAIL

Application partially functions but has significant issues affecting usability or functionality. Issues may relate to the user interface, operational logic, or feature performance: Grade 1

Application meets minimum requirements but clearly needs improvement in technical aspects and usability. It is very basic, with minimal additional features or enhancements beyond essential functions: Grade 2

Application is functional and usable but lacks significant innovation. Well-executed and meets course requirements, but not notably innovative or distinctive: Grade 3

Application is technically high-quality and includes thoughtful additional features. Good consideration of user interface and user experience. Tools and techniques are used effectively, and the application stands out positively (additional features should be purposeful rather than merely decorative): Grade 4

Application is innovative, exceptionally well-executed, and provides users with something new and significant. It creatively and effectively utilizes course tools. Technically flawless, highly user-friendly, and offers an outstanding user experience. Demonstrates a clear understanding of leveraging low-code platforms for broader application development opportunities: Grade 5

Assessment criteria, fail (0)

See the evaluation criteria above

Assessment criteria, satisfactory (1-2)

See the evaluation criteria above

Assessment criteria, good (3-4)

See the evaluation criteria above

Assessment criteria, excellent (5)

See the evaluation criteria above

Enrollment

30.05.2025 - 15.09.2025

Timing

02.09.2025 - 21.12.2025

Number of ECTS credits allocated

5 op

Mode of delivery

Contact teaching

Campus

Kupittaa Campus

Teaching languages
  • English
Seats

90 - 110

Degree programmes
  • Degree Programme in Information and Communications Technology
Teachers
  • Virtuaalihenkilö3 IECS
  • Tiina Ferm
Groups
  • PINFOS25B
    PINFOS25B
  • PINFOS25C
    PINFOS25C
  • ExchangeIECS25
    Exchange IECS 25
  • PINFOS25A
    PINFOS25A

Objective

By the end of this course, students can:

understand the role of no-code and low-code tools in design processes.
design basic solutions in NCLC platforms.
collaborate in teams on an NCLC project.
consider NCLC implementation constraints and opportunities.
evaluate their NCLC-implemented projects.
reflect on the entire process.

Content

This course delves into the "Implement" and "Operate" stages of the CDIO framework using low-code/no-code tools. The students will complete a NCLC project including the following steps:
*Introduction to Software Development and No-Code/Low-Code Platforms
*Implementation with No-Code/Low-Code Platform
*Testing, Feedback, and Iteration

Materials

Material provided by the teacher and shared in learning environment (ITS).

Teaching methods

This course consists of:
- lectures: theoretical background and demonstrating the use of various low code/ no-code frameworks and environments that can be used for example in software / game / web development.
- practice sessions: practicing the use of LCNC tools introduced in lecture, learning project working skills
- group work: students will complete a LCNC project where they use the tools and skills learned in lectures and practice

Exam schedules

-

International connections

In the course, skills are learned through exercises and practical project work.

Only electronic materials are used in the implementation.

Completion alternatives

-

Student workload

The student completes tasks related to the course, with an estimated workload:
- Theory lessons: 9 x 2h = 18h
- Practical lessons: 10 x 2h = 20h
- Group work: 2 x 2h = 4h
- Final event: 4h
- Other independent/group work: approximately 90h
TOTAL: approximately 135h

Content scheduling

This course delves into the "Implement" and "Operate" stages of the CDIO framework using Low-Code/No Code (LCNC) tools. The students will complete a LCNC project including the following steps:
- Introduction to Software Development and LCNC Platforms
- Implementation with LCNC Platform
- Testing, Feedback, and Iteration

The course is implemented during weeks 38 - 50 as follows:
- Theory, weeks 38 - 47: 2h contact session for 9 weeks
- Practice, weeks 39 - 49: 2h contact session with your own tutor
- Group work, weeks 48-49: 2h independent working
- Final event, week 50

Further information

Available in ITS.

Evaluation scale

H-5

Assessment methods and criteria

The course assessment is based on:
1. Active participation
2. Timely submission of weekly exercises
3. The final LCNC project outcome

Each section (1-3) receives its own grade, and to pass the course, each section must be approved.

The final grade is calculated based on the weighted scores from each section:
1. Attendance 25%
2. Weekly assignments 50%
3. Final project 25%

Section 1: Attendance
Attendance fewer than 13 times: Fail
Attendance 13 times: Grade 1
Attendance 14 times: Grade 2
Attendance 15 times: Grade 3
Attendance 16 times: Grade 4
Attendance more than 16 times: Grade 5

Section 2: Weekly Assignments

There are 9 weekly assignments, each graded from 0 to 3 points as follows:

0 points: Assignment not submitted on time OR Submission is incomplete and does not match instructions OR Submission shows signs of cheating, e.g., identical to another student's work.

1 point: Assignment submitted on time AND submission is incomplete or partially matches instructions.

2 points: Assignment submitted on time AND submission mostly matches instructions but contains minor shortcomings.

3 points: Assignment submitted on time AND submission fully matches instructions.

Grading scale based on total points:
Fewer than 13 points: Fail
13–15 points: Grade 1
16–18 points: Grade 2
19–21 points: Grade 3
22–24 points: Grade 4
25–27 points: Grade 5

NOTE: Passing the course requires submission of at least 50% of the assignments. Only assignments submitted on time will be evaluated.

Section 3: Final Project

No final project produced and presented at the final event OR the project submission includes cheating (e.g., the final product is clearly not the group's own work) OR the application is significantly unfinished, non-functional, or incomprehensible: FAIL

Application partially functions but has significant issues affecting usability or functionality. Issues may relate to the user interface, operational logic, or feature performance: Grade 1

Application meets minimum requirements but clearly needs improvement in technical aspects and usability. It is very basic, with minimal additional features or enhancements beyond essential functions: Grade 2

Application is functional and usable but lacks significant innovation. Well-executed and meets course requirements, but not notably innovative or distinctive: Grade 3

Application is technically high-quality and includes thoughtful additional features. Good consideration of user interface and user experience. Tools and techniques are used effectively, and the application stands out positively (additional features should be purposeful rather than merely decorative): Grade 4

Application is innovative, exceptionally well-executed, and provides users with something new and significant. It creatively and effectively utilizes course tools. Technically flawless, highly user-friendly, and offers an outstanding user experience. Demonstrates a clear understanding of leveraging low-code platforms for broader application development opportunities: Grade 5

Assessment criteria, fail (0)

See the evaluation criteria above

Assessment criteria, satisfactory (1-2)

See the evaluation criteria above

Assessment criteria, good (3-4)

See the evaluation criteria above

Assessment criteria, excellent (5)

See the evaluation criteria above

Enrollment

01.12.2024 - 14.01.2025

Timing

14.01.2025 - 30.04.2025

Number of ECTS credits allocated

5 op

Mode of delivery

Contact teaching

Campus

Kupittaa Campus

Teaching languages
  • Finnish
  • English
Seats

0 - 60

Degree programmes
  • Degree Programme in Information and Communication Technology
  • Degree Programme in Business Information Technology
  • Degree Programme in Information and Communications Technology
Teachers
  • Mikko Peltonen de Santiago
  • Tiina Ferm
  • Laura Järvenpää
Groups
  • PINFOK25A
    PINFOK25A
  • PINFOK25C
    PINFOK25C

Objective

By the end of this course, students can:

understand the role of no-code and low-code tools in design processes.
design basic solutions in NCLC platforms.
collaborate in teams on an NCLC project.
consider NCLC implementation constraints and opportunities.
evaluate their NCLC-implemented projects.
reflect on the entire process.

Content

This course delves into the "Implement" and "Operate" stages of the CDIO framework using low-code/no-code tools. The students will complete a NCLC project including the following steps:
*Introduction to Software Development and No-Code/Low-Code Platforms
*Implementation with No-Code/Low-Code Platform
*Testing, Feedback, and Iteration

Materials

Materials are distributed in the learning platform (ITS).

Teaching methods

This course consists of:
- lectures: theoretical background and demonstrating the use of various low code/ no-code frameworks and environments that can be used for example in software / game / web development.
- practice sessions: practicing the use of LCNC tools introduced in lecture
- group work: students will complete a LCNC project where they use the tools and skills learned in lectures and practice

Exam schedules

-

International connections

In the course, skills are learned through exercises and practical project work.

Only electronic materials are used in the implementation.

Student workload

The student completes tasks related to the course, with an estimated workload:
- Theory lessons: 8 x 2h = 16h
- Practical lessons: 10 x 2h = 20h
- Group work: 2 x 2h = 4h
- Final event: 4h
- Other independent/group work: approximately 90h
TOTAL: approximately 135h

Content scheduling

This course delves into the "Implement" and "Operate" stages of the CDIO framework using Low-code/No-code (LCNC) tools. The students will complete a LCNC project including the following steps:
- Introduction to Software Development and LCNC Platforms
- Implementation with LCNC Platform
- Testing, Feedback, and Iteration

The course is implemented as follows:
- Theory: 2h contact session for 8 weeks
- Practice: 2h contact session with your own tutor
- Group work: 2h independent working
- Final event, week 50

Further information

ITS, email

Evaluation scale

H-5

Assessment methods and criteria

The course is assessed by
- active participation and timely submission of practice tasks
- the final LCNC project outcome

Additional information about the assessment is provided in the first lecture.

Assessment criteria, fail (0)

The student fails the course if he/she fails
- to attend enough contact sessions (lecture, practice, group work)
- to complete enough practice tasks (less than 50%)

LCNC-project contribution and result:
No active participation in the LCNC project OR there is no product to present in the final session.

Assessment criteria, satisfactory (1-2)

Participation: Lectures and practice sessions are mostly attended at the rate greater than 75%
Weekly practice tasks: 50% - 70% are submitted in time

LCNC-project contribution and result:
Based on peer-reviews, the student is contributing less than other group members AND the project was presented in the final session.

Assessment criteria, good (3-4)

Participation: Lectures and practice sessions are attended at the rate greater than 85%
Weekly practice tasks: 70% - 95% are submitted in time

LCNC-project contribution and result: Active contribution in project work and is at least at average level based on peer-reviews AND the project was presented in the final session.

Assessment criteria, excellent (5)

Participation: Lectures and practice sessions are attended at the rate greater than 90%
Weekly practice tasks: at least 95% of the tasks are submitted in time

LCNC-project contribution and result:
* Active contribution in project work and is above average level based on peer-reviews AND
* The project was presented in the final session AND
* The student showed innovative ways of using LCNC tools, in addition to technical and project management skills.

Enrollment

01.06.2024 - 23.09.2024

Timing

23.09.2024 - 13.12.2024

Number of ECTS credits allocated

5 op

Mode of delivery

Contact teaching

Unit

Engineering and Business

Campus

Kupittaa Campus

Teaching languages
  • Finnish
Seats

60 - 80

Degree programmes
  • Degree Programme in Business Information Technology
Teachers
  • Matti Kuikka
  • Mika Koivunen
Groups
  • PTIETS24A
    PTIETS24A
  • PTIETS24B
    PTIETS24B

Objective

By the end of this course, students can:

understand the role of no-code and low-code tools in design processes.
design basic solutions in NCLC platforms.
collaborate in teams on an NCLC project.
consider NCLC implementation constraints and opportunities.
evaluate their NCLC-implemented projects.
reflect on the entire process.

Content

This course delves into the "Implement" and "Operate" stages of the CDIO framework using low-code/no-code tools. The students will complete a NCLC project including the following steps:
*Introduction to Software Development and No-Code/Low-Code Platforms
*Implementation with No-Code/Low-Code Platform
*Testing, Feedback, and Iteration

Materials

Material provided by the teacher and shared in learning environment (ITS).

Teaching methods

This course consists of:
- lectures: theoretical background and demonstrating the use of various low code/ no-code frameworks and environments that can be used for example in software / game / web development.
- practice sessions: practicing the use of LCNC tools introduced in lecture
- group work: students will complete a LCNC project where they use the tools and skills learned in lectures and practice

Exam schedules

-

International connections

In the course, skills are learned through exercises and practical project work.

Only electronic materials are used in the implementation.

Completion alternatives

-

Student workload

The student completes tasks related to the course, with an estimated workload:
- Theory lessons: 8 x 2h = 16h
- Practical lessons: 10 x 2h = 20h
- Group work: 2 x 2h = 4h
- Final event: 4h
- Other independent/group work: approximately 90h
TOTAL: approximately 135h

Content scheduling

This course delves into the "Implement" and "Operate" stages of the CDIO framework using Low-Code/No Code (LCNC) tools. The students will complete a LCNC project including the following steps:
- Introduction to Software Development and LCNC Platforms
- Implementation with LCNC Platform
- Testing, Feedback, and Iteration

The course is implemented during weeks 39 - 50 as follows:
- Theory, weeks 39 - 47: 2h contact session for 8 weeks
- Practice, weeks 39 - 49: 2h contact session with your own tutor
- Group work, weeks 48-49: 2h independent working
- Final event, week 50

Further information

Available in ITS.

Evaluation scale

H-5

Assessment methods and criteria

The course is assessed by
1. Active participation
2. Timely submission of practice tasks
3. The final LCNC project outcome

See details in Finnish.

Enrollment

01.06.2024 - 09.09.2024

Timing

02.09.2024 - 18.12.2024

Number of ECTS credits allocated

5 op

Mode of delivery

Contact teaching

Unit

Engineering and Business

Campus

Kupittaa Campus

Teaching languages
  • Finnish
Seats

80 - 110

Degree programmes
  • Degree Programme in Information and Communication Technology
Teachers
  • Jaakko Lamminpää
  • Noora Maritta Nieminen
  • Paula Steinby
Groups
  • PTIVIS24B
    PTIVIS24B
  • PTIVIS24C
    PTIVIS24C
  • PTIVIS24A
    PTIVIS24A

Objective

By the end of this course, students can:

understand the role of no-code and low-code tools in design processes.
design basic solutions in NCLC platforms.
collaborate in teams on an NCLC project.
consider NCLC implementation constraints and opportunities.
evaluate their NCLC-implemented projects.
reflect on the entire process.

Content

This course delves into the "Implement" and "Operate" stages of the CDIO framework using low-code/no-code tools. The students will complete a NCLC project including the following steps:
*Introduction to Software Development and No-Code/Low-Code Platforms
*Implementation with No-Code/Low-Code Platform
*Testing, Feedback, and Iteration

Evaluation scale

H-5

Enrollment

29.05.2024 - 14.09.2024

Timing

02.09.2024 - 18.12.2024

Number of ECTS credits allocated

5 op

Mode of delivery

Contact teaching

Unit

Engineering and Business

Campus

Kupittaa Campus

Teaching languages
  • Finnish
Seats

80 - 110

Degree programmes
  • Degree Programme in Information and Communication Technology
Teachers
  • Mauri Suhonen
  • Annukka Kinnari
  • Jetro Vesti
Groups
  • PTIVIS24D
    PTIVIS24D
  • PTIVIS24E
    PTIVIS24E
  • PTIVIS24F
    PTIVIS24F

Objective

By the end of this course, students can:

understand the role of no-code and low-code tools in design processes.
design basic solutions in NCLC platforms.
collaborate in teams on an NCLC project.
consider NCLC implementation constraints and opportunities.
evaluate their NCLC-implemented projects.
reflect on the entire process.

Content

This course delves into the "Implement" and "Operate" stages of the CDIO framework using low-code/no-code tools. The students will complete a NCLC project including the following steps:
*Introduction to Software Development and No-Code/Low-Code Platforms
*Implementation with No-Code/Low-Code Platform
*Testing, Feedback, and Iteration

Materials

Materiaali jaetaan itslearningissä.

Teaching methods

Tämä kurssi käyttää seuraavia oppimismenetelmiä:
- Luennot: teoreettinen tausta ja erilaisten Low Code/No-Code -kehysten ja ympäristöjen käytön esittely. Näitä kehyksiä/ympäristöjä voidaan käyttää esimerkiksi ohjelmisto-/pelikehityksessä tai mobiilisovellus- tai websovelluskehityksessä.
- Käytännön harjoitukset: luennoilla esiteltyjen LCNC-työkalujen käytön harjoittelu.
- Ryhmätyö: opiskelijat tekevät LCNC-projektin, jossa he käyttävät luennoilla ja harjoituksissa opittuja työkaluja ja taitoja.

Exam schedules

Ei tenttiä.

International connections

Opintojaksolla opitaan taitoja harjoitusten ja käytännön projektityön avulla.

Opintojaksolla käytetään vain sähköisiä materiaaleja.

Student workload

Opiskelija suorittaa kurssiin liittyviä tehtäviä, joiden arvioitu työmäärä:
- Teoriatunnit: 8 x 2h = 16h
- Käytäntötunnit: 10 x 2h = 20h
- Ryhmätyö: 2 x 2h = 4h
- Lopputapahtuma: 4h
- Muu itsenäinen/ryhmätyöskentely: noin 90h
YHTEENSÄ: 135h

Content scheduling

Tämä kurssi perehdyttää opiskelijan CDIO-viitekehyksen vaiheisiin "Toteuta" (Implement) ja "Käytä" (Operate) käyttäen Low-Code/No-Code -työkaluja. Opiskelijat suorittavat Low-Code/ No-Code (LCNC)-projektin, joka sisältää seuraavat vaiheet:
- Johdatus ohjelmistokehitykseen ja Low-Code/ No-Code -alustoihin
- Toteutus Low-Code/ No-Code -alustalla
- Testaus, palaute ja iteraatio

Kurssi toteutetaan viikkojen 39 - 50 aikana seuraavasti:
- Teoria, viikot 39 - 47: 2h/viikko kontaktitunti 8 viikon ajan
- Käytäntö, viikot 39 - 49: 2h/viikko kontaktitunti oman tuutorin kanssa
- Ryhmätyö, viikot 48-49: 2h/viikko itsenäinen työskentely
- Lopputapahtuma, viikko 50

Further information

Opettaja viestii kurssiin liittyvistä asioista itslearningissä.

Jos opiskelijalla on kysyttävää, hänen tulee lähettää sähköpostia opettajalle/tutorille.

Evaluation scale

H-5

Assessment methods and criteria

Kurssin arviointiin vaikuttavat:
- aktiivinen osallistuminen
- harjoitustehtävien ajoissa palauttaminen
- lopullisen LCNC-projektin tulos

Lisätiedot arvioinnista kerrotaan ensimmäisellä luennolla.

Assessment criteria, fail (0)

Kurssisuoritus on hylätty, jos
- opiskelija ei osallistu riittävästi lähiopetustilaisuuksiin (luennot, harjoitukset, ryhmätyö)
- opiskelija palauttaa alle 50% tehtävistä määräajassa

LCNC-projektiin osallistuminen ja sen tulos:
Opiskelija ei osallistu aktiivisesti projektiin tai hänellä ei ole esitettävää lopputapahtumassa.

Assessment criteria, satisfactory (1-2)

Osallistuminen: Mukana kontakti- ja harjoitustunneilla vähintään 75%.
Harjoitustehtävät: 50% - 70% tehtävistä tehty määräajassa.

LCNC-projektiin osallistuminen ja sen tulos: Osallistuu projektiin, mutta vertaispalautteen mukaan vähemmän kuin muut JA projektiryhmä esitti tuotoksensa lopputapahtumassa.

Assessment criteria, good (3-4)

Osallistuminen: Mukana kontakti ja harjoitustunneilla vähintään 85%.
Harjoitustehtävät: 70% - 95% tehtävistä tehty määräajassa.

LCNC-projektiin osallistuminen ja sen tulos: Osallistuu projektiin ja aktiivisuus projektissa vertaispalautteen mukaan vähintään keskitasoa JA projektiryhmä esitti tuotoksensa lopputapahtumassa.

Assessment criteria, excellent (5)

Osallistuminen: Mukana kontakti ja harjoitustunneilla vähintään 90% päivänä.
Harjoitustehtävät: Vähintään 95% tehtävistä tehty määräajassa.

LCNC-projektiin osallistuminen ja sen tulos: Osallistuu projektiin ja aktiivisuus projektissa vertaispalautteen mukaan parempi kuin ryhmän keskiarvo JA projektiryhmä esitti lopputapahtumassa tuotoksensa JA opiskelija osoitti innovatiivisia tapoja käyttää LCNC-työkaluja sekä ymmärrystä teknisistä ja projektinhallinnan taidoista.

Enrollment

01.06.2024 - 09.09.2024

Timing

02.09.2024 - 18.12.2024

Number of ECTS credits allocated

5 op

Mode of delivery

Contact teaching

Unit

Engineering and Business

Campus

Kupittaa Campus

Teaching languages
  • English
Seats

70 - 110

Degree programmes
  • Degree Programme in Information and Communications Technology
Teachers
  • Poppy Skarli
  • Noora Maritta Nieminen
  • Hazem Al-Bermanei
  • Tiina Ferm
Groups
  • PINFOS24C
    PINFOS24C
  • PINFOS24A
    PINFOS24A
  • PINFOS24B
    PINFOS24B

Objective

By the end of this course, students can:

understand the role of no-code and low-code tools in design processes.
design basic solutions in NCLC platforms.
collaborate in teams on an NCLC project.
consider NCLC implementation constraints and opportunities.
evaluate their NCLC-implemented projects.
reflect on the entire process.

Content

This course delves into the "Implement" and "Operate" stages of the CDIO framework using low-code/no-code tools. The students will complete a NCLC project including the following steps:
*Introduction to Software Development and No-Code/Low-Code Platforms
*Implementation with No-Code/Low-Code Platform
*Testing, Feedback, and Iteration

Materials

Material provided by the teacher and shared in learning environment (ITS).

Teaching methods

This course consists of:
- lectures: theoretical background and demonstrating the use of various low code/ no-code frameworks and environments that can be used for example in software / game / web development.
- practice sessions: practicing the use of LCNC tools introduced in lecture
- group work: students will complete a LCNC project where they use the tools and skills learned in lectures and practice

Exam schedules

-

International connections

In the course, skills are learned through exercises and practical project work.

Only electronic materials are used in the implementation.

Completion alternatives

-

Student workload

The student completes tasks related to the course, with an estimated workload:
- Theory lessons: 8 x 2h = 16h
- Practical lessons: 10 x 2h = 20h
- Group work: 2 x 2h = 4h
- Final event: 4h
- Other independent/group work: approximately 90h
TOTAL: approximately 135h

Content scheduling

This course delves into the "Implement" and "Operate" stages of the CDIO framework using Low-Code/No Code (LCNC) tools. The students will complete a LCNC project including the following steps:
- Introduction to Software Development and LCNC Platforms
- Implementation with LCNC Platform
- Testing, Feedback, and Iteration

The course is implemented during weeks 39 - 50 as follows:
- Theory, weeks 39 - 47: 2h contact session for 8 weeks
- Practice, weeks 39 - 49: 2h contact session with your own tutor
- Group work, weeks 48-49: 2h independent working
- Final event, week 50

Further information

Available in ITS.

Evaluation scale

H-5

Assessment methods and criteria

The course is assessed by
1. Active participation
2. Timely submission of practice tasks
3. The final LCNC project outcome

See details in Finnish.

Enrollment

01.12.2023 - 01.02.2024

Timing

01.02.2024 - 30.04.2024

Number of ECTS credits allocated

5 op

Mode of delivery

Contact teaching

Unit

Engineering and Business

Campus

Kupittaa Campus

Teaching languages
  • English
Seats

60 - 120

Degree programmes
  • Degree Programme in Information and Communications Technology
Teachers
  • Mikko Peltonen de Santiago
  • Noora Maritta Nieminen
  • Tiina Ferm
Groups
  • PINFOK24B
    PINFOK24B
  • PINFOK24A
    PINFOK24A
  • PINFOK24C
    PINFOK24C

Objective

By the end of this course, students can:

understand the role of no-code and low-code tools in design processes.
design basic solutions in NCLC platforms.
collaborate in teams on an NCLC project.
consider NCLC implementation constraints and opportunities.
evaluate their NCLC-implemented projects.
reflect on the entire process.

Content

This course delves into the "Implement" and "Operate" stages of the CDIO framework using low-code/no-code tools. The students will complete a NCLC project including the following steps:
*Introduction to Software Development and No-Code/Low-Code Platforms
*Implementation with No-Code/Low-Code Platform
*Testing, Feedback, and Iteration

Materials

Material provided by the teacher and shared in ItsLearning

Teaching methods

This course consists of:
- lectures: theoretical background and demonstrating the use of various low code/ no-code frameworks and environments that can be used for example in software / game / web development.
- practice sessions: practicing the use of LCNC tools introduced in lecture
- group work: students will complete a LCNC project where they use the tools and skills learned in lectures and practice

Exam schedules

There is no exam in this course

Completion alternatives

Currently there are no optional methods to complete this course

Content scheduling

This course delves into the "Implement" and "Operate" stages of the CDIO framework using low-code/no-code tools. The students will complete a NCLC project including the following steps:
- Introduction to Software Development and No-Code/Low-Code Platforms
- Implementation with No-Code/Low-Code Platform
- Testing, Feedback, and Iteration

Further information

ItsLearning

Evaluation scale

H-5

Assessment methods and criteria

The course is assessed by
- active participation and timely submission of practice tasks
- the final LCNC project outcome

More detailed description of assessment is provided in the first lecture and ItsLearning

Assessment criteria, fail (0)

The student fails
- to attend enough contact sessions (lecture, practice, group work)
- to complete enough practice tasks
- to complete and attend LCNC project in his/her team

Assessment criteria, satisfactory (1-2)

The student understands and is capable of using LCNC tools in basic level.
The student has basic understanding on the limitations of LCNC tools.
The student can follow the project as a team member and contribute to the project at basic level.

Assessment criteria, good (3-4)

The student has more advanced understanding on LCNC tools and also shows understanding in different processes during the project.

Assessment criteria, excellent (5)

The student shows innovative ways to use LCNC tools and shows great understanding on both technical and project skills.