Dr. D. Y.

Patil Vidya Pratishthan Society’s

Dr. D. Y. Patil Arts, Commerce and Science College Pimpri Pune-18.
2019-2020

A
Project Report
On

“STUDENT RESULT MANGMENT SYSTEM”

Submitted in partial fulfillment of T.Y.B.B.A(C.A) Sem-V1
as laid down by the Savitribai Phule Pune University
2019-2020

Under Guidance of
MR.

Submitted By
Rushi Karad (Roll no-39)

1
 Seat No.:_______

Dr. D. Y. Patil Vidya Pratishthan Society’s

Dr. D. Y. Patil Arts, Commerce and Science College
Pimpri Pune-18.

CERTIFICATE

This is to certify that Rushi Karad and has successfully completed the project titled
“STUDENT RESULT MANGMENT SYSTEM” for T.Y.B.B.A(C.A) (Sem-V) of Savitribai
Phule Pune University for the academic year 2019-2020.

Project Guide Vice-Principal & H.O.D Principal

(Computer Science)

Examiner 1:______________ Examiner 2:______________

2
ACKNOWLEDGEMENT

3
 ACKNOWLEDGEMENT

Every task goes to completion but matters how it is done and in how much time
it is done and what standard is follows. Since its very short duration project this things
matters lot.

So we would like to sincerely thank all those who have helped me in making
project a success. First of all we would like to offer thanks to Mrs.Madhuri Darekar
Mam who guide us and provided valueable information about PHP Programming and
details of various products, without whom such an interactive project was impossible
also for letting us this great opportunity to test our skills through the creation of our
project part out syllabus.

We express our special thanks to Vice-Principal & H.O.D. Dr.Ranjit Patil and
all staff members of Dr.D.Y.Patil Arts Commerce & Science College Pimpri, Pune who
assist us throughout this project

We finally thanks to all my college staff and my colleagues, for encouraging and
helping me in doing such a big Project. Our sincere thanks go towards the faculty of
our college for their kind co-operation and attention for the creation of this project.

Further, we wish to thank all persons, friends, who knowingly or unknowingly helped
us in completion of this project. If something is left, we are sorry for that.

Thank you every one!

Sincerely

Rushi Karad

4
 Index

Sr.N Topics Page No.

1 Introduction 7
2 Existing System 9
3 Proposed System 11
4 Fact Finding Techniques 13
5 Feasibility Study 15
5.1 Technical Feasibility -
5.2 Operational Feasibility -
5.3 Economical Feasibility -
6 Operating Environment 17
6.1 Hardware Specification -
6.2 Software Specification -
7 Analysis and Design 18
7.1 ER Diagram 19
7.2 Use case Diagram 20
7.3 Sequence Diagram 21
7.4 Class Diagram 22
7.5 Deployment Diagram 23
7.6 Data Dictionary 24-25
8 Screen Layout 27
8.1 Input Screen -
8.2 Output Screen -
9 Limitations 35
10 Conclusion 37
11 Bibliography 39

5
INTRODUCTION

6
 INTRODUCTION

An individual report card of each student has to be displayed and printed at a

keystroke according to any selected format. An important aid for teachers and
students to judge their performance. Merit list printing by totals for a class by
individual subject marks for a class. Student performance in a particular subject
or all the subjects must be expressed. Performance of teachers of various classes
can be easily compared

The system displays the list of all issues that are open, closed, in progress. If the user can get
registered by clicking on the logon button and provide the required information as specified.
Each time the registered customer come on to the site he can makes use of the user name and
the password that is allocated to him

 User configurable grading system.

 User configurable examination pattern.
 Examinations-weight age handling.
 Calculated / Average Column handling.
 Grace marks handling.
 Special Analysis section.
 Sub-subjects marks entry handling.

7
Existing System

8
 Existing System

4.1.1 Existing System with Limitations

 It is time consuming process as the user has to type the dbase commands. He has to
remember all the commands which are difficult.
 It is limited to a single system.
i. A user who wants only to have some information has to contact the administrator
every time.

9
Proposed System

10
 Proposed System

4.1.2 Proposed System Features

 User friendliness is provided in the application with various controls.

 The system makes the overall project management much easier and flexible.

 It can be accessed over the internet.

 Vast amount of data can be stored.

 There is no risk of data mismanagement at any level while the project development is
under process.

 Relationship between the administrator, owner/developer and subcontractor can be

maintained very easily.

 It provides high level of security using different protocols like https etc.

Objectives of proposed system

The objective of “Restaurant management system” is to easily track the information of all
customers and menus and items. The main goal of the software is to build a good management
tool for all customers. The main purpose of this software is to reduce the time taken through
manual system in order to maintain all the records.

11
Fact Finding Techniques

12
 Fact Finding Techniques

Fact-finding techniques are used to gather requirements and information concerning the
business and the industry it participates in.

 Interview technique is used to gather user and client requirements in depth. In addition,
finding out how the current system works from the views of users, and users
expectations from the new system. Also, subjects that require depth information/
knowledge can be discussed by using interview technique such as: budget, management
background and so forth.

 Observation technique is used to observe the business and current system; also to note
down requirement and facts that has not mentioned in the interviews. This is a highly
successful technique, because developers have the chance of experiencing the current
system themselves, not just relying on the words of the users.

 Questionnaire is used to take the views of large number of groups. For the project a
questionnaire was produced regarding on the home delivery service and handed out to
the customers to understand their buying pattern.

 Prototyping and storyboard is the visual technique, which is used to conform the
understanding of the system requirements that users and client required. Also, at the
interface stage is the main techniques to determine the layout and navigation through
windows. In addition the technique has the ability to bring the users and developers
together, which will increase the chances of success.

 Use-case diagram is the description of a particular interaction between the system and
one or more of its users. The role is to show the functionality of the system from the
user perspective. Also, it shows the interaction between tasks and activities. Which is
useful at the stage of conceptual and logical design where entities, attributes and
relationships are identified, then E-R diagram.

13
Feasibility Study

14
 Feasibility Study

1. Technical Feasibility:

This included the stud y of function. Performance and constraints that may affect the ability to
achieve an acceptable system. For this feasibility study. We studied complete functionality to
be everything was possible using Visual Basic and MS Access.

2. Operational Feasibility:

No doubt the proposed system if fully GUI based that is very user friendly and all inputs to be
taken all self explanatory even to a layman .Beside, a proper training has been conducted to let
know the essence of the system to the user so that they feel comfortable with new system. As
far our study is concerned the client are comfortable and happy as the system has cut down
their loads and doing.

3. Economic Feasibility:

This is very important aspect to be considered while developing a project. We decided the
technology based on minimum possible cost factor. All hardware and software cost has to be
affordable to common business persons. And Organizations. Overall we have estimated that the
benefits the benefits the organization is going to receive from the proposed system will surely
overcome the initial costs and later on running cost for system.

15
Operating Environment

16
 Operating Environment

1. Software Requirement:

1. Visual basic 6.0

2. MS access 2007

2. Hardware Requirement:

1. Minimum Dual-Core,

2. 2.0 GB memory capacity,

3. 500GB storage capacity hard disk

17
ANALYSIS AND DESIGN

18
 Analysis and Design

ER Diagram

19
20
Use Case Diagram

<<includes>>

Login validation

Add results

Admin
add attendance

Add schedules

21
22
 <<includes>>

Login validation

updates Personal details

Student
Views attendance

Views Results

Views Schedules

23
 <<includes>>

Login Validation

View personal details

Staff Views attendance

View results

View schedules

Class Diagram:-
Admin Subject
aId subjectId
subjectdetails
Notify login()
notificationId update details() addSubjectDetails()
notificationDetails viewDetails() viewsubjectDetails()
validation() Results
notification() resultId
validate
add Results()
loginId view Results()
password modifyResults()

validation()

Staff
tId
tName

login()
viewDetails()
Student
sId
sName

login()
viewDetails()

24
Deployment Diagram

Printer
Applicat
on
Customer Server

Databas
e

25
Sequence diagram:-

Login users attendance schedules

: Admin

Login Request
valid

confirmation
create students

confirmation

Add Attendance

updateattendance

response

Add Schedules

update schedules

response

26
 2: valid

1: Login Request 4: create students

Login
users
3: confirmation 5: confirmation
: Admin
8: response 9: Add Schedules
11: update schedules
6: Add Attendance
7: updateattendance 10:
12: response

attendanc
e

schedules

Data Dictionary
Student Table:-

27
 Srmd:Student

1 name Varchar(30)

2 Rno Int(30)

3 Class_name Varchar(30)

Admin Login:-

Srms;Admin Login

1 Userid Varchar(30)

2 passwors Varchar(30)

28
Srms Class:-

Srms Class

1 name Varchar(30)

3 Id Int(30)

29
Srms Resulr:-

Srms Result

Name Varchar(30)

# Rno Int(30)

Class Varchar(30)

# P1 Int(3)

# P1 Int(3)

# P3 Int(3)

# P4 Int(3)

# P5 Int(3)

# Marks Int(3)

# percentage float

30
 Screen Layout

Home Page:-

31
Admin And Student Login:-

32
Feacthures:-

:-

Student Feature:-
33
DashBord:-

34
Add Class:-

35
Manage Class:-

36
37
Add Student:-

Add Result:-

38
39
Manage Result:-

40
Limitations

41
 Limitations

Our system is not online system so than customer cannot place order online
Cannot send the KOT (Kitchen Order Ticket) to kitchen
Cannot hold the customer table for long time
No multiple bills can be generated simultaneously
Can’t add multiple users like waiters, chef, cashier, captain

42
Conclusion

43
 Conclusion

Our system is friendly and will try to work out solution in a way that favors the interests of
every user, solve problems faster, manage data, so that all the transactions become fast and
there should not be any error in transaction like calculation mistake and bill generation.

The applicaton has been tested with live data and has provided a successful result.
Hence the software has proved to work efficiently.

44
Bibliography

45
 Bibliography

1. Books:

1. Charles Humped (2000) ‘Visual Basic’ University of

Toronto

2. Herbert Scheldt (2000) ‘Visual Basic 6.0’ Tata McGraw Hill

3. John Bukowski (2000) ‘Visual Basic 6.0’ ‘BPB Publicatons

4.Jamie Jaworsky ‘Visual Basic 6.0’Techmedia

5.Stefen Denninger ‘Visual Basic 6.0’Author’s Press

6.Ian Somerville ‘Software engineering’

7.Rajeev mall ‘Software engineering’

8.Elmasri Navathe ‘Fundamentals of database systems’

2.Online Reference:

1.www.w3schools.com

2.www.theserverside.com

3.www.visual.com

4 www.letustechbysbg.com

5 www.draw.io

46
47