MIS 304: Intro to Problem Solving and Programming Fall 2015 Unique Numbers: 04280, 04285, 04290

Transcription

1 Instructor Ramakrishna Dantu Information, Risk and Operations Management (IROM) Department Class Times MW 12:30 2:00 p.m, 2:00 3:30 p.m, 3:30 5:00 p.m Class Location UTC Office CBA Mailbox IROM Department, CBA Phone Office Hours MW 10:30 12:00 and by Appointment Teaching Assistants TBD TA TBD Course Description Object-oriented program design and processing, language fundamentals and applications involving business problems. Topics include structured programming containing if/else structure, loops (while/for), functions, files, object-oriented programming principles. Student Learning Outcomes The student will be able to 1. develop problem-solving skills to design and develop solutions (programs) for business problems using Python language 2. employ the concepts of memory, variables, and references in a program. 3. understand and write general programming principles such as: sequence, selection (if/else), and iteration (while/for) 4. design and code modular programs using the constructs of classes and functions. 5. design and write code involving input/output (E.g., keyboard and/or files) 6. write basic object-oriented programs to demonstrate encapsulation, abstraction, composition, etc., 7. describe the differences between objects, classes, and instances. Required Textbooks and Other Course Materials Starting Out with Python, 3 rd edition by Tony Gaddis, Pearson, 2015 You are expected to read and study this textbook! You will be responsible for any assigned material in the textbook regardless of class coverage. So if you don t understand the material, be sure to ask your instructor. If you use a previous version of the text or any other text, it is your responsibility to keep track of the differences between the texts. All assignments, readings, and lectures come from the recommended text and the instructor is not responsible for mapping the old or different text to the new text. There is no guarantee that the older text will be exactly like the recommended text. Required Material 1. USB Flash drive for saving your files (assignments) in the lab. 2 GB will be more than sufficient. 2. Access to make sure that the listed in Canvas is one you actually check. All the announcements will be sent using Canvas. 3. MSB account number when we meet in the computer lab. This is your user name and password to login to the Mod Lab computers. If you don t know your username and password, you can find/change them at

2 Development Environment Follow the instructions given in the Appendix A for installing Python for Windows. Mac comes with Python preinstalled. However, for installing Python 3.x on Mac, follow the instructions in the link below: Classroom Participation You are expected to participate in the classroom discussion by answering questions, asking questions, raising issues, and making observations. You will learn more if you attend class regularly, take notes, ask questions and contribute to discussions. Coming to class is important, since many exam questions come from lectures and class discussion. Although attendance does not DIRECTLY factor into your course grade, there is a clear correlation between consistent attendance and strong performance on homework and exams. You can use any development environment you would like, but no environment will be taught. You will be responsible for learning the environment you choose. All code must run at the command prompt or IDLE for grading. Descriptions of Major Assignments and Examinations There will be five homework assignments, two exams, quizzes, and one final. See the tentative schedule below for further details. Attendance Class attendance is required. However, I may not take roll. Homework There will be five homework assignments. Your homework is due by 5:00 pm of the due date. There will be no makeup homework or homework for extra credit. Late homework will not be accepted. You must follow the class programming standards on every homework assignment. It is possible to have a project that works, but does not make an A. You will lose points if you fail to follow instructions carefully. Small details matter in programming, and therefore matter in your homework. The homework assignments will require students to write programs by applying course concepts learned during the semester. More specific instructions about the assignments will be posted on Canvas. Grades Assignment Weight Final Average Final Letter Grade Exam 1 25% A Exam 2 25% A- Final Exam 35% B+ Homework 10% B Assignments Quizzes 5% B C C C D D D F

3 Grading Policy HW Turn in Format 1. You are required to submit your assignments electronically through Canvas by 5:00pm on the due date. After that, no homework will be accepted. 2. Do not upload zip or rar files. 3. All.py files must open in Notepad on Windows or TextEdit on Mac and must display as a complete program with spacing and formatting as our standards indicate. 4. Make sure to write your full name as a comment at the very beginning of each.py file submitted for grading. 5. Any notifications/announcements regarding class will be posted on Canvas and sent via . You are responsible for checking for updates and your s for announcements. 6. Only homework submitted through Canvas will be graded. Homeworks submitted via will not be accepted. Grades will be posted on Canvas. 7. Note: In the past, many students thought they turned in their homework, but didn t actually submit the file, or they turned in the wrong version. Please be CAREFUL when submitting your homework on Canvas. Any errors in submission will cause you to get a ZERO! Please do not ask me to make an exception for you. If I make one for you, I have to make it for everyone. This makes it impossible for students to get their grades back in a timely manner. In the real world, consequences for not turning work in correctly are much more severe than a ding to your grade. In the professional world if you fail to turn in a bid on time and lost business for the company, you may lose your job. Mistakes do happen, but you need to act like a professional and accept the consequences. This policy is not flexible. ALWAYS double-check your submissions. Program Grading 1. If your program does not compile, you will not receive more than 20% of the maximum points. 2. If your program compiles but does not execute, you will not receive more than 35% of the maximum points. 3. If your program compiles and executes yet does not give the required output, you will not receive more than 50% of the maximum points. 4. You will get the maximum points only if your program compiles properly and executes according to the requirements specified in the assignment. 5. Your.py files must open in Notepad on Windows or TextEdit on Mac to receive full credit. 6. Your.py files must execute at the command prompt or IDLE, or they will not be graded. 7. You must name the.py files as specified or they will not be graded. 8. If must adhere to the coding standards as discussed in the class. Exams There will be two exams and a final. There will be no makeup exams under any circumstances. If you miss an exam and have a valid, legitimate, documented, non-academic reason, you must contact me by or phone BEFORE the time the exam starts. If you contact me AFTER the exam, it is considered missing the exam. Exams are closed book and include coding problems and possibly some short questions, multiple-choice questions, or matching. Final Exam The final exam will be comprehensive. It can be a combination of coding problems, short answer, multiple-choice, or matching.

4 Grades are calculated as follows: (5Homeworks / 500) 10 + (2Exams / 200) 50 + (1Final /100) 35+ (Quizzes /100) Feedback on Assignments Assignment feedback will be reported on Canvas. It is your responsibility to check the site to confirm that your assignment feedback is correct. However, you must do so within one week of the day the homework is returned or feedback is posted on Canvas. After the one-week window, your grade for that assignment is permanent. Canvas Use & Class Learning Your use of Canvas's should be for course-related messages only; please see UT Austin s Acceptable Use Policy. Messages for selling football tickets and posting party invites are not considered course-related unless your instructor has specifically allowed this usage for his/her class. See UT s Acceptable Use Policy at Information Privacy Password-protected class sites, such as Canvas, are available for all accredited courses taught at The University. Syllabi, handouts, assignments and other resources may be available within these sites. Site activities could include exchanging , engaging in class discussions and chats, and exchanging files. In addition, class rosters are a component of the sites. Students who do not want their names included in these electronic class rosters must restrict their directory information in the Office of the Registrar, Main Building, Room 1. For more information, see Using for Official Correspondence to Students is recognized as an official mode of university correspondence; therefore, you are responsible for reading your for university and course-related information and announcements. You are responsible for keeping the university informed about changes to your address. You should check your regularly and frequently. You can find UT Austin s policies and instructions for updating your address at Religious Holidays By UT Austin Policy, you must notify me of your pending absence at least 14 days before the date of observing a religious holy day. If you must miss a class, an examination, a work assignment, or a project to observe a religious holy day, I will give you an opportunity to complete the missed work within a reasonable time after the absence. Documented Disability Statement The University of Texas at Austin provides, upon request, appropriate academic accommodations for qualified students with disabilities. If you require special accommodations, you must obtain a letter that documents your disability from the Services for Students with Disabilities area of the Division of Diversity and Community Engagement ( or TTY). Present the letter to me at the beginning of the semester so we can discuss the accommodations you need. No later than five business days before an exam, you should remind me of any testing accommodations you will need so that I can make arrangements. For more information, visit

5 University of Texas Honor Code The core values of The University of Texas at Austin are learning, discovery, freedom, leadership, individual opportunity, and responsibility. Each member of the university is expected to uphold these values through integrity, honesty, trust, fairness, and respect toward peers and community. Scholastic Dishonesty Policy Students are encouraged to discuss the assignments with one another and to seek help from the instructors and lab proctors. However, each student must complete his or her own individual homework assignments independently. Copying another person's program (with or without their permission), or collaboration with other students to the extent that the result is in fact multiple submissions of one program rather than independent work is subject to the University dishonest policy. Any dishonesty such as cheating, false representation, plagiarism, etc. that comes to my attention will result in an F in the course. The University defines academic dishonesty as cheating, plagiarism, unauthorized collaboration, falsifying academic records, and any act designed to avoid participating honestly in the learning process. Scholastic dishonesty also includes, but is not limited to, providing false or misleading information to receive a postponement or an extension on an exam or other assignment, and submission of essentially the same written assignment for two different courses without faculty permission. The McCombs School of Business has no tolerance for acts of scholastic dishonesty. The responsibilities of both students and faculty with regard to scholastic dishonesty are described in detail in the BBA Program s Statement on Scholastic Dishonesty at Ethics.aspx. By teaching this course, I have agreed to observe all faculty responsibilities described in that document. By enrolling in this class, you have agreed to observe all student responsibilities described in that document. If the application of the Statement on Scholastic Dishonesty to this class or its assignments is unclear in any way, it is your responsibility to ask me for clarification. Students who violate University rules on scholastic dishonesty are subject to disciplinary penalties, including the possibility of failure in the course and/or dismissal from the University. Since dishonesty harms the individual, all students, the integrity of the University, and the value of our academic brand, policies on scholastic dishonesty will be strictly enforced. You should refer to the Student Judicial Services website at to access the official University policies and procedures on scholastic dishonesty as well as further elaboration on what constitutes scholastic dishonesty. Final Review Week A period of five class days prior to the first day of final examinations in the long sessions shall be designated as Final Review Week. The purpose of this week is to allow students sufficient time to prepare for final examinations. During this week, there shall be no scheduled activities such as required field trips or performances; and no instructor shall assign any themes, research problems or exercises of similar scope that have a completion date during or following this week unless specified in the class syllabus. During Final Review Week, an instructor shall not give any examinations constituting 10% or more of the final grade, except makeup tests and laboratory examinations. In addition, no instructor shall give any portion of the final examination during Final Review Week. During this week, classes are held as scheduled. In addition, instructors are not required to limit content to topics that have been previously covered; they may introduce new concepts as appropriate.

6 Students with disabilities Students with disabilities may request appropriate academic accommodations from the Division of Diversity and Community Engagement, Services for Students with Disabilities, , Behavior Concerns Advice Line (BCAL) BCAL is a service for students, faculty, and staff of the university to discuss their concerns about another individual s behavior. Trained staff members will assist the caller in exploring available options and strategies. They will also provide appropriate guidance and resource referrals to address the particular situation. Dialing (512) will connect you to trained staff members 24/7/365. Calls to BCAL can be anonymous, and there is also an on-line reporting form (not anonymous). Campus Safety Please note the following recommendations regarding emergency evacuation, provided by the Office of Campus Safety and Security, , Occupants of buildings on The University of Texas at Austin campus are required to evacuate buildings when a fire alarm is activated. Alarm activation or announcement requires exiting and assembling outside. Familiarize yourself with all exit doors of each classroom and building you may occupy. Remember that the nearest exit door may not be the one you used when entering the building. Students requiring assistance in evacuation should inform the instructor in writing during the first week of class. In the event of an evacuation, follow the instruction of faculty or class instructors. Do not re-enter a building unless given instructions by the following: Austin Fire Department, The University of Texas at Austin Police Department, or Fire Prevention Services office. Behavior Concerns Advice Line (BCAL): Further information regarding emergency evacuation routes and emergency procedures can be found at: Emergency Preparedness Every member of the university community must take appropriate and deliberate action when an emergency strikes a building, a portion of the campus, or entire campus community. Emergency preparedness means we are all ready to act for our own safety and the safety of others during a crisis. It takes an effort by all of us to create and sustain an effective emergency preparedness system. Your support is important to achieving the best possible outcomes during a crisis event. Emergency communications are tested monthly (every first Wednesday at 11:50 a.m)). The university uses various communications channels during emergencies. If you require assistance in evacuation during emergency situation, inform me in writing of your needs during the first week of class. This information will be provided to the Fire Prevention Services. If you have an emergency either on or off campus that they should call 911 to report the situation. Finally, review the document emergency terms that provides, along with definitions for key terms, instructions to follow during emergencies. Information related to emergency preparedness can be found at

7 TENTATIVE SCHEDULE Descriptions of major assignments and examinations: Week Date Chapter Topic Details Homework/Exam Aug 24 Aug 26 First day of classes Aug 31 Aug 31 Chapter 2 Input, Processing, and Output Sep 02 Chapter 2 Input, Processing, and Output Sep 07 Sep 07 Labor day holiday Sep 09 Chapter 3 Decision Structures and Boolean Logic Sep 11: Last day to add a course or drop a course for possible refund Sep 14 Sep 14 Chapter 3 Decision Structures and Boolean Logic Sep 16 Chapter 4 Repetition Structures HW 1 due on Sep 19 th (2,3) Sep 21 Sep 21 Chapter 4 Repetition Structures Sep 23 Chapter 5 Functions Sep 28 Sep 28 Chapter 5 Functions Sep 30 Chapter 5 Functions Exam 1 Review Oct 05 Oct 05 Exam 1 Exam 1 (Chapters 2,3,4,5) Oct 07 Chapter 6 Files and Exceptions HW 2 due on Oct 10 th (4,5) Oct 12 Oct 12 Chapter 6 Files and Exceptions Oct 14 Chapter 7 Lists and Tuples Oct 19 Oct 19 Chapter 7 Lists and Tuples Oct 21 Chapter 8 Strings HW 3 due on Oct 24 th (6,7) Oct 26 Oct 26 Chapter 8 Strings Oct 28 Chapter 9 Dictionaries and Sets Nov 02 Nov 02 Chapter 9 Dictionaries and Sets Nov 03: Last day to Change to/from Pass/Fail and to Drop a Class with Dean Approval Nov 04 Chapter 10 Classes and OO Programming Nov 09 Nov 09 Chapter 10 Classes and OO Programming Nov 11 Chapter 10 Classes and OO Programming HW 4 due on Nov 14 th (8,9,10) Exam 2 Review Nov 16 Nov 16 Exam 2 Exam 2 Chapters 6,7,8,9 Nov 18 Chapter 11 Inheritance Nov 23 Nov 23 Chapter 11 Inheritance Nov 25 Chapter 13 GUI Programming Nov 30 Nov 30 Chapter 13 GUI Programming Dec 02 Final Exam Review Final Exam Review (Comprehensive) Dec 04 Last day of HW 5 due on Dec 4 th (11, 13) classes Dec 07 Dec 10 Final Exam Thursday, Dec 10, :00 to 5:00pm Dec 11 Final Exam Friday, Dec 11, :00 to 5:00pm Dec 12 Final Exam Saturday, Dec 12, :00 to 10:00pm Your instructor reserves the right to adjust this schedule in any way that serves the educational needs of the students enrolled in this course. It is the student s responsibility to ensure they have the most current syllabus.