2. Project Overview
This document aims at defining overall software requirement for
STUDENT RESULT MANAGEMENT SYSTEM .Efforts have been made
to define the requirements exhaustively and accurately. The final product
will be having only features/functionalities mentioned in this document and
assumptions for any additional functionality/feature should not be made by
any of the parties involved in developing/testing/implementing /using this
product .
Student Result Management System divided in two modules–
Student
Admin
3. Admin /Student Module
Secure Admin Login
Admin Dashboard
Admin can add/update/ Class
Admin can add/update/ Subjects
Admin can add/update/ Active/Inactive Subject combination with class
Admin can register new student and also edit info of the student
Admin can declare/ edit result of a student.
Admin can add/delete notices.
Admin can change own password
Students-
Student can search their result using valid rollid.
Student can also view the notices.
4. Purpose
This specification document describes the capabilities that will be provided by
the software application STUDENT RESULT MANAGEMENT SYSTEM .
It also states the various constraints by which the system will abide. The
intended audience for this document is the development team, testing team and
end users of the product
Scope
The application will manage the information about various students enrolled in this
course in different years, the subjects offered during different semesters of the course,
the marks obtained by the various students in various subjects in different semesters.
The application will greatly simplify and speed up the result preparation and
management process.
5. Requirement Specification
Hardware Configuration:
Client Side
Server Side
RAM 1 GB
Hard Disk 20GB
Processor 2.0GHz
RAM 512 MB
Hard Disk 10GB
Processor 1.0 GHz
6. Continue.....
Software Requirement:
Client Side
Server Side
Web Browser Google Chrome or any
compatible browser
Operating System Windows or any equivalent OS
Web Server APACHE
Server side Language PHP5.6 or above version
Database Server MySQL
Web Browser Google Chrome or any
compatible browser
Operating System Windows or any equivalent OS
11. Implementation and
System Testing
After all phase have been perfectly done, the system
will be implemented to the server and the system can
be used.
System Testing
The goal of the system testing process was to
determine all faults in our project .The program was
subjected to a set of test inputs and many explanations
were made and based on these explanations it will be
decided whether the program behaves as expected or
not. Our Project went through two levels of testing
Unit testing
Integration testing
21. Conclusion
The package was designed in such a way that future modifications can be
done easily. The following conclusions can be deduced from the development of the
project.
Automation of the entire system improves the efficiency
It provides a friendly graphical user interface which proves to be better when
compared to the existing system.
It gives appropriate access to the authorized users depending on their
permissions.
It effectively overcomes the delay in communications.
Updating of information becomes so easier.
System security, data security and reliability are the striking features.
The System has adequate scope for modification in future if it is necessary
22. Bibliography
The following books were referred during the analysis and execution phase of the
project
PHP and MySQL Web Development
Book by Luke Welling
Head First PHP & MySQL
Book by Lynn Beighley and Michael Morrison
PHP & MySQL for Dummies
Book by Janet Valade
WEBSITES:
www.google.com
www.w3schools.com
www.tutorialspoint.php
https://stackoverflow.com
USECASE DIAGRAM: A Use case is a description of set of sequence of actions. Graphically it is rendered as an ellipse with solid line including only its name. Use case diagram is a behavioral diagram that shows a set of use cases and actors and their relationship. It is an association between the use cases and actors. An actor represents a real-world object. Primary Actor – Sender, Secondary Actor Receiver.
Class Diagram:
A description of set of objects that share the same attributes operations, relationships, and semantics