Documente Academic
Documente Profesional
Documente Cultură
We are thankful to Nepal College of Information and Technology for providing us the chance to
build software during the minor project and managing the resources and specialists to assist our
project.
We are indebted to Head Project Coordinator Dr. RoshanChitrakar, who is our actual supporter
for this actionthey have managed everything a student need.
We are grateful to our respected HOD Er. MadanKadariyaand Er.PrakashPaudel , who will be the
part of our project team with their assistance, advices and suggestions.
1
ABSTRACT
The Project Titled Internal Marks Calculation System is web based application. It calculates
the internal marks of engineering student of Pokhara University. This application had been
developed using CSS and HTML as the front end and JavaScript, PHP and SQL server as the
back end.
Keywords: InternalMarks,HTML,CSS,PHP,SQL
TABLE OF CONTENTS
2
ACKNOWLEDGEMENT.............................................................................. 1
ABSTRACT.............................................................................................. 2
1 INTRODUCTION.................................................................................. 1
1.1 PROBLEM STATEMENT.......................................................................1
1.2 OBJECTIVES......................................................................................2
1.3 SIGNIFICANT OF STUDY.....................................................................2
2 METHODOLOGY.................................................................................. 3
2.1 SOFTWARE DEVELOPMENT LIFECYCLE................................................3
2.1.1 ANALYSIS PHASE............................................................................................... 5
2.1.2 DESIGN PHASE.................................................................................................. 5
2.1.3 CODING PHASE................................................................................................. 5
2.1.4 TESTING PHASE................................................................................................. 5
2.2 TOOLS TO BE USED...........................................................................6
3 LITERATURE REVIEW........................................................................... 7
3.1 WHAT IS FRONT END AND BACK END..........................................................7
3.2 CSS.................................................................................................7
3.3 HTML...............................................................................................7
5 CONCLUSION.................................................................................... 10
6 FURTHER WORKS.............................................................................. 11
7 BIBLIOGRAPHY................................................................................. 12
8 APPENDIX........................................................................................ 13
LIST OF FIGURE
3
LIST OF TABLE
4
1 INTRODUCTION
1
1.1 PROBLEM STATEMENT
In analog system calculating internal marks is very irritating and time wasting so this system can
solve this problem and calculate the exact internal marks of non-practical subject.
1.2 OBJECTIVES
After the investigation of the data collection process, objectives of our project Internal Marks
Calculation System has been list out. The core objectives of our project are as follows:
3. Gives the information to student that they are qualified or not for board examination.
The scope of this project is to give facilities for teacher to calculate internal marks.
3. Students also know that they are qualified or not for board examination
2
2 METHODOLOGY
This project work adopts thefollowing methodologies for the application of knowledge, skills,
tools and techniques to a broad range of activities in order to meet the requirements of our
project Internal marks calculation system.
The framework we will be using for developing this project is Incremental model. This model
combines linear sequential model with the iterative prototype model. New functionalities will be
added as each increment is developed. The phases of the linear sequential model are: Analysis,
Design, Coding and Testing. The software repeatedly passes through these phase in iteration
andan increment is delivered with progressive change.
3
.
4
2.1.1 ANALYSIS PHASE
In this phase, analysis will be performed in order to find out the requirements of the system. The
outcome of this phase would be a SRS which is an acronym for System Requirement
Specifications.
In this phase the SRS would be translated into the systems design. Context Diagram, DFD, ER
Diagram, Use Case Diagram and Class Diagram will be developed.
In this phase, coding will be done according to the design and a working system will be
developed by the end of this process.
In this phase, the system is tested with each testing, a list of changes to the system developed, is
suggested and the changes will be applied to the software and the software would be delivered as
a successive increment until a satisfying system is achieved. The tools used for documentation,
designing and developing UI/UX, testing are listed below in table:
TOOLS PURPOSE
5
Dreamweaver CS6 Design
6
3 LITERATURE REVIEW
The biggest challenge of a school office authority is to manage each and every student detail and
their marks effectively and efficiently, often cases occur of changes in marks, pass list, name
changes, data losses etc. In the existing scenario each students marks are separately entered by
their teachers first in a sheet of paper and then later an office staff copies the mark into a register.
It is extremely tedious to search data from this registers and usually mark registers are kept
separate from student registers, moreover there are every chance of entering wrong marks of the
student. To overcome all the cons of the existing system, the proposed software is developed to
make the entry and the retrieval of student data much easier. InPokhara University, 50% Marks is
evaluated from internal marks. Internal marks are very important for those students who are
punctual and intelligent but they cannot give final exam properly. Internal marks calculating
system is very easy to use for both the teacher and student. Providing input in each required field
results system automatically calculate the internal marks of those student who are qualified for
board examination but displays NQ for those student who are not qualified for board
examination.
Simply front endmeans user appearance and back end means database and other internal parts.
3.2 CSS
3.3 HTML
7
4 SECTION OF WORK DETAIL
The project schedule has been designed as per requirements and constraints involved. This
project is scheduled to be completed in about 2 months. Requirement analyses have been given
more emphasis. Research and database management is to be done first and well documented.
Debugging and Testing is to be done prior to the completion of the project.
4.1 Schedule
Design System 14
Develop Documentation 60
8
4.2 Work Breakdown
3 Testing Bibek,Rupak,Suman
TABLE3:WORKBREAKDOWN
9
5 CONCLUSION
Finally we developed a project Internal Marks Calculation System which is very important for
calculating the internal marks of engineering student of PokharaUniversity .
10
6 FURTHER WORKS
This is simple project for calculating the internal marks of 4th semester. If we develop this project
we will calculate internal marks of all subject of engineering and management .which makes
easy for teacher to calculate the internal marks and also easy for students to see their internal
marks of each subject.
11
7 BIBLIOGRAPHY
1. Blanck, Peter. eQuality: The Struggle for Web Accessibility by Persons with Cognitive
Disabilities, Cambridge Disability Law and Policy Series, 2015.
2. Horton, Sarah and Quesenbery, Whitney. A Web for Everyone, Rosenfeld Media, 2012.
Keith, Jeremy. Bulletproof Ajax, New Riders Press, 2007.
URL: http://www.slideshare.com/
URL:www.docshare.com
URL:www.wufoo.com
12
8 APPENDIX
8.1 Snapshot
9
13
14
15
16
17
18
19
20
21
22
9.1 Source Code
department.php
<!DOCTYPE html>
<html>
<head>
<title>
</title>
23
<body>
<br><br>
<center>
</center>
<a href="modify.php?dept=computer">Modify</a><br>
<a href="delete.php?dept=computer">Delete</a><br>
<a href="view.php?dept=computer">View</a><br>
</div>
</div>
<a href="modify.php?dept=computer">Modify</a><br>
<a href="delete.php?dept=computer">Delete</a><br>
24
<a href="view.php?dept=computer">View</a><br>
</div>
</div>
<a href="modify.php?dept=computer">Modify</a><br>
<a href="delete.php?dept=computer">Delete</a><br>
<a href="view.php?dept=computer">View</a><br>
</div>
</div>
<div class="clearfix"></div>
<br>
<center>©2017  Team</center>
</div>
</div>
</body>
</html>
25
final.php
<!DOCTYPE html>
<html>
<head>
<title>
</title>
<body>
<div class="form">
26
ROLL NO: 1<br>
</div>
</div>
</form>
</div>
<div class="clearfix"></div>
</div>
</div>
</body>
</html>
index.php
<!DOCTYPE html>
<html>
<head>
27
<meta charset="utf-8" />
<title>
</title>
<body>
<div class="form">
</div>
</div>
28
<input class="form-control" type="text" name="subject_id"
placeholder="SUBJECT ID*" required><br>
</div>
</div>
</form>
</div>
<div class="clearfix"></div>
Team</center>
</div>
</div>
</body>
</html>
29