Srs for Notice Board

SOFTWARE REQUIREMENT SPECIFICATION (MCA NOTICE BOARD) INDEX

1. Introduction 1.1. Purpose 1.2. Product Scope

2. Users of Notice Board

3. Technologies to be used

4. Oerall !escription

". Securit#

$. !%! $.1. &onte't flo( diagra)

*. +,- !iagra)

. Tables

1. Introduction 1.1Purpose

Its a notice board for correspondence and notice regarding to department of Computer Science and Application(MCA). It will improve the former way of  sending notices to the department or any personnel it will save the valuable time of department. it will help head of  department to send notice to the faculty of his department and the faculty will also able to send these notices to the students. Suppose there is a student he wants to view the notice then he can easily able to view the notice with the help of this website with the name of  the sender and the date on which it sent. Only the authenticated student s faculties are able to receive and send the notice if he is not authenticated user then he has to register himself if he/she is related to MCA department. 1.2Product Scope

It will replace the former way of sending notice to any department, institution, company it is the one of the fastest way of sending notice to any department or institution by saving the valuable time which is spend in paper wor which is used formerly.

2. Users of Notice Board

3. Technologies To Be Used !or developing the Admin "otice #oard system the following are used$ %rogramming language$ &ava 'atabase server$ MyS(). *eb Server$ Apache+ omcat-.. *eb technologies$ 0S%, 1M) and 0avaScript.

4. Overall Description  he MCA "otice #oard is internet base Application using  0S%,1M),0A2ASC3I% it has 4 main actors, 1od , Students,  eachers, Admin. Admin is responsible for add and Manage students, teachers and 1O' of department. An 1O' can send notice to eachers and Students, eachers of  the department can send "otice to all students , and also  eachers and Students can view there notice using there )ogin if  they are register in MCA "otice board.

5. Security  he server on which the MCA "otice #oard is deployed will have its own security to prevent unauthori5ed delete access. 2alidation of 6elds is re7uired for register new user. Only 2alid admin Can add and Manage 'ata of users.

6. DFD Context flow diagram

7. E-R Diagram

1 Requirements . Admin Requirement-add students, add teachers, add 1O'. 8sed session Manage students 9:dit, delete;. Manage students 9:dit, delete;. Manage students 9:dit, delete;. <. )ogin/)ogout 9Authenticate user;. =. HOD Requirement +used session Create "otice 9!or eachers and Students;. Send "otice to register student email Id. 4. Teacher Requirement -used session Create "otice 9for Students;. 2iew "otice 9Send by 1O';. >. Student Requirement + used session 2iew "otice 9Send by 1O';.

Software RequirementOperating system I':

$ *indow ?% @ higher.

$ "et #eans -...

!ront end

$ 1M), CSS,0A2A SC3I%.

#ac end

$ 0S%, M S().

)anguage

$ 0ava.

Hardware RequirementIntel %4.> B15 or above. >
1 Data Dictionary "otice able

1O' able

 eachers able

Students able