Low-Code Software Development Basics (5 cr)

Evaluation scale

H-5

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

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

-

Pedagogic approaches and sustainable development

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

Evaluation 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

Failed (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

Further information

Available in ITS.