Difference between revisions of "IU:TestPage"

From IU
Jump to navigation Jump to search
(Replaced content with " = No-Code and Low-Code Development = * Course name: No-Code and Low-Code Development == Course Characteristics == === Key concepts of the class === * no-code/low-code d...")
Tag: Replaced
Line 11: Line 11:
 
=== What is the purpose of this course? ===
 
=== What is the purpose of this course? ===
 
The main purpose of this course is to enable students to build, deploy, and update applications for various business or technical purposes using no-code and low-code platforms.
 
The main purpose of this course is to enable students to build, deploy, and update applications for various business or technical purposes using no-code and low-code platforms.
  +
=== Course objectives based on Bloom’s taxonomy ===
  +
  +
==== - What should a student remember at the end of the course? ====
  +
By the end of the course, the students should be able to
  +
* By the end of the course, the students should be able to ...
  +
* list most popular no-code and low-code platforms and tools
  +
* define what the common use cases for no-code and low-code solutions
  +
* explain the difference between low-code and no-code development platforms
  +
  +
==== - What should a student be able to understand at the end of the course? ====
  +
By the end of the course, the students should be able to
  +
* By the end of the course, the students should be able to ...
  +
* describe the typical steps of no-code / low-code development process
  +
* discuss the evolution and future of low-code/no-code application development
  +
* describe how do low-code and no-code work
  +
* describe main advantages and disadvantages of using no-code and low-code tools
  +
  +
==== - What should a student be able to apply at the end of the course? ====
  +
By the end of the course, the students should be able to
  +
* By the end of the course, the students should be able to ...
  +
* build, deploy, and update applications using no-code and low-code tools
  +
* determine requirements and select appropriate tools
  +
* create app's workflows, data models, and user interfaces using the visual IDE
  +
* select and connect APIs, code customized front-end and database queries
  +
* test user acceptance of software

Revision as of 12:42, 29 November 2021

No-Code and Low-Code Development

  • Course name: No-Code and Low-Code Development

Course Characteristics

Key concepts of the class

  • no-code/low-code development
  • rapid application development

What is the purpose of this course?

The main purpose of this course is to enable students to build, deploy, and update applications for various business or technical purposes using no-code and low-code platforms.

Course objectives based on Bloom’s taxonomy

- What should a student remember at the end of the course?

By the end of the course, the students should be able to

  • By the end of the course, the students should be able to ...
  • list most popular no-code and low-code platforms and tools
  • define what the common use cases for no-code and low-code solutions
  • explain the difference between low-code and no-code development platforms

- What should a student be able to understand at the end of the course?

By the end of the course, the students should be able to

  • By the end of the course, the students should be able to ...
  • describe the typical steps of no-code / low-code development process
  • discuss the evolution and future of low-code/no-code application development
  • describe how do low-code and no-code work
  • describe main advantages and disadvantages of using no-code and low-code tools

- What should a student be able to apply at the end of the course?

By the end of the course, the students should be able to

  • By the end of the course, the students should be able to ...
  • build, deploy, and update applications using no-code and low-code tools
  • determine requirements and select appropriate tools
  • create app's workflows, data models, and user interfaces using the visual IDE
  • select and connect APIs, code customized front-end and database queries
  • test user acceptance of software