CREATE ACCOUNT

If a new user wants to create a new account then he can create a new account by filling all the details.

Fig 15-Create Account

CHANGE PASSWORD

If a user wants to change his password then he can change the password with the help of this change password option .

Fig 16-Change Password

STUDENT SECTION

The first menu is of students details. It deals with student university roll no, student name, DoB, blood group, date of admin etc. we can update, save, add new student detail, search, update   and finally exit.

Fig 10- Student Details

STUDENT ATTENDENCE

This section deals entire information about student attendance record .Thus it help user to access and maintain attendance regularly.

Fig 11-Student Attendance

FEE RECORD

This section tells about information about the student fees submission, whether the fees has been submitted or is pending. It also tells if the student is a new admission or not..

Fig 12-Fee Record

RESULT RECORD

This section provides a complete information about the result of the student. It ask the user about students rollno and displays the result as per the semester making it convenient to maintain the result information. It also calculates the grand total.

Fig 13-Result Record

DMC

This section provides information about the receiving of the detail marks sheet by the student or not. If dmc is received the correct option is marked .

Fig 14-DMCRecord

 TEACHER SECTION

Under teacher section we have the first menu item teacher profile .It consists details of teacher and the process to add new teacher details and save ,delete, update, search and exit buttons.

Fig 7-Teacher profile

                                     TEACHER ATTENDENCE

It tells about teacher attendance whether teacher is present, absent or is on leave and to store monthly attendance.

Fig 8-Teacher Attendance

                                                    TIME TABLE

It tells about the time table of the teachers. We can update ,search ,insert delete and make changes to the time table

Fig 9-Time Table

OUTPUT SCREENS

WELCOME PAGE

The first screen appears of the project is the welcome screen .It uses a progress bar which tells that how much time is left to open the project.

        

  

              Fig 4- Welcome page

                                                 LOGIN PAGE

The second page appears after welcome screen is the login page. It is used by administrator or the person who have account to see the details.

Fig 5-Login Page

     MAINFRAME

After login the mainframe appears which consist of different frames that are situated on the menu bar. Each menu consists of different menu items and their information.

Fig 6- Mainframe page             

                                         

TESTING

Testing was done after the system was put in place. This was done in two ways namely Unit Testing and integration testing. Test Plan The Software Test Plan (STP) is designed to prescribe the scope, approach, resources, and schedule of all testing activities. The plan will identify items to be tested, the features to be tested, the types of testing to be performed, the personnel responsible for testing, the resources and schedule required to complete testing. The purpose of the software test plan is such as:

To achieve the correct code and ensure all Functional and Design

Requirements are implemented as specified in the documentation.

To provide a procedure for Unit and System Testing.

To identify the test methods for Unit and System Testing.

Process of Test Plan

Identify the requirements to be tested. All test cases shall be derived using the current design specification.

Identify particular test to use to test each module.

Identify the expected results for each test.

Perform the test.

Document the test data, test cases used during the testing process.

The following explain the ways in which testing is done.

Unit Testing

Unit testing was carried out on individual modules of the system to ensure that they are fully functional units. We did this by examining each unit, for example the student profile page. It was checked to ensure that it functions as required and that it adds student’s data and other details and also ensured that this data is sent to the database. The success of each individual unit gave us the go ahead to carryout integration testing. All identified errors were dealt with.

 Integration Testing

We carried out integration testing after different modules had been put together to make a complete system. Integration was aimed at ensuring that modules are compatible and they can be integrated to form a complete working system. For example we tested to ensure that when a user is logged in, he/she is linked to the appropriate page, and also could access the database. 

SOFTWARE DESIGNS

4.1 DATA FLOW DIAGRAM

After interpretation of the data, tables were drawn and process of data determined to guide the researcher of the implementation stage of the project. The tools, which were employed during this methodology stage, were mainly tables, Data Flow Diagrams (DFDs) and Entity Relationship Diagrams (ERDs). The design ensures that only allows authorized users to access the system’s information.

                                                  Fig 1-DFD

4.2 CONTROL FLOW DIAGRAM

 System Architecture This gives a high level view of the new system with the main components of the system and the services they provide and how they communicate. The system is implemented using a three-tier architecture that      comprises of user interface, process management and DBMS.

4.3                                 DATABASE DESIGN
A relational database design was used to design the database. A relational database management system (RDBMS) is an excellent tool for organizing large amount of data and defining the relationship between the datasets in a consistent and understandable way. A RDBMS provides a structure which is flexible enough to accommodate almost any kind of data. Relationships between the tables were defined by creating special columns (keys), which contain the same set of values in each table. The tables can be joined in different combinations to extract the needed data. A RDBMS also offered flexibility that enabled redesign and regeneration of reports from the database without need to re-enter the data. Data dictionaries were used to provide definitions of the data used; these included the final data structures for the various tables and their corresponding data fields, description and sizes .The user application programs and interface were developed using core java language (SQL) and MYSQL.

SQL is a language used to create, manipulate, examine and manage relational databases. SQL was standardized in 1992 so that a program could communicate with most database systems without having to change the SQL commands. Unfortunately one must connect to the database before sending SQL commands and each database vendor has a different interface as well as different extensions of SQL. Though SQL is well suited for manipulating database, it is unsuitable as a

Application language and programmers use it primarily as a means of communicating with databases, another language is needed to feed SQL statements to a database and process results for visual display or report generation. The advantage of java  and mysql  is that you can run their programs easily.

4.3.1 ENTITY-RELATIONSHIP DIAGRAM

                      

         Fig 3- ER Diagram

SOFTWARE AND HARDWARE REQUIREMENTS

Hardware Requirement

HARDWARE	Minimum system requirement
Processor	2.4 GHZ processor speed
Memory	400 MB RAM ( 2 GB Recommended)
Disk space	80 GB (including 20 GB for database Management system)
Display	800 x 600 colors (1024 x 768 High color- 16 bit Recommended)

Table 1.4 Hardware requirement

The table above shows hardware components of the machine that allows the system to function as required for using OFFICE AUTOMATION.

Software Requirements

Software	Minimum system requirement
Operating system	Windows 7 or later
Database management system	MySQL server 5.0 MySQL Server 5.1
Run Time environment	ECLIPSE IDE

Table 1.5 Software Requirement

The table above shows software requirements recommended to enable the system to run as required for using OFICE AUTOMATION System.

 INTRODUCTION TO SQL

SQL (Structured Query Language) is a special purpose programming language designed for managing data held in a relational database management system (RDBMS).

Originally based upon relational algebra and tuple relational calculus, SQL consists of a data definition language and a data manipulation language. The scope of SQL includes data insert, query, update and delete schema creation and modification, and data access control. Although SQL is often described as, and to a great extent is, a declarative language (4GL), it also includes procedural elements.

SQL was one of the first commercial languages for Edgar F. Codd's relational model, as described in his influential 1970 paper "A Relational Model of Data for Large Shared Data Banks".Despite not entirely adhering to the relational model as described by Codd, it became the most widely used database language.

SQL became a standard of the American National Standards Institute (ANSI) in 1986, and of the International Organization for Standards (ISO) in 1987. Since then, the standard has been enhanced several times with added features. Despite these standards, code is not completely portable among different database systems, which can lead to vendor lock-in. The different makers do not perfectly adhere to the standard, for instance by adding extensions, and the standard itself is sometimes ambiguous.

Language elements

The SQL language is subdivided into several language elements, including:

·         Clauses, which are constituent components of statements and queries. (In some cases, these are optional.)

·         Expressions, which can produce either scalar values, or tables consisting of columns and rows of data.

·         Predicates, which specify conditions that can be evaluated to SQL three-valued logic (3VL) (true/false/unknown) or Boolean truth values and which are used to limit the effects of statements and queries, or to change program flow.

·         Queries, which retrieve the data based on specific criteria. This is an important element of SQL.

·         control transactions, program flow, connections, sessions, or diagnostics.

·         SQL statements also include the semicolon (";") statement terminator. Though not required on every platform, it is defined as a standard part of the SQL grammar.

OPERATORS

Operator	Description	Example
=	Equal to	Author = 'Alcott'
<> or !=	Not equal to	Dept <> 'Sales'
>	Greater than	Hire_Date > '2012-01-31'
<	Less than	Bonus < 50000.00
>=	Greater than or equal	Dependents >= 2
<=	Less than or equal	Rate <= 0.05
BETWEEN	Between an inclusive range	Cost BETWEEN 100.00 AND 500.00
LIKE	Match a character pattern	First_Name LIKE 'Will%'
IN	Equal to one of multiple possible values	DeptCode IN (101, 103, 209)
IS or IS NOT	Compare to null (missing data)	Address IS NOT NULL

                                                                 Table 1.3 Operators in SQL