|
|
@@ -3,89 +3,20 @@
|
|
3
|
3
|
|
|
4
|
4
|
|
|
5
|
5
|
|
|
6
|
|
-[verano2016 - Coralys]
|
|
7
|
6
|
|
|
8
|
|
-The Introduction to Computer Programming course provides an introduction to the fundamental concepts of computer programming and the solution of problems through algorithm design, including parallel programming techniques. Students will have a full understanding of the basic components of a program starting with control structures using conditional and iterative instructions with logical expressions, as well as the definition and use of variables and data types. They will develop procedures and functions for common tasks that are repeated or more complex tasks that require decomposition, including recursive functions. They will use structured data types such as arrays, queues, files and pointers. Also, the students will be exposed to the computer's structure: input and output, memory, and the central processing unit. A general look into the Computer Science field and its effect in society, including ethical implications in computation, is included.
|
|
|
7
|
+This is the first of a series of lab experiences that were developed as part of the NSF-sponsored project "Development of engaging and readily transferable laboratory experiences for the introductory programming course" (DUE-1245744). The main goal of these lab experiences is that the students of introductory programming courses will practice the concepts and skills learned in class and obtain attractive products that will motivate them to further explore the endless opportunities of fun and applicability of Computer Science.
|
|
9
|
8
|
|
|
10
|
|
-During this semester the students in the Introduction to Computer Programming course will be participating in the project: "Engaging Introductory Programming Laboratory" (EIP). In this project, sponsored by the TUES program of the National Science Foundation, students will be able to work on laboratory experiences where they will practice the concepts and skills learned in class and obtain attractive products that will motivate them with the possibilities that Computer Science offers them.
|
|
11
|
|
-
|
|
12
|
|
-Each of the laboratory experiences will use libraries and programming sections that have been developed by professors and students of the Computer Science program of the University of Puerto Rico, RÃo Piedras campus. When the laboratory experience is completed, the student will not only reinforce the concepts learned in class, but will also get to know products that he or she will be capable of producing with a bit more knowledge and experience in computing.
|
|
13
|
|
-
|
|
14
|
|
-In today's laboratory experience you will learn how we will work in the upcoming meetings, how to access the files that will be used, and how to turn in the work. You will also learn to manage the basic elements of Qt, the platform that will allow us to develop and execute projects in C++.
|
|
|
9
|
+Each of the laboratory experiences uses libraries and reusable code developed by professors and students of the Computer Science program at the University of Puerto Rico, Río Piedras campus ([http://ccom.uprrp.edu](http://ccom.uprrp.edu)). When each laboratory experience is completed, the student will not only reinforce the concepts learned in class, but will also get a glimpse of the products that he or she may achieve with a bit more knowledge and experience in computing.
|
|
15
|
10
|
|
|
|
11
|
+In this first laboratory experience you will learn the workflow for the the upcoming meetings, how to access the files that will be used, and how to turn in your deliverables. You will also learn how to manage the basic elements of Qt, the platform that will allow us to develop and execute projects in C++.
|
|
16
|
12
|
|
|
17
|
13
|
## Objectives:
|
|
18
|
14
|
|
|
19
|
|
-1) Understand the goals of the laboratory for the Introduction to Computer Programming course (CCOM-3033).
|
|
20
|
|
-
|
|
21
|
|
-2) Get to know the laboratory experiences prepared and the general expectations of the laboratory sessions.
|
|
22
|
|
-
|
|
23
|
|
-3) Get to know the programming in pairs strategy.
|
|
24
|
|
-
|
|
25
|
|
-4) Get to know the rules of the laboratory sessions and the methods of evaluation.
|
|
26
|
|
-
|
|
27
|
|
-5) Practice the use of *Git* and *Bitbucket* to download and store the necessary files for each laboratory experience.
|
|
28
|
|
-
|
|
29
|
|
-6) Practice how to compile, fix errors, and execute a program using Qt.
|
|
30
|
|
-
|
|
31
|
|
-
|
|
32
|
|
----
|
|
33
|
|
-
|
|
34
|
|
----
|
|
35
|
|
-
|
|
36
|
|
-## About the laboratory
|
|
37
|
|
-
|
|
38
|
|
-### Course and evaluation policy
|
|
|
15
|
+1) Get to know the laboratory experiences prepared and the general expectations of the laboratory sessions.
|
|
39
|
16
|
|
|
40
|
|
-* All of the students should be registered in the Moodle page for Section 1 of the Laboratory using the email they most frequently read. The page can be found in moodle.ccom.uprrp.edu. All of the information, materials and assignments for the course will be on this page; each student is responsible for checking the page regularly and understanding the calendar for turning in their work.
|
|
41
|
|
-* All cellphones must remain off during the laboratory session. If one of these devices interrupts the session, the professor will assume it's an emergency and will ask the student to leave the laboratory. Moreover, the cellphone must not be on vibrate or emit light signals, and it cannot be on the desk. Just shut it off and put it away. This way you may concentrate while in class.
|
|
42
|
|
-* Only the laboratory laptops will be used.
|
|
43
|
|
-* The laboratory session will start promptly, so you should arrive on time. In the case of something extraordinary happening in which the professor shall be absent or late, the Department will be notified. If you arrive more than 15 minutes late, please do not enter the laboratory. If you leave the laboratory, let it be for an emergency; it is expected that once the session starts, the student will remain in the laboratory until it is finished.
|
|
44
|
|
-* For each laboratory session, there will be documents in Moodle related to the laboratory experience that you should read before arriving at the laboratory. Read and follow the instructions in the *Pre-Lab* session. The documents for each laboratory experience will be available in Moodle the Friday of the previous week.
|
|
45
|
|
-* There will be a *Pre-Lab* quiz that you should take during the first 10 minutes of the laboratory session. The quiz is taken using Moodle and will not be available after 10 minutes from the time the laboratory session begins. The quiz will be related to the concepts learned in class that will be necessary for the laboratory experience, and will also include reading comprehension questions for the week's laboratory session instructions. Quizzes will not be reset or retaken. However, the worst grade will be eliminated.
|
|
46
|
|
-* The laboratory experiences will be worked on in pairs. After each laboratory experience, each pair should hand in the files indicated in the instructions using Moodle. The final hand in date to hand in the files for each experience is the Tuesday that follows the laboratory session. Since the laboratory experiences will be worked on in pairs, only one member will hand in the work.
|
|
47
|
|
-* When the work for each laboratory session is finished, each student must take a *Post-Test* which lasts 10 minutes. With the Pre-Lab and Post-Test we evaluate the utility of the laboratory experience in learning the concepts and skills. The Post-Test will not be worth any points in the laboratory grade, but will be used to give a bonus on each laboratory experience. The Post-Test will be available on Moodle on Friday when the laboratory session is held, until 11:59pm of the following Tuesday.
|
|
48
|
|
-* Feel free to come by my office to clarify any doubts. If the door is open, you are welcome to come in; if it is closed, please wait for office hours. In the case of you having a scheduling conflict with the assigned office hours, you may schedule a meeting at any moment.
|
|
49
|
|
-* Responsibility and honesty are very important qualities for the Computer Science Department.
|
|
|
17
|
+2) Practice the use of *Git* and *Bitbucket* to download and store the necessary files for each laboratory experience.
|
|
50
|
18
|
|
|
51
|
|
-
|
|
52
|
|
-#### Evaluation
|
|
53
|
|
-
|
|
54
|
|
-* The laboratory grade will be 25% of the course grade.
|
|
55
|
|
-* The "Pre-Lab" tests will be 40% of the laboratory grade.
|
|
56
|
|
-* The work turned in will be 60% of the laboratory grade.
|
|
57
|
|
-* The criteria to obtain a bonus of 5 points in each laboratory experience are as follows:
|
|
58
|
|
-
|
|
59
|
|
- 1) You obtain 80 in the Pre-Lab and maintain or improve your grade in the Post-Test.
|
|
60
|
|
-
|
|
61
|
|
- 2) You obtain 75 or more in the Pre-Lab and improve by 15 points or more from Pre-Lab to Post-Test.
|
|
62
|
|
-
|
|
63
|
|
- 3) You obtain 80 or more in the Pre-Lab and improve by 10 points or more from Pre-Lab to Post-Test.
|
|
64
|
|
-
|
|
65
|
|
- 4) You obtain 85 or more in the Post-Test.
|
|
66
|
|
-
|
|
67
|
|
-* The total score for the delivered work will not be more than 100.
|
|
68
|
|
-
|
|
69
|
|
-
|
|
70
|
|
-
|
|
71
|
|
-### Programming in pairs
|
|
72
|
|
-
|
|
73
|
|
-During the entire semester the laboratory experiences will be worked on using the programming in pairs technique. Each pair will use one computer and each student in the pair will have one of two roles: conductor or navigator. The conductor will be in charge of writing and editing the code or the requirement for the laboratory. The navigator will read and evaluate what the conductor is writing to indicate if there was an error or to make suggestions. The pairs for each laboratory session will be announced on the Moodle page.
|
|
74
|
|
-
|
|
75
|
|
-
|
|
76
|
|
-### Pre-Lab and Post-Test
|
|
77
|
|
-
|
|
78
|
|
-Each laboratory experience contains a section called *Pre-Lab*. In this section you will find the objectives for the experience and the concepts you should review and study before arriving at the laboratory. There will be a link on the Moodle page for a short quiz that you should take during the first 10 minutes of the laboratory session. The quiz will not be available after the 10 minutes have passed from the time the laboratory session begins. The concepts that you should review for the laboratory experience are concepts covered during the course conference sections. The short quiz will also have reading comprehension questions for the laboratory instructions.
|
|
79
|
|
-
|
|
80
|
|
-The *Post-Test* is a short test about the same skills and concepts that are evaluated in the Pre-Lab. The Post-Test will be available on Moodle from the Friday of the laboratory session, until 11:59pm on the following Tuesday. These tests allows us to evaluate the efficacy of the laboratory experience in the learning of concepts and skills throughout the course. The points obtained will be used as a bonus for the laboratory grade.
|
|
81
|
|
-
|
|
82
|
|
-
|
|
83
|
|
-### Turning in the work
|
|
84
|
|
-
|
|
85
|
|
-When each laboratory experience is over, each pair should hand in the files with the implemented code or some other material. These deliveries will be done using Moodle and the instructions will be included in each laboratory experience.
|
|
86
|
|
-
|
|
87
|
|
-
|
|
88
|
|
----
|
|
|
19
|
+3) Practice how to compile, fix errors, and execute a program using Qt.
|
|
89
|
20
|
|
|
90
|
21
|
---
|
|
91
|
22
|
|
|
|
@@ -93,17 +24,17 @@ When each laboratory experience is over, each pair should hand in the files with
|
|
93
|
24
|
|
|
94
|
25
|
### Electronic book
|
|
95
|
26
|
|
|
96
|
|
-The instructions for the laboratory experience for this semester are contained in the electronic book you can access in http://eip.ccom.uprrp.edu/_book-en/.
|
|
|
27
|
+The instructions for the laboratory experience for this semester are contained in the electronic book you can access in [http://eip.ccom.uprrp.edu/_book-en/](http://eip.ccom.uprrp.edu/_book-en/).
|
|
97
|
28
|
|
|
98
|
|
-In the Moodle page we will indicate the name of the corresponding laboratory for each week and you can access the instructions using the index of the electronic book.
|
|
|
29
|
+We will publish the name of each week’s lab experience in our course’s Moodle page.
|
|
99
|
30
|
|
|
100
|
|
-This is a preliminary version of the book and therefore may contain errors. We would appreciate it if you would tell us if you find any errors or if you have any suggestion that could help clarify the instructions.
|
|
|
31
|
+This is a preliminary version of the book and therefore may contain errors. We would appreciate it if you would tell us if you find any errors or if you have any suggestion that could help clarify the instructions. Please notify us at: eip.uprrp@upr.edu.
|
|
101
|
32
|
|
|
102
|
33
|
### Bitbucket and Git
|
|
103
|
34
|
|
|
104
|
|
-*Bitbucket* is a repository or deposit for digital files which can be accessed online and allows the development of group projects in an ordered and simple manner. The files for the Introduction to Programming Laboratory will be stored in this site and can be downloaded to your personal computers using *Git*.
|
|
|
35
|
+*Bitbucket* is a repository or deposit for digital files that can be accessed online and allows the development of group projects in an ordered and simple manner. The files for the Introduction to Programming Laboratory will be stored in this site and can be downloaded to your personal computers using *Git*.
|
|
105
|
36
|
|
|
106
|
|
-*Git* is an open source program used to manage program files developed in groups. You can obtain this program in <http://git-scm.com/>. At the start of each laboratory experience you will download the necessary files to one of the classroom laptops using the command `git clone url` from the terminal in each computer.
|
|
|
37
|
+*Git* is an open source version control system that is primarily used for software development. The EIP team used Git during software development of the lab experiences. You as a student probably will not need to use of Git's version control capabilities for the coding assignments in the lab experiences. However, you will use Git to download the lab experience's source code files at the beginning of each session, e.g. using `git clone url`. You can obtain *Git* at http://git-scm.com/.
|
|
107
|
38
|
|
|
108
|
39
|
### Terminal and Linux
|
|
109
|
40
|
|
