Computer Science Technology Department

Computer Science Technology Department Houston Community College Department Phone Number: a b Houston Community College COSC 1436 Programming Fundamental I C# Course Syllabus Instructor Course Reference Number (CRN) Course Description: Course Prerequisite(s) Course Semester Credit Hours (SCH) (Lecture, Lab) Course Location/Times Name: PK Louie Tel: 713 718 5241 Office: Stafford Scarcella E120C Email: pk.louie@hccs.edu Website: http://tc3.hccs.edu/louiepk 51385 Course Level Beginning Introduces the fundamental concepts of structured programming. Topics include software development methodology, data types, control structures, functions, arrays, and the mechanics of running, testing, and debugging. This course assumes computer literacy. Must be at college-level skills in reading and writing, place into MATH 1314 College Algebra or higher. Credit Hours 4.0 (Lecture 3, Lab 3) Total Course Contact Hours: 96 Stafford Scarcella E106 Monday Wednesday 09:00am 12:00pm Instructional Materials (Textbook) For C#: C# Programming From Problem Analysis to Program Design. 3 rd Edition Author: Barbara Doyle. ISBN: 978-0-538-45302-8. Publisher: Cengage. ISBN: 0-538-45302-8. Publisher: Cengage. Instructional Methods (select one) Face to Face Web-enhanced (49% or less) Distance (100%) Type of Instruction (Lecture, Lecture/Lab, COOP, Practicum) Lecture/Lab, Course Length (number of weeks) 16 Weeks Computer Science Technology Department Page 1 of 12

EGLS3 -- Evaluation for Greater Learning Student Survey System At Houston Community College, professors believe that thoughtful student feedback is necessary to improve teaching and learning. During a designated time, you will be asked to answer a short online survey of research-based questions related to instruction. The anonymous results of the survey will be made available to your professors and division chairs for continual improvement of instruction. Look for the survey as part of the Houston Community College Student System online near the end of the term. Course Requirement, Policy, and Course Calendar Instructor's Requirements Academic Honesty: Students are expected to complete all materials (examinations and exercises) on their own. Each student must code and debug his own program code (No help from other students. Help from the instructor or tutor is permitted). All the work that you turn in is expected to be your own. Both giving and receiving information about quizzes, projects, or test constitutes academic dishonesty. The penalty for academic dishonesty will be grade of F and dismissal from this course Working together on programming assignments is not permitted. However, helping a fellow student understand the intent of a specification is OK. Students who work together too closely together (e.g. designing their solution together) should be aware that this is a form of cheating called COLLUSION and is subject to academic penalties. The homework, programs, and exams must be the work of the student turning them in. Acts that exceed the bounds defined by the approved collaboration practices will be considered cheating. Such acts include: Copying solutions, code, or programs from someone else or giving someone else your solution, code, or programs. Getting help in debugging. (except from your instructor) Participating in a discussion group that develops a solution that everyone copies. We urge everyone in the class to take appropriate measures for protecting one's work. You should protect your files, homework solutions sheets, etc as deemed reasonable. Studying for test together is permitted and encouraged. Please ask for advice if you are unsure about how to work together with your friend in a legal helpful manner It is always OK to "work together" with your instructor. Make-up Exam Policy: As a general rule, I do not give any makeup examination. Computer Science Technology Department Page 2 of 12

FOR A PROGRAMMING ASSIGNMENT TO BE GRADEABLE IT MUST CONFORM TO THE SPECIFICATION, BE EXECUTABLE AND PRODUCE THE CORRECT OUTPUT. PROGRAMS NOT MEETING THE ABOVE CONDITIONS ARE WORTH ZERO POINTS Submitted work that is incomplete will be returned for re-working and will be assessed late points. Late Assignments Policy: The late penalty is 5 points per day 30 point max. No late work accepted after 2 calendar weeks past the due date. It is your responsibility to deliver the assignments by the due date deadline. Technology failure and Murphy s Law are not acceptable excuses. Early submissions are encouraged and is good protection from Murphy s Law. I will compile and run your code. Use the Visual Studio IDE to create a Project/Solution to write your code and debug your assignment Naming your Project The Project/Solution folder name will consist of your initials prefixed to the assignment filename Example: If Triangle.pgm is the Assignment filename, then the Project-name is pk.triangle Enter this name in the name textbox of the New Project Wizard Required source files: TestDriver.cs <Classname>.cs Program.cs This is a Console Main() consisting of Unit Tests. The test will use hard wired test values and externally calculated verifiable answers. This is the class implementation. This is typically a user interactive Console Interface. Submitting your Assignments for Grading Submission methods: 1 Copy your VS project folder to my USB flash drive (preferred method) 2 Email with attached zipped VS project folder. Must have a timestamp before deadline Computer Science Technology Department Page 3 of 12

3 Email with attached source files. Must have a timestamp before deadline Instructor Grading Criteria You must pass the final exam to pass the course. MidTerm 10% Final 20% Programming 50% Reading quiz && In class exercises 15% There will be Chapter quiz for each chapter in the textbook. Quizzes will be due at the start of the next Chapter. Course Calendar Reading responsibility: C# Programming From Problem Analysis to Program Design Barbra Doyle Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6 Chapter 7 Introduction to Computing Programming Data Types and Expressions Method and Behaviors Creating your own Classes Making Decisions Repeating Instructions Arrays Session 1 M1 August 29, 2011 Session 2 W1 August 31, 2011 Labor Day September 5, 2011 Session 3 W2 September 7, 2011 Session 4M3 September 12, 2011 lntroduction to Computing and Programming Chapter 1 History of Computers System and Application Software System Software Application Software Software Development Process Computer Science Technology Department Page 4 of 12

Steps in the Program Development Process Programming Methodologies Structured Procedural Programming Object-Oriented Programming Evolution of C# and.net Programming Languages.NET Why C#? Types of Applications Developed with C# Web Applications Windows Applications Console Applications Exploring the First C# Program Elements of a C# Program Comments Using Directive Namespace Class Definition Main() Method Method Body-Statements Compiling, Building, and Running an Application Typing Your Program Statements Compilation and Execution Process Compiling the Source Code Using Visual Studio IDE Debugging an Application Syntax Errors Run-time Errors Creating an Application Session 5 W3 September 14, 2011 Turn in Reading Quiz Chapter 1 Session 6 M4 September 19, 2011 Session 7 W4 September 21, 2011 Session 8 M5 September 26, 2011 Data Types and Expressions Chapter 2 Data Representation Bits Bytes Binary Numbering System Character Sets Kilobyte, Megabyte, Gigabyte, Terabyte, Petabyte Memory Locations for Data Identifiers Variables Literal Values Types, Classes, and Objects Types Computer Science Technology Department Page 5 of 12

Classes Objects Predefined Data Types Value Types Integral Data Types Floating-Point Types Decimal Types Boolean Variables Declaring Strings Making Data Constant Assignment Statements Basic Arithmetic Operations Increment and Decrement Operations Compound Operations Order of Operations Mixed Expressions Casts Formatting Output Programming Example: CarpetCalculator Coding Standards Naming Conventions Spacing Conventions Declaration Conventions Session 9W5 September 28, 2011 Turn in Reading Quiz Chapter 2 Session 10 M6 October 3, 2011 Session 11 W6 October 5, 2011 Methods and Behaviors Chapter 3 Anatomy of a Method Modifiers Return Type Method Name Parameters Method Body Calling Class Methods Predefined Methods Writing Your Own Class Methods Void Methods Value-Returning Method Types of Parameters Named and Optional Parameters Default Values with Optional Parameters Named Parameters Coding Standards Naming Conventions Computer Science Technology Department Page 6 of 12

Spacing Conventions Declaration Conventions Commenting Conventions Session 12 M7 October 10, 2011 Turn in Reading Quiz Chapter 3 Session 13 W7 October 12, 2011 Session 14 M8 October 17, 2011 Creating Your Own Classes Chapter 4 The Object Concept Private Member Data Writing Your Own Instance Methods Constructor Accessor Mutators Other Instance Methods Property Calling Instance Methods Calling the Constructor Calling Accessor and Mutator Methods Calling Other Instance Methods Testing Your New Class Coding Standards Naming Conventions Classes Properties Methods Constructor Guidelines Spacing Conventions Session 15 W8 October 19, 2011 Turn in Reading Quiz Chapter 4 Review for Midterm Exam Session 16 M9 October 24, 2011 Midterm Exam Session 17 W9 October 26, 2011 Session 18 M10 October 31, 2011 Session 19 W10 November 2, 2011 November 3, 2011 Last Day for Administrative Student Withdrawals- 4:30pm Session 20 M11 November 7, 2011 Making Decisions Chapter 5 Boolean Expressions Boolean Results Conditional Expressions Equality, Relational, and Logical Tests Short-Circuit Evaluation Computer Science Technology Department Page 7 of 12

Boolean Data Type If..else Selection Statements One-Way if Statement Two-Way if Statement Nested if... else Statement Switch Selection Statements Ternary Operator exp? trueexp : falseexp Order of Operations Coding Standards Guidelines for Placement of Curly Braces Guidelines for Placement of else with Nested if Guidelines for Use of White Space with a Switch Spacing Conventions Advanced Selection Statement Suggestions Session 21 W11 November 9, 2011 Turn in Reading Quiz Chapter 5 Session 22 M12 November 14, 2011 Session 23 W12 November 16, 2011 Session 24 M13 November 21, 2011 Repeating Instructions Chapter 6 Why Use a Loop? Using the While Statement Counter-Controlled Loop Sentinel-Controlled Loop State-Controlled Loops Using the For Statement Loop Using the Foreach Statement Using the Do... while Structure Nested Loops Recursive Calls Unconditional Transfer of Control Continue Statement Deciding Which Loop to Use Coding Standards Guidelines for Placement of Curly Braces Spacing Conventions Advanced Loop Statement Suggestions Last day Drop April 21, 2011 Easter April 22-24, 2011 Session 25 W13 November 23, 2011 Turn in Reading Quiz Chapter 6 Session 26 M14 November 28, 2011 Session 27 W14 November 30, 2011 Session 28 M15 December 5, 2011 Computer Science Technology Department Page 8 of 12

Arrays Chapter 7 Array Basics Array Declaration Array Initializers Array Access Sentinel-Controlled Access Using Foreach with Arrays Array Class Arrays as Method Parameters Pass by Reference Array Assignment P arams Parameters Arrays in Classes Array of User-Defined Objects Arrays as Return Types Coding Standards Guidelines for Naming Arrays Advanced Array Suggestions Session 29 W15 December 7, 2011 Turn in Reading Quiz Chapter 7 Review for Final Session 30 M16 December 12, 2011 Final Exam Computer Science Technology Department Page 9 of 12

Learning Objective, Students Learning Outcome, and Program Spec Note: This section of the syllabus provides the general course learning objectives, the expected students learning outcome, the course scope in terms of the department program, and the instrument used to evaluate the course. If you have any question, contact the instructor or the department. HCC Grading Scale Grade GPA Points A = 100-90 4 points per semester hour B = 89-80: 3 points per semester hour C = 79-70: 2 points per semester hour D = 69-60: 1 points per semester hour 59 and below = F 0 points per semester hour IP (In Progress) 0 points per semester hour W(Withdrawn) 0 points per semester hour I (Incomplete) 0 points per semester hour AUD (Audit) 0 points per semester hour IP (In Progress) is given only in certain developmental courses. The student must re-enroll to receive credit. COM (Completed) is given in non-credit and continuing education courses. To compute grade point average (GPA), divide the total grade points by the total number of semester hours attempted. The grades "IP," "COM" and "I" do not affect GPA. Course Student Learning Outcomes (SLO): 1 Explain the purpose of computer programming language 2 Identify and explain programming development lifecycle including planning, analysis, design, development, and maintenance. 3 Analyze problems. 4 Design algorithms using pseudo code, flowcharts, and structured charts Explain and use programming language elements including syntax, data types, conditional statement, control structures, procedures, arrays, classes, and objects. Create a program based on specification. 5 Use Integrated Development Environment (IDE) for the editing, building, debugging, and testing of programs. 6 Apply proper documentation and formatting of source code. Learning Objectives Student Assignments Refer to the course calendar Computer Science Technology Department Page 10 of 12

Student Assessment(s) 1 Explain the purpose of computer programming language Assessment criteria under development 2 Identify and explain programming development lifecycle including planning, analysis, design, development, and maintenance. Assessment criteria under development 3 Analyze problems. Assessment criteria under development 4 Design algorithms using pseudo code, flowcharts, and structured charts Explain and use programming language elements including syntax, data types, conditional statement, control structures, procedures, arrays, classes, and objects. Create a program based on specification. Assessment criteria under development 5 Use Integrated Development Environment (IDE) for the editing, building, debugging, and testing of programs. Assessment criteria under development 6 Apply proper documentation and formatting of source code. Assessment criteria under development Program/Discipline Requirements: Academic Discipline/CTE Program Student Learning Outcomes(PSLO) Instructors will use standard syllabus that will satisfy CurricuUNET requirements and improve on-going assessment of student-centered learning and teaching. 1 Identify the fundamental principles of programming, including those of algorithm analysis, software design, operating systems, and database 2 Design and write computer programs that are correct, simple, clear, efficient, well organized, and well documented 3 Know and be able to apply important data structures and algorithms 4 Understand the hardware and software aspects of computer systems that support application software development 5 Develop software engineering proficiency SCANS and/or Core Curriculum Competencies: If applicable 1 C1: Allocates Time Students will learn to allocate time to perform each task (online course will emphasize this task more). 2 C5: Acquires and Evaluates Information Student will be able to identify need for data, obtain it from existing sources or create them, and evaluate information. 3 C6: Organizes and Maintains Information Students will learn to organize their assignments and manage to complete them with specific deadline. 4 C18: Selects Technology Students will use flowcharts to understand the subject. Students will select appropriate compiler to run program. 5 C20: Maintains and Troubleshoots Technology Student will be able to prevent, identify or solve problems in machines, computers, Computer Science Technology Department Page 11 of 12

and other technologies. 6 F9: Problem Solving Students will learn problem-solving methodology (pseudo code). 7 F10: Seeing Things in the Minds Eye Student will be able to organize and process symbols, pictures, graphs, objects or other information. Every semester, calendar based weekly learning material (reading, hands exercises for inclass, web enhanced, or online assignments, and scheduled quiz/test/exam) will be posted as part of the syllabus. HCC Policy Statement Access Student Services Policies on their Web site: http://hccs.edu/student-rights Distance Education and/or Continuing Education Policies Access DE Policies on their Web site: Access CE Policies on their Web site for non-credit classes: http://de.hccs.edu/de/de-student-handbook http://hccs.edu/ce-student-guidelines Competencies: If applicable Computer Science Technology Department Page 12 of 12