Lesson Plan Guideline

Superior University

Object Oriented Programming(OOP)

Module Handbook

Contents
1

Lesson Plan Guideline

1. Staff and Course Delivery Arrangements............................................03 2. Course Introduction............................................................................03 3. Course Objective................................................................................04 4. Course Coverage................................................................................05 5. Student Gains.....................................................................................06 6. Teaching and Learning Methodology..................................................06 7. Summative Assignment Details..........................................................08 8. Assessment Details and Policies.........................................................11 9. Reference Material.............................................................................12 10. Lecture Plan.....................................................................................13 11. Learning Outcomes..........................................................................15 12. Academic & Disciplinary Policies......................................................15 13. Assessment Grades and Percentages...............................................16

1.

STAFF AND COURSE DELIVERY ARRANGEMENTS

1.1 Teaching Staff Module Leader 2

Lesson Plan Guideline

Name Room and Building Phone Number Email Consultation Hours Module Tutor Name Room and Building Phone Number Email Consultation Hours H.M.Shahzad CS IT Faculty Room Will be provided in class (if necessary)

Will be provided in class (if necessary) Will be decided in class (if necessary)

1.2 Course Delivery Arrangements Course Name and Code: Programming Fundamentals Credit Hours: 4 Lecture Duration: 4 hours per week for the 15 week semester Day: Time: Venue: 2. Course Introduction

This course makes students familiar with the notion of Object Oriented and computer programming. It helps them learning various programming constructs (like variables, conditional structures, loops, functions etc) and discusses object oriented concepts like classes and objects, encapsulation & abstraction and how to achieve them in Code. It is an imperative course in computer science field and it is required to understand the programming logic used behind electronic machines such as computer. It provides a basic foundation to become an expert computer programmer. The purpose of this course is to implement real world situations in the form of computer programs in OOP by understanding the syntax and logics.
3

Lesson Plan Guideline

This course introduces students to general programming concepts, and it can serve as the foundation course for a complete path in computer programming skills. Although the programming concepts introduced in this course apply to most programming languages.
Program: Semester: Pre Requisites: Follow Up: Text Book: BCS/BTC/MIT 2nd Nill Object Oriented Programming OOP: From Problem Analysis to Program Design By D.S. Malik Sessio n: 2010-2014

3. Course Aims Students shall be able to

Understand the different programming paradigms. Understand programming constructs like iteration, decision and functions. Understand the memory management & application execution. Think in terms of classes and objects. Solve basic real world problems by using simple interaction between objects. Save their application data using files (text and binary). To learn the OOP language syntax and techniques. To learn the basic concept of computer programming and programming logics used in developing computer programs. To program computer system, one should implement his/her programming logics by using a programming language such as C++. To understand the OOP development in a real practical environment. To learn the basic techniques of program debugging To learn the concept of testing program to produce error free programs. Familiarize themselves with the introductory concepts of programming. Create simple programs. Create and call methods. They will also work with in-built methods.

Lesson Plan Guideline

Fix programming errors.

4. Course Coverage: Key Topics included in this course are as follows: a) Different Programming Paradigm b) Object Orientation c) Concept of Classes d) Real World Examples e) Structure f) Employee Management System in Structure g) Classes h) Objects i) Function j) Overloading & Overriding k) Inheritance l) Dynamic Memory Allocation in Array m) Multiple Inheritance n) Templates

5. Student Gain

Lesson Plan Guideline

Classification Topics At the end of this module, successful students will be able to demonstrate the knowledge of: Understand the different programming paradigms. Understand the OOP syntax. Understand the control structure to implement program logics Understand different data types and data structures. Learn to use IDE for programming language Learn modular approach to write effective programs. Learn different debugging and testing techniques.

Knowledge and Comprehension

Application and Skills

At the end of this module, the successful students will be able to: Able to construct program organization and implement in modular approach. Implement their programming logics in c++ language by using different control structures. Produce effective and quality programs in c++ according to the concept of object orientation.

Analysis and Synthesis

At the end of this module successful students will be able to: Analyse the real world problem and implement in c++ language. Debug their programs to make them efficient. Able to analyse new problems to write c++ programs. Able to understand the errors and problems in already developed programs.

6. Teaching and Learning Methodology 6.1 Lectures:

Lesson Plan Guideline

Lectures seek to make accessible to students the module and program aims in addition to crucial background and factual knowledge. Interactive
Lectures will introduce the concepts, theories, and application of the subject using relevant examples. The lectures will also be used to discuss the problems of business areas and the relevant research methods. Students will be asked questions, often in the form of short activities and are expected to discuss material from previous weeks. Students would be free to ask any question related to the subject matter during and after lectures.

6.2 Individual Responsibilities

There will be some other exercises that you need to do by hand or on the computer, you are expected to complete these in your own time. Attendance will be monitored every week. If you fail to attend at least 80% of the sessions you will receive an F grade for the module. All three hours per week are equally important. Thus attendance in a particular week will be deemed complete only if you attend for the full three hours. You are expected to turn up for all classes on time and be ready to participate in class. It is not acceptable for you to disturb the class by entering late. If you are unavoidably late, then please wait outside until the lecturer indicates you may come in. You should apologize to the lecturer after the class, and explain the reason for being late. All mobile phones must be turned off before entering the class.

7. Assessment
There would be no unseen exam and assessed coursework bears the 100% credit. All work will be marked on the absolute scale, and the marks will be combined to give an overall percentage mark for the module. This percentage mark will then be converted to a grade on the University Grading Criteria, using the conversion given in Table 1. A combined mark of 50% translates into the pass grade of D. However, in order to pass the module you need not only a combined mark of 50% or better but also a mark of 30% or better in each exam and the coursework. If you fail to get 30% or better in just one component then you will be given a grade F, no matter how well you have done in the other component. 7

Lesson Plan Guideline

Table 1 Percentage Mark 80-100 70-79 60-69 50-59 Below 50 Grade A B C D F

8-ASSIGNMENTS
There are two assignments during the semester, first assignment is assignment in first lecture and will be due in 13th lecture, whereas second assignment is assigned immediately after mid term and will be due in 28th lecture.

8.1- PRE-MID
The Assignment before mid is to form a group of 1-2 students. Students are required to implement the concepts learned up to mid and develop any OOPlanguage program.

8.1.1 Example Assignments

1. 2. Data Sorter : that can be used to arrange any type of data such as number, string, character, etc, in any sequence in an interactive environment Tax Calculator: that can be used to find income tax on a given amount of salary of an employee after applying different income tax rules in an interactive environment..

8.1.2 Guidelines
Students are required to perform assignment as per the following guidelines:a. Pseudo code should be properly prepared before implementation. b. There should be 100 to 150 lines of codes. c. Program should cover the concept of loops and conditions. d. Program should cover the following data structures i. Array ii. String e. Hard copy should contains project description, pseudocode, source code, and sample test data. f. There should be a CD that contains all of the project documentations and source code. g. All documentation should follow APA referencing format. (Contact course instructor in this regard)

Lesson Plan Guideline

Note : Example assignments will be provided on request.

8.2 POST-MID ASSIGNMENT

The Assignment after mid is to form a group of 3-4 students. Students are required to implement the concepts learned up to final term and develop any C language program.

8.2.1 Example Assignments

1. 2. Text Editor : that can be used to make any text file, reopen those files and make all of the text manipulations on it in an interactive graphical environment. Set Calculator : that can be used to apply different set theory functions such as union, intersection, DeMorgans Law, etc,. in an interactive graphical environment .

Note: Student may inquire further in this regard.

8.2.2 Guidelines
Students are required to perform assignment as per the following guidelines:a. Pseudocode should be properly prepared before implementation. b. There should be 400 to 500 lines of codes. c. Program should cover the concept of loops and conditions. d. Modular programming approach should be followed to implement the concept in C language. e. Program should cover the following data structures i. Array ii. String f. g. h. i. There should be a proper use of pointers and file handling. Use of graphics is optional. User manual to operate software Hard copy should contain project description, pseudocode, source code, sample test data, and user manual. j. There should be a CD that contains all of the project documentations, source code, user manual, and presentation slides. k. All documentation should follow APA referencing format. (Contact course instructor in this regard) Note : Example assignments will be provided on request.

Lesson Plan Guideline

9.

ASSESSMENT DETAILS AND POLICIES

9.1 Types and due date of assignment

9.1.1 Assignment 1 Weight Due Date Group Base 10% In 13th Lecture (1-2 person)

9.1.2

Assignment 2 Weight 20% + 10% Due Date In 28th Lecture Presentations In 29th and 30th lectures Group Base (3-4 persons)

9.2 Assessment Items and Evaluation Criteria

9.2.1 Assignment 1 The assignment will be evaluated on the following contents: Program description Pseudocoding Language implementation Testing & debugging Execution 9.2.1.1 Distribution of marks Program description Requirement specifications Basic analysis Pseudocoding Language implementation Control structure use Data structure use Coding style Testing & debugging Execution Error free execution With errors & warning execution 2 marks 1 mark 1 mark 2 marks 3 mark 1 mark 1 mark 1 mark 1 mark 2 mark 1 mark 1 mark

10

Lesson Plan Guideline

9.2.2

Assignment 2

The assignment will be evaluated on the following contents: Program description Pseudocoding Language implementation User manual Testing & debugging Execution 9.2.2.1 Distribution of marks Program description Requirement specifications Basic analysis Pseudocoding Structure chart Module pseudocoding Pseudocoding conventions Language implementation Control structure use Data structure use Coding style File handling Pointer use Modular approach Testing & debugging User manual Content completion Execution Error free execution With errors & warning execution
9.2.3 Presentation

2 marks 1 mark 1 mark 4 marks 1 mark 2 marks 1 mark 7 mark 1 mark 2 mark 1 mark 2 marks 1 mark 2 marks 1 mark 1 mark 1 mark 2 mark 1 mark 1 mark

Each group will present its final assignment in 29th and 30th lecture. The final project presentation will be evaluated on the following criteria: Personality 1 mark Confidence 1 mark Language 1 mark Focus to main idea 1 mark Group coordination 1 mark Answer to questions 2 marks Presentation material 3 marks Slides 2 mark Content completion 1 mark 11

Lesson Plan Guideline

10. Reference Material

10.1 BOOKS
Course Books 1. Programming: From Problem Analysis to Program Design By D.S. Malik

12

Lesson Plan Guideline

11. Lecture Plan

13

Lesson Plan Guideline

Lecture Plan Session

Topics Overview of the course, significanc e of subject , Introductio n to programmi ng paradigm; OOP Language Intro and Overview, OOP language Feature and programmi ng model

Session Objective To introduce the students about different programming paradigm

Week1

Students will get familiar with OOP Programming Language

Week2

Week3

Pointers Dynamic Pointers Structures Functions in Structures (Parameterized Functions; Return values; Function arguments and parameters; Type conversions in parameters) Employee Management System

This session will provide an understanding of the Pointers and its application in OOPand OOP. To understand of the Structure and its application. Develop a Employee Management System in Structure.

Week 4

Week 5

Employee Management System Class Objects Data Hiding

Develop a Employee Management System in Structure. To learn about Classes in OOP and Objects To learn about Data Hiding Concept in OOP

Week 6

14

Lesson Plan Guideline

Function and Classes Week 7 Private ,Public , protected specifier in OOP Mid Term Examinations Overloading Operator Overloading Overloading Binary Operator Overloading Overloading Binary Operator Overriding Week 11 Polymorphism and Virtual Function Templates Week 13 Function Templates Class Templates File Handling Advantages of File Handling File Handling Week 15 Text Files Binary Files To understand function used in Classes To learn about Private, Public and Protected Specifier in OOP.

Week 8

Week 9

To learn the concept of overloading and operator overloading and overloading binary operator. To understand the Overriding concept with Binary Operator To understand the Overriding concept in OOP. To learn about polymorphism and virtual function used in OOP. To understand the concept of Templates in OOP

Week 10

Week 12

Week 14

Final Term Exam

15

Lesson Plan Guideline

12. Academic & Disciplinary Policies

12.1 Late Submission:
According to the University policy an assessment item submitted after the due date, without an approved extension, will be penalized at a rate of 10% per day of the possible maximum mark for the assessment item for each day or part day that the item is late. You can submit your assignment up to 4 days after due date. Late submission subjects to maximum 40% deduction in overall marks. Assessment items submitted more than four days after the due date will be awarded zero marks.

13.2 Absenteeism:
Late coming and shortage in attendance i.e. 3 continual absents from class, ensure that students will be struck off from the relevant subject. 13.3 Scholastic Honesty: Superior University expects each student to do his/her own work. The University has "zero tolerance" for cheating, plagiarism, unauthorized collaboration on assignments and papers, using "notes" during exams, submitting someone else's work as one's own, submitting work previously submitted for another course, or facilitating acts of academic dishonesty by others. The penalties are severe! 13.4 Plagiarism University policy prohibits students plagiarizing, collusion, copying and ghost writing any material under any circumstances. A student plagiarizes if he or she presents the thoughts or works of another as ones own. This definition may include: Using anothers ideas without due acknowledgement; Working with others without permission and presenting the resulting work as though it was completed independently. Aiding another student to plagiarize is also a violation of the plagiarism Policy and may invoke a penalty.

14. Cover Sheets for Assessment:

A Faculty specific Assignment Cover Sheet (available at university bookshop) is to be completed and attached to each assessment item to be submitted.

16

Lesson Plan Guideline

15. Assessment GPA and Percentages:

(80-100%) This is an outstanding standard indicating comprehensive
knowledge and understanding of the relevant materials; demonstration of an outstanding level of academic ability; mastery of skills (as identified in the assessment task); and achievement of all assessment objectives. This is an excellent standard indicating a very high level of knowledge and understanding of the relevant materials; demonstration of a very high level of academic ability; sound development of skills (as identified in the assessment task); and achievement of all assessment objectives. This is a very good standard indicating a high level of knowledge and understanding of the relevant materials; demonstration of a high level of academic ability; reasonable development of skills (as identified in the assessment task); and achievement of all assessment objectives. This is a satisfactory standard indicating an adequate knowledge and understanding of the relevant materials; demonstration of an adequate level of academic ability; satisfactory development of skills (as identified in the assessment task); and achievement of most assessment objectives.

(70-79%)

(60-69%)

(50-59%)

Fail (less than 50%)

This is an unsatisfactory standard indicating an inadequate knowledge and understanding of the relevant materials; insufficient evidence of academic ability; failure to develop skills (as identified in the assessment task); and failure to achieve assessment objectives.

17