New Documentation
New Documentation
New Documentation
On
“School Data Management System”
By
Sudhanshu Ashok Nimkarde
P.E. Society’s
Modern Institute of Business Studies, Nigdi , Pune-44
2022-2023
INDEX
Chapter 1 INTRODUCTION Pg. No.
1. Introduction of project - 04
2. Existing System and Need for System - 04
3. Scope of Work - 05
4. Operating Environment - Hardware and Software - 05
5. Detail Description of Technology Used - 05
Chapter 4: Testing
1. Introduction to Software Testing - 22
2
Page
2. Test case - 23
Drawbacks and Limitations - 24
Proposed Enhancements - 25
Conclusion - 26
Bibliography - 27
ANNEXURES:USER INTERFACE SCREENS - 28
3
Page
Chapter 1: INTRODUCTION
1. Introduction of project :
4. Operating Environment :
Hardware :
• Processor : Intel core i5-4005 1.70GHz
• XAMPP Server
Language JAVA
Database MySQL
7
Page
Chapter 2: PROPOSED SYSTEM
1. Proposed System :
1. Data is efficient for use - This system is made to help to user access all the
users data under one roof
2. Reliable and user friendly - This system helps us to store the data which is
even reliable to access. However the GUI is provided in the system to deal
with system very easily.
3. Much advanced and easy to fetch data - This system is much advanced as
we can store the data in integrated database also within system with
features to views any users data.
2. Objectives of System :
10.It helps the institution to function with social responsibility and ensures
the socio-emotional development of the community.
3. User Requirements :
9
Page
Chapter 3: ANALYSIS AND DESIGN
Name
No Username Password
Contact Class
ID Student Admin
Teacher
Role
ID
No
Name Employee
ID
Post
Name No
10
Page
4. Data Flow Diagram :
Login
School
Save & Management Homepage
Upload
System
Registration
11
Page
5. Object Diagram :
Student 1
NameOfStud=”Sam”
StudentID=1
Age=15
School
Same:”Convent”
Course:10
Capacity:500
Name:String
Student 2
NameOfStud=”Roshni”
StudentID=2
Age = 20
12
Page
6. Class Diagram :
STUDENT
1 TEACHER - sname: string
+ tname : string - spass: string
+ pass: string teaches - sphone: integer
+ phone : integer - sclass: integer
+ update_profile () + update_profile()
+ change password() + login ()
+ change password()
Pays &
learn
CHAPTER
SUBJECT
- cname : string
- cweight : integer - subname : string
- cdes : string - sprice: integer
+ display ()
+ display()
13
Page
7. Use Case Diagram :
LOG IN
<<include>>
HOME
TEACHER
UPDATE
ADMIN
USER
CHECK
STUDENT
INFORMAT
ION
EMPLOYEES
System Boundary
14
INFO
Page
8. Activity Diagram :
STUDEN
T
Initial
State
LOG IN
CHECEK
HOME PROFILE
CHOOSE
PERSON TYPE
VIEW INFORMATION
15
Page
9. Collaboration Diagram :
1.login details
USER LOGIN
2. Select Person
SELECT
3. fill info
ff
FILL DETAILS
4.fill info
:SAVE
16
Page
10.Deployment Diagram :
MOBILE
INTERNET
USER
EDUCATION APP
DATABASE
FIREBASE SERVER
17
Page
11.Component Diagram :
Database
Student
<<component>>
Application
<<component>>
Employee Final
18
Page
12. Table Design :
▪ Data Element
Employee employee
13 E_no Employee number 10 It store Chapter It contains
number employee Muster employe
number number
14 E_id Employee number 20 It store Chapter It contain
ID employee Muster employee
number name
15 E_pass Employee text 10 It store Chapter It contain
password employee Muster employee
password password
16 E_gender Employee text 10 It store Chapter It contain
Gender gender of Muster gender of
employee employees
21
Page
Chapter 4: TESTING
Software testing can be defined as the action for checking if the tangible
result or output of product matches with the projected or expected output (of your
client), and testing also ensures that the product is free from any bug or defect.
Testing of software involves the implementation of a module or part of a system
of a product to evaluate all or some of its properties. Through testing, testers can
identify errors, gaps in the requirement, or missing elements in a projector system
(that has been developed). Testing can be done both manually or with the help of
automated tools available in the market.
22
Page
2. Test Cases :
particular point then they can check it multiple times this in-turn gives them
Page
26
Page
➢ BIBLIOGRAPHY :
https://www.google.com
https://1000projects.org
https://developers.com
27
Page
➢ ANNEXURE 1 : USER INTERFACE SCREENS
1. Login Screen :
2. Home Screen:
28
Page
3. Teacher:
29
Page
4. Student:
30
Page
5. Employee:
31
Page
6. Teacher Database:
7. Student Database:
32
Page
8. Employee Database:
9. Help:
33
Page
Page
34