School Management System Documentation

OVERVIEW

Introduction:

The title of the project is “School Management system”. This project will handle whole the activities of the school. SMS has most of the facilities that a modern school requires to computerize

its day-to-day jobs. It provides facilities to keep the records of student, fees, teaching and non-teaching staff with all their required details along with all required, transaction handling. It has facilities to generate various types of reports, which are required, by the management during normal business operations to operate the business effectively.

Objective:

This project is based on the RDBMS technology. The main objective of this project is to computerize the manual system & reduce the time consumption.

In other words we can say that our project has the following objectives:

• Make all the system computerize
• Reduce time consumption
• Reduce error scope
• All system managements are automated
• Centralized database management
• Easy operations for operator of the system
• No paper work requirement

PROJECT CATEGORY

This project as title “School management system” is comes under the Relational Database Management System (RDBMS). This application is developed with the help of C# and SQL Server. This application can also be run on the network environment so it can be said as network application.

TOOLS/PLATFORM

This project is developed using the tools, which are most suited for development of the Application Package. These tools are as follows: -

1. C# (For front end)
2. SQL Server (For Database Storage as Back end)

HARDWARE & SOFTWARE REQUIREMENT

HARDWARE:

Processor :  Pentium-II or higher

Processor Speed : 533 MHZ

Hard Disk Space : 20 GB (min.)

Ram Memory : 32 MB (64 MB recommended)

SOFTWARE:

Operating System : Windows 95/98/NT/2000

Database Server : SQL SERVER

Front end : C#

 SYSTEM DESIGN

System Design is the solution to the creation of a new system. This is the important aspect made up of several steps. The complete, efficient and successful system should provide the following in succession:

• From where should we start
• Where we have to go
• Where should we stop

If the project is to be successful, we will need answer this question. The answer of these questions is schema manner and is known as system design.

A systematic manner will be followed so as to achieve beneficial result at the end. It involves starting with a vague idea and ultimately developing it up into a useful system. The design phase is transition from a user oriented to a document oriented to the programmers.

Software report can be broken into a series of steps starting with the basic ideas and ending with the finished project.

The steps for the successful project are as follows:

We should define problem completely and the goals should be known before our destination. In the next step, we should specify inputs and outputs of our interest

Then the structure of various database should be designed which will be used during the

Programming. Next, we should design our programs of user friendly nature and always provide a way to the user to read back the origin if he/she find any complex problem at any stage We should know the function of each and every program which will leads us to or helps us to read at the specified goal.

Then we write these individual programs which later on joining solve our problem

Next step involve then testing of these programs and correction – if necessary

At last, linking all the programs in a well-specified manner and combining in the form of a menu, submenu etc. will be our defined problem. Out of these defined steps, few of the major steps will respect to Project.

Scope :

This project will help the management to manage day to day details very easy and secure.

Requirements Summary

The following preliminary lists are based on initial interviews

Business Requirements

The business goal for the application is to manage all the details and reports related to schools.

Business requirements with the following additional details:

• User needs a method to add or modify a new class details.
• User needs a method to view all the class details.
• User needs a method to add or modify a new student details.
• User needs a method to view all the student details.
• Admin need a method to add or modify a new employee.
• Admin need a method to view all the employee details.
• User needs a method to add or modify a new expense details.
• User needs a method to view all the expense details.
• User needs a method to add or modify a new subject details.
• User needs a method to view all the subject details.
• User needs a method to add or modify a new Fee details.
• User needs a method to view the fee details.
• User needs a separate method to add or modify a new attendance record of students and employees.
• User needs a separate method to view all attendance record of students and employees.
• User needs a method to sort all attendance record.
• User needs a method to add or modify a new examination details.
• User needs a method to view all the examination details.
• The application should support the capability to use multi user environment.

User Requirements

User requirements are categorized by user type.

User

• Save the class details in the database.
• Edit or modify the details of class, if required.
• View all the class details.
• Save the student details in the database.
• Edit or modify the details of student, if required.
• View all the student details.
• Save the new expense details in the database.
• Edit or modify the details of new expense, if required.
• View all the new expense details.
• Save the subject details in the database.
• Edit or modify the details of subject, if required.
• View all the subject details.
• Save the fee details in the database.
• Edit or modify the details of fee, if required.
• View all the fee details.
• Save the attendance details of the students and employees in the database.
• Edit or modify the details of attendance details, if required.
• View all the attendance details.
• Save the examination details in the database.
• Edit or modify the details of examination, if required.
• View all the examination details.

Admin

• Save the employee details in the database.
• Edit or modify the details of employee, if required.
• View all the employee details.

 Operational Requirements

The following requirements provide a high-level view of how the system will run:

• Processor usage should not exceed 80 percent during concurrent uses.
• Backups will occur incrementally throughout the day.
• A full weekly backup is required to WORM drives.
• Ensure that information is easy to access either, and meaningful for the user and the company.
• Minimize the technical knowledge that user need to save the student or teacher details, search for any details, and generate various reports.

System Requirements

These are additional constraints from a system perspective:

• Previous details related to all management must be imported in the new system.

• The administrator must be able to monitor everything from the IT department.

• The information must be accessible by everyone in the company as per the rights specify.

Success Criteria

To determine the success of this project, the following metrics can be quantified and used to analyze success factors.

Messaging Automation:

• Save all the valid details – All details should be valid for a better success.

Follow our new blog for latest updates..Click here