A Presentation On: Student and Examination Management System (Saems)
A Presentation On: Student and Examination Management System (Saems)
INTRODUCTION/PROBLEM UNDERSTANDING
Students & Examinations are the basis of any educational Systems. Thus the informations related to both are the most vital piece for any educational institute. Hence, in this project we are managing the information of the two & restricting the access regarding the same on the basis of who accesses it & what should a user can access or manipulate.
SOLUTION STRATEGY
First, we need requirement gathering and analysis. Then a SRS document should be made for the same on the basis of that analysis. With a goal to transform the SRS to a structure suitable for implementation in some programming language we need to design the model of the project.
SOLUTION STRATEGY(CONTD.)
Then after the design phase we implement the project in some programming language i.e. Coding is done after design. Finally the coded project is then tested for errors. If, any error occurs then its suitably debugged & the system so is an appropriate one. Lastly, we install the software thus prepared to solve the problem of project.
INTRODUCTION
1.
2.
3.
Purpose Overview Environmental Characteristics 3.1 Hardware 3.2 Peripherals 3.3 People
PURPOSE
To solve the purpose of results of various examinations of a university & to implement the grading system in the results .
OVERVIEW
This document is the System Requirements Specifications (SRS) and its purpose is to formally describe the function and performance requirements allocated to the Result Processing. It can be used as a basis of preparing design specification document and system acceptance criteria. The Result Processing Project will provide ease to the College admin who is involved in processing the result. In addition the user can configure the system as per the requirement of the Institution. This SRS fully describes the external behavior of the application or other factors necessary to provide a complete and comprehensive description of the requirements of the software.
DOCUMENT CONVENTIONS
1.2.1 Assumptions: Users are familiar with using a computer. Users system should have windows operating system installed. 1.2.2 Dependencies: 1.1.2.1 Software: Product is web-based application Product may not be available on LINUX platform. 1.2.2.2 Hardware: Minimum display of 800x600 pixels with 16 bit colors
PROJECT SCOPE
This project will meet all the basic requirements of the university regarding the results & in addition will also provide the students an authorization to print their own results at any particular instant of time & also the details of all the students will be achieved by this software.
FUNCTIONAL REQUIREMENTS
We have two users ie a superuser and a user. Userclass1 or SuperUser Userclass2 or User
USERCLASS1:
A superuser can perform any of the following functions:*Insert information for a new student. *Modify the information of a student. *Delete a student record. *Search student(s) record. *Create the result *semester exam *supplementary exam *Display the result
USERCLASS2:
A user can perform any of the following functional requirement:*Display student information. *Display the result.
Software Interface
User InterfaceCommunication Interface
COMMUNICATION INTERFACE
Windows Linux
SOFTWARE INTERFACE
Netbeans 6.9 MySql
COMMUNICATION INTERFACE
Windows based system Linux Based System Java Development Kit Java Runtime Environment
DESIGN PHASE
DESIGN PHASE
The goal of design phase is to transform the requirements specification in to a structure that is suitable for implementation in some programming language. A distinct design approach are being followed in different industries. Traditional design approach and object-oriented design approach. The tradition approach require two different activities to be performed first, a structured analysis of requirement specification is carried out and then this structured analysis is transformed into software design. Structured analysis involves preparing a detailed analysis of the different function to be carried out by the system and identification of the data flow among the different function. After structured analysis, architectural design(high level) and detailed(low level) design are carried out. High-level design involves decomposing the system in to modules. During detailed design, the different modules are designed in greater detail. Object-oriented design is relatively technique. In this technique, various objects that occurs in the problem domain and the solution domain are first identified and different kinds relationship that exists among these objects are identified. This object structure is further refined to obtain the detailed design.
ENTITY-RELATIONSHIP DIAGRAM
DFD(CONTD)
DFD(CONTD)
DFD(CONTD)
DATA DICTIONARY
A
data dictionary lists the purpose of all data items & the definition of all composite data items in terms of their component data items.
DATA DICTIONARY
DATA DICTIONARY(CONTD)
DATA DICTIONARY(CONTD)
DATA DICTIONARY(CONTD)
GUI
MAINFRAME.JAVA
Working on an altogether new testing which have learned in this semester was a great challenging for over learn and we are glad that an achieved it to completion. We learned and gained the hands on experience of Java. It is an important technology which will help a great impact on our professional prospects. It is quite tough to complete such a project within a small time span after learning a new technology. But we have tried a lot to some a point and to make the project concrete. We found some errors while working on this project but the error detection & removal of those had been done by us efficiently. So, it is a great experience to together & complete the project efficiently.
FUTURE SCOPE
This application can be easily implemented under various situations. Some of which can be:
We can add new features as and when we require. Reusability is possible as and when required in this application. There is flexibility in all the modules.
THE END