CAVITE STATE UNIVERSITY Computer Programming I PDF 2024
Document Details
Uploaded by Deleted User
Cavite State University
2024
NESTOR MIGUEL T. PIMENTEL
Tags
Related
- Introduction to Computer Programming (CS109) Lecture Notes PDF
- Week 1 - Introduction to Java Lecture Notes PDF
- CS508 Modern Programming Languages Midterm PDF
- Introduction to Programming and Problem Solving (CS101) Lecture 1 PDF
- II-Sem Computer Science Syllabus PDF
- Java Programming Syllabus PDF - PARUL University
Summary
This is a syllabus for Computer Programming I offered at Cavite State University, Bacoor City Campus. It includes course description, intended learning outcomes, course requirements and programming methodologies.
Full Transcript
![](media/image2.png) Table of Contents [**COURSE DESCRIPTION** 2](#course-description) [**COURSE REQUIREMENTS** 2](#course-requirements) [**CSS Combinators** 4](#programming-cycle) [**CSS Pseudo Class**](#algorithm) [**CSS Pseudo Codes Elements**](#pseudocodes) 6 7 +-----------------------+...
![](media/image2.png) Table of Contents [**COURSE DESCRIPTION** 2](#course-description) [**COURSE REQUIREMENTS** 2](#course-requirements) [**CSS Combinators** 4](#programming-cycle) [**CSS Pseudo Class**](#algorithm) [**CSS Pseudo Codes Elements**](#pseudocodes) 6 7 +-----------------------+-----------------------+-----------------------+ | Republic of the | | **COURSE DESCRIPTION* | | Philippines | | * | | | | ===================== | | **CAVITE STATE | | = | | UNIVERSITY** | | | | | | | | **Bacoor City | | | | Campus** | | | | | | | | SHIV, Molino VI, City | | | | of Bacoor | | | +-----------------------+-----------------------+-----------------------+ | | | **NC-DCIT 22: | | | | COMPUTER PROGRAMMING | | | | I** | | | | | | | | The course covers the | | | | use of general | | | | purpose programming | | | | language to solve | | | | problems. The | | | | emphasis is to train | | | | students to design, | | | | implement, test, and | | | | debug programs | | | | intended to solve | | | | computing problems | | | | using fundamental | | | | programming | | | | constructs. | +-----------------------+-----------------------+-----------------------+ | MISSION | | **[PROGRAM OUTCOMES | | ------- | | ADDRESSED BY THE | | | | COURSE. AFTER | | Cavite State | | COMPLETING THIS | | University shall | | COURSE, THE STUDENTS | | provide excellent, | | MUST BE ABLE | | equitable and | | TO:]{.smallcaps}** | | relevant educational | | | | opportunities in the | | | | arts, science and | | | | technology through | | | | quality instruction | | | | and relevant research | | | | and development | | | | activities. | | | | | | | | It shall produce | | | | professional, skilled | | | | and morally upright | | | | individuals for | | | | global | | | | competitiveness. | | | | | | | | VISION | | | | ------ | | | | | | | | The premier | | | | university in | | | | historic Cavite | | | | recognized for | | | | excellence in the | | | | development of | | | | globally competitive | | | | and morally upright | | | | individuals. | | | | | | | | Instructor, Computer | | | | Programming 1 | | | | | | | | edan.belgica\@cvsu.ed | | | | u.ph | | | +-----------------------+-----------------------+-----------------------+ | | | 1. Attain the | | | | vision, mission, | | | | goals and | | | | objectives of the | | | | university, | | | | campus and | | | | department, | | | | | | | | 2. Deliver a gender | | | | fair and gender | | | | sensitive | | | | instruction to | | | | students aligned | | | | with University | | | | goals and | | | | objectives, | | | | | | | | 3. Present necessary | | | | concepts, | | | | techniques, and | | | | process to | | | | provide the | | | | skills necessary | | | | to define and | | | | analyze the | | | | effective | | | | communication in | | | | organization, | | | | | | | | 4. Show how to | | | | collect and | | | | structure | | | | information in | | | | the development | | | | of requirements | | | | and | | | | specifications, | | | | | | | | 5. Develop skills | | | | for effective | | | | interpersonal | | | | communication to | | | | develop consensus | | | | using classical | | | | techniques as | | | | well as computer | | | | facilitated | | | | groupware to | | | | demonstrate and | | | | analyze small | | | | group dynamics as | | | | related to | | | | working with | | | | users. | +-----------------------+-----------------------+-----------------------+ | | | **COURSE REQUIREMENTS | | | | ** | | | | ===================== | | | | == | +-----------------------+-----------------------+-----------------------+ | | | 1. Quizzes / | | | | Activities | | | | | | | | 2. Participations | | | | | | | | 3. Major | | | | Examinations | +-----------------------+-----------------------+-----------------------+ +-----------------------------------------------------------------------+ | ![](media/image2.png) | | | | Republic of the Philippines | | | | **CAVITE STATE UNIVERSITY** | | | | **Bacoor City Campus** | | | | SHIV, Molino VI, City of Bacoor | | | | INTENDED LEARNING OUTCOMES | | -------------------------- | | | | **After the completion of the unit, students will be able to:** | | | | 1. Familiarize with the hardware and software concepts of the | | computer system | | | | 2. Identify the steps involved in developing programs through the | | SDLC model | | | | 3. Define what algorithm and pseudocode are | | | | 4. Identify the different symbols used in flowcharting | | | | 5. Describe the concepts of using conditional statements and looping | | constructs | | | | 6. Recognize the use of Java as a programming language | | | | 7. Learn the language elements in Java | | | | 8. Use array in a Java program | +-----------------------------------------------------------------------+ | | +-----------------------------------------------------------------------+ | **Programming Cycle** | | ===================== | +-----------------------------------------------------------------------+ | | +-----------------------------------------------------------------------+ | **Algorithm** | | ============= | +-----------------------------------------------------------------------+ | | +-----------------------------------------------------------------------+ | | +-----------------------------------------------------------------------+ | **Pseudocodes** | | =============== | +-----------------------------------------------------------------------+ | | +-----------------------------------------------------------------------+ | - while not at end of list compare adjacent elements if second is | | greater than first switch them | | | | - get next two elements | | | | - if elements were switched repeat for entire list | +-----------------------------------------------------------------------+ | | +-----------------------------------------------------------------------+ | **Flowchart** | | ============= | +-----------------------------------------------------------------------+ | | +-----------------------------------------------------------------------+ | - **Flow lines** are indicated by directed lines to **show the | | direction of data** or the control flow. The arrowhead is | | sometimes not shown when the direction of flow is clear. Flow | | lines are used to connect blocks by exiting from one and entering | | another. | | | | - **Ovals or rounded rectangles** in a flowchart are called | | **Terminal Blocks**. These blocks are used to indicate the start | | and end of a module or program. An oval is labeled with the name | | of the module at the start. The end is indicated by the word end | | or stop for the top or Control Module. A start has no flow line | | entering it and only one exiting it. On the other hand, an end or | | exit has one flow line entering it but none exiting it. | | | | - The **hexagon**, which is called an **initialization block**, is | | used for declaring / initializing variables. It has one entrance | | and one exit. You can only use variables that had been | | initialized. | | | | - The **rectangle** indicates a **processing block**, for such | | things as calculations, opening and closing files, and so forth. | | A processing block has one entrance and one exit. | | | | - The **parallelogram** indicates general input and output | | operations. An **I/O block** has one entrance and only one exit. | | | | - The **diamond or \"Decision block\"** indicates a decision. It | | has one entrance and exactly two exits from the block. Entry/exit | | points are through the vertices. It is a logical statement that | | should evaluate to TRUE or FALSE. Exit points are labeled to | | indicate when each will be used (e.g., using T and F, or to be | | more readable, using Yes or Y and No or N). | | | | | | | | - **Circles or Connectors** are used for in-page **connectors**, | | labeled with uppercase letters while pentagons are used for | | off-page connectors, labeled with uppercase letters and a number | | (typically the page number of the matching pair). The circle is | | used as a connection point between two sections of a flowchart | | that are not adjacent or closely located to each other. These | | connectors should be used as little as possible. They should only | | be used to enhance readability. Overuse, however, decreases | | readability and produces a cluttered effect. | +-----------------------------------------------------------------------+ +-----------------------------------------------------------------------+ | | +-----------------------------------------------------------------------+ | **Programming methodology** | | =========================== | +-----------------------------------------------------------------------+ | | +-----------------------------------------------------------------------+ **Types of Programming Methodologies** There are many types of programming methodologies prevalent among software developers − Procedural Programming Object-oriented Programming