School Management System

SCHOOL MANAGEMENT SYSTEM PROJECT REPORT | SCHOOL MANAGEMENT SYSTEM

Project Overview

1.1 Description Of the organization:

A school is an institution designed for the teaching of students (or "pupils") under the supervision of teachers. Most countries have systems of formal education, which is commonly compulsory. In these systems, students progress through a series of schools. The names for these schools vary by country, but generally include primary school for young children and secondary school for teenagers who have completed primary education.

In addition to these core schools, students in a given country may also have access to and attend schools both before and after primary and secondary education. Kindergarten or pre-school provide some schooling to very young children (typically ages 3–5). University, vocational school, college or seminary may be available after secondary school. A school may also be dedicated to one particular field, such as a school of economics or a school of dance. Alternative schools may provide nontraditional curriculum and methods.

There are also non-government schools, called private schools. Private schools may be for children with special needs when the government does not supply for them; religious, such as Christian schools, hawzas, yeshivas and others; or schools that have a higher standard of education or seek to foster other personal achievements. Schools for adults include institutions of corporate training and Military education and training.

A school management system is a software application for educational establishments to manage the data. This system provides capabilities for management of students, teachers and staff records. It also provides the capabilities to manage the fee structure, the attendance of the students and teachers.

1.2Organizational Objectives:

· To allow teachers, and school officials to view required reports.

· Handling the admissions process.

· To facilitate teacher attendance record keeping,

· To facilitate student attendance record keeping,

· To manage the data of a particular student or a teacher.

1.3 Functions Provided:

This school management system software provides various services to the user, mentioned below:

· A user account.

· Maintains the profiles of the teachers and the students.

· Maintains the attendance of them.

1.4 Functions/Activities with respect to the proposed system:

Records and Profiles Management: This software has a module dedicated to management of students, teachers and staff records, which makes it useful profile management software. This profile management system captures master data such as name and contact information of the students, parents, teachers and other supporting staff.

Attendance Management: With this, student and teacher attendance becomes very easy to capture and maintain. Reports about absent students or those reporting late can be generated with this attendance management software.

SRS Documentation:

1. Introduction

A software requirements specification (SRS) is a complete description of the behavior of the system to be developed. This Software Requirement Specification is written accordance with the IEEE STD 830-1998 model.

1.1 Purpose

This SRS Document contains the complete software requirements for a School Management System (SMS) and describes the design decisions, architectural design and the detailed design needed to implement the system. It provides the visibility in the design and provides information needed for software support. The intended audiences for this document are the development team, testing team and the end users of the product

1.2 Scope

The software product “School Management System” will be an application that will be used for maintain the records in an organized manner and to replace old paper work system. The application will manage the information about various students and teachers. It is also designed to calculate the attendance record of the teachers and the students and also the annual fee of the students. Specific reports will also be generated regarding the teachers and the students.

1.3 Definitions, Acronyms and Abbreviations

Following abbreviations have been used throughout this document:

IEEE : The Institute of Electrical and Electronics Engineers, Inc.

SRS : Software Requirements Specification

SMS : School Management System

1.4 References

· http://eljabiri1.tripod.com/sitebuildercontent/sitebuilderfiles/Req-Gathering-1-.pdf

· http://www.westfallteam.com/Papers/The_Why_What_Who_When_and_How_Of_Software_Requirements.pdf

· http://en.wikipedia.org/wiki/Requirements_analysis

· http://portal.acm.org/citation.cfm?id=1010800.1010802

· http://en.wikipedia.org/wiki/Secondary_data

· http://brent.tvu.ac.uk/dissguide/hm1u3/hm1u3text3.htm

1.5 Overviews

This document has been prepared in accordance with the IEEE STD 830-1998, IEEE Recommended Practice for Software Requirements Specification. [IEEE 830-1998 (1998)]. It provides the information of Product perspective, Product functions, User characteristics, Constraints, Assumptions and dependencies and specific requirement.

2. The Overall Description

This section of the SRS describes all general factors of the product and its requirements.

2.1 Product Perspective

The application will be a window-based, self contained and independent software product.

2.1.1 System Interfaces

None

2.1.2 User Interfaces

The application that will be developed will have a user friendly and menu based interface. Following screens will be provided:

· A login screen for entering the username and password, so that the authorized user can have an access without any problems.

· There will be a screen which will be displaying the major tasks that the system will be performing i.e. a student profile, teacher profile, and attendance record and fee management.

· All the major tasks mentioned above will have their separate forms and will perform the desired actions.

Following reports will also be generated:

· Student Report

· Teacher Report

2.1.3 Hardware Interfaces

· Screen resolution of at least 800 X 600required for proper and complete viewing of screens. Higher resolution would not be a problem

· Support for printer (dot-matrix/desk-jet/inkjet, etc. – any will do) – that is, appropriate drivers are installed and connected printer will be required for printing of the reports.

· Standalone system or network based – not a concern, as it will be possible to run the application on any of these.

2.1.4 Software Interfaces

· Any window based operating system can be used (windows 95/98/2000/XP/NT)

· Oracle as DBMS for database. Future release of the application will aim at upgrading oracle 8i as the DBMS.

· Visual basic 6 for coding, developing the software.

2.1.5 Communications Interfaces

None

2.1.6 Memory Constraints

At least 64MB RAM and 2GB space on hard disk will be required for running the application.

2.1.7 Operations

The product release will not cover any automated housekeeping aspects of the database. The DBA at the client site (i.e. the hospital) will be responsible for manually deleting old/non required data. Database backup and recovery will also have to be handled by the DBA. However, the system will provide a “RESET SYSTEM” function that will delete (upon confirmation from the administrator) all the existing information from the database.

2.1.8 Site Adaptation Requirements

The terminals at the client site will have to support the hardware and software interfaces specified in the above sections.

2.2 Product Functions

The system will allow access only to authorized users entering the appropriate password. A summary of the major function that the software will perform are as follows:

· A login facility to allow only the authorized users to have an access to the software system. This prevents the unauthorized users to misuse the software.

· User (as Data Entry Operator) will be able to add/delete/modify information about different students and teachers present in the school.

· The reports can also be generated in case a user wants them. The reports will contain all the details about the student or the teacher whose reports are generated. For e.g. their name, id, age, gender, phones no etc.

2.3 User Characteristics

· Educational level: At least graduate should be comfortable with English language.

· Experience: The operator should be well versed about the nature and the processes of the school

· Technical expertise: should be comfortable using general purpose applications on a computer.

2.4 Constraints

· GUI is only in English.

· Login and password is used for identification of user and there is no facility for Guest.

2.5 Apportioning of Requirements

Not required.

3. Specific Requirements

This section contains the software requirements to a level of detail sufficient to enable designers to design the system and the tester to test that system.

3.1 External interfaces

This interface will be the actual interface through which the user will communicate with the application and perform the desired tasks. The following screens will be provided:

Login Screen:

The login screen will be the first screen that a user will face. This screen is responsible to allow the authorized users to access the application. It will accept the username and password from the user and verify it. If the username and password match, then the user will be allowed an access to the application else and error will be raised i.e. ACCESS DENIED. The fields available on this screen will be:

· Username : Varchar2 of length up to 10 characters.

· Password : Number of length up to 15 characters.

Menu Screen:

This screen will display 4 small screens inside of it which will perform the major tasks. In the menu screen we can select any of these three screens and perform the desired actions. The three screens will be, Student Information, Teacher Information, Attendance Management.

Student Information Screen:

The user can add, delete and modify the student record as per his needs. This screen will show the user, information about each and every student present in the school. He can also add a new record in the database if a new student takes admission in the school. The fields available on this screen will be:

· ID : Number of length up to 10 digits

· Name : Varchar2 of length up to 20 digits

· Admission No : Number of length up to 10 digits

· Roll No : Number of length up to 10 digits

· Fathers Name : Varchar2 of length up to 20 digits

· Mothers Name : Varchar2 of length up to 20 digits

· Address : Varchar2of length up to 50 digits

· Gender : Varchar2of length up to 6 digits

· Age : Number of length up to 2 digits

· Phone No : Number of length up to 10 digits

· Date of Birth : Numeric of length up to 10 digits

Teacher Information Screen:

The user can add, delete and modify the teacher record as per his needs. This screen will show the user, information about each and every teacher present in the school. The fields available on this screen will be:

· ID : Number of length up to 10 digits

· Name : Varchar2 of length up to 10 digits

· Address : Varchar2 of length up to 50 digits

· Gender : Varchar2 of length up to 6 digits

· Age : Number of length up to 2 digits

· Marital Status : Varchar2 of length up to 8 digits

· Phone no : Number of length up to 10 digits

· Date of Birth : Number of length up to 10 digits

· Subject : Varchar2 of length up to 10 digits

Attendance Management Form:

This form will allow the user to have an access to the attendance of the students and the teachers. The database will provide the details regarding the attendance of each and every student and teacher present in the school. The fields available on this screen will be:

· ID : Number of length up to 20 digits

· Name : Varchar2 of length up to 20 digits

· No of Days Present : Number of length up to 3 digits

· No of Days Absent : Number of length up to 3 digits

· Total Working Days : Number of length up to 3 digits

3.2 System features

Student Information Management

Description

The system will maintain all the information regarding the students such as Name, Gender, Date of Birth, ID (Unique), Address, Phone no., Age, etc. This system will also allow the user to add/delete/update the information as per his requirements.

Validity checks:

· If you are adding any record then you must give a unique ID number.

· If you are adding any record then you must give a unique roll no. number.

· The phone number must exceed 10 digits.

· The ID field cannot be left blank.

Sequencing information

After a successful login the user will be allow to choose from the options such as Student Information, Teacher Information, Attendance Management. He can choose any one of these. As far as Student Information Management is concerned the user will have to enter the ID of the student in order to generate the desired details. After the ID has been given the user will click on the “Show Record” button and he will be displayed the necessary information about that student.

Teacher Information Management

Description

The system will maintain all the information regarding the teachers such as Name, Gender, Date of Birth, ID (Unique), Address, Phone no., Age, etc. This system will also allow the user to add/delete/update the information as per his requirements.

Validation Checks:

· If you are adding any record then you must give a unique ID number.

· If you are adding any record then you must give a unique roll no. number.

· The phone number must exceed 10 digits.

· The ID field cannot be left blank.

Sequencing information

The user will have to enter the ID in order to get the details about a particular teacher. Then the user will click the “Show Record” button to obtain the necessary details.

Attendance Information Management

Description

The system will maintain all the information regarding the attendance of the teachers and students. The system will maintain the details regarding such as Name, Number of Days Present, No o Days Absent, Total Working Days.

Validation Checks:

· The ID field cannot be left blank.

Sequencing information

The user will have to enter the ID, which can be for a student or a teacher, and the system will generate the details accordingly. The user just has to enter the ID then he has to click the show attendance record button and the necessary details will be shown.

Report generation:

Student Report:

A report will be generated containing the details of all the students. There will be an individual report for each student which will tell the user about his/her ID, Name, Age, Address, Class etc.

Teacher Report

A report will be generated containing the details of all the teachers. There will be an individual report for each teacher which will tell the user about his/her ID, Name, Age, Address, Subject etc.

3.3 Performance Requirements

None

3.4 Design Constraints

None

3.5 Software System Attribute

3.5.1 Security

The application will be password protected. The users will have to enter the correct user name and password in order to access the software.

3.5.2 Maintainability

The system will be designed in a maintainable order. The system can be easily modified and renewed according to the need of the user.

3.5.5 Portability

The system will be easily portable on any windows based application that has oracle installed.

3.6 Logical Database Requirements

The following information will be stored in the database:

· Student Info: ID, Name, Admission No, Roll No, Father’s Name, Mother’s Name, Address, Gender, Age, Phone No, Date of Birth.

· Teacher Info: ID, Name, Address, Gender, Age, Marital Status, Phone No, Date of Birth, Subject.

· Attendance Info: Student ID, Teacher ID, Name

3.7 Other Requirements

None

Chapter 2

System Design

2. System Analysis

Systems analysis is the study of systems sets of interacting entities, including computer systems. This field is closely related to operations research. It is also "an explicit formal inquiry carried out to help someone, referred to as the decision maker, identify a better course of action and make a better decision than he might have otherwise made.

2.1 Block Diagram

2.2 Overview of the system

This software is basically developed for the user so that the user can maintain the records in an organized manner. For this purpose we have created different modules that are dedicated to the management of students, teachers and staff records, also the user can maintain the attendance records which makes it useful management software. This software also stores all fee-related information along with the frequency at which it is collected.

2.2.1 Processes and input output identification

This section contains the details about all the processes that are performed in the software system and also tells us about the input and output identification i.e. what is the input being given and what is the desired output.

· Student and Teacher profile management process: These two processes are responsible to maintain the profiles of the students and the teachers present in the school. All the details regarding each and every student and teacher are kept in their respective modules.

Input: The user will enter the details of a new student or a teacher if the user wants to add a new record, he can also update and delete a particular record.

Process: All the processing regarding the addition, updating and deletion of a record is done here.

Output: The user can see the records of a particular student and teacher.

· Attendance management process: This process is responsible for the attendance of all the students and the teachers present in the school. The user can always keep a check on the attendance of a student or a teacher.

Input: The user has to enter the details of the student or a teacher depending upon his needs, that whether he/she want to look up for a student’s attendance record or a teacher’s attendance record. User will enter the desired details.

Process: The specific record will be searched in the data base.

Output: The user will get the attendance record for a student or a teacher depending upon the input he has given.

2.2.2 Input / Output data description:

Process Name	Input /Output	Data Elements
Teacher Profile	Teacher Details	Name, Address, Gender, Age, Marital_status, Phone_no., date_of_ birth, Subject, Teacher_ID
Student Profile	Student Details	Name, Address, Gender, Age, Phone_no., Date_of_birth, admission_no., roll_no, Student_ID, Fathers_name, Mothers_name
Attendance Management	Attendance Details	Student_ID, Teacher_ID, Name

Table 2.1 Input / Output Data Description

2.3Use Case Diagrams

A use case diagram is defined by and created from a Use-case analysis. Its purpose is to present a graphical overview of the functionality provided by a system in terms of actors, their goals (represented as use cases), and any dependencies between those use cases.

The main purpose of a use case diagram is to show what system functions are performed for which actor. Roles of the actors in the system can be depicted.

2.4ER Diagram

2.5System DFD Up To Two Levels

A data-flow diagram (DFD) is a graphical representation of the "flow" of data through an information system. DFDs can also be used for the visualization of data processing (structured design). Following are the DFD’s up to 2 levels for this software system.

Level-0 DFD

Fig 2.5 Level - 0 DFD

Admin

User Database

Level-1 DFD

Fig 2.5 Level – 1 DFD

Database

SQL> create table login_hunny (username varchar2(20) not null, password varchar2(20) not null);

SQL>desclogin_hunny;

Name Null? Type

----------------------------------------- -------- -------------

USERNAME NOT NULL VARCHAR2(20)

PASSWORD NOT NULL VARCHAR2(20)

Student Profile

SQL>create table student_profile(stud_ID number(10) primary key not null,stud_name varchar2(20) not null,stud_adm_no number(10) unique not null,st_rl_novarchar(10) not null,f_namevarchar(20) not null,m_name varchar2(20)not null,stud_add varchar2(20) not null,gender varchar2(10) not null constraint s_check check (gender in ('Male','Female')),age number(10) not null,ph_no number(10) not null,D_O_Bdate,class varchar2(10) not null);

SQL>descstudent_profile

Name Null? Type

----------------------------------------- -------- -------------

STUD_ID NOT NULL NUMBER(10)

STUD_NAME NOT NULL VARCHAR2(20)

STUD_ADM_NO NOT NULL NUMBER(10)

ST_RL_NO NOT NULL VARCHAR2(10)

F_NAME NOT NULL VARCHAR2(20)

M_NAME NOT NULL VARCHAR2(20)

STUD_ADD NOT NULL VARCHAR2(20)

GENDER NOT NULL VARCHAR2(10)

AGE NOT NULL NUMBER(10)

PH_NO NOT NULL NUMBER(10)

D_O_B DATE

CLASS NOT NULL VARCHAR2(10)

Teacher Profile

create table teacher_profile(teacher_ID number(10) primary key not null,teacher_name varchar2(20) not null,address varchar2(20) not null,gender varchar2(10) not null constraint t_check check (gender in ('Male','Female')),marital_status varchar2(10) not null constraint m_check check (marital_status in ('Single','Married')),phone_no number(10) not null,date_of_birthdate,subject varchar2(10) not null);

SQL>descteacher_profile

Name Null? Type

----------------------------------------- -------- -------------

TEACHER_ID NOT NULL NUMBER(10)

TEACHER_NAME NOT NULL VARCHAR2(20)

ADDRESS NOT NULL VARCHAR2(20)

GENDER NOT NULL VARCHAR2(10)

MARITAL_STATUS NOT NULL VARCHAR2(10)

PHONE_NO NOT NULL NUMBER(10)

DATE_OF_BIRTH DATE

SUBJECT NOT NULL VARCHAR2(10)

Student Attendance

SQL>create table stud_attendance (ID number(10) primary key not null, days_present number(10), Foreign Key (ID) references student_profile(stud_ID));

SQL>descstud_attendance

Name Null? Type

----------------------------------------- -------- -----------

ID NOT NULL NUMBER(10)

DAYS_PRESENT NOT NULL NUMBER(10)

Teacher Attendance

create table student_profile(stud_ID number(10) primary key not null,stud_name varchar2(20) not null,stud_adm_no number(10) unique not null,st_rl_novarchar(10) not null,f_namevarchar(20) not null,m_name varchar2(20)not null,stud_add varchar2(20) not null,gender varchar2(10) not null constraint s_check check (gender in ('Male','Female')),age number(10) not null,ph_no number(10) not null,D_O_Bdate,class varchar2(10) not null);

SQL>descteacher_attendance

Name Null? Type

----------------------------------------- -------- ------------

ID NOT NULL NUMBER(10)

DAYS_PRESENT NUMBER(10)

Interface Design

Login Form

Purpose: This form is responsible for the security of the software. It will not allow any unauthorized access.

Menu Form

Purpose: This form displays the main modules in our project. We can select either one of two.

Student Profile

Purpose: This form is responsible to keep a track of student records. We can add, delete, update, edit any record we want to, that is available in the database. We can also print the reports of the student.

Teacher Form

Student Attendance

Purpose: This form tells us about the percentage of attendance for a particular student. The records are stored in the database, and ID and Name are fetched automatically. We just have to navigate them and click Show Attendance button to show their attendance.

Teacher Attendance

Purpose: This form tells us about the percentage of attendance for a particular teacher. The records are stored in the database, and ID and Name are fetched automatically. We just have to navigate them and click Show Attendance button to show their attendance.

Chapter 3

System Development and Implementation

Login Form

Coding:

Private Sub Command1_Click()

On Error GoTo Label1

User = Text1.Text

pass = Text2.Text

Dim oconn As New ADODB.Connection

Dim rs As New ADODB.Recordset

Dim strSQL As String

strSQL = "SELECT * FROM login_hunny"

Set oconn = New ADODB.Connection

oconn.Open "Provider=MSDAORA.1;Password=1234;User ID=bca1;Data Source=orcl;Persist Security Info=True"

rs.CursorType = adOpenStatic

rs.CursorLocation = adUseClient

rs.LockType = adLockOptimistic

rs.OpenstrSQL, oconn, , , adCmdText

var_pass = rs("PASSWORD")

var_user = rs("USERNAME")

If pass = var_pass And User = var_user Then

menu.Show

Else

MsgBox "Bad Password"

End If

Exit Sub

Label1:

MsgBox "Bad Username"

Text1.Text = ""

Text2.Text = ""

Text1.SetFocus

End Sub

Private Sub Command2_Click()

End

End Sub

Menu Form

Coding:

Private Sub Command1_Click()

menu.Hide

student_profile.Show

End Sub

Private Sub Command2_Click()

menu.Hide

attendance_student.Show

End Sub

Private Sub Command4_Click()

End

End Sub

Student Profile Form

Coding:

Private Sub Command1_Click()

'Adding Records

On Error GoTo Label1

Command9.Enabled = True

Command10.Enabled = False

Command11.Enabled = False

Command12.Enabled = False

Call student_text_unlock

Text3.SetFocus

Adodc1.Recordset.AddNew

Exit Sub

'Error Handling Code

Label1:

If Err.Number = -2147467259 Or Err.Number = 13 Or Text11.Text = "" Then

MsgBox ("Expected Values in Gender Field Are: Male and Female")

Text11.Text = ""

Text11.SetFocus

ElseIfErr.Number = -2147217838 Then

MsgBox ("This ID is already registered, enter another ID")

Text3.Text = ""

Text3.SetFocus

End If

End Sub

Private Sub Command10_Click()

'Move To Previous Record

On Error GoTo Label5:

If Adodc1.Recordset.BOF = True And Adodc1.Recordset.EOF = True Then

MsgBox "No Record Exist", , "School Management System"

Else

Adodc1.Recordset.MovePrevious

If Adodc1.Recordset.BOF = True Then

Adodc1.Recordset.MoveFirst

MsgBox "First Record", , "School Management System"

End If

Exit Sub

'Error Handling Code

Label5:

If Err.Number = -2147217842 Then

Adodc1.Recordset.MoveFirst

End If

End Sub

Private Sub Command11_Click()

'Move To Next Record

On Error GoTo Label6:

If Adodc1.Recordset.BOF = True And Adodc1.Recordset.EOF = True Then

MsgBox "No Record Exist", , "School Management System"

Else

Adodc1.Recordset.MoveNext

If Adodc1.Recordset.EOF = True Then

Adodc1.Recordset.MoveLast

MsgBox "Last Record", , "School Management System"

End If

Exit Sub

'Error Handling Code

Label6:

If Err.Number = -2147217842 Then

Adodc1.Recordset.MoveLast

End If

End Sub

Private Sub Command12_Click()

'Move To Last Record

On Error GoTo Label4

If Adodc1.Recordset.BOF = True And Adodc1.Recordset.EOF = True Then

MsgBox "No Record Exist", , "School Management System"

Else

If Adodc1.Recordset.BOF = True And Adodc1.Recordset.EOF = True Then

MsgBox "Last Record", , "School Management System"

Else

Adodc1.Recordset.MoveLast

End If

Exit Sub

'Error Handling Code

Label4:

If Err.Number = -2147217842 Then

Adodc1.Recordset.MoveLast

End If

End Sub

Private Sub Command2_Click()

'Editing Records

'Unlocking all the text boxes, so the user can

'edit their values at runtime (Calling function from module)

Text3.SetFocus

Call student_text_unlock

End Sub

Private Sub Command3_Click()

'Saving A Record

Command9.Enabled = True

Command10.Enabled = True

Command11.Enabled = True

Command12.Enabled = True

If Text3.Text = "" Or Text4.Text = "" Or Text5.Text = "" Or Text6.Text = "" Or Text7.Text = "" Or Text8.Text = "" Or Text9.Text = "" Or Text10.Text = "" Or Text11.Text = "" Or Text12.Text = "" Or Text13.Text = "" Or Text14.Text = "" Then

MsgBox "Cannot Save Empty Record", , "School Management System"

Else

If IsNumeric(Text3.Text) = True And IsNumeric(Text4.Text) = False And IsNumeric(Text5.Text) = True And IsNumeric(Text6.Text) = True And IsNumeric(Text7.Text) = True And IsNumeric(Text8.Text) = True And IsDate(Text9.Text) = True And IsNumeric(Text10.Text) = False And IsNumeric(Text11.Text) = False And IsNumeric(Text12.Text) = False And IsNumeric(Text13.Text) = False And IsNumeric(Text14.Text) = False Then

Adodc1.Recordset.Update

MsgBox "Record saved successfully", , "School Management System"

Else

MsgBox "Invalid Value ", , " "

End If

End Sub

Private Sub Command4_Click()

'Deleting A Record

On Error GoTo Handler1:

If MsgBox("Are you sure you wan't to delete record", vbOKCancel + vbExclamation, "Deleting Record") = vbOK Then

Adodc1.Recordset.Delete

Adodc1.Recordset.MoveFirst

MsgBox "Record deleted successfully", , "School Management System"

End If

Exit Sub

'Error Handling Code

Handler1:

If Err.Number = 3021 Then

Resume Next

End If

End Sub

Private Sub Command5_Click()

DataReport1.Show

End Sub

Private Sub Command6_Click()

student_profile.Hide

menu.Show

End Sub

Private Sub Command7_Click()

'Show Record with the help of User ID

On Error GoTo Label6

Adodc1.Recordset.MoveFirst

'Taking Teacher ID from the user

If Text1.Text = "" Then

MsgBox ("Please enter the above details")

Else

'Opening connection

Dim strSQL As String

strSQL = "select * from student_profile where stud_id=" & Text1.Text & ""

Set oconn = New ADODB.Connection

oconn.Open "Provider=MSDAORA.1;Password=1234;User ID=bca1;Data Source=orcl;Persist Security Info=True"

rs.CursorType = adOpenStatic

rs.CursorLocation = adUseClient

rs.LockType = adLockOptimistic

rs.OpenstrSQL, oconn, , , adCmdText

'Checking whether the record is available in the database or not

Do While Adodc1.Recordset.Fields("stud_id") <> Text1.Text

If Adodc1.Recordset.Fields("stud_id") = Text1.Text Then

Adodc1.Enabled = True

End If

Adodc1.Recordset.MoveNext

Loop

oconn.Close

End If

Exit Sub

'Error Handling Code

Label6:

If Err.Number = 3021 Then

MsgBox ("There is no such record with this ID")

Adodc1.Recordset.MoveLast

Else

Adodc1.Refresh

End If

End Sub

Private Sub Command8_Click()

'Unlocking all the textboxes, so the user cannot enter any value at runtime

'Calling a function from module

Call student_text_unlock

Call student_clear

Text3.SetFocus

Command10.Enabled = True

Command11.Enabled = True

End Sub

Private Sub Command9_Click()

Adodc1.Refresh

Command10.Enabled = True

Command11.Enabled = True

Command12.Enabled = True

End Sub

Private Sub Form_Load()

'All the text boxes are locked so that the user

'cannot modify their values at runtime

Call student_text_lock

End Sub

Private Sub Option2_Click()

student_profile.Hide

teacher_profile.Show

Option1.Value = True

End Sub

Teacher Profile Form

Coding:

Private Sub Command1_Click()

'Adding Records

On Error GoTo Label1

Command9.Enabled = True

Command10.Enabled = False

Command11.Enabled = False

Command12.Enabled = False

Call teacher_text_unlock

Text3.SetFocus

Adodc2.Recordset.AddNew

Exit Sub

'Error Handling Code

Label1:

If Err.Number = -2147467259 Or Err.Number = 13 Then

MsgBox ("Expected Values in Gender Field Are: Male and Female adn in Status Field are: Single or Married")

Text6.Text = ""

Text6.SetFocus

Text7.Text = ""

'ElseIfErr.Number = -2147217838 Then

' MsgBox ("This ID is already registered, enter another ID")

' Text3.Text = ""

' Text3.SetFocus

End If

End Sub

Private Sub Command10_Click()

'Move To Previous Record

On Error GoTo Label2:

Command9.Enabled = True

Command12.Enabled = True

If Adodc2.Recordset.BOF = True And Adodc2.Recordset.EOF = True Then

MsgBox "No Record Exist", , "School Management System"

Else

Adodc2.Recordset.MovePrevious

If Adodc2.Recordset.BOF = True Then

Adodc2.Recordset.MoveFirst

MsgBox "First Record", , "School Management System"

End If

Exit Sub

'Error Handling Code

Label2:

If Err.Number = -2147217842 Then

Adodc2.Recordset.MovePrevious

End If

End Sub

Private Sub Command11_Click()

'Move To Next Record

On Error GoTo Label3:

Command9.Enabled = True

Command12.Enabled = True

If Adodc2.Recordset.BOF = True And Adodc2.Recordset.EOF = True Then

MsgBox "No Record Exist", , "School Management System"

Else

Adodc2.Recordset.MoveNext

If Adodc2.Recordset.EOF = True Then

Adodc2.Recordset.MoveLast

MsgBox "Last Record", , "School Management System"

End If

Exit Sub

'Error Handling Code

Label3:

If Err.Number = -2147217842 Then

Adodc2.Recordset.MoveNext

End If

End Sub

Private Sub Command12_Click()

'Move To Last Record

On Error GoTo Label4

If Adodc2.Recordset.BOF = True And Adodc2.Recordset.EOF = True Then

MsgBox "No Record Exist", , "School Management System"

Else

If Adodc2.Recordset.BOF = True And Adodc2.Recordset.EOF = True Then

MsgBox "Last Record", , "School Management System"

Else

Adodc2.Recordset.MoveLast

End If

Exit Sub

'Error Handling Code

Label4:

If Err.Number = -2147217842 Then

Adodc2.Recordset.MoveLast

End If

End Sub

Private Sub Command2_Click()

'Editing Records

'Unlocking all the text boxes, so the user can

'edit their values at runtime (Calling function from module)

Call teacher_text_unlock

Text3.SetFocus

End Sub

Private Sub Command3_Click()

'Saving A Record

Command9.Enabled = True

Command10.Enabled = True

Command11.Enabled = True

Command12.Enabled = True

If Text3.Text = "" Or Text4.Text = "" Or Text5.Text = "" Or Text6.Text = "" Or Text7.Text = "" Or Text8.Text = "" Or Text9.Text = "" Or Text10.Text = "" Then

MsgBox "Cannot Save Empty Record", , "School Management System"

Else

If IsNumeric(Text3.Text) = True And IsNumeric(Text4.Text) <> True And IsNumeric(Text5.Text) <> True And IsNumeric(Text6.Text) <> True And IsNumeric(Text7.Text) <> True And IsNumeric(Text8.Text) = True And IsDate(Text9.Text) = True And IsNumeric(Text10.Text) <> True Then

Adodc2.Recordset.Update

MsgBox "Record saved successfully", , "School Management System"

Else

MsgBox "Invalid Value ", , " "

End If

End Sub

Private Sub Command4_Click()

'Deleting A Record

On Error GoTo Label5

If MsgBox("Are you sure you wan't to delete record", vbOKCancel + vbExclamation, "Deleting Record") = vbOK Then

Adodc2.Recordset.Delete

Adodc2.Recordset.MoveFirst

MsgBox "Record deleted successfully", , "School Management System"

End If

Exit Sub

'Error Handling Code

Label5:

If Err.Number = 3021 Then

Resume Next

End If

End Sub

Private Sub Command5_Click()

DataReport2.Show

End Sub

Private Sub Command6_Click()

teacher_profile.Hide

menu.Show

End Sub

Private Sub Command7_Click()

'Show Record with the help of User ID

On Error GoTo Label6

Adodc2.Recordset.MoveFirst

'Taking Teacher ID from the user

If Text1.Text = "" Then

MsgBox ("Please enter the above details")

End If

'Opening connection

Dim strSQL As String

strSQL = "select * from teacher_profile where teacher_id=" & Text1.Text & ""

Set oconn = New ADODB.Connection

oconn.Open "Provider=MSDAORA.1;Password=1234;User ID=bca1;Data Source=orcl;Persist Security Info=True"

rs.CursorType = adOpenStatic

rs.CursorLocation = adUseClient

rs.LockType = adLockOptimistic

rs.OpenstrSQL, oconn, , , adCmdText

'Checking whether the record is available in the database or not

Do While Adodc2.Recordset.Fields("teacher_id") <> Text1.Text

If Adodc2.Recordset.Fields("teacher_id") = Text1.Text Then

Adodc2.Enabled = True

End If

Adodc2.Recordset.MoveNext

Loop

oconn.Close

Exit Sub

'Error Handling Code

Label6:

If Err.Number = 3021 Then

MsgBox ("There is no such record with this ID")

Adodc2.Recordset.MoveLast

Else

Adodc2.Refresh

End If

End Sub

Private Sub Command8_Click()

'Unlocking all the textboxes, so the user cannot enter any value at runtime

'Calling a function from module

Call teacher_text_unlock

Call teacher_clear

Text3.SetFocus

Command10.Enabled = True

Command11.Enabled = True

End Sub

Private Sub Command9_Click()

Adodc2.Refresh

Command9.Enabled = True

Command10.Enabled = True

Command11.Enabled = True

End Sub

Private Sub Form_Load()

'All the text boxes are locked so that the user

'cannot modify their values at runtime

Call teacher_text_lock

End Sub

Private Sub Option1_Click()

teacher_profile.Hide

student_profile.Show

Option2.Value = True

End Sub

Student Attendance

Coding:

Private Sub Command1_Click()

Command10.Enabled = False

'Show Record with the help of User ID

On Error GoTo Label6

Adodc4.Recordset.MoveFirst

'Opening connection

Dim strSQL As String

strSQL = "select * from stud_attendance where id=" & Text1.Text & ""

Set oconn = New ADODB.Connection

oconn.Open "Provider=MSDAORA.1;Password=1234;User ID=bca1;Data Source=orcl;Persist Security Info=True"

rs.CursorType = adOpenStatic

rs.CursorLocation = adUseClient

rs.LockType = adLockOptimistic

rs.OpenstrSQL, oconn, , , adCmdText

'Checking whether the record is available in the database or not

Do While Adodc4.Recordset.Fields("id") <> Text1.Text

If Adodc4.Recordset.Fields("id") = Text1.Text Then

Adodc4.Enabled = True

Else

Adodc4.Recordset.MoveNext

End If

Loop

oconn.Close

Exit Sub

'Error Handling Code

Label6:

If Err.Number = 3021 Then

MsgBox ("There is no attendance entry for this ID")

Command10.Enabled = True

Else

Adodc4.Refresh

End If

End Sub

Private Sub Command10_Click()

new_stud_attendance.Show

End Sub

Private Sub Command2_Click()

DataReport1.Show

End Sub

Private Sub Command3_Click()

menu.Show

attendance_student.Hide

End Sub

Private Sub Command4_Click()

End Sub

Private Sub Command5_Click()

Text4.Text = (Val(Text3.Text) / 253) * 100

End Sub

Private Sub Command6_Click()

Adodc3.Refresh

End Sub

Private Sub Command7_Click()

'Move To Previous Record

On Error GoTo Label1:

If Adodc3.Recordset.BOF = True And Adodc3.Recordset.EOF = True Then

MsgBox "No Record Exist", , "School Management System"

Else

Adodc3.Recordset.MovePrevious

If Adodc3.Recordset.BOF = True Then

Adodc3.Recordset.MoveFirst

MsgBox "First Record", , "School Management System"

End If

Exit Sub

'Error Handling Code

Label1:

If Err.Number = -2147217842 Then

Adodc3.Recordset.MoveFirst

End If

End Sub

Private Sub Command8_Click()

'Move To Next Record

On Error GoTo Label2:

If Adodc3.Recordset.BOF = True And Adodc3.Recordset.EOF = True Then

MsgBox "No Record Exist", , "School Management System"

Else

Adodc3.Recordset.MoveNext

If Adodc3.Recordset.EOF = True Then

Adodc3.Recordset.MoveLast

MsgBox "Last Record", , "School Management System"

End If

Exit Sub

'Error Handling Code

Label2:

If Err.Number = -2147217842 Then

Adodc3.Recordset.MoveLast

End If

End Sub

Private Sub Command9_Click()

'Move To Last Record

On Error GoTo Label3

If Adodc3.Recordset.BOF = True And Adodc3.Recordset.EOF = True Then

MsgBox "No Record Exist", , "School Management System"

Else

If Adodc3.Recordset.BOF = True And Adodc3.Recordset.EOF = True Then

MsgBox "Last Record", , "School Management System"

Else

Adodc3.Recordset.MoveLast

End If

Exit Sub

'Error Handling Code

Label3:

If Err.Number = -2147217842 Then

Adodc3.Recordset.MoveLast

End If

End Sub

Private Sub Option2_Click()

If (Option2.Value = True) Then

attendance_student.Hide

attendance_teacher.Show

Option1.Value = True

End If

End Sub

Teacher Attendance

Coding

Private Sub Command1_Click()

Command10.Enabled = False

'Show Record with the help of User ID

On Error GoTo Label6

Adodc7.Recordset.MoveFirst

'Opening connection

Dim strSQL As String

strSQL = "select * from teacher_attendance where id=" & Text1.Text & ""

Set oconn = New ADODB.Connection

oconn.Open "Provider=MSDAORA.1;Password=1234;User ID=bca1;Data Source=orcl;Persist Security Info=True"

rs.CursorType = adOpenStatic

rs.CursorLocation = adUseClient

rs.LockType = adLockOptimistic

rs.OpenstrSQL, oconn, , , adCmdText

'Checking whether the record is available in the database or not

Do While Adodc7.Recordset.Fields("id") <> Text1.Text

If Adodc7.Recordset.Fields("id") = Text1.Text Then

Adodc7.Enabled = True

Else

Adodc7.Recordset.MoveNext

End If

Loop

oconn.Close

Exit Sub

'Error Handling Code

Label6:

If Err.Number = 3021 Then

MsgBox ("There is no attendance entry for this ID")

Command10.Enabled = True

Else

Adodc7.Refresh

End If

End Sub

Private Sub Command2_Click()

DataReport2.Show

End Sub

Private Sub Command3_Click()

menu.Show

attendance_teacher.Hide

End Sub

Private Sub Command4_Click()

Text4.Text = (Val(Text3.Text) / 253) * 100

End Sub

Private Sub Command6_Click()

Adodc3.Refresh

End Sub

Private Sub Command7_Click()

'Move To Previous Record

On Error GoTo Label1:

If Adodc6.Recordset.BOF = True And Adodc6.Recordset.EOF = True Then

MsgBox "No Record Exist", , "School Management System"

Else

Adodc6.Recordset.MovePrevious

If Adodc6.Recordset.BOF = True Then

Adodc6.Recordset.MoveFirst

MsgBox "First Record", , "School Management System"

End If

Exit Sub

'Error Handling Code

Label1:

If Err.Number = -2147217842 Then

Adodc6.Recordset.MoveFirst

End If

End Sub

Private Sub Command8_Click()

'Move To Last Record

On Error GoTo Label3

If Adodc6.Recordset.BOF = True And Adodc6.Recordset.EOF = True Then

MsgBox "No Record Exist", , "School Management System"

Else

If Adodc6.Recordset.BOF = True And Adodc6.Recordset.EOF = True Then

MsgBox "Last Record", , "School Management System"

Else

Adodc6.Recordset.MoveLast

End If

Exit Sub

'Error Handling Code

Label3:

If Err.Number = -2147217842 Then

Adodc6.Recordset.MoveLast

End If

End Sub

Private Sub Command9_Click()

'Move To Next Record

On Error GoTo Label2:

If Adodc6.Recordset.BOF = True And Adodc6.Recordset.EOF = True Then

MsgBox "No Record Exist", , "School Management System"

Else

Adodc6.Recordset.MoveNext

If Adodc6.Recordset.EOF = True Then

Adodc6.Recordset.MoveLast

MsgBox "Last Record", , "School Management System"

End If

Exit Sub

'Error Handling Code

Label2:

If Err.Number = -2147217842 Then

Adodc6.Recordset.MoveLast

End If

End Sub

Private Sub Option1_Click()

If (Option1.Value = True) Then

attendance_student.Show

attendance_teacher.Hide

Option2.Value = True

End If

End Sub

Data Reports

Student Report

Teacher Report

Chapter 4

4.1 Objectives achieved

In this software we are allowing the teachers, and school officials to view required various reports. This software handles the admission process of students. It helps us to facilitate teacher and student attendance record keeping. It is also maintaining the student and teacher profiles that contain their details. This system also provides the facility to update both student and teacher profile.

4.2 Scopes and Improvements

There can be various amendments that can be made to this system. We can add some other modules to enhance the working of this system. Like fees module can be added that manages the fee structure of students. It will calculate students fees on the basis of some formula.

References.

· http://eljabiri1.tripod.com/sitebuildercontent/sitebuilderfiles/Req-Gathering-1-.pdf

· http://www.westfallteam.com/Papers/The_Why_What_Who_When_and_How_Of_Software_Requirements.pdf

· http://en.wikipedia.org/wiki/Requirements_analysis

· http://portal.acm.org/citation.cfm?id=1010800.1010802

· http://en.wikipedia.org/wiki/Secondary_data

· http://brent.tvu.ac.uk/dissguide/hm1u3/hm1u3text3.htm

FREE DOWNLOAD BCA MCA MANAGEMENT SYSTEM PROJECT SYNOPSIS REPORT WITH SOURCE CODE (ASP.NET PHP JAVA)

FREE DOWNLOAD IGNOU BCA MCA PROJECT, SYNOPSIS AND FINAL REPORT WITH SOURCE CODE

Friday, May 15, 2020