0% found this document useful (0 votes)
110 views

Student Point

This document is a project report submitted by D. Krishna Chaitanya in partial fulfillment of the requirements for a Bachelor of Technology degree in electronics and computer engineering from Jawaharlal Nehru Technological University. The report describes a student point project developed under the guidance of P. Dilip. It includes an abstract, contents page, introduction, literature review, analysis, design, implementation, testing, conclusion, and references.
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
110 views

Student Point

This document is a project report submitted by D. Krishna Chaitanya in partial fulfillment of the requirements for a Bachelor of Technology degree in electronics and computer engineering from Jawaharlal Nehru Technological University. The report describes a student point project developed under the guidance of P. Dilip. It includes an abstract, contents page, introduction, literature review, analysis, design, implementation, testing, conclusion, and references.
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 35

STUDENT POINT

A Project report submitted in


partial fulfillment of the requirement for the award of the Degree of

BACHELOR OF TECHNOLOGY
IN
DEPARTMENT OF ELECTRONICS AND COMPUTER ENGINEERING

Submitted
By
D.Krishna Chaitanya 15671A1906
Under the Guidance of
P.Dilip
Assistant Professor

Department of Electronics and Computer Engineering


J.B. Institute of Engineering & Technology
(UGC Autonomous,PermanentlyAffiliated to JNT University, Hyderabad)
Bhaskar Nagar (Post),MoinabadMandal, R.R. Dist.-500075
2015-2019
J.B. INSTITUTE OF ENGINEERING AND TECHNOLOGY

(UGC Autonomous & Accredited by NBA&NAAC, Approved by AICTE & Affiliated to


JNTU, Hyderabad)

CERTIFICATE

This is to certify that the mini project report entitled STUDENT POINT being
subitted by Mr/Mrs D.Krishna Chaitanya in partial fulfillment for the award of the Degree of
Bachelor of Technology in Electronics And Computer Engineering to the Jawarlal Nehru
Technological University is a record of bonafied work carried out by him under my guidance
and supervision.
The results embodied in this mini project report have not been submitted to
any other University or Institute for the award of any Degree or Diploma
.

Mr. P.Dilip Mr. K. Roshan


Assistant Professor Associate Professor
Internal guide HOD-ECM

External Examiner
DECLARATION

I D.Krishna Chaitanya bearing Roll No: 15671A1906, a bonafide student of J.B.


Institute of Engineering and Technology, would like to declare that the mini project titled
“STUDENT POINT” A partial fulfillment of B.Tech Degree course of Jawaharlal Nehru
Technological University is my original work in the year 2018 under the guidance of Mr.
P.DILIP, Assistant Professor, Electronics and Computer Engineering Department and it has
not previously formed the basis for any degree or diploma or other any similar title submitted
to any university.

D.KRISHNA CHAITANYA
Date: Roll No:15671A1906
ACKNOWLEDGEMENT
I would like to express my sincere gratitude to my guide, Mr.
P.Dilip,Assistant/Associate Professor, Electronics and Computer Engineering Department,
whose knowledge and guidance has motivated me to achieve goals I never thought possible.
He has consistently been a source of motivation, encouragement, and inspiration. The time I
have spent working under his supervision has truly been a pleasure.
I take it as a great privilege to express our heartfelt gratitude to Mr. K.Roshan ,Head
of the Department for his valuable support and all senior faculty members of ECM
department for their help during my course. Thanks to programmers and non-teaching staff of
ECM department of J.B.I.E.T.
I thank my principal Dr. Towheed Sultanafor extending his utmost support and co-
operation in providing all the provisions, and Management for providing excellent facilities to
carry out my project work.
Finally special thanks to my parents, sister for their support and encouragement
throughout my life and this course. Thanks to all my friends and well-wishers for their
constant support.

D.KRISHNA CHAITANYA
Roll No:15671A1906
CONTENTS

ABSTRACT
LIST OF FIGURES
LIST OF TABLES
LIST OF SCREENS
SYMBOLS AND ABBREVATIONS
1. INTRODUCTION
1.1 Motivation
1.2 Problem definition
1.3 Objective of Project
1.4 Limitations of Project
2. LITERATURE SURVEY
2.1 Introduction
2.2 Existing System
2.3 Disadvantages of Existing system
2.4 Proposed System
2.5 Conclusion
3. ANALYSIS
3.1 Introduction
3.2 Software Requirement Specification
3.3 Flowcharts
4. DESIGN
4.1 Introduction
4.2 DFD / ER / UML diagram
4.3 Module design and organization
5. IMPLEMENTATION & RESULTS
5.1 Introduction
5.2 Explanation of Key functions
5.3 Method of Implementation Output screens

6. TESTING & VALIDATION


6.1 Introduction
6.2 Design of test cases and scenarios

i
6.3 Validations
6.4 Software Testing
6.5 Validation Testing
7. CONCLUSION
REFERENCES

ii
ABSTRACT

The main concept of the website is to provide a platform for the users who want to
know everything about computers. The World Wide Web e-learning provides a simple means
of exploring the immense volume of pages of information residing on internet. Information on
web is presented on web pages, which appear as a collection of text, graphics and pictures. E-
learning resource locator drawbacks on authentication to access the data. Database security is
provided. It is a time efficient approach.

Much of the web success is due to the simplicity with which it allows users to refer
the information. A digital library that provides all learning materials for the students. This
website contains information regarding aptitude, interview questions, reference books on
different technologies. If any contests are held in any of the platform updates will be provided
in this website.

iii
LIST OF FIGURES

S.No Name Of The Diagram Page no

1 UML Diagram 8

2 Use Case Diagram 9

3 Sequence Diagram for sign up 10

4 Sequence Diagram for login 11

5 Data Flow Diagram 12

LIST OF TABLES

S.NO NAME OF THE TABLE

1 User registration
2 Admin/student login
3 Validation message for user registration
4 Validation message for user login

iv
LIST OF SYMBOLS

S.NO NOTATION NOTATION DESCRIPTION


NAME
Class Name
Represents a collection
+public
1 Class -attribute of similar entities
-private
#protected -attribute grouped together

+operation
+operation

NAME Association represents


Class Class static relationships b/w
2 Association
A B classes. Roles represents
Class Class the way the two classes
A B see each other.

3 Actor It aggregates several


classes into a single class

4 Aggregation Class A Class B Interaction between


system and external
environment
Class B Class B

5
Relation Used for additional
Uses
(uses) process communication

Extends relationship is
Relation extends used when one use case
6
(extends) is similar to another use
case but does a bit more

Communication
7 Communicatio Between various use
cases.
n

v
State of the processes
State
8 State
Initial state of the object
9 Initial State

10 Final state of the object


Final state

11 Control flow Represents various


control flow between the
states

12 Decision box Represents decision


making process from a
constraint

Interaction between the


13 Use case system and external
environment

Represents physical
14 Component modules which are a
collection of components

Represents physical
15 Node modules which are a
collection of components

A circle in DFD
16 Data represents a state or
process which has been
process/state
triggered due to some
event or action

vi
Represents external
17 External entity entities such as
keyboard,sensors,
etc
Represents
18 communication between
Transition
processes
Represents the message
19 Message exchanged

vii
LIST OF ABBREVATION

S.NO ABBREVATION EXPANSION

1 HTML Hyper Text Markup Language


2 CSS Cascading Style Sheet
3 JS Java Script
4 PHP Personal Home Page
5 SQL Sequential Query Language

viii
1.INTRODUCTION

1.1 Motivation:
The main motivation behind the idea of developing STUDENT POINT is to help the
students regarding aptitude,interview,programming,videos,etc. There are websites which
provide information about aptitude and programming languages saperately, but there is no
specific website which provides altogether in a single website. So, we came up with this idea
of developing a website which provides the information about aptitude, and technical
questions,interview questions,books,etc.
1.2 Problem Definition:
There exists no website which provides notes within the college environment. There
exists a system in our college where notes are made available to the student Ecap portal which
is not well structured and it does not provide updated content.
In addition to these nowadays user experience is what matters. Mobility and
Flexibility are the two key factors. Most of the students spend much time on internet referring
various websites and learning new technologies, and this website is specially made for our
college where faculty can upload the notes rather than mailing every individual.
1.3 Objectives of the project:
This project helps in making the task easier by providing different kinds of notes, and
E-books at one place and save time of students in referring Internet during exams. We also
provide programming tricks,interview question,Aptitude ,referrence books regarding latest
technology like AI,data science,AWS ,.e.t.c. in one platform.
1.4 Limitations of the Project:
 Security limitations.
 Limited size of Data Base.

1
2.LITERATURE SURVEY

2.1 Introduction:
This section gives detailed explanation about the existing system, disadvantages of
the existing system and the new proposed system and will differentiate the existing system
with the current system in the field of how beneficial it will be comparing to the current
existing systems.
2.2Existing System:
The World Wide Web E-Learning Provides a simple means of exploring the
immense volume of pages of information residing on internet. Information on web is
presented on Web pages, which appear as a collection of text, graphics, and pictures.
2.3Disadvantages of existing system:
The major problem people face in the existing system is it does not provide
authentication to access the data.
 No database security is provided.
 It is not time efficient approach.

2.4Proposed System:
Proposed system is developed using in such a way that much of the web success is
due to the simplicity with which it allows users to refer the information. A digital library that
provides all learning materials for the students. This website contains information about
aptitude, workshops and technical events. Our proposed system has the following advantages:
 User friendly interface.
 Fast access to data.
 Less error.
 Look and feel environment.
2.5 Conclusion:
This project is designed for the purpose to reduce time and also to reduce the burden
of users to access multiple websites. As the comparison with the existing system, the new
system is like everything at one place. As per the new system it is very easy access to the
notes and syllabus and offline access provided in our application will allow the user to access
the notes anywhere irrespective of Internet issues and location.

2
3.ANALYSIS

3.1 Introduction:
This section is to analyze the problem and understand its context. The first activity in
the phase is studying the existing system and other is to understand the requirements and
domain of the new system. Both the activities are equally important, but the first activity
serves as a basis of giving the functional specifications and then successful design of the
proposed system. Understanding the properties and requirements of a new system is more
difficult and requires creative thinking and understanding of existing running system is also
difficult, improper understanding of present system can lead diversion from solution.

3.2 Software Requirement Specifications:


3.2.1 User Requirements:
Functional Requirements:
 These are the requirements given to the system during Requirements Phase of
the Software Development.
 The user should be able to choose from a variety of departments available in
the application.
 The user should be able to view all the department blocks simultaneously.
 The system should minimize the overall time spent by the user in searching and
downloading different applications.
 The user should be able to view the application in the desired layout.
3.2.1 Software Requirements:
 Operating System- Windows 7 and above.
 Programming Languages-HTML,CSS,PHP,Bootstrap and JS.
 Database – MySQL.
3.2.2 Hardware requirements:
 Flexible internet facility.
 RAM(Minimum of 2gb).

3
3.3 System Architecture:

Fig:System Architecture

4
4.DESIGN

4.1 Introduction
Design engineering deals with the various Unified Modeling Language (UML) is a
standard language for writing software blue prints. The UML is a language for
 Visualizing
 Specifying
 Constructing
 Documenting the artifacts of a software intensive system.

The UML is a language which provides vocabulary and the rules for combining
words in that vocabulary for the purpose of communication. A modeling language is a
language whose vocabulary and the rules focus on the conceptual and physical representation
of a system. Modeling yields an understanding of a system.
4.1.1 Building Blocks of the UML:
The vocabulary of the UML encompasses three kinds of building blocks:
 Things
 Relationships
 Diagrams
Things are the abstractions that are first-class citizens in a model relationships tie
these things together; diagrams group interesting collections of things.
4.1.2 Things in the UML:
There are four kinds of things in the UML:
 Structural things
 Behavioral things
 Grouping things
 Annotational things
Structural things are the nouns of UML models. The structural things used in the
project design are:
First, a class is a description of a set of objects that share the same attributes,
operations, relationships and semantics.

5
Window
Origin
Size
open()
close()
move()
display()

Fig: Classes
Second, a use case is a description of set of sequence of actions that a system
performs that yields an observable result of value to particular actor.

Fig: Use Cases


Third, a node is a physical element that exists at runtime and represents a
computational resource, generally having at least some memory and often processing
capability.

Fig: Nodes
Behavioral things are the dynamic parts of UML models. The behavioral thing used
is:
Interaction:
An interaction is a behavior that comprises a set of messages exchanged among a set
of objects within a particular context to accomplish a specific purpose. An interaction
involves a number of other elements, including messages, action sequences (the behavior
invoked by a message, and links (the connection between objects).

Messages

6
4.1.3 Relationships in the UML:
There are four kinds of relationships in the UML:
 Dependency
 Association
 Generalization
 Realization
A dependency is a semantic relationship between two things in which a change to
one thing may affect the semantics of the other thing (the dependent thing).

Dependencies

An association is a structural relationship that describes a set links, a link being a


connection among objects. Aggregation is a special kind of association, representing a
structural relationship between a whole and its parts.

Association

A generalization is a specialization/ generalization relationship in which objects of


the specialized element (the child) are substitutable for objects of the generalized element (the
parent).

Generalization

A realization is a semantic relationship between classifiers, where in one classifier


specifies a contract that another classifier guarantees to carry out.

Realization

7
4.2 UML Diagram:
UML uses elements and associates them in different ways to form diagrams that represent
static, or structural aspects of a system, and behavioral diagrams, which capture the dynamic
aspects of a systems. There are two main categories; structure diagrams and behavioral
diagrams.

Fig:4.2 UML diagram.

8
4.2.1 Use case Diagram:

Use case is a set of scenarios that describing an interaction between a user and a
system. The two main component of use case diagram are use cases and actors. They are
helpful in exposing requirements and planning the projects.
Use Case Diagram is the combination of use cases of a system, a use case shows a
single function of the system. By looking at the use case diagram the stake holder will know
what functionality the system have or will be included.
They will know exactly who will be interacting with system. And identify which
functionality is included. So, we have designed the following use case diagram for our project.

Fig 4.2.1:Use case Diagram.

9
4.2.2 Sequence Diagram:

A sequence diagram is an interaction diagram that shows how objects operate with
one another and in what order. It is a construct of a message sequence chart. A sequence
diagram shows object interactions arranged in time sequence.
Sequence Diagram for Sign up:

Fig 4.2.2: Sequence diagram for sign up.

10
Sequence Diagram for Login:

Fig 4.2.2: Sequence Diagram for Login.

11
4.2.3 DATA FLOW DIAGRAM:
Data flow diagram (DFD) is graphical representation of the "flow" of data through an
information system. A DFD shows what kind of information will be input to and output from
the system, how the data will advance through the system, and where the data will be stored.
Our project needs a Data Flow diagram to show the flow of the data in the application. So, we
have designed a data flow diagram for our website.

Fig 4.2.3:Data flow Diagram.

12
4.3 Module Design and Organization
There are three modules in the system
1. Admin
2. User
Admin:
In this module, admin is the main authority of this site . so he has all privileges to
upload, delete files and update of any account.
In Admin page, he has certain links such as:
 Uploads files.(Books,other files).
 Updates.
 Advisory panel.
 Contact us.
User:
In this module the candidate can get registered providing their personal details and
get logged into their candidate home page, from where they can access the data provided by
admin.

13
5.IMPLEMENTATION AND RESULTS

5.1 Introduction:
This project is developed using HTML,CSS,Bootstrap,Javascript as front end and
MySQLi,PHP as back end in Windows environment. The web applications used for this
project are PHP and MySQLi. This system provides optimized utilization of resources,
improved productivity, and efficient management of resources as it is completely
computerized and has centralized database maintenance.
5.2 Explanation of key Functions
5.2.1 Java Script:
 Giving the user more control over the browser.
 Detecting the user's browser and OS. The ability to detect the user's browser and
OS allows your script to perform platform-dependent operations, if necessary.
 Performing simple computations on the client side.
 Validating the user's input.
JavaScript helps the browser to perform input validation without wasting the user's
time by the Web server access. If the user makes a mistake in the input, the user will get an
error message immediately! On the other hand, if the input information is validated only on
the server, then the user would have to wait for the server response.
 Java Scripts are used as HTML tags alone will not be sufficient in developing an
application interactively.
 Alert (“string”): This message is known as confirmation message. By this we
can display an alert window.
 onsubmit() :It is invoked as soon as the user press the submit button on the web
page.

14
5.3 Method of Implementation:
5.3.1 Output Screens:
Login page:
 In this page Users can login with their username and password.

SignUp page:
 In this page Users can register.

15
Home Page:

Books:

16
Settings:

17
6. TESTING AND VALIDATION

6.1 Introduction:
The purpose of testing is to discover errors. Testing is the process of trying to
discover every conceivable fault or weakness in a work product. It provides a way to check
the functionality of components, sub assembles, assembles and/or a finished product. It is the
process of exercising software with the intent of ensuring that the software system meets its
requirements and user expectations and does not fail in an unacceptable manner. There are
various types of test. Each test type addresses a specific testing requirement.
6.2 Design of test cases and scenarios:
6.2.1 Test case for user register:

Expected Actual
S.No Test Case Input Status
Output Output

User Name,
Registered Registered
1 Password, Email, Passed
Registration Successfully Successfully
Phone, Place

6.2.2 Test case for user and admin login:

Expected Actual
Test Case Input Status
Output Output
S.No

Valid username Login Login


1 Login Passed
and password successfully successfully

6.3 Validations:
6.3.1 Validation and messages for user registration:

S No Field Name Validations Messages Remarks


If the field is No
1 User Name Enter username
not filled
If the field is
Password is No
2 Password not filled (max
incorrect
8 characters)
If the field is Enter valid No
3 Email
not filled email

18
Should contain
If the field is No
4 Phone maximum of 10
not filled
characters
If the field is No
5 Place Enter the field
not filled

6.3.2 Validation and messages for user login:

S.No Field Name Validations Messages Remarks

Invalid
If field is not
1 User Name username or No
filled
password
Invalid
If field is not
2 Password username or No
filled
password

6.4 Software Testing:


Once the source code has been generated, the software must be tested to uncover as
many errors as possible before delivery to the customer. Software testing is a critical element
of software quality assurance and represents the ultimate review of specification design and
code generation.
6.4.1 Testing Objectives:
 Testing is a process of executing a program with the intent of finding an error.
 A good test case is one that has a high probability of finding an error as yet
Undiscovered.

 A successful test is one that uncovers an as yet undiscovered error.

6.4.2 Testing Principles:


 All tests should be traceable to customer requirements.
 Tests should be planned large before testing begins.
 Testing should begin “In the Small” and progress towards “In the Large”.
The system can be tested in one of the following two ways:-
 White-Box Testing.
 Black-Box Testing.

19
6.4.3 White Box Testing:
This is performed knowing the internal workings of a product. Tests are conducted to
ensure that “all gears mesh”, that is, that internal operation performs according to
specification and all internal components have been adequately exercised. This can be done
on close examination of procedural detail. Providing test cases that exercise specific set of
conditions, and / or, loops, tests, logical paths, through the software.

Using the white-box testing we can derive test cases that,


 Guarantee that all independent paths within a module have been exercised at
least once.
 Exercise all logical decisions on their true and false sides.
 Execute all loops at their boundaries and within their operational bounds and
 Exercise internal data structures to assure their validity.
By the test cases each of the modules have executed at least once and tested for bugs.
All the logic decisions on their true and false sides are executed so that the system will
perform well.
6.4.4 Black Box Testing:
Knowing the specified function that a product has been designed to perform tests
can be conducted that demonstrates each function is fully operational, at the same time
searching for errors in each function. It enables us to derive sets of input conditions that will
fully exercise all function requirements for documents.
It attempts to find errors in the following categories:
 Incorrect or missing functions
 Interface errors
 Errors in data structures or external database access
 Performance errors
 Initialization and termination errors

6.4.5 Unit Testing:


It focuses verification effort on the smallest unit of system design i.e., – the module.
Using the procedural design description as a guide, important control paths are tested to
uncover errors within the boundary of the module.

20
6.4.6 Integration Testing:
It’s a systematic technique for construction of the program structure while
conducting to uncover errors associated with interfacing. The objective is to take unit tested
modules and build a program structure that has been dictated by design.
6.5 Validation Testing:
Validation succeeds when system functions in a manner that can be reasonably
expected by the end user. This is achieved through a series of black-box test that demonstrates
with requirements. There are two tests conducted for the system validation. They are as
follows:-
6.5.1 Alpha Testing:
A customer conducts it at the developer’s site. The software is used in a natural
setting with the developer “looking over the shoulder” of the user and recording errors and
usage problems.
6.5.2 Beta Testing:
This test is conducted at one or more users sited by the end user(s) of the software.
Here the developers generally not present. Therefore, the beta test is a “live “application of
the software in an environment that can’t be controlled by the developer.

21
7.CONCLUSION

This project STUDENT POINT is developed to purpose to reduce time and also to
reduce the burden of users to access multiple websites.provide resources to users regarding
programming,aptitude,interview questions,video lecturers,reference books of latest
technologies like AI.etc to the users. So, that they can easily navigate through the application
for more information in more secure manner by using computerized system which is
maintained at centralized databases.
The goals that can be achieved by the project are:

 Instant access.
 User friendly
 Responsive webpage
 Improved productivity.
 Optimum utilization of resources.
 Efficient management of records.
 Simplification of the operations.
 Less processing time and getting required information.
 Reduce time and also to reduce the burden of users to access multiple
websites.

22
REFERENCES

Web Sites:
 www.w3schools.com.
 https://getbootstrap.com
 http://php.net/manual/en/intro-whatis.php
 https://www.javatpoint.com
 https://phptherightway.com/#pdo_extensionphptherightway.com
 https://www.allphptricks.com/simple-user-registration-login-script-in-
php-and-mysqli
 https://www.tutorialrepublic.com/php-tutorial/php-mysql-login-
system.php

23

You might also like