Smart Class Thesis

Smart Class Assistant
Supervised by
Mr. Syed Zulqarnain Arif
Developed by
Asim Raza
FA15-BCS-008
DEPARTMENT OF COMPUTER SCIENCE

COMSATS UNIVERSITY ISLAMABAD,
ABBOTTABAD CAMPUS
JULY, 2019
A Thesis Presented to
COMSATS University Islamabad, Abbottabad Campus
In Partial fulfillment
Of the requirements for the degree of
Bachelors of Science
In
Computer Sciences
By
Asim Raza
July 2019
ii
FINAL APPROVAL
This is to certify that we have read the thesis submitted by ______________________. It is

our judgment that this thesis is of sufficient standard to warrant it acceptances by the
COMSATS Institute of Information Technology, Abbottabad for the ____________
1. External Examiner __________________________________

Mr.
2. Internal Examiner ___________________________________

Mr.
Assistant Professor,
Department of Computer Science,
COMSATS University Islamabad,
Abbottabad Campus.
3. Supervisor ___________________________________
Mr. Zulqarnain Arif
Lecturer,
Abbottabad Campus.
4. Head of Department ____________________________

Abbottabad Campus.
iii
DEDICATION
I dedicate this thesis to my Parents, who have provided moral support, motivation and
financial assistance throughout my education. I dedicate this thesis to my teachers who
supported and encouraged me throughout my degree.
Asim Raza
iv
DECLARATION
I Asim Raza hereby declare that I have produced the work presented in this thesis with great
enthusiasm, integrity and honesty under guidance of my supervisor and teachers. I also
declare that I haven’t copied any material from any source except referred to wherever due. I
shall stand by all the consequences in case of any violation of HEC rules, found in this report.
Asim Raza
Signature: -
v
ACKNOWLEDGEMENT
First of all, thanks to Allah Almighty for his illimitable blessings and guidance to
accomplished my goals. To my dear parents, their motivation, support and prayers that they
have rendered to me throughout our studies. I regard it a great honor to express my deep
sense of gratitude to my learned Supervisor Mr. Syed Zulqarnain Arif for his keen interest,
motivation and constant guidance that he has provided in the completion of this thesis.
vi
PROJECT IN BRIEF
Project Title Smart Class Assistant
Organization COMSATS University Islamabad, Abbottabad Campus.
Undertaken by Asim Raza.
Supervised by Mr. Syed Zulqarnain Arif.
Starting Month September 2019.
Ending Month July 2019.
Software Used Python, MSQL
Environment Used Windows 8.1
System Used Intel core i5
vii
PREFACE
This report will present the detail study, design and implementation done on the project
“Moon Rover Robot”. To easily understand the project, we have divided it into seven
chapters.
Chapter One Provides an introduction to the organization, objective of the project,

problem statements and system advantages.
Chapter Two This chapter should present the details of different hardware
components being used in the project and why these components have
been selected. Also show how the hardware will interact with the
software components.
Chapter Three This chapter contains the detailed design of the system like the class
diagram of the system, the Use Case diagram, the System Block
diagram and the Flowchart.
Chapter Four This chapter concerns with the commenting conventions, development
plan and configuration management tool.
Chapter Five This chapter contains traceability matrix and test plan.
Chapter Six This chapter contains the user guide. In which all the detail include that
facilitate the user to view our system functions.
Chapter Seven This chapter includes future enhancement and conclusion.
References Includes the list of books and manuals and other material referenced
during the project.
viii
ABSTRACT
This project based on the Cu-online web portal for students and teacher . Teacher portal is the
Domain of this project .Product act as web extension to help teacher to make and upload
marks sheets effective and efficiently. Teachers as user of cu-online face difficult to single
handily enter the data of each student in the class. Teacher have more than there classes a lot
of data need to be enter and upload required a lot of effort .Our product allow the teacher to
fetch the data from cu-online into xml sheets. Teachers will enter the remain data with their
voice
ix
TABLE OF CONTENTS
Chapter # 1 .......................................................................................................................... 1
Introduction......................................................................................................................... 1
1.1 Introduction .............................................................................................................. 2
1.2 Objective ........................................................................................................................ 2
1.3 Scope .............................................................................................................................. 2
1.4 Feasibility Study ............................................................................................................ 3
1.4.1 Technical Feasibility ....................................................................................................... 3
1.4.2 Operational Feasibility .................................................................................................... 3
1.4.3 Resource Feasibility ........................................................................................................ 3
1.4.4 Financial Feasibility ........................................................................................................ 4
Chapter # 2 .......................................................................................................................... 5
Requirement Analysis ......................................................................................................... 5
2.1 Introduction ................................................................................................................... 6
2.1.1 Definition, Acronyms and Abbreviations ....................................................................... 6
2.2 Overall Description ....................................................................................................... 6
2.2.1 Product Perspective......................................................................................................... 6
2.2.2 Product Functionality ..................................................................................................... 6
2.2.3 User and Characteristics ................................................................................................. 7
2.2.4 Operating Environment .................................................................................................. 7
2.2.5 Design and Implementation Constraints ........................................................................ 7
2.3 Specific Requirements ................................................................................................... 8
2.3.1 External Interface Requirements ................................................................................... 8
2.3.2 Functional Requirements ................................................................................................ 8
2.4 Non-functional Requirements ....................................................................................... 8
2.4.1 Performance Requirements ............................................................................................ 8
2.4.2 Safety and Security Requirements .................................................................................. 8
2.4.3 Software Quality Attributes ............................................................................................ 9
Chapter # 3 ........................................................................................................................ 10
System Design .................................................................................................................... 10
3.1 Introduction ................................................................................................................. 11
3.2 Use case diagram ......................................................................................................... 11
3.3 Class Diagram ............................................................................................................. 12
x
3.4 Package Diagram......................................................................................................... 13
3.5 Flow chart .................................................................................................................... 14
3.6 Deployment Diagram .................................................................................................. 15
3.7 Sequence Diagram ....................................................................................................... 16
3.7.1 Create Account .............................................................................................................. 16
3.7.2 Login .............................................................................................................................. 16
3.7.3 Check Assignments ....................................................................................................... 17
3.7.4 Upload Assignments ...................................................................................................... 17
3.7.5 Check MCQ’s ................................................................................................................ 17
3.7 Fully Dressed Use Cases .............................................................................................. 18
3.7.1 Create Account .............................................................................................................. 18
3.7.2 Login .............................................................................................................................. 19
3.7.3 Fetch Data ..................................................................................................................... 20
3.7.4 Update Mark sheet ........................................................................................................ 21
3.7.5 Update Mark sheet ........................................................................................................ 22
Chapter # 4 ........................................................................................................................ 23
Development and Configuration Management ................................................................ 23
4.1 Introduction ................................................................................................................. 24
4.2 Coding Standards ........................................................................................................ 24
4.2.1 Function Calls ............................................................................................................... 24
4.2.2 Comments ...................................................................................................................... 24
4.2.3 Web................................................................................................................................ 24
4.2.4 Functions ....................................................................................................................... 24
4.2.5 Arrays ............................................................................................................................ 24
4.2.6 If-Else Statement ........................................................................................................... 24
4.1 Development Schedule ................................................................................................ 25
Chapter # 5 ........................................................................................................................ 26
Quality Assurance ............................................................................................................. 26
5.1 Introduction ................................................................................................................. 27
5.2 Test Cases .................................................................................................................... 27
Chapter # 6 ........................................................................................................................ 30
User Manual ...................................................................................................................... 30
6.1 Introduction ................................................................................................................. 31
6.1.1 Login .............................................................................................................................. 31
xi
6.1.2 Marks ............................................................................................................................ 31
6.1.3 Mark sheet ..................................................................................................................... 32
6.1.4 Edit Excel sheet ............................................................................................................. 32
6.1.5 Upload Marks to portal................................................................................................. 33
Chapter # 7 ........................................................................................................................ 34
Conclusion & Future Work .............................................................................................. 34
7.1 Introduction ................................................................................................................. 35
7.2 Future Enhancements ................................................................................................. 35
7.3 Conclusion and Discussion .......................................................................................... 35
xii
List of Tables
Table 1.1 Financial Feasibility ....................................................................................................4
Table 2.1 Definations ..................................................................................................................6
Table 2.2 Acronyms ...................................................................................................................6
Table 2.3 User and Characteristics ..............................................................................................7
Table 3.1 Create Account .......................................................................................................... 18
Table 3.2 Login ......................................................................................................................... 19
Table 3.3 Fetch Data ................................................................................................................. 20
Table 3.4 Update mark sheet ..................................................................................................... 21
Table 3.5 Check MCQ’s ............................................................................................................ 22
Table 5.1 Test case 1 ................................................................................................................. 27
Table 5.2 Test case 2 ................................................................................................................. 28
Table 5.3 Test case 3 ................................................................................................................. 29
xiii
List of Figures
Figure 3.1 Use case .................................................................................................................. 11

Figure 3.2 Class Diagram .......................................................................................................... 12
Figure 3.3 Package Diagram ..................................................................................................... 13
Figure 3.4 Activity Diagram ...................................................................................................... 14
Figure 3.5 Deployment Diagram ............................................................................................... 15
Figure 3.6 Create Account ......................................................................................................... 16
Figure 3.7 Login ....................................................................................................................... 16
Figure 3.8 Check Assignment.................................................................................................... 17
Figure 3.9 Upload Assignment .................................................................................................. 17
Figure 3.10 Check MCQ’s ........................................................................................................ 17
Figure 4.1 Gant Chart ................................................................................................................ 25
Figure 6.1 Login........................................................................................................................ 31
Figure 6.2 Marks ....................................................................................................................... 31
Figure 6.3 Mark sheet ............................................................................................................... 32
Figure 6.4 Edit .......................................................................................................................... 32
Figure 6.5 Upload Mark to portal .............................................................................................. 33
xiv
Chapter # 1
Introduction
1
1.1 Introduction
Purpose of this project is efficient solution for the Teachers. Teachers will be able to
make and upload mark sheet is few minutes. User friendly interface allow the teacher to
upload the mark sheets easily.
This project based on the Cu-online web portal for students and teacher. Teacher portal is
the Domain of this project .Product act as web extension to help teacher to make and upload
marks sheets effective and efficiently. Teachers as user of cu-online face difficult to single
handily enter the data of each student in the class. Teacher have more than there classes a lot
of data need to be enter and upload required a lot of effort .Our product allow the teacher to
fetch the data from cu-online into xml sheets. Teachers will enter the remain data with their
voice.
1.2 Objective
 Fetch the data related to the class and it’s student from the portal of example
registration numbers, old marks.
 Create a new excel sheets and populate the data in it. Create new columns for new
enter like sessional marks etc.
 Capture the voice commands effectively and update the excel sheets accordingly.
 Allow the user to upload the excel sheet thought the system(understudy) interface.
 MCQs can be checked by the system
 Automatic Checked paper marks will be populate into the excel sheets by the system
1.3 Scope
The product scope of the project includes the following.
 System will Fetch the data related to the class and it’s student from the portal of
example registration numbers, old marks.
 System will Create a new Excel sheets and populate the data in it. Create new
columns for new enter like sessional marks etc.
 System will Capture the voice commands effectively and update the excel sheets
accordingly buyer can contact seller using email.
 System will upload the excel sheet thought the system (understudy) interface to the
portal.
Department of Computer Science, COMSATS Islamabad, Abbottabad Campus 2

 System will allow the Teacher to check MCQ’s can be checked by the system Seller
can login.
 System will Checked MCQS marks will be populate into the excel sheets by the
system
 Check the plagiarism locally between assignments
1.4 Feasibility Study

A feasibility report is the result of detailed examination and analysis of proposed idea or
project. It is done before an idea is approved or implemented. In report, multiple aspects of
proposed idea are examined like its potential market, its investment needs, component needs,
marketing needs. It is an overall study of the project that has been carried out and the findings
have been listed in the feasibility report.
 Technical feasibility
 Financial feasibility
 Resources feasibility
 Operational feasibility
1.4.1 Technical Feasibility

This project is technically feasible and we can achieve this through the following
software and hardware involved in this project that are:
 We use different libraries of python to implement.
 SMSAPI library for sms sending.
 Pyaudio for for real-time audio read/write.
 Copyleaks Python SDK for checking the plagirism.
 Pycairo, PIL, PILLOW,SCIPY, SIMPLE ITK for image processing
1.4.2 Operational Feasibility
Operational feasibility refers to the measure of solving problems with the help of a
new proposed system. It helps in taking advantage of the opportunities and fulfills the
requirements as identified during the development of the project. It takes care that the
management and the users support the project.
1.4.3 Resource Feasibility

Our project requires the following hardware and software:

 All the required resources are available locally and online.

 Python 3.7.0
 A Desktop computer/Laptop.
 Internet required
1.4.4 Financial Feasibility

Financial feasibility is the sources, prices of availability and financing of tools and
other components that are required for the project. It is the analysis of the ability to done
project successfully, taking into account technological, economic, and legal, scheduler and
other factors. The table 1.1 shows the required tools and their prices.
Resource Name Price Source
Python IDE(Eclipse with pydev) Free https://marketplace.eclipse.org/content/

pydev-python-ide-eclipse
NLKT https://www.nltk.org/install.html
Sponsors/Funding sources Self
Table 1.1: Financial Feasibility

Chapter # 2
Requirement Analysis

2.1 Introduction
This chapter specifies all the requirements for Class Assistant. These requirements
relate to the functionality, constraints, performance attribute and the system interface.
2.1.1 Definition, Acronyms and Abbreviations

In the table 2.1 definitions are written which we are using in this project.
My SQL Server My SQL Server is used to handle user data base at server
end of the system.
Table 2.1: Definitions
In the table 2.2 acronyms and abbreviations are written which we are using in this
project.
UI User Interface
CSS Cascading Style Sheet
HTML Hyper Text Mark-up Language
PHP Hyper Text Pre-processor
Table 2.2: Acronyms and Abbreviations
2.2 Overall Description

Overall description contains some factors which describe the project.
2.2.1 Product Perspective

“Smart Class Assistant” is product which create easies for the user(Teacher) to check
MCQS and the fetch data for him/her . Create mark sheets with voice commands which are
way more effective and efficient then typing.
2.2.2 Product Functionality

Pak Zameen is capable of doing the following functionalities:
 System will Fetch the data related to the class and it’s student from the portal
of example registration numbers , old marks.
 System will Create a new Excel sheets and populate the data in it. Create new
columns for new enter like sessional marks etc.
 System will Capture the voice commands effectively and update the excel
sheets accordingly.

 System will upload the excel sheet thought the system(understudy) interface to
the portal.
 System will allow the Teacher to check MCQs can be checked by the system
 System will Checked MCQS marks will be populate into the excel sheets by
the system
2.2.3 User and Characteristics
The User of this system will be:
 Teacher will be able to Check MCQs though the System

 Teacher will be able to enter Numeric marks value into the system
 Teacher can fetch the students data with respect to class into the excel Sheet
 Teacher can upload excel sheet though the system.
The Table 2.3 shows following Users are directly or indirectly involved with our
system.
User Characteristics Frequency % Importance

Users Educated(at least should know how 70 – 80 1
to use computers)
Table 2.3 Users and Characteristics

2.2.4 Operating Environment
The operating environment for running of system is shown in below Table 2.4
Requirement Specification
Hardware Platform Computer/Laptops
Operating Systems Windows OS
Table 2.4 Operating Environment
2.2.5 Design and Implementation Constraints

The Design and implementation constraints depend upon the desirable qualities which
may be design goals for system. Some common constraints are given below.
 Communication Constraints
Communication and network error may cause to give access denied to server.
 Database Constraints
My SQL is used for database query handling.

 Language Constraint
We will use Html, CSS, JavaScript, Bootstrap, JQuery and PHP for web
development and Advanced OOP for client-server android application development
2.3 Specific Requirements

Requirements are description of features and functionalities of target system
it convey the expectations of users from the product. Some basic and mandatory requirements
which makes it possible for a system to work accordingly to user need are as follows:
2.3.1 External Interface Requirements

All the external interface requirements are given below
 Hardware Interfaces
o Laptop/Personal Computer
 Software Interfaces
o Windows Operating System
 Communications Interfaces
o We will use xamp to communicate with server from website.
2.3.2 Functional Requirements
The System can perform the following functionalities:
 Web scrapping
 Upload marks
 Get student data
 Add marks
 Add assignment
2.4 Non-functional Requirements

Some requirements perform important role to make product more successful. If they
are not addressed properly, undesirable result can occur which create bad impact on user
satisfaction. So some following non-functional requirement will help us to assure the user
satisfaction.
2.4.1 Performance Requirements

The Smart class Assistant will perform well if the software and hardware
requirements are in accordance with the assumed hardware and software requirements
2.4.2 Safety and Security Requirements
Application isn’t creating any safety hazards for the user because it will not be critical

in operating environment and it will be not harmful to anyone. Passwords will be secured by
not being displayed while typing.
2.4.3 Software Quality Attributes
Based on the standards, these software quality model was divided into eight
quality categories.
 Reliability
o Error free
o Update log regularly
 Availability
This system will perform efficiently and will be available most of the time.
This system will remain in a specified operable and committable state. It will be
operational and will be able to deliver the relevant services.
 Usability
The system will be easy to handle with no expected failure. The GUI interface
of the application will be user friendly.
 Maintainability
The system will be easy to handle with no expected failure. The GUI interface
of the application will be user friendly.
 Portability
This system can easily adopt and adjust itself in the new environment; design
of system is very flexible which makes it possible to adjust in the new environment.

Chapter # 3
System Design

3.1 Introduction
In this chapter we are going to discuss about the system design and the design
documents used in the project.
3.2 Use case diagram

Use case diagrams are usually referred to as behavior diagrams used to describe a set
of actions (use cases) that some system or systems (subject) should or can perform in
collaboration with one or more external users of the system (actors) as shown in the figure
3.1.
Figure 3.1: Use Case Diagram

3.3 Class Diagram

A class diagram is an illustration of the relationships and source code dependencies
among classes in the Unified Modeling Language (UML). In this context, class defines the
methods and variables in an object, which is a specific entity in a program or the unit of code
representing that entity as shown in figure 3.2.
Figure 3.2: Class Diagram

3.4 Package Diagram

Package diagram, a kind of structural diagram, shows the arrangement and
organization of model elements in middle to large scale project. Package diagram can show
both structure and dependencies between sub-systems or modules, showing different views
of a system, for example, as multi-layered (aka multi-tiered) application - multi-layered
application model as shown in figure 3.3.
Figure 3.3: Package Diagram

3.5 Flow chart

A flowchart is a type of diagram that represents an algorithm, workflow or process.
The flow chart shows the steps as boxes of various kinds, and their order by connecting the
boxes with arrows as shown figure 3.4.
Figure 3.4: Flow Chart

3.6 Deployment Diagram

A deployment diagram is a UML diagram type that shows the execution architecture
of a system, including nodes such as hardware or software execution environments, and the
middleware connecting them. Deployment diagrams are typically used to visualize the
physical hardware and software of a system as shown in figure 3.5.
Figure 3.5 Deployment Diagram

3.7 Sequence Diagram

A deployment diagram is a UML diagram type that shows the execution architecture
of a system, including nodes such as hardware or software execution environments, and the
middleware connecting them. Deployment diagrams are typically used to visualize the
physical hardware and software of a system.
The sequence diagrams for this system are as under.
3.7.1 Create Account
The sequence diagram for creating account is shown in figure 3.6.
Figure 3.6 Create account
3.7.2 Login
The sequence diagram for login is shown in figure 3.7.
Figure 3.7 Login

3.7.3 Check Assignments
The sequence diagrams\ for checking assignments is shown in figure 3.8.
Figure 3.8 Check Assignments
3.7.4 Upload Assignments
The sequence diagram for uploading assignment is shown in figure 3.9.
Figure 3.9 Upload Assignments
3.7.5 Check MCQ’s

The sequence diagram for checking MAQ’s is shown in figure 3.10.
Figure 3.10 Upload Assignments

3.7 Fully Dressed Use Cases

The fully dressed use cases of the system are as under
3.7.1 Create Account
Fully dressed use case for creating account is as under in table 3.1.
ID: 1
Function Create Account
Description Teacher must register his account on system
Primary Actor Teacher
Outputs Teacher successfully signs up.
Basic Flow Teacher request to create account

System ask for user details
Teacher entered detail
System ask for confirmation
Teacher confirmed from email

Account created
Alternatives System displays a message that the username/email already exists
Pre-condition Teacher visit the extension
Post-condition Teacher will get registered after they provide the valid information
Effects Database Updated.
Table 3.1 Create Account

3.7.2 Login
Fully dressed use case for creating account is as under in table 3.2.
ID: 2
Function Login
Description The user login to the system
Outputs Teacher successfully signs in.
Basic Flow Teacher request to login.

System provide login form.
Teacher enter username and password.
System check username and password
Teacher successfully logged in
Alternatives System displays a message that the username/password doesn’t match
Pre-condition Teacher must have account.
Post-condition Teacher logged into the system
Table 3.2 Login

3.7.3 Fetch Data

Fully dressed use case for fetching data is as under in table 3.3.
ID: 3
Function Fetch data
Description Teacher select class and send command for fetching data from portl.
Outputs Teacher successfully fetched data.
Basic Flow Teacher request to fetch data

System ask for user details
The system provides the user a dialog box to fetch by class or subject
Teacher entered detail
The system will confirm all the details and fetch the data from portal
accordingly
System generate a xml sheet
Alternatives Invalid class

Invalid values
Pre-condition Teacher logged into portal
Post-condition Data fetched and a xml sheet populate
Table 3.3 FetchData

3.7.4 Update Mark sheet

Fully dressed use case for fetching data is as under in table 3.4.
ID: 4
Function Update
Description Teacher select class then System will recognize the voice of the Teacher
and insert the numeric values into the excel sheet related to the student
Outputs Teacher successfully update mark sheet.
Basic Flow The user requests to insert marks into excel sheet via voice command
The system will ask for the excel file director.
commands with respect to student registration number or Name.
Alternatives Error file or path error Message is displayed

Invalid Student registration Number
Invalid Number command
Pre-condition Teacher logged into portal
Excel mark sheets is ready to use or populated with initial data i.e
registration number of student.
Post-condition Marks updated
Table 3.4 Update mark sheet

3.7.4 Check MCQ’s

Fully dressed use case for checking MCQ’s is as under in table 3.5.
ID: 5
Function Check MCQ’s
Description System will mark MCQ’s by comparing them with answer key.
Outputs Teacher successfully update mark sheet.
Basic Flow The user request to check MCQ’s
The system includes the uploaded MCQ’s and key.
System will compare MCQ’s with answer key
System will maintain MCQ’s record
System will save record in xml file
Alternatives Error file

Path error message displayed
Pre-condition Teacher should be logged in.
MCQs marks are saved in xml sheet
Post-condition MCQ’s marked
Table 3.4 Update mark sheet

Chapter # 4
Development and
Configuration Management

4.1 Introduction
In this chapter we will explain:
 Which tools are used for developing the application?

 Which libraries are used in application
 What is our coding standard and style?
These things are discussed in detail which would be helpful for developers and
stakeholders for understanding the system for future revisions and modifications.
4.2 Coding Standards

Java coding standards, Object oriented approach and professional design patterns are
used.
4.2.1 Function Calls

Functions are called with no white space between function name, opening parenthesis
and first parameter, space between commas in each parameter.
4.2.2 Comments
Following comments types are used
 We use (<! -- -- >)symbol for single line comment

 We use (/**/)symbol for multi-line comment
4.2.3 Web
Web programming language code was written in PHP it has predefined libraries and
built-in functions to facilitate coders, we have used many amongst them.
4.2.4 Functions
Static means this method belongs to the class Main and not to a specific instance of
Main. Which means we can call the method from a different class like that Main.fun(). void
means this method doesn't return a value. Methods can return single value in Java and it has
to be defined in the method declaration.
4.2.5 Arrays
Arrays used are called by the index numbers and after that semicolon is used in case
of Java.
4.2.6 If-Else Statement
An if statement can be followed by an optional else statement, which executes when
the Boolean expression is false.

4.1 Development Schedule

The development schedule of the whole tenure is shown in figure 4.1.
Figure 4.1 Gantt Chart

Chapter # 5
Quality Assurance

5.1 Introduction
Our most significant motif of testing is to check whether our robot is working as per
desired standards or not. Testing is the critical phase in development phase in which we sort
out errors and bugs in application.
5.2 Test Cases

Test case is a text, that takes trial data, requirements, and predictable outcomes
established for a specific trial state to validate agreement beside of an exact condition. Trial
Item acts as the initial topic aimed at the trial implementation, and spread over a secure input
values, the Robot has a complete result. In test cases include get commands, show result.
Test Case No 1 Login

In this test case user must logged in as in Table 5.3.
Test case TC01
Test Case Version: Test Case Version:
Version 1.0 Version 1.0
Functionality Functionality
User Teacher
Normal Flow Expected Results Actual Results
User name User must logged in User logged in.

L001
Password
1234
Alternative Flow Expected Results Actual Results(login/not)
User name User should not logged Incorrect password for this user
in and error message
L001
shown
Password
12345
Date 17/07/2019

Tester Name Asim Raza
Verified By Asad Zeb
Table 5.1: Login
Test Case No 2 Login as FYP member

In this test case user directly be on FYP page as in Table 5.2.
Test case TC02
User Actor
Flow Expected Results Actual Results
Username Main page for the FYP Pass

Committee member is
Default
loaded with the FYP
Password Committee navigation bar
Default
Date 17/07/2019
Table 5.2: Login as FYP member

Test Case No 3 Check MCQ’s

In this test case we check whether MCQ’s checking is right or not as shown in Table
5.5.
Test case TC03
User Actor
Normal Flow Expected Results Actual Results
Upload MCQ’s to System compare with Pass

check answer key and give correct
result
Alternative Flow Expected Results Actual Results
Upload some MCQ’s System should mark these Pass

with double answer as false
or cutting
Date 17/07/2019
Table 5.3: MCQ’s checking

Chapter # 6
User Manual

6.1 Introduction
A user guide, also commonly known as a technical communication document, is

intended to give assistance to people using a particular system. It is usually written by
a technical writer, although user guides are written by programmers, product or project
managers, or other technical staff, particularly in smaller companies. The user guide of the
system is as under.
6.1.1 Login
The user can login to system by entering username and password in given fields as
shown in Figure 6.1.
Figure 6.1: Login
6.1.2 Marks
User can search/upload marks by following figure 6.2.
Figure 6.2: Marks

6.1.3 Mark sheet

Teacher can edit marks of quiz in following mark sheet as shown in figure 6.3.
Figure 6.3: Mark sheet

6.1.4 Edit Excel sheet
User can edit by following figure 6.4
Figure 6.4 Edit

6.1.4 Upload Marks to portal

User can upload marks on portal by following figure 6.5.
Figure 6.5 Upload Marks

Chapter # 7
Conclusion & Future Work

7.1 Introduction
This project based on the Cu-online web portal for students and teacher . Teacher
portal is the Domain of this project .Product act as web extension to help teacher to make and
upload marks sheets effective and efficiently. Teachers as teacher of cu-online face difficult
to single handily enter the data of each student in the class. Teacher have more than there
classes a lot of data need to be enter and upload required a lot of effort .Our product allow the
teacher to fetch the data from cu-online into xlm sheets. Teachers will enter the remain data
with their voice .
7.2 Future Enhancements

In future we want to make a lot of more new ideas in this to ease for teacher and
students both to get rid of their manual works and will try to practically implement this
system in educational institutes.
7.3 Conclusion and Discussion

This project based on the Cu-online web portal for students and teacher .
Teacher portal is the Domain of this project .Product act as web extension to help teacher to
make and upload marks sheets effective and efficiently. Teachers as teacher of cu-online
face difficult to single handily enter the data of each student in the class. Teacher have more
than there classes a lot of data need to be enter and upload required a lot of effort .Our
product allow the teacher to fetch the data from cu-online into xlm sheets. Teachers will
enter the remain data with there voice .
The objective of this project is Fetch the data related to the class and it’s student from
the portal of example registration numbers , old marks, Create a new excel sheets and
populate the data in it. Create new columns for new enter like sessional marks etc, Capture
the voice commands effectively and update the excel sheets accordingly.Allow the teacher to
upload the excel sheet thought the system(understudy) interface.MCQs can be checked by the
system Automatic Checked paper marks will be populate into the excel sheets by the system.

References
[1]
[2]
[3]
[4]

Smart Class Thesis

Uploaded by

Copyright:

Available Formats

You might also like

Smart Class Thesis

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Smart Class Thesis

Uploaded by

Copyright:

Available Formats

Smart Class Assistant

DEPARTMENT OF COMPUTER SCIENCE

COMSATS University Islamabad, Abbottabad Campus

Of the requirements for the degree of

This is to certify that we have read the thesis submitted by ______________________. It is

1. External Examiner __________________________________

2. Internal Examiner ___________________________________

4. Head of Department ____________________________

Department of Computer Science,

financial assistance throughout my education. I dedicate this thesis to my teachers who

supported and encouraged me throughout my degree.

Project Title Smart Class Assistant

Organization COMSATS University Islamabad, Abbottabad Campus.

Undertaken by Asim Raza.

Supervised by Mr. Syed Zulqarnain Arif.

Starting Month September 2019.

Ending Month July 2019.

Software Used Python, MSQL

Environment Used Windows 8.1

System Used Intel core i5

Chapter One Provides an introduction to the organization, objective of the project,

Chapter Seven This chapter includes future enhancement and conclusion.

Figure 3.1 Use case .................................................................................................................. 11

Department of Computer Science, COMSATS Islamabad, Abbottabad Campus 2

1.4 Feasibility Study

1.4.1 Technical Feasibility

1.4.3 Resource Feasibility

Department of Computer Science, COMSATS Islamabad, Abbottabad Campus 3

 All the required resources are available locally and online.

1.4.4 Financial Feasibility

Resource Name Price Source

Python IDE(Eclipse with pydev) Free https://marketplace.eclipse.org/content/

Sponsors/Funding sources Self

Table 1.1: Financial Feasibility

Department of Computer Science, COMSATS Islamabad, Abbottabad Campus 4

Department of Computer Science, COMSATS Islamabad, Abbottabad Campus 5

2.1.1 Definition, Acronyms and Abbreviations

Table 2.1: Definitions

Table 2.2: Acronyms and Abbreviations

2.2 Overall Description

2.2.1 Product Perspective

2.2.2 Product Functionality

Department of Computer Science, COMSATS Islamabad, Abbottabad Campus 6

 Teacher will be able to Check MCQs though the System

User Characteristics Frequency % Importance

Table 2.3 Users and Characteristics

Table 2.4 Operating Environment

2.2.5 Design and Implementation Constraints

Department of Computer Science, COMSATS Islamabad, Abbottabad Campus 7

2.3 Specific Requirements

2.3.1 External Interface Requirements

2.4 Non-functional Requirements

2.4.1 Performance Requirements

2.4.2 Safety and Security Requirements

Department of Computer Science, COMSATS Islamabad, Abbottabad Campus 8

Department of Computer Science, COMSATS Islamabad, Abbottabad Campus 9

Department of Computer Science, COMSATS Islamabad, Abbottabad Campus 10

3.2 Use case diagram