PAKISTAN NAVY ENGINEERING COLLEGE, NATIONAL UNIVERSITY OF SCIENCES AND

TECHNOLOGY, KARACHI
PNEC NUST

Student Lab Manual

Object Oriented Programming

CS-212

Name: ____________________________________________________________________

CMS-ID: _______________________ Class: ____________ Section: _____________

Batch: ________________________ Semester: ________________________________

Department: ________________________________________________________________

EE UG Revised Curricula 2018

DEPARTMENT OF ELECTRONICS & POWER ENGINEERING
 Lab Manual Contents

1. Lab Rubrics with Marks Distribution

2. List of Experiments
3. Lab Assessment Record
4. Detailed Experiment Sheets
 Lab Rubrics with Marks Distribution

National University of Sciences & Technology- Pakistan Navy Engineering College

(Group-2): Computer Programming Lab Rubric
Skill Level
Rubrics BT
Rubrics Indicator Needs Work Developing Competent Exemplary
Code Domain
2.0 3.0 4.0 5.0
Experimental R1 P Ability to gather materials, follow All required materials are Most required materials All required materials are Materials are gathered
Methods experimental procedure, control not gathered, procedure is are gathered, procedure gathered, selected materials with clarity and precision,
variables, present data/ evidence inadequately followed, could be better followed, are suitable, procedures are procedure is efficiently
using charts/ tables/graphs to enable inattentive to safety mostly attentive to well followed, and followed, limitations are
comprehension/interpret findings, measures. safety. limitations are considered, analyzed, demonstrates
compare these values in literature, attentive to safety. exemplary safety.
error analysis, identify limitations and
attentive to comply safety procedures.
☐ ☐ ☐ ☐ ☐

Coding R2 P Ability to fulfill coding No name, date, or No name, date, or Includes name, date, and Includes name, date, and
Standards requirements. assignment title included assignment title included assignment title. assignment title.
 Poor use of white space Poor use of white space White space makes program Good use of white space.
(indentation, blank lines). (indentation, blank fairly easy to read. Organized work.
 Disorganized and messy lines). Organized work. Good use of variables (no
 Poor use of variables (many Disorganized and messy Good use of variables (few global variables,
global variables, ambiguous Poor use of variables global variables, unambiguous naming)
naming). (many global variables, unambiguous naming).
ambiguous naming).
☐  ☐  ☐ ☐
☐
 
Documenta- R3 A Ability to follow documentation, No documentation included. Basic documentation Clearly documented Clearly and effectively
tion prepare and produce documentation has been completed including descriptions of all documented including
describing variables, purpose of including descriptions of variables. descriptions of all
functions/control structure and all variables. Specific purpose is noted for variables.
result. Purpose is noted for each function and control Specific purpose is noted
each function. structure. for each function, control
structure, input
requirements, and output
results.

☐ ☐ ☐ ☐
☐

Runtime R4 A Ability to execute error free efficient Does not execute due to Executes without errors. Executes without errors. Executes without errors
Efficiency logical solution in given time. errors. User prompts contain User prompts are excellent user prompts,
User prompts are little information, poor understandable, minimum good use of symbols,
misleading or non-existent. design. use of symbols or spacing in spacing in output.
No testing has been Some testing has been output. Thorough and organized
completed. completed. Thorough testing has been testing has been completed
A difficult and inefficient A logical solution that is completed. and output from test cases
solution. easy to follow but it is Solution is efficient and easy is included.
not the most efficient. to follow (i.e. no confusing Solution is efficient, easy to
tricks). understand, and maintain.
☐ ☐ ☐ ☐ ☐
 List of Experiments
S No Laboratory Topics

Demonstration of Visual Studio 2010 Environment. Use of program editor, compiler, linker and debugger.
1
Sample program run and debug.

2 Identifiers, Variables, Data Types, I/O Statements

3 Operators, Mathematical expressions

4 Control Statements (if & If-else)

5 Control Statements (switch)

6 Loops (for)

7 Loops (while)

8 Loops (do-while)

9 Functions, Passing arguments by value & by Reference

10 Recursion, function overloading, inline functions

11 Arrays, Defining Arrays, Initializing Array Elements

12 Passing arrays to functions, Multi-dimentional Arrays

13 Open ended problem

 Lab Assessment Record
Session: __________________ Lab Venue: _______________________

Departme
Course Title CMS ID Student Name
nt
EE/ME/IME

Marks Obtained Total Teacher

Experiment Marks Initial
S No Date R1 R2 R3 R4
Title/Experiment Number (20)

10
 Lab N0. 01
Task # 1
Objective:

Code:

Output: