Difference between revisions of "IU:CreateTestPage"
Jump to navigation
Jump to search
R.sirgalina (talk | contribs) |
R.sirgalina (talk | contribs) |
||
| Line 65: | Line 65: | ||
| 3 || Creating product infrastructure with no-code/low-code tools || 20 |
| 3 || Creating product infrastructure with no-code/low-code tools || 20 |
||
|} |
|} |
||
| + | === Section 1 === |
||
| + | |||
| + | ==== Section title ==== |
||
| + | Fundamentals to no-code/low-code development |
||
| + | |||
| + | ==== Topics covered in this section ==== |
||
| + | * Overview of no-code/low-code tools and common use cases |
||
| + | * Organizing and storing your data with no-code databases tools |
||
| + | * Business Logic and functionality through Workflows |
||
| + | * Configuring a no-code API service |
||
| + | * No-code tools for UI/UX design |
||
| + | |||
| + | ==== What forms of evaluation were used to test students’ performance in this section? ==== |
||
| + | {| class="wikitable" |
||
| + | |+ |
||
| + | |- |
||
| + | ! Form !! Yes/No |
||
| + | |- |
||
| + | | Development of individual parts of software products || 1 |
||
| + | |- |
||
| + | | Homework and individual projects || 1 |
||
| + | |- |
||
| + | | Midterm evaluation || 0 |
||
| + | |- |
||
| + | | Testing (written or computer based) || 0 |
||
| + | |- |
||
| + | | Reports || 0 |
||
| + | |- |
||
| + | | Essays || 0 |
||
| + | |- |
||
| + | | Oral polls || 0 |
||
| + | |- |
||
| + | | Discussions || 1 |
||
| + | |} |
||
| + | |||
| + | ==== Typical questions for ongoing performance evaluation within this section ==== |
||
| + | # Name popular no-code/low-code tools and their respective use-cases |
||
| + | # Define what the common use cases for no-code and low-code solutions |
||
| + | # Explain the difference between low-code and no-code development platforms |
||
| + | # Describe how no-code tools support organizing product data |
||
| + | # Describe how low-code tools support retrieving and editing the data through APIs |
||
| + | |||
| + | ==== Typical questions for seminar classes (labs) within this section ==== |
||
| + | |||
| + | |||
| + | ==== Typical questions for final assessment in this section ==== |
||
| + | # Design an Entity Relation Diagram for your product |
||
| + | # Organize your products data into a database model on a no-code tool |
||
| + | # Design API architecture and methods for your tool |
||
| + | # Deploy your API methods and connect them with the database |
||
| + | # Configure business logic for the API methods |
||
Revision as of 14:30, 10 November 2021
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
- 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
- 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
- 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
Course evaluation
| Type | Points |
|---|---|
| Labs/seminar classes | 30 |
| Interim performance assessment | 30 |
| Final Project | 40 |
Grades range
| Grade | Points |
|---|---|
| A. Excellent | [90, 100] |
| B. Good | [75, 89] |
| C. Satisfactory | [60, 74] |
| D. Poor | [0, 59] |
Resources and reference material
- NoCode Education, Learn about no code tools:
- James Martin. 1991. Rapid application development. Macmillan Publishing Co., Inc., USA.
Course Sections
The main sections of the course and approximate hour distribution between them is as follows:
| Section | Section Title | Teaching Hours |
|---|---|---|
| 1 | Fundamentals of no-code/low-code development | 20 |
| 2 | Mobile and web development with no-code/low-code platforms | 20 |
| 3 | Creating product infrastructure with no-code/low-code tools | 20 |
Section 1
Section title
Fundamentals to no-code/low-code development
Topics covered in this section
- Overview of no-code/low-code tools and common use cases
- Organizing and storing your data with no-code databases tools
- Business Logic and functionality through Workflows
- Configuring a no-code API service
- No-code tools for UI/UX design
What forms of evaluation were used to test students’ performance in this section?
| Form | Yes/No |
|---|---|
| Development of individual parts of software products | 1 |
| Homework and individual projects | 1 |
| Midterm evaluation | 0 |
| Testing (written or computer based) | 0 |
| Reports | 0 |
| Essays | 0 |
| Oral polls | 0 |
| Discussions | 1 |
Typical questions for ongoing performance evaluation within this section
- Name popular no-code/low-code tools and their respective use-cases
- Define what the common use cases for no-code and low-code solutions
- Explain the difference between low-code and no-code development platforms
- Describe how no-code tools support organizing product data
- Describe how low-code tools support retrieving and editing the data through APIs
Typical questions for seminar classes (labs) within this section
Typical questions for final assessment in this section
- Design an Entity Relation Diagram for your product
- Organize your products data into a database model on a no-code tool
- Design API architecture and methods for your tool
- Deploy your API methods and connect them with the database
- Configure business logic for the API methods