A

Project Report
On
STUDENT GRADING SYSTEM
Submitted
In
Partial Fulfillment of the Requirements for the Award of the Degree of
Master of Computer Applications
IVthSem
Session: 2021-2022

Submitted by
Arman Gogul
Roll No. 42328

Under the Guidance of Under the Co-Guidance of

Mr. Vivek Dixit Mr. Pramod singh
Director Assistant Professor
Brain stroming solution SoS in Computer Application
Beside sitlamata mandir SMKV, Bastar(C.G.)
Santosh nagar, Raipur (C.G)

Submitted to
SCHOOL OF STUDIES IN COMPUTER APPLICATION
SHAHEED MAHENDRA KARMA VISHWAVIDYALAYA, BASTAR
JAGDALPUR, CHHATTISGARH, INDIA

Website - www.bvvjdp.ac.in
 DECLARATION BY CANDIDATE

This is to certify that the project report entitled “Student Grading System”, is
submitted by Arman Gogul, Roll No 42328 Student of Master of Computer Applications IVTh
Semester in the partial fulfillment for the award of the degree of Master of Computer
Applicationsin SoS in Computer Applicatoion at Shaheed Mahendra Karma
Vishwavidyalaya, Bastar, Jagdalpur (C.G.) comprises the original work carried out by me.

Name : ArmanGogul
Class : MCA IVth Sem.
Roll no. 42328
 CERTIFICATE OF APPROVAL

This is to certify that the project work entitled “Student Grading System” submitted
by Arman Gogul, Roll No 42328 Student of MCA IVTHSemesterin partial fulfillment of the
requirements for the award of the Post Graduation of SoS in Computer Application, session
2021-22 at Shaheed Mahendra Karma Vishwavidyalaya, Bastar, Jagdalpur is a record of the
student’s own work. This work has not been submitted to any other University or institute for
the award of any degree or diploma to the best of my knowledge.

(Signature of Project Guide)

Mr. Pramod Singh
Assistant Professor
SoS in Computer Application
SMKV, Bastar (C.G.)
(Signature of HOD)
Dr. Vinod kumar soni
Assistant Professor & Head
SoS in computer Application
SMKV, Bastar (C.G)

(Signature of examiner)
 ACKNOWLEDGEMENT

The austerity and satisfaction that one gets on completing a project cannot be fulfilled
without mentioning the people who made it possible, with gratitude, we are very much
thankful to the Almighty God who helped us all the way throughout the project and who has
molded us into what we are today.

We are privileged to express our sincere gratitude to honorable Shaheed Mahendra

Karma Vishwavidyalaya, Bastar, Jagdalpur, for all encouragement he gave us. We express
our sincere thanks to extreme gratitude to Dr. Vinod Kumar Soni,(HOD) of Computer
Application for all his valuable suggestions and guidance throughout our project.

We wish to express our hearty gratitude to our onternal project guide, Mr pramod
singh, Assistant Professor for his valuable suggestions and guidance throughout the tenure of
our project. We extend our sincere thanks to all the college staff members who helped us to
complete this project successfully.

Finally, we express our sincere thanks to our entire friends and all the other people who
had imparted their knowledge and expertise upon us.

Arman Gogul
MCA IVth Sem.
 TABLE OF CONTENTS

TOPIC PAGE NO.

1. INTRODUCTION..........................................................................................................01-05

1.1 ABOUT STUDENT GRADING SYSTEM........................................................................02

1.2 ADMIN PANEL.............................................................................................................02-03

1.3 COURSE MANAGEMENT................................................................................................03

1.4 GRADING MANAGEMENT........................................................................................03-04

1.5 STUDENT RESULT MANAGEMENT.............................................................................04

1.6 THIS PROJECT FOLLOWING MODULES......................................................................04

1.7 OBJECTIVE OF STUDENT GRADING SYSTEM...........................................................05

2. SYSTEM REQUIREMENTS AND ANALYSIS.........................................................06-09

2.1 HARDWARE AND SOFTWARE REQUIREMENT.....................................................07

2.1.1 HARDWARE ...............................................................................................................07

2.1.2 SOFTWARE..................................................................................................................07

2.2 APACHE..........................................................................................................................07

2.3 PHP..............................................................................................................................07-08

2.4 MYSQL............................................................................................................................08

2.5 PROBLEM STATEMENT...............................................................................................08

2.6 OBJECTIVE OF THE PROJECT ...................................................................................08

2.7 NON FUNCTIONAL REQUIREMENT..........................................................................08

2.8 FUNCTIONAL REQUIREMENT..............................................................................08-09

3. SYSTEM DESIGN AND SPECIFICATION...........................................................10-21

3.1 SPIRAL MODEL........................................................................................................11-12

3.2 DESIGN INTRODUCTION.......................................................................................12-13

3.3. DATABASE....................................................................................................................13

3.4 APPLICATION DESIGN.................................................................................................13

3.4.1 ADMINISTRATOR......................................................................................................13

3.4.2 STUDENTS...................................................................................................................13

3.5 DATA FLOW DIAGRAM..............................................................................................14

3.5.1 LEVELS IN DATA FLOW DIAGRAM.................................................................14-17

3.5.2 ER DIAGRAM..............................................................................................................18

3.6 MY SQL DATA TABLE...........................................................................................19-21

3.6.1 ADMIN TABLE............................................................................................................19

3.6.2 TABLE CGPA RESULT ..............................................................................................19

3.6.3 COURSE TABLE ........................................................................................................19

3.6.4 DEPARTMENT TABLE .............................................................................................19

3.6.5 FACULTY TABLE .....................................................................................................20

3.6.6 FINAL RESULT TABLE ............................................................................................20

3.6.7 LEVEL TABLE............................................................................................................20

3.6.8 RESULT TABLE .........................................................................................................20

3.6.9 SEMESTER TABLE ..................................................................................................20

3.6.10 SESSION TABLE ......................................................................................................20

3.6.11 STAFF TABLE ...........................................................................................................21

3.6.12 STUDENT TABLE ....................................................................................................21

4. IMPLEMENTATION.................................................................................................22-24

4.1 IMPLEMENTATION.......................................................................................................23

4.1.1 MODULE DETAILS.....................................................................................................23

4.2 LOGIN MODULES..........................................................................................................23

4.2.1 ADMINISTRATOR MODULE....................................................................................23

4.2.2 STUDENT MODULE ..................................................................................................23

4.3.3 COURSE MODULE ....................................................................................................23

5.3.4 GRADING MODULE..............................................................................................23-24

5. SCREENSHOT............................................................................................................25-31

1 HOME PAGE......................................................................................................................26

2 ADMINISTRATOR LOGIN...............................................................................................26

3 STUDENT LOGIN ............................................................................................................27

4 STUDENT DASHBOARD................................................................................................27

5 DASHBOARD ...................................................................................................................28

6 ADD NEW SESSION........................................................................................................28

7 ADD FACULTY................................................................................................................29

8 ADD DEPARTMENT.........................................................................................................29

9 ADD STUDENT ................................................................................................................30

10 ADD COURSES................................................................................................................30

12 IEW RESULTS.................................................................................................................31

6. UPDATE PROFILE ........................................................................................................31

6. TESTING.....................................................................................................................32-35

6.1. TESTABILITY...............................................................................................................33

6.2. TYPES OF TESTING...............................................................................................33-34

6.2.1 BETA TESTING...........................................................................................................34

6.2.2 TYPES OF BETA TESTING................................................................................34-35

6.2.3 DISADVANTAGE OF BETA TESTING..................................................................35

6.2.4ADVANTAGE OF BETA TESTING............................................................................35

7. CONCLUSION............................................................................................................36-38
INTRODUCTION

1
 INTRODUCTION

In this century, technology has drastically improved and computer science plays an
important role in the development of technology. Due to the increased career prospects in the
computer science field and interests among the hobbyist, there has been a tremendous increase
in the number of computer science courses offered at the universities and in the enrollment of
students in the computer science department. Programming is one of the most important parts
of Programming is one of the most important parts of learning computer science. Large
numbers of courses offered at the universities teach programming languages, technologies, and
other principles. Professors provide programming assignments to the students to give them
experience and knowledge about programming languages.

A fully functional project based on Student Grading System Project which uses php
with MySQL Database. Following PHP project contains all the essential features which can
be in use by the second-year IT students for their college projects. It has a number of features
that will allow users to manage the results of the students with grading criteria. This web
application’s concept is all clear. It’s the same as real-life scenarios and well-implemented on
it. To download free Student Grading System Project in PHP MySQL .

1.1. ABOUT STUDENT GRADING SYSTEM

In particular, this Student Grading System Project in PHP focuses mainly on managing
student-related records. To be more precise, the system helps to keep track of students and
track results with respect to their chosen level. Also, the system displays all the available
faculty and departments. In addition, the system allows setting up courses
too(codeastro.com).Evidently, this project contains an admin panel with a student panel. In an
overview of this web application, the student has to log into the system using the credentials
provided by the administrator. The students can view their enrolled list of courses with their
respective faculty, department, and semester. Additionally, the students can view their personal
semester results. In fact, the result section displays the overall grade with points, total units,
and scores obtained. With it, the system also allows printing/downloading the result. Besides,
the students can view and update their profiles.

1.2. ADMIN PANEL

2
 An administrator has full control over the system. He/she can manage students,
faculties, departments, and so on. Here, each and every section has its own respective details
such as name, and other important details. Here, an admin can add students’ records directly by
filling up required forms. During the customer registration, an admin has to provide details
such as name, level, faculty, department, session, and matric number. But before any of these,
the admin first has to set up a number of fields for further process. It includes
sessions(codeastro.com), faculty, and department. For the management of these mentioned
terms, the user has to provide names and other important details. In fact, faculties and
departments are linked to each other and the department section depends upon the selected
faculty. Similarly, the student registration form also includes a faculty field that only returns
department names depending upon the selected faculty.

1.3. COURSE MANAGEMENT

Moreover, an admin has to set up and manage all the courses(codeastro.com) for the
students. In order to manage this section, an admin has to provide the course title with code,
unit, level, semester, and faculty. Here, the system does list a number of courses for each
mentioned semester. This means the user can store a number of courses in different semesters.
In fact, the whole point of result calculation falls under this rule of the system. With it, the
course unit helps to play a vital role in calculating total course units during the management of
student results. As mentioned earlier, the faculty and department fields are interconnected to
each other. As a result, this particular thing helps to differentiate students based on their studies
and course. Either way, all the students enrolled under a particular faculty department contain
the course set under the same faculty department.

1.4. GRADING MANAGEMENT

On Grading Management On one hand, the system allows the administrator to request
for computing the student’s GPA. For this, the admin has to filter the student manually by
providing level, session, faculty, and department. And the system returns search results based
on the user’s request which the admin can select semester-wise. Here, the semester field
depends upon the number of semester details provided by the admin during the system
management.

While proceeding toward the GPA section(codeastro.com) for computing the

semester’s results, the admin has to provide the total scores obtained under each course. At

3
last, the user can compute a result. The same procedure goes on and on depending upon the
semesters. Meanwhile, the system gets ready with the overall score of the student with GPA,
class of diploma, total unit, and more. With it, now the administrator can proceed to compute
the student’s CGPA.

1.5. STUDENT RESULT MANAGEMENT

Grading Criteria On the other hand, the user can view overall results and grading
criteria. Once the system computes a student’s CGPA, then the admin can request his/her
results. The student filtration process is the same as mentioned earlier. Here, the user can view
each(codeastro.com) student’s semester-wise results as well as final results. In terms of
semester-wise results, the system displays details such as the name of the course with units,
scores obtained, grades, GPA, class of diploma, and more. Also, the user can print/download
the results in PDF format. Regarding final results, the system displays the name of the student
with his/her matric number, faculty, department, CGPA, and a class of diploma. In fact, all
the results are properly calculated and highlighted under respective classes such as distinction,
upper class, and so on. Besides, the admin can view grading criteria and update user profiles.

In addition to it, the students can also view their respective results once after it gets
managed by the administrator. Also, all the important overall records can be viewed easily
from the admin dashboard. It helps to highlight the total number of failed and passed students
and more. Last but not least, a clean and simple dashboard is presented with various color
combinations for a greater user experience while using this Online Student Grading
Management System Project in PHP MySQL. For its UI elements, a free open-source CSS
framework; Bootstrap is on board with some Vanilla CSS too. Presenting a new Student
Grading System Project in PHP MySQL which includes an admin panel with a student panel.
That too contains all the essential features to follow up and is a knowledgeable resource for
learning purposes.

1.6. THIS PROJECT FOLLOWING MODULES

• Admin panel
• Student panel
• Manage Current Session
• Set up Faculty, Departments
• Student Management
• Course Management
4
 • Compute GPA
• Compute CGPA
• Manage results semester-wise
• View Student’s Result
• Print/Download Student’s Result (PDF)
• View/Update User Profiles
• Grading Criteria

1.7. OBJECTIVE OF STUDENT GRADING SYSTEM

• Communicate achievement status to student, parents and others.

• Provide information and feedback that students can use for self-evalution and growth.
• Encourage student growth mindset and progress in learning.
• Help identify students for available educational opportunities (courses or programs).
• Evaluate the effectiveness of curricular, instructional and assessment practices.
• Identify how well a student meets the prioritized standards in a grade level or course.
• Provide an official record of performance.
• Accurately reflect student achievement as related to academic standards and college and
career readness standards & be consistent with external assessments.

5
 SYSTEM
REQUIREMENTS
AND ANALYSIS

6
 SYSTEM REQUIREMENTS AND ANALYSIS

2.1. HARDWARE & SOFTWARE REQUIREMENT

2.1.1. HARDWARE

Processor Pentium-II or higher

Processor Speed 533 MHZ
Hard Disk Space 20 GB (min.)
Ram Memory 32 MB (64 MB recommended)

2.1.2. SOFTWARE

Operating System Windows 95/98/NT/2000 /10/7/8

Database Server MySql /XAMP/WAMP
Front end PHP
Text Editor Notepad++, Dream viewer

2.2. APACHE

The Apache HTTP Server Project is an effort to develop and maintain an open-source
HTTP server for modern operating systems including UNIX and Windows. The goal of this
project is to provide a secure, efficient and extensible server that provides HTTP services in
sync with the current HTTP standards.

The Apache HTTP Server ("https") was launched in 1995 and it has been the most popular web
server on the Internet since April 1996. It has celebrated its 20th birthday as a project in
February 2015.

2.3. PHP

 PHP stands for PHP: Hypertext Preprocessor.

 PHP is a server-side scripting language, like ASP.
 PHP scripts are executed on the server.
 PHP supports many databases (MYSQL, Informix, Oracle, Sybase, Solid, Generic
ODBC, etc.).
7
 PHP is an open source software.
 PHP is free to download and use.

2.4 MYSQL

 MYSQL is a database server

 MYSQL is ideal for both small and large applications
 MYSQL supports standard SQL
 MYSQL compiles on a number of platforms
 MYSQL is free to download and use
 How to access MySQL: http://localhost/phpmyadmin

2.5. PROBLEM STATEMENT

Programming assignments are currently uploaded to a server by the students. The

professor has to login to the server, manually compile and execute the programming files
submitted by the students, and then assign a grade to the student. The grade that is assigned to
the student is usually stored in an Excel worksheet. There is no advanced consolidated system
which can manage all of this features and maintain the records.

2.6. OBJECTIVE OF THE PROJECT

The objective of the Online Grading System, is to provide a consolidated web system
which allows professors to a create course, post assignments, assign deadlines for assignments,
and grade the assignments submitted by the student. The Online Grading System also allows
the student to register for courses, view assignments submitted by the Professor, submit
assignments, and check grades.

2.7. NON FUNCTIONAL REQUIREMENTS

1. The Project should be developed using J2EE technologies.

2. The project should support Linux Operating System.

3. Database included should be MySQL database.

4. Assignment projects submitted by students can be C, C++ and Java files.

5. Assignment description files posted by Professors and/or Students should be created usin
Rich Text Format Editor.
2.8. FUNCTIONAL REQUIREMENTS

8
1. Only Administrator can add professors and start new semester.

2. Professors can add and delete students to the online grading system.

3. Professors can add and delete courses to the online grading system.

4. Professors can post assignments, compile, execute, and grade the programming assignments
submitted by the students.

5. Students can enroll courses and drop courses.

6. Students can view assignments assigned by the professors.

7. Students can submit programming projects.

9
SYSTEM DESIGN
AND
SPECIFICATION

10
 SYSTEM DESIGN AND SPECIFICATION

3.1. SPIRAL MODEL

As originally envisioned, the iterations were typically 6 months to 2 years long. Each
phase starts with a design goal and ends with a client reviewing the progress thus far.Analysis
and engineering efforts are applied at each phase of the project, with an eye toward the end
goal of the project.

The steps for Spiral Model can be generalized as follows:

The new system requirements are defined in as much details as possible. This usually
involves interviewing a number of users representing all the external or internal users and other
aspects of the existing system.

1. A preliminary design is created for the new system.

2. A first prototype of the new system is constructed from the preliminary design. This is
usually a scaled-down system, and represents an approximation of the characteristics of
the final product.
3. Constructing and testing the second prototype.
4. At the customer option, the entire project can be aborted if the risk is deemed too
great.Risk factors might involve development cost overruns, operating-cost
miscalculation, or any other factor that could, in the customer’s judgment, result in a
lessthan-satisfactory final product.
5. The existing prototype is evaluated in the same manner as was the previous prototype, and
if necessary, another prototype is developed from it according to the fourfold procedure
outlined above.
6. The preceding steps are iterated until the customer is satisfied that the refined prototype
represents the final product desired.
7. The final system is constructed, based on the refined prototype.
8. The final system is thoroughly evaluated and tested. Routine maintenance is carried on a
continuing basis to prevent large scale failures and to minimize down time.

11
 Fig1: Spiral Model

ADVANTAGES

1. Technique (i.e. document, feedback etc.) become more realistic as work progresses,
because important issues discover earlier.
2. It is more able to cope with the changes that are software development generally entails.
3. Software engineers can get their hands in and start working on the core of a project earlier.

3.2. DESIGN INTRODUCTION

Design is the first step in the development phase for any techniques and principles for
the purpose of defining a device, a process or system in sufficient detail to permit its physical
realization.

12
 Once the software requirements have been analyzed and specified the software design
involves three technical activities - design, coding, implementation and testing that are
required to build and verify the software.

The design activities are of main importance in this phase, because in this activity,
decisions ultimately affecting the success of the software implementation and its ease of
maintenance are made. These decisions have the final bearing upon reliability and
maintainability of the system. Design is the only way to accurately translate the customer’s
requirements into finished software or a system.

Design is the place where quality is fostered in development. Software design is a

process through which requirements are translated into a representation of software. Software
design is conducted in two steps. Preliminary design is concerned with the transformation of
requirements into data.

3.3. DATABASE

The database is the third and final layer of a web application. The database is used to
store and retrieve the user information when necessary. In the Online Grading System,
MySQL data is used to store and retrieve the user information.

3.4. APPLICATION DESIGN

The Online Grading System application consists of three types of users. They are
Administrator, Professors, and Students. Detailed user privileges are as follows:

3.4.1. ADMINISTRATOR

1. Administrator has the highest privilege.

2. Administrator can add professors.
3. Administrator can add a semester at the start of a university academic semester.

3.4.2. STUDENTS

1. Students can register in the system.

2. Students can enroll for a course or drop a course.
3. Students can view the assignments posted by professors for enrolled course

13
3.5. DATA FLOW DIAGRAMS

A data flow diagram is graphical tool used to describe and analyze movement of
data through a system. These are the central tool and the basis from which the other
components are developed. The transformation of data from input to output, through
processed, may be described logically and independently of physical components
associated with the system. These are known as the logical data flow diagrams.

The physical data flow diagrams show the actual implements and movement of
data between people, departments and workstations. A full description of a system
actually consists of a set of data flow diagrams. Using two familiar notations Yourdon,
Gane and Sarson notation develops the

data flow diagrams. Each component in a DFD is labeled with a descriptive name.
Process is further identified with a number that will be used for identification purpose.
The development of DFD’S is done in several levels. Each process in lower level
diagrams can be broken down into a more detailed DFD in the next level. The lop-level
diagram is often called context diagram. It consists a single process bit, which plays vital role
in studying the current system. The process in the context level diagram is exploded into other
process at the first level DFD.

The idea behind the explosion of a process into more process is that understanding at
one level of detail is exploded into greater detail at the next level. This is done until further
explosion is necessary and an adequate amount of detail is described for analyst to understand
the process.

Larry Constantine first developed the DFD as a way of expressing system requirements
in a graphical from, this lead to the modular design.

A DFD is also known as a “bubble Chart” has the purpose of clarifying system
requirements and identifying major transformations that will become programs in system
design. So it is the starting point of the design to the lowest level of detail. A DFD consists of
a series of bubbles joined by data flows in the system.

3.5.1. LEVELS IN DATA FLOW DIAGRAM

14
0 –level DFD

it is also known as a context diagram. It is designed to be an abstraction view,

Fig2: 0 level DFD

1– level DFD

1 level DFD , the context diagram is decomposed into multiple bubbles/processes.

In this level, we highlight the main function of the system and breakdown the high level
process of 0- level DFD into subprocesses.

15
 Fig3: 1-level DFD

2– level DFD

Level 2 DFD is also the highest abstraction of the data flow diagram. This level also broadens
the idea from the DFD level 1. It includes the sub-processes from level 1 as well as the
data that flows.

16
Fig4: 2-level DFD

17
 3.5.2. ER DIAGRAM

username
Login id
password
dd

staff id Login Student id

dd
1 Matric no.
1 N
administrator Student
has

password
password
N
permission
Per id
d
1 Permodule
pername
dd

1
manage
name
N Exm.stu.id
N N
level Mrk. no.
marks
examination
students Mrk.desc
Exm.id
1
Mrk.stu_id
sesson departmentt Exm.desc
Mrk.type
Exm.name
has
Exm. type
N
results
Matric no no.
Result desc
Result type
Result id

Fig5: student grading system

18
19
3.6. MY SQL DATA TABLES
TABLE 1: ADMIN

TABLE 2: CGPARESULT

TABLE 3: COURSE

TABLE 4: DEPARTMENT

TABLE 5:FACULTY
20
TABLE 6: FINAL RESULT

TABLE 7: LEVEL

TABLE 8: RESULT

TABLE 9: SEMESTER

TABLE 10: SESSION

TABLE 11: STAFF

21
TABLE 12: STUDENT

22
 IMPLEMENTATION

IMPLEMENTATION

4.1. IMPLEMENTATION

23
 The Student grading system in used in the following modules that can be
implemented.
4.1.1. MODULES DETAILS

The Implemented modules in given below:

1. .Administration /Login module
2. Student Modules
3. Course Module
4. Grading module

4.2. LOGIN MODULES

Login modules is implemented in the online Student grading system to

only allowed a register person. we have to use this module in security purpose
related on the detail.
4.2.1. ADMINISTRATION MODULES

The Student grading system in Administration modules is used to

collection the admin personal information. It has to collect the staff id,
name, phone number also.
4.2.2. STUDENT MODULES

Student grading system Student modules is used to collection the

Student personal information. It has to collect the student id, name, phone
number also.

4.2.3. COURSE MODULE

an admin has to set up and manage all the courses(codeastro.com)

for the students. In order to manage this section, an admin has to provide
the course title with code, unit, level, semester, and faculty
4.2.4 GRADING MODULE

On Grading module On one hand, the system allows the

administrator to request for computing the student’s GPA. For this, the

24
admin has to filter the student manually by providing level, session,
faculty, and department.

25
SCREENSHOT

5. SCREENSHOT

26
 HOME PAGE

Fig6: Home form of student grading system

 ADMINISTRATOR LOGIN

Fig7.: Administrator login form of student grading

system

 STUDENT LOGIN

27
 Fig8: student login form of student grading
system
 STUDENT DASHBOARD

Fig9: student dashboard form of student grading system

 DASHBOARD

28
 Fig10: dashboard form of student grading
system

 ADD NEW SESSION

Fig11: add new session form of student grading system

 ADD FACULTY

29
 Fig12: add faculty form of student grading system

 ADD DEPARTMENT

Fig13:add department form of student grading system

 ADD STUDENT

30
 Fig14: add student form of student grading system

 ADD COURSES:

Fig15: add course form of student grading system

 VIEW RESULTS:

31
 Fig16: view results form of student grading system

 UPDATE PROFILE:

Fig17: update profile form of student grading system

32
TESTING

TESTING

33
 Testing is the critical element of any software quality assurance and represents the
ultimate review of specification, design and code generation.

Software testing has a dual function; it is used to establish the presence of defects in
program and it is used to help judge whether or not the program is usable in practice. Thus
software testing is used for validation and verification, which ensure that software conforms to
its specification and meets the need of the software customer.

Developer resorted Alpha testing, which usually comes in after the basic design of the
program has been completed. The project scientist will look over the program and give
suggestions and ideas to improve or to correct the design. They also report and give after a
program has been created.

6.1. TESTABILITY

Software Testability is simply how easily a computer program can be tasted. The check
list that follows provides a set of characteristics that lead to testable software.
• Operability
• Observables
• Controllability
• Decomposability
• Simplicity
• Stability
• Understandability

6.1.1. FOLLOWING ARE THE ATTRIBUTES OF THE GOOD TEST

• A good test has a high probability of finding an error.

• A good test is not redundant.
• A good test should be “Best of Breed”.
• A good test would be neither too simple nor too compile

6.2.TYPES OF TESTING
• Defect testing
• Unit testing
• Loop testing
34
• black-box testing
• Whitebox testing
• Alpha testing
• Beta testing

6.2.1. BETA TESTING

Beta Testing is performed by “real users” of the software application in “real
environment” and it can be considered as a form of external User Acceptance Testing. It is the
final test before shipping a product to the customers. Direct feedback from customers is a
major advantage of Beta Testing. This testing helps to test products in customer’s environment.

Beta version of the software is released to a limited number of end-users of the product
to obtain feedback on the product quality. Beta testing reduces product failure risks and
provides increased quality of the product through customer validation.

• Beta testing is performed by Clients or End Users who are not employees of the
organization.

• Beta testing is performed at a client location or end user of the product.  

• Reliability, Security, Robustness are checked during Beta Testing.

• Beta Testing typically uses Black Box Testing.  

• Beta testing doesn’t require any lab environment or testing environment. The software is
made available to the public and  is said to be real time environment.  

• Only a few weeks of execution are required for Beta testing.  

• Most of the issues or feedback is collected from Beta testing will be implemented in future
versions of the product.  

• Beta testing also concentrates on the quality of the product, but gathers users input on the
product and ensures that the product is ready for real time users.

6.2.2 TYPES OF BETA TESTING

35
There are different types of Beta tests in software testing, and they are as follows:

Traditional Beta testing: Product is distributed to the target market, and related data is
gathered in all aspects. This data can be used for Product improvement.

Public Beta Testing: Product is publicly released to the outside world via online channels and
data can be gathered from anyone. Based on feedback, product improvements can be done. For
example, Microsoft conducted the largest of all Beta Tests for its OS — Windows 8 before
officially releasing it.

Technical Beta Testing: Product is released to the internal group of an organization and

gathers feedback/data from the employees of the organization.

Focused Beta: Product is released to the market for gathering feedback on specific features of
the program. For example, important functionality of the software.

Post-release Beta: Product is released to the market and data is gathered to make

improvements for the future release of the product.

6.2.3. ADVANTAGES OF BETA TESTING

• Reduces product failure risk via customer validation.

• Beta Testing allows a company to test post-launch infrastructure.
• Improves product quality via customer feedback
• Cost effective compared to similar data gathering methods
• Creates goodwill with customers and increases customer satisfaction.

6.2.4. DISADVANTAGES OF ALPHA TESTING

In depth, functionality cannot be tested as software is still under development stage

Sometimes developers and testers are dissatisfied with the results of alpha testing.

36
CONCLUSION

37
 CONCLUSION

Ensuring the fairness and consistency of grading is challenging in large project-based

design courses. Jury-based evaluation and grading rubrics can be helpful in addressing these
challenges, but scalability becomes an issue as the class size grows. Online grading systems,
such as the one presented in this paper, have a number of advantages over analog grading
methods, including scalability, real-time feedback on the status of grading, the reduced
potential for human error in compiling grades, the ability for jury members to grade remotely
and to revise their grades after submission, the ability for course administrators to easily review
grading results and remove statistical outliers from the score set, the ability to return both
provisional and final grades to the course faculty, staff, and students in a timely manner, and
the ability to archive and export grading data for future use. As a result, online grading
systems can be very helpful in reducing the logistical problems associated with collecting,
processing, and returning the grades produced by grading juries.

The online system presented in this work is a clear improvement over paper-based
rubrics and may serve as an example for others interested in developing similar tools. The
online grading pages are well liked by the course administration and have been well received
by the course faculty and staff. However, it was also shown that small details can interfere
with usability and thus user satisfaction and that compatibility with mobile devices is a
necessary requirement that must be addressed in the future.

FUTURE SCOPE

The Online Grading System contains the necessary features to support the assignment
management system. For the future course of the project,

1. A tree structure can be implemented to better manage the files across different semesters and
years. This can also be used to add or delete a folder and upload/download files so that other
files besides assignments can be uploaded and saved for a corresponding semester by the
professors.

2. Currently the Online Grading System supports C, C++ and Java programming assignments.
In the future more programming languages can be supported.

38
3. Further enhancements to the Online Grading System such as approval method canbe
implemented.

39
REFRENCES

1. Software Engineering - R.S. Pressman

2. PHP for Dummies
3. PHP Beginners Guide by McGraw-Hill Publication
4. JavaScript by McGraw-Hill Publication
5. http://www.resgroup.net/

6. http://www.a1realestate.solutions
7. Wikipedia.org
8. www.w3schools.com

9. www.webcampzg.org

40