The document outlines a proposed school management system that would automate key functions like student attendance tracking, timetable generation, and communication between students, teachers, and parents. It would allow remote access and help reduce issues around manual work, time waste, and lack of communication. The system requirements, user roles, use cases, interface designs, database structures, and benefits are all described at a high level. Security measures would also help ensure the right users have access to only relevant data.

1. School Management
System
110 M. Jamshed Mahmood
104 Aaqab Nadeem

3. Problem
Definition
 Student Attendance
 TimeWastage
 StationaryCost
 Maintains Problem
 ManualWork
 Reputation Problem
 Lake of communication

4. ObjectiveAnd
Description
 It is designed for better interaction between students, teachers,
parents & management.This management software very
gracefully handles all the requirements for easy school
management.
 The school management system being web based can be accessed
from anywhere in the world, which enables the students, teachers,
parents & the management be in touch with each other at all
times.

5. Functional
Requirements
 Hardware requirements
 Processor
 Ram
 Hard disk
 Internet Connection
 Software requirements
 Operating system(Windows)
 Compatible Browser

6. Functional
Requirements
 Admin shall login
 Admin shall add new student, teacher, and class and modify them.
 Admin shall update school data.
 Admin shall access all the data about student &Teacher related.
 Admin shall manage the school activity.
 Admin shall generate time table.
 Student shall login by his/her id.
 Teacher shall login by his/her id.
 Student shall view study activity of his class.
 Declare result online.
 Parents shall login through his child id.
 Parents shall view reports of his child.
 Record attendance of students
 Generate various reports

7. Non-
Functional
Requirements
 The system should be easy to use.
 The system should be available 24 hour.
 The system should response at the time
 System should provide specific information to specific user.
 The system should not fail.
 Right information is available to right student and teacher at right
time.

8. Non-
Functional
Requirements
Security requirements are important factors in this system as
classified data will be stored in the database. User validation will be
done during login to insure that the user is valid and that the user
only has access to his or her permission data. General users will only
have access through the user interface.
The system will have consistent interface formats and button sets
for all forms in the application, will have a form based interface for
all data entry and viewing formats, and will generate reports that
are formatted in a table and that should look like the existing
manual report formats for user friendliness.
The system will be easily maintained by the developer or other
authorized trained person and it shall respond as fast as possible in
generating report and producing the timetable.

9. UseCase
Diagram

10. Data flow
diagram

11. Class diagram

12. Sequence
Diagram
(StudentRegistration)

13. Sequence
Diagram
(Attendance)

14. Architecture of
theSystem

15. Interface
Design
(AdminLoginPage)

16. Interface
Design
(MainAdminPage)

17. Interface
Design
(StudentRegistrationForm)

18. Interface
Design
(StudentAttendance)

19. Interface
Design
(Timetable)

20. TestCase

21. Benefits
 Complete automation of all operations
 Centrally stored information with zero redundancy
 Frequent interaction with teachers
 Reliable update on child's attendance, progress report and fee
payment.
 Automated student attendance
 Computerized management of marks and grades
 Access to attendance, timetable, marks, grades and examination
schedule

22. Database
(StudentRegistration)

23. Database
(StudentAttendance)

24. Database
(Timetable)

25. Database
(FeeDetail)

26. Database
(Result)

27. Database
(Payment)