School Management System
Software Requirements Specification
Version 1.0
Group Id: <…..
Supervisor Name :< Muhammad Ahmad Lodhi >
Revision History
Date Version Description Author
(dd/mm/yyyy)
05/12/2016 1.0 Scope, Functional and Non- 1: …..
Functional requirement, Use
case diagram, Usage
scenarios, Adopted
Methodology and Work Plan.
Table of Contents
1. Scope (of the project)
2. Functional Requirements Non Functional requirements
3. Use Case Diagram
4. Usage Scenarios
5. Adopted Methodology
6. Work Plan (Use MS Project to create Schedule/Work Plan)
SRS Document
Scope of Project:
The School Management System being web based can be accessed
from anywhere in the world, which enables the student, teacher, parents and
the management be in touch with each other at all times. The need of School
management System is developed for better interaction between students,
teacher, parents and managements. This project will handle whole the
activities of the School. School Management System has most of the
facilities that a modern school requires to computerize its day-to-day jobs. It
provides facilities to keep the record of student, fees, exam, time table,
events, teaching and non-teaching staff will all their required details.
Functional and Non-Functional Requirements:
Functional Requirement:
1: Admin:
Admin shall login.
Admin should create account for teachers, students and parents.
Admin shall add new student, teacher and classes and modify them.
Admin shall manage creation of classes, courses offered and who will
teach that course.
Admin shall generate exams schedule, date sheet, fees and financial
issues.
Admin shall maintain teacher attendance.
Admin shall update school news and events,
Admin shall access all the data about student related.
2: Student:
Student shall login by his/her id.
Student shall view his/her result card.
Student shall view the news events of the school.
Student shall view attendance of their class.
3: Teacher:
Teacher shall login.
Teacher shall view student result card.
Teacher will enter each student marks.
Teacher will maintain attendance of student.
Teacher shall views news event.
Teacher shall views student attendance.
4: Parent:
Parent shall login from anywhere.
Parent shall view attendance of their child.
Parent shall view results/reports cards of their child.
Parents shall view news events of school.
Non-Functional Requirement:
System should be available 24 hours.
System should provide specific information to the specific users.
System should be easy to use.
System should perform all of its functionality excellently and
effectively without any inconvenience.
Operating system(window Xp , seven etc)
Tools(visual studio 2012, SQL server 2012)
Language(C#, .Net)
Use Case Diagram(s):
School Management System
Approved
parent
Create Account
for User
Add
Add Student
Student
Add
Promote Student
Subjects Maintain
Student
Add <<Include>>
Teacher
<
Add Class View Teacher
Maintain View
Login
Generate
Exam
View Parent
Admin
Attendance
Generate
Date sheet
Generate Fees
Student
Maintain
Teacher
Update News
Usage Scenarios:
Use Case Login
Title:
Use Case Id: 1
Description: This use case is about login to the system
Actions Users
: 1: Correct ID and password will be required to login in the
system given by admin.
Alternative In case of forget password users should contact to the
Paths: admin to recover the password.
Pre- All must- required information about the parent should be
Conditions: available
Post- A new account for parent added to the system
Conditions: successfully.
Author: F16…
Exceptions: System should give access to the users after complete
verification.
Use Case Approved Parent Registration
Title:
Use Case Id: 2
Description: This use case is about approving a parent registration.
Actions: By Admin
1: Required information will be taken from student about their
parent.
2: Then admin will create account for them and give detail to
them to login from any location.
Alternative Only register student parent should login
Paths:
Pre- All must- required information about the parent should be
Conditions: available
Post- A new account for parent added to the system successfully.
Conditions:
Author: F1602…
Exceptions: System should create only one account for their parents.
Use Case Create account for User
Title:
Use Case Id: 3
Description: This use case is about creating account for a user who will use
a system.
Actions: By Admin
1: Required information will be taken from students and
teachers.
2: Then admin will create account for them and give detail to
them to login.
Alternative Only register students and teachers should login.
Paths:
Pre- All must- required information about the students and
Conditions: teacher should be available
Post- A new account for student and teacher added to the system
Conditions: successfully.
Author: F1….
Exceptions: System should create only one account for their users.
Use Case Title: Add Student
Use Case Id: 4
Description: This use case is about adding a new student to existing
system in class.
Actions: By Admin
1: Click on “Add Student” button.
2: A form will be appeared.
3: Complete the form with accurate data.
4: After completing the form click on “submit button” to register
in a system.
Alternative The system should check for the un-fill form.
Paths:
Pre- All must- required information about the new student should
Conditions: be available
Post- A new student added to the system successfully.
Conditions:
Author: F16….
Exceptions: System should add a new student just in school timings.
Use Case Title: Promote Student
Use Case Id: 5
Description: This use case is about promoting a student from one class to
upper class after completing the course successfully.
Actions: By Admin
1: Click on “Promote Student” button.
2: Form will be appear.
3: Enter Class name in a form then a list will appear with names
of all students.
4: Then promote those student to the next class who have passed
the class.
5: Then submit the list.
Alternative System should give warning to the admin if admin tries to
Paths: promote fail student.
Pre- All must- required information about the promoting student
Conditions: should be available
Post- A promote student added to the system successfully.
Conditions:
Author: F1….
Exceptions: System should promote only passed students.
Use Case Title: Add Teacher
Use Case Id: 6
Description: This use case is about adding a new Teacher to existing
system in class
Actions: By Admin
1: Click on “Add Teacher” button.
2: A form will be appeared.
3: Complete the form with accurate data.
4: After completing the form click on “submit button” to register
in a system.
Alternative The system should check for the un-fill form.
Paths:
Pre- All must- required information about the new teacher should
Conditions: be available
Post- A new teacher added to the system successfully.
Conditions:
Author: F1….
Exceptions: System should add a new teacher just in school timings.
Use Case Title: Add Class
Use Case Id: 7
Description: This use case is about adding a new class to existing system
in class
Actions: By Admin
1: Click on “Add Class” button.
2: A form will be appeared.
3: Complete the form with accurate data.
4: After completing the form click on “submit button” to register
in a system.
Alternative Paths: It also include Add subject use case in the add class.
Class should be added with particular subjects.
Pre-Conditions: All must- required information about the new class
should be available.
Post-Conditions: A new class added to the system successfully.
Author: F16….
Exceptions: No Exception.
Use Case Title: Maintain Courses
Use Case Id: 8
Description: This use case is about maintaining a new classes after
announcement of new classes.
Actions: By Admin
1: Click on “Maintain courses” button.
2: A form will be appeared.
3: Complete the form with accurate data.
Alternative New Courses should be announce in a free time. Two
Paths: courses should not be given to one teacher with same
timings.
Pre- All must- required information about the maintain courses
Conditions: should be available
Post- A courses added to the system successfully.
Conditions:
Author: F1…
Exceptions: No Exception.
Use Case Title: Generate Exam Schedule
Use Case Id: 9
Description: This use case is about generating a new exam schedule to
existing system.
Actions: By Admin
1: Click on “Generate Exam Schedule” button.
2: A form will be appeared.
3: Complete the form with accurate data.
4: After completing the form click on “submit button” to register
in a system.
Alternative The system should check for the un-fill form.
Paths:
Pre- All must- required information about the new schedule
Conditions: should be available
Post- A new schedule added to the system successfully.
Conditions:
Author: F1….
Exceptions: System should generate a new schedule after finishing
courses.
Use Case Title: Generate Date Sheet
Use Case Id: 10
Description: This use case is about generating a new Date Sheet to
existing system.
Actions: By Admin
1: Click on “Generate Date Sheet” button.
2: A form will be appeared.
3: Complete the form with accurate data.
4: After completing the form click on “submit button” to register
in a system.
Alternative The system should check for the un-fill form.
Paths:
Pre- All must- required information about the new date sheet
Conditions: should be available
Post- A new schedule to the system successfully.
Conditions:
Author: F16….
Exceptions: System should generate a new date sheet after finishing
courses.
Use Case Title: Generate Fees
Use Case Id: 11
Description This use case is about generating a new fees to existing system.
:
Actions: By Admin
1: Click on “Generate fees” button.
2: A form will be appeared.
3: Complete the form with accurate data.
4: After completing the form click on “submit button” to register
in a system.
Alternative The system should check for the un-fill form and should
Paths: generate for a particular and each class.
Pre- All must- required information about the new fees should be
Conditions: available
Post- A new fees to the system successfully.
Conditions:
Author: F160….
Exceptions: System should generate a new fees when new classes starts.
Use Case Maintain Teacher Attendance
Title:
Use Case Id: 12
Description: This use case is about maintaining teacher attendance on
daily basis.
Actions: By Admin
1: Click on “Teacher Attendance” button.
2: A form will be appeared with list of all teachers.
3: Admin should mark them who is present, absent or leave.
4: Then submit the list.
Alternative No alternative paths.
Paths:
Pre- All must- required information about the new attendance
Conditions: should be available
Post- A new day attendance added to the system successfully.
Conditions:
Author: …..
Exceptions: No exceptions.
Use Case Title: Update news
Use Case Id: 13
Description: This use case is about updating news.
Actions: By Admin
1: Click on “update News” button.
2: Enter new news to the system.
3: Then Submit it.
Alternative No alternative paths.
Paths:
Pre- All must- required information about the new news should
Conditions: be available
Post- A new news added to the system successfully.
Conditions:
Author: F16….
Exceptions: No Exception
Use Case Title: Add Student Marks
Use Case Id: 14
Description: This use case is about adding student marks for each
subject.
Actions: By Teacher
1: Click on “Add student marks” button.
2: A sheet will appear.
3: Enter the marks for each student and each subject.
4: Then submit the form.
Alternative System should check the marks of each student and each
Paths: subject to not over exceed.
Pre- All must- required information about the new news should
Conditions: be available
Post- A new news added to the system successfully.
Conditions:
Author: F16….
Exceptions: Marks should be added after completion paper checking.
Use Case Title: Maintain Student Attendance
Use Case Id: 15
Description: This use case is about maintaining Student attendance on
daily basis.
Actions: By Teacher
1: Click on “Student Attendance” button.
2: A form will be appeared with list of all student in a particular
class.
3: Teacher should mark them who is present, absent or leave.
4: Then submit the list.
Alternative No alternative paths.
Paths:
Pre- All must- required information about the new attendance
Conditions: should be available
Post- A new day attendance added to the system successfully.
Conditions:
Author: F1602466E1
Exceptions: No exceptions.
Use Case Title: View Result
Use Case Id: 16
Description: This use case is about viewing result. In this case we see the
result of each student.
Actions: By Teacher, by Parent and by Student.
1: Click on “View Result” button.
2: A form will be appeared.
3: Complete the form with particular student and class.
4: Then submit the form.
Alternative If the student is not in the system then it should give
Paths: warning to the user.
Pre- All must- required information about the view result should
Conditions: be available
Post- A user see the result successfully.
Conditions:
Author: F16….
Exceptions: No exceptions.
Use Case Title: View Events
Use Case Id: 17
Description: This use case is about viewing events. In this case we see the
event or news of holiday, new classes, result announcement
etc.
Actions: By Teacher, by Parent and by Student.
1: Click on “View Events” button.
2: A page will open with news or event.
Alternative No alternate paths.
Paths:
Pre- All must- required information about the view events should be
Conditions: available
Post- A user see the events successfully.
Conditions:
Author: F1….
Exceptions: No exceptions.
Use Case Title: View Attendance
Use Case Id: 18
Description: This use case is about viewing attendance of student. In this
case we see the event or news of holiday, new classes, result
announcement etc.
Actions: By Teacher, by Parent and by Student.
1: Click on “View Attendance” button.
2: Form will be appear.
3: Complete the form with Class name and student name.
4: Submit the form.
5: After submitting a list will be appear.
Alternative 1: Teacher can check the list of all student.
Paths: 2: Student will only check his/her attendance.
3: Parent will only check their child attendance.
Pre- All must- required information about the view Attendance
Conditions: should be available
Post- A user see the events successfully.
Conditions:
Author: …..
Exceptions: No exceptions.
Adopted Methodology
For School Management System I would like VU Process Model which is
the combination of Water Fall Model and Spiral Model.
1: Water Fall Model:
It is also known as Linear Sequential Life cycle Model. It is very simple to
understand and use. In a water fall model each phase must be completed fully before the
next phase can begin. In this model the testing starts only after the development is
completed. It has five stages.
Advantages of Water Fall Model:
This model works for small projects where requirements are very well
understood.
Phases do not overlap.
Disadvantages of Water Fall Model:
It is very difficult to go back once the application is in testing phase.
Not a good model for Object Oriented and Complex project.
High amount of risk and uncertainty.
2: Spiral Model:
The main idea behind this model is to avoid risk as there is always a possibilities of
risk in development of software. So the Spiral model is waterfall plus analysis risk. It has
four stages Panning, risk analysis, development and planning next.
Advantages of Water Fall Model:
Good for large and critical-mission projects.
Additional Function can be added at a later date.
Avoidance of risk is enhanced.
Disadvantages of Water Fall Model:
Does not work well for small projects. Can be a costly model to use.
Project success is highly dependent on the risk analysis phase.
Vu Process Model:
Vu process Model is the combination of water fall and spiral model.
Reason for Choosing Vu Process Model:
The main idea behind choosing Vu process is to get benefits of both Water fall
and spiral model.
It is sequential model with back ward repetition.
If we want to do correction at any phase then we can go back and make changes.
Work Plan (Use MS Project to create Schedule/Work Plan)
The chart was very big so I divided it into two diagram for clearness.
