library management system sds

LAB MANAGEMENT SYSTEM

Software Design Specification

Date of Submission : 11-11-2009

Submitted by:

Neeraj Rohilla (G.L.) (IT/06/367)

Hitesh (IT/06/318)

Vishal (CSE/07/358)

Abhinav vasisht (CSE/07/301)

Amanpreet (CSE/07/203)

Aarti (CSE/07/315)


Table of Contents

1. REVISION HISTORY...............................................................................................................................................................4

3. INTRODUCTION.....................................................................................................................................................5

3.1 DOCUMENT OUTLINE...............................................................................................................................................................5

3.2 DOCUMENT DESCRIPTION.....................................................................................................................................................6

3.2.1 Introduction...................................................................................................................................................................... 6

Contractor........................................................................................................................................................................................ 6

Project Manager......................................................................................................................................................................... 6

Contract Manager..................................................................................................................................................................... 6

Systems Engineer..................................................................................................................................................................... 6

Quality Manager......................................................................................................................................................................... 6

Project Stakeholders............................................................................................................................................................... 6

Project Team................................................................................................................................................................................. 6

3.2.2 System Overview........................................................................................................................................................ 7

4. DESIGN CONSIDERATIONS...........................................................................................................................8

4.1 ASSUMPTIONS AND DEPENDENCIES..................................................................................................................................8

4.2 GENERAL CONSTRAINTS........................................................................................................................................................8

4.3 GOALS AND GUIDELINES.......................................................................................................................................................8

4.5 DEVELOPMENT METHODS.....................................................................................................................................................8

5. ARCHITECTURAL STRATEGIES.............................................................................................................................10

..............................................................................................................................................................................................11

..............................................................................................................................................................................................12

6. SYSTEM ARCHITECTURE..............................................................................................................................17

6.1 SUBSYSTEM ARCHITECTURE..............................................................................................................................................17

7. POLICIES AND TACTICS................................................................................................................................17

8. DETAILED SYSTEM DESIGN.......................................................................................................................17

8.1 CLASSIFICATION...................................................................................................................................................................... 17

8.2 DEFINITION................................................................................................................................................................................18

8.3 RESPONSIBILITIES...................................................................................................................................................................18

8.4 CONSTRAINTS.......................................................................................................................................................................... 19

of 106


8.5 COMPOSITION.......................................................................................................................................................................... 19

LAB MANAGEMENT SYSTEM BASICALLY COMPOSITION OF SIX COMPONENTS THESE ARE:-..............................19

8.6 DATABASE DESIGN................................................................................................................................................................19

8.7 TABLE SCHEMAS.....................................................................................................................................................................24

8.8 CLASS DIAGRAMS AND CLASSES....................................................................................................................................37

8.9 USES/INTERACTIONS.............................................................................................................................................................38

8.10 RESOURCES........................................................................................................................................................................... 38

8.11 PROCESSING..........................................................................................................................................................................39

8.12 INTERFACE/EXPORTS.........................................................................................................................................................40

8.13 DETAILED SUBSYSTEM DESIGN.....................................................................................................................................41

9. SOURCE CODE DETAILS...............................................................................................................................41

10. OUTPUT.................................................................................................................................................................68

11. GLOSSARY........................................................................................................................................................107

12. BIBLIOGRAPHY..............................................................................................................................................107

of 106


1. Revision History

Version Name Reason For Changes Date

1.0 Lab Management system Initial Revision 11-11-2009

of 106


3. IntroductionIt is my desire that a completed software design specification meet the following criteria:

It should be able to adequately serve as training material for new project members, imparting to them enough information and understanding about the project implementation, so that they are able to understand what is being said in design meetings, and won't feel as if they are drowning when they are first asked to create or modify source code.

It should serve as "objective evidence" that the designers and/or implementers are following through on their commitment to implement the functionality described in the requirements specification.

It needs to be as detailed as possible, while at the same time not imposing too much of a burden on the designers and/or implementers that it becomes overly difficult to create or maintain.

3.1 Document OutlineLab management system follow the below outline to describe the project.

Introduction

System Overview

Design Considerations

o Assumptions and Dependencies

o General Constraints

o Goals and Guidelines

o Development Methods

Architectural Strategies

o Data Flow Diagrams

System Architecture

o System architecture diagram

Policies and Tactics

o Password tactics

o Database policies

o ...

Detailed System Design

o classification

o Definition

o Responsibility

o Constraints

o Composition

o Database Design

o Table Schema

o Class diagram and specification

o Uses/interaction

of 106


o Resources

o Interface/exports

o Detailed subsystem design

Glossary

Bibliography

3.2 Document Description

3.2.1 IntroductionThe purpose of Software Design Specification is to make the users understand about the project. So that they come to know about the details of the project. An overview is provided to them so that they can easily use and understand the project.

The scope of this document lies in acceptance by the users for the project. If the project satisfies the requirements of users then it will be accepted by the users and SDS helps the users to understand the project.

The audience for an SRS document can be:

Contractor The Contractor is responsible for developing, updating, and obtaining approval for the SRS, if it is included as a requirement in the contract.

Project ManagerThe Project Manager is responsible for coordinating the efforts of those involved in the SRS development, review, and approval.

Contract ManagerThe Contract Manager verifies that the SRS deliverable is provided, reviewed, and approved.

Systems EngineerThe Systems Engineer may provide input in developing the SRS.

Quality ManagerThe Quality Manager verifies the quality of the SRS.

Project StakeholdersThe project stakeholders are involved in requirements gathering to allow the project team to document and verify their software requirements.

Project TeamThe project team member(s) is responsible for assisting with gathering requirements and developing and reviewing the SRS.

of 106


3.2.2 System Overview

Lab management system module is a solution to computerize all the manual management work of every lab in the college. Lab management system provides the information about the each lab in the college. In this labs are divided into four subparts named as “COMPUTER LABS”, “SCIENCE LABS”, “MECHANICAL LABS”, “ELECTRICAL & ELECTONIC LABS”. Each subpart section lab has its own administrator which has all rights to access the labs information. Each lab under these subsections has its own specific data and information. Like COMPUTETR LAB section holds the information about the number of computer lab with its specified work. Each computer lab distinguished by its working technology environment and each lab have some specific information to manage the labs like “REQUIREMENT SECTION”, “MAINTEANACE SECTION”, “STOCK SECTION”, “DUMB STOCK SECTION”, “NETWORK SECTION”, “SERVER SECTION”,”TIME TABLE SECTION”, “ALLOTMENT SECTION”. In the same way science labs, mechanical labs and electrical labs are managed.

Lab. Management System provides the facility of managing the laboratory assets and maintenance in any institute. It is not a single task but a combination of many activities like:

Addition of Lab Equipments.

Maintenance Register.

Lab Equipment Register

Server Accreditation.

Time Tables for student lab working.

AMC and Maintenance Details

Equipment allotment Register

Various Lab Assistance Reports and details.

Dumb stock details.

Other lab assets (chairs, tables, almirah etc.) records.

Maintenance of Lab requirement details.

All these tasks require a lot of human work and security. Because some of the information can be quite confidential for institute and loss of that information can cause a lot of loss. This module may be the very first activity but other modules depend on it for their functionality. So, such a system is really needed which can ease, simplify and secure these tasks.

of 106


4. Design Considerations

4.1 Assumptions and DependenciesSome of the assumptions that are made in advance are:

Lab Management system handles four different section.

Lab administrator rights bound to its own lab management section.

There are only four lab sections with different lab related data.

A common grading system is used for all the students and companies.

Appropriate software and hardware are available.

An operating system supporting all the hardware and software is available.

4.2 General Constraints End user cannot access intermediate files without login.

If end-user is accessing the intermediate file without login, then he/she can access the secured information without any authority. hence security constraint provides authentication

4.3 Goals and GuidelinesThe main goals of developing this module are:

To make the process of handling data and records more simple.

To reduce the manual work.

To increase the speed of the work.

4.5 Development MethodsThe development model followed to develop this project is SDLC.

SDLC adheres to important phases that are essential for developers, such as planning, analysis, design, and implementation, and are explained in the section below. There are several SDLC Models in existence. The oldest model, that was originally regarded as “the SDLC” is the WATERFALL MODEL

of 106


WATERFALL MODEL: A sequence of stages in which the output of each stage becomes the input for the next. These stages generally follow the same basic steps but many different waterfall methodologies give the steps different names and the number of steps seems to vary between 4 and 7.

The steps can be characterized and divided as follows:

• Project planning, feasibility study, Initiation: To generate a high-level view of the intended project and determine the goals of the project. The feasibility study is sometimes used to present the project to upper management in an attempt to gain funding. Projects are typically evaluated in three areas of feasibility: economical, operational, and technical. Furthermore, it is also used as a reference to keep the project on track and to evaluate the progress.

• Requirements gathering and Systems Analysis: The goal of systems analysis is to find out where the problem is in attempt to fix the system. This step involves breaking down the system in different pieces and drawing diagrams to analyze the situation. Analyses project goals, breaking down functions that need to be created, and attempts to engage users so that definite requirements can be defined.

• Systems design: Functions and operations are described in detail, including screen layouts, business rules, process diagrams and other documentation. The output of this stage will be to describe the new system as a collection of modules or subsystems.

• Coding: Modular and subsystem programming code will be accomplished during this stage. This stage is intermingled with the next in that individual modules will need testing before integration to the main project.

• Testing: The code is tested at various levels. Unit, system and user acceptance testing are often performed. This is a very grey area as many different opinions exist as to what the stages of testing are and how much if any iteration occurs. Iteration is not generally part of the Waterfall model, but usually some occurs at this stage.

• Installation, Implementation or Deployment: The final stage of a project or the initial development, where the software is put into production and is used by the actual business.

• Maintenance, Business as Usual: The life of the system which includes changes and enhancements before the decommissioning or sunset of the system. Maintaining the system is a very important aspect of SDLC. As key personnel change position in the organization, new changes will be implemented, which will require system updates.

of 106


5. Architectural Strategies

of 106


STUDENT /FACULTY (G.U.I)


STUDENT /FACULTY (G.U.I)

COMPUTER ALLOTEMENT

COMPUTER ALLOTEMENT

LAB ATTENDENCE

LAB ATTENDENCE

LAB PRACTICALS

LIST

LAB PRACTICALS

LIST

LAB CHARGESLAB CHARGES

Comp_allotment Lab_charges

Practical_details

Only view

Lab_attendence

TIME TABLE SHEDULE

TIME TABLE SHEDULE

Time_table

Level-0


of 106

PERSON/USER

ADMIN LOGINADMIN LOGIN

LAB MANAGEMENT (G.U.I)LAB MANAGEMENT (G.U.I)

LOGIN TERMINATED

LOGIN INCORRECT

P_ID, PASSWORD

LOGIN CORRECT

LOGIN ACCEPTED


of 106

LAB MANAGEMENT SYSTEM ADMIN (G.U.I)

LAB MANAGEMENT SYSTEM ADMIN (G.U.I)

COMPUTER LABS SECTION

COMPUTER LABS SECTION

SCIENCE LAB SECTION

SCIENCE LAB SECTION

ELECTRICAL & ELECTONICS LABS

ELECTRICAL & ELECTONICS LABS

MECHANICAL LAB SECTION

MECHANICAL LAB SECTION

VIEW, UPDATE, DELETE, INSERT

After correct Admin’s LoginAfter correct Admin’s Login

Level-1.0


of 106

Lab id detailsLab id details

Bt_labid

Equipment id details


Bt_equipid

lab detailslab details

Lab_info

Lab incharge details


Lab_incharge

Stock requirement details


Require_stock

Maintenance stock details


Maintainance_stock

Dumb stock detailsDumb stock details

Dumb_stock

Computer allotment details

Computer allotment details

Comp_allotment

Level-1.1LAB MANAGEMENT SYSTEM

COMP ADMIN (G.U.I)

LAB MANAGEMENT SYSTEM COMP ADMIN (G.U.I)


Network diagramNetwork diagram

Network_daig

Lab charges detailsLab charges details

Lab_charges


of 106


Bt_labid



Bt_equipid


Lab_info



Lab_incharge



Require_stock



Maintainance_stock


Dumb_stock

Level-1.1LAB MANAGEMENT SYSTEM MECHANICAL ADMIN (G.U.I)

LAB MANAGEMENT SYSTEM MECHANICAL ADMIN (G.U.I)



Lab_charges


of 106


Bt_labid



Bt_equipid


Lab_info



Lab_incharge



Require_stock



Maintainance_stock


Dumb_stock

Level-1.1LAB MANAGEMENT SYSTEM

SCIENCE ADMIN (G.U.I)

LAB MANAGEMENT SYSTEM SCIENCE ADMIN (G.U.I)



Lab_charges


Bt_labid


Lab_info



Require_stock


Dumb_stock

Level-1.1


of 106


Bt_labid



Bt_equipid


Lab_info



Lab_incharge



Require_stock



Maintainance_stock


Dumb_stock

Level-1.1LAB MANAGEMENT SYSTEM ELECTRICAL &

ELECTRONICS ADMIN (G.U.I)

LAB MANAGEMENT SYSTEM ELECTRICAL & ELECTRONICS ADMIN (G.U.I)



Lab_charges


6. System Architecture

About System Architecture

6.1 Subsystem ArchitectureIn the lab management systems have four subsystem or sub module these are:-

7. Policies and Tactics Administrators are assigned with their default passwords and they can change it

afterwards.

Password can be changed only after Logging in.

For database we have used MySQL as back end.

For coding of different forms we have used separate files and query strings. A simple HTML form calls a file for insertion in database.

For easy understanding of file operation simple names are used for naming the files.

Every administrator need first login to go in the corresponding section

8. Detailed System Design

8.1 ClassificationLab management system basically covers four main lab sections

Computer lab section

of 106


Electronic lab section

Mechanical lab section

Science lab section


Science lab section


Electronics lab section

Here in the above lab section or you can say sub module have its own administrator.

Lab management system has two sections for faculty and students.

8.2 DefinitionCOMPUTER LAB SECTION-

This lab section holds the information about all the computer lab of the college. And this lab section holds the computer allotment process of each student. L.M.S. contains all the data like requirement stock, reserve stock, complaint stock etc.

ELECTRONIC LAB SECTION-

This lab section hold the electronic lab data like electronic equipment description, practical list of labs, maintained stock, dump stock etc.

MECHANICAL LAB SECTION-

This lab section holds the mechanical lab related data. It holds the information about the equipment, machine uses, requirement stock etc.

SCIENCE LAB SECTION-

Science lab section holds the all science lab data it may physics or chemistry.

STUDENT/FACULTY INTERFACE-

Student and faculty interfaces provide some of facility to student as well as faculty. They can see the time table of any lab, attendance of student, marks, lab charges of each students etc.

8.3 ResponsibilitiesLab management system provides the following services and facility to the end users:-

It has user friendly interface having quick authenticated access to documents. Easily scalable to grow with changing system requirement. Secured check in, check out & updates. Increase the processing speed Minimization the calculation, data entry Easy retrieval of information Easy verification and monitoring of records Preparation of various reports in a short time and at a short notice Reduce manpower More security and safety of data Quick query processing Easy access to data Reliable and efficient

8.4 Constraints Lab Management system handles four different section.

of 106


Lab administrator rights bound to its own lab management section.

There are only four lab sections with different lab related data.

Appropriate software and hardware are available.

An operating system supporting all the hardware and software is available.

8.5 Composition

Lab management system basically composition of six components these are:-COMPUTER LAB SECTION-

This lab section holds the information about the entire computer lab of the college. And this lab section holds the computer allotment process of each student. L.M.S. contains all the data like requirement stock, reserve stock, complaint stock etc.






Science lab section hold the all science lab data it may physics or chemistry.

STUDENT/FACULTY INTERFACE-

Student and faculty interfaces provide some of facility to student as well as faculty. They can see the time table of any lab, attendance of student, marks, lab charges of each students etc.

8.6 Database DesignThe database of the module mainly contains tables and views etc for data. Different features of database design are:

Data is in the form of tables which can be related to each other.

Tables have unique valued attributes to avoid redundancy.

Tables are related to each other through foreign keys.

Data is entered in a proper format allowed by the database engine.

Different operations like insert, update, delete, search and view etc can be performed on database.

E-R DIAGRAM FOR LAB MANAGEMENT SYSTEM

of 106


of 106


HAS HAS

BT_Department

Lab_info

BT_labincharge

A_login

BT_equipid

BT_labid

BT_Branch

Lab_incharge

Require_stock

Maintainance_stock

Dump_stock

Lab_marks

Network_diag

Lab_attendence

Comp_allotment

Practical_details

Reserve_stock

Time_table

Lab_charges

A

B

C

D

E

F

J

I

H

G

K

L

M

N

O

P

S

R

Q


of 106

BR_ID

BR_CODE

BR_NAME

BR_SEATS

A

D_NAMEBD_ID

LAB_NAMECLAB_ID

EQUIP_ID

EQUIP_NAME

EQUIP_CODE

D

P_NAMEEINSTUCT_ID

INSTUCT_NAME

INSTUCT_EMAIL

A_ID

A_PASS

A_NAME

A_EMAIL

A_CONTACT

F

QUANTITY

CONDITION

USES

G

LAB_ID(C)

INSTRUCT_ID

H INSTUCT_NAME(E)

BR_ID(A)

BR_NAME(A)

BR_NAME (A)

D_ID (B)

D_NAME (B)

INSTUCT_CONTACT

INSTUCT_ADDRESS

D_ID (B)

P_ID

EQUIP_NAME (D)

LAB_NAME(C)

LAB_ID(C)

LAB_NAME(C)

EQUIP_ID

REQUR_QUANTITY

IEQUIP_NAME(D)

REMARK

LAB_NAME(C)

D_NAME (B)

EQUIP_ID

FAULT

JEQUIP_NAME(D)

QUANTITY

LAB_NAME(C)

D_NAME (B)

DATE OF FAULT

DAI_PATHOLAB_NAME

EQUIP_ID

KEQUIP_NAME(D)

LAB_NAME(C)


of 106


of 106

CO_ID (J)

Show Tables

Show Foreign key with reference (j)

Show Primary key

Show connector

Show Normal Attribute


8.7 Table schemas

The main tables that were created in the database are:

Name of the tableBT_Branch

Description Different Branch Description

Attribute Description TypeExamples of values

Br_ID ID of branch int(2) 1

Br_Code Code of branch Char(3) CSE

Br_Name Name of branch Varchar(15) Computer Science

Br_Seats Seats available Int(3) 60

Primary KeyBr_ID

Foreign Keys

SQL Codecreate table bt_branch(br_id int(2) primary key,br_code char(3),br_name varchar(15),br_seats int(3));

Name of the tableBT_Department

Description Different Department Description


D_ID Id of department Int(3) 1

D_Name Name of department Varchar(30) computers

Primary KeyD_ID

Foreign Keys

SQL Codecreate table bt_department(d_id int(3) primary key,d_name varchar(30));

of 106


Name of the tableBt_labid

Description Different lab Description


lab_ID Id of lab Int(3) 1

Br_id Branch id Int(2) 1

Br_name Name of branch Varchar(15) Computer

Lab_name Name of lab Varchar(15) Data structure lab

Primary KeyLab_id

Foreign KeysBr_id, Br_name references Bt_branch.

SQL Codecreate table bt_labid(lab_id int(3) primary key,lab_name varchar(15),br_id int(2) references bt_branch,br_name varchar(15) references bt_b

ranch);

Name of the tableBt_equipid

Description Different Equipment Description


Equip_id Id of equipment Int(3) 1

Equip_name Name of eqipment Varchar(25) Monitor

Equip_code Code of eqipment Varchar(20) 223mn76kk

Br_name Name of branch Varchar(15) computer

of 106


Primary Keyequip_id

Foreign KeysBr_name references from bt_branch.

SQL Codecreate table bt_equipid(equip_id int(3) primary key,equip_name varchar(15),equip_code varchar(20),br_name varchar(15) references bt_branch

);

Name of the tableBt_labincharge

Description Different lab incharge Description


Instruct_id Id of lab incharge Int(3) 1

Dept_id Id of department Varchar(3) 1

Dept_name Name of Depatment Varchar(30) computer


Instruct_name Name of instructor Char(25) Rahul boss

Instruct_email Email id of instructor Varchar(30) [email protected]

Instruct_contact Contact number of instructor

Varchar(10) 9813812489

Instruct_address Address of instructor Varchar(35) Vikas puri-16 delhi.

of 106


Primary KeyInstruct_id

Foreign KeysDept_id, Dept_name references from bt_departement..

SQL Codecreate table bt_labincharge(instruct_id int(3) primary key,dept_id varchar(3) references bt_department,dept_name varchar(30) references bt

_department,lab_id int(3),instruct_name char(25),instruct_email varchar(40),instruct_contact varchar(10),instruct_address varchar(50));

Name of the tableA_Login

Description Administrator Login Information


A_ID Use to login admin panel char(4) A001,A002

A_Pass Use to login admin panel

Md5(“”)

Varchar(20) Abc123

A_Name Name of member Varchar(25) MR. kulwant mehta

D_ID Associated department like head of dept

int(3) 2

A_Email Email id of member Varchar(20) [email protected]

A_Contact Phone no of member Char(15) 09999113101

Primary KeyA_ID

Foreign KeysD_ID references from Bt_department.

SQL Codecreate table a_login(a_id char(4) primary key,a_pass varchar(20),a_name varchar(30),d_id int(3) references bt_department,a_email varchar(3

0),a_contact varchar(15));

of 106

mailto:[email protected]


Name of the tableLab_info

Description Different lab information Description




Equip_name name of equipment varchar(25) monitor

quantity quantity of equipment

Int(3) 45

Eq_condition Condition of equipment

char(10) ok

uses Uses of equipment in lab

Varchar(50) For practical prupose

Primary KeyLab id +equip name

Foreign KeysLab_id, lab_name references from Bt_labid & Equip_name references from Bt_equipid

SQL Codecreate table lab_info(lab_id int(3) primary key references bt_labid,lab_name varchar(15) references bt_labid,equip_name varchar(30) ref

erences bt_equipid,quantity int(3),eq_condition varchar(10),uses varchar(50));

Name of the tableRequire_stock

Description Materials purchase/require stock.





of 106



Reqr_quantity Quantity required Int(3) 200

Remark Special Specification Varchar(30) L.G. company dvd

Primary KeyEquip_id

Foreign KeysEquip_id, Equip_name references from Bt_equipid & lab_name references from BT_labid & Dept_name refrences from Bt_department

SQL Codecreate table require_stock(equip_id int(3) primary key references bt_equipid,equip_name varchar(15) references bt_equipid,lab_name varchar

(15) references bt_labid,dept_name varchar(30) references bt_department,req_quantity int(3),remark varchar(30));

Name of the tableMaintainance_stock

Description Complained stock descriptions.



Equip_name name of equipment varchar(25) Monitor


Dept_name Name of Depatment Varchar(30) Computer

Fault Fault description Varchar(40) Interface problem 8088

quantity Quantity of equipment

Int(3) 200

Date of fault Date of fault date 2009-09-09

of 106


Primary KeyEquip_id


SQL CodeCreate table maintain_stock (equip_id int(3) references bt_equipid,equip_name varchar(25) references bt_equipid,lab_name varchar(15) references bt_labid,dept_name varchar(30) references bt_department,fault varchar(40),quantity int(3),date_of_fault date,primary key(equip_id));

Name of the tableReserve_stock

Description Reserved stock descriptions.



Equip_name name of equipment varchar(25) Monitor


Dept_name Name of Depatment Varchar(30) Computer

quantity reserved Quantity Int(3) 200

condition Condition of equipment

char(10) Ok

Primary KeyEquip_id+lab name


SQL CodeCreate table reserve_stock (equip_id int(3) references bt_equipid,equip_name varchar(25) references bt_equipid,lab_name varchar(15) references bt_labid,dept_name varchar(30) references bt_department,fault varchar(40),quantity int(3),condition char(10),primary key(equip_id,lab_name));

of 106


Name of the tabledumb_stock

Description Dump stock descriptions.






quantity Quantity of dumb stock

Int(3) 200

Remark Special Specification Varchar(30) L.G. company dvd

Primary KeyEquip_id+lab name


SQL Codecreate table dumb_stock(equip_id int(3) primary key references bt_equipid,equip_name varchar(15) references bt_equipid,lab_name varchar

(15) references bt_labid,dept_name varchar(30) references bt_department,req_quantity int(3),remark varchar(30));

Name of the tablePractical_details

Description Different practical descriptions




of 106


semester Semester name Char(7) Third

practical Name of practical

Varchar(150) Study of 8086 micro kit.

Primary KeyNo primary key need

Foreign KeysLab_name references from Bt_labid and Br_name references from Bt_branch

SQL Codecreate table practical_details(lab_name varchar(15) references bt_brid,semester char(7),br_name varchar(15) references bt_branch,practical

int(150));

Name of the tableComp_allotment

Description Computer allotment descriptions.



Pc_IPaddress Name of computer

varchar(25) 198.163.01.11

Roll_no Roll no of student

Char(10) CSE/06/001

Name Name of student

Varchar(25) Neha

Primary KeyRoll_no + lab_name

Foreign KeysLab_name references from Bt_labid and roll_no, name references from student_details

SQL Codecreate table comp_allotment (lab_name varchar(15) references bt_labid,pc_ipaddress varchar(25),roll_no char(10) references student_details,name varchar(25),primary key(roll_no,lab_name));

of 106


Name of the tableNetwork_daig

Description Different lab network diagram descriptions.



Diag_path Diagram pathe Varchar(40) C:\mydocument\mydaigrma

Primary KeyLab_name

Foreign KeysLab_name references from Bt_labid

SQL Codecreate table network_diag(lab_name varchar(15) references bt_labid(lab_name),diag_path varchar(40),primary key(lab_name));

Name of the tableLab_attendence

Description Student’s labs attendance descriptions.




Char(10) CSE/06/001


Varchar(25) Neha

attendance Student attendance

Int(2) 24

of 106




SQL Codecreate table lab_attendence( lab_name varchar(15) references bt_labid,roll_no char(10),name varchar(25),attendence int(2),primary key(roll_no,lab_name));

Name of the tableLab_marks

Description Student’s labs marks descriptions.




Char(10) CSE/06/001


Varchar(25) Neha

marks Student marks Int(2) 24



SQL Codecreate table lab_marks(lab_name varchar(15) references bt_labid,roll_no char(10),name varchar(25) references student_details,marks int(2),primary key(roll_no,lab_name));

Name of the tableTime_table

Description Different labs time table descriptions.




of 106


semester Semester name Char(7) Third

Time_table Lab time table Varchar(150) In another module

Primary KeyLab _name

Foreign KeysLab_name references from Bt_labid and Br_name references from Bt_branch

SQL Codecreate table time_table(lab_name varchar(15) references bt_labid,br_name varchar(15) references bt_branch,semester cahr(7),time_table varchar(150),primary key(lab_name));

Name of the tableLab_charges

Description Student’s lab fine descriptions.



Char(10) CSE/06/001


Varchar(25) Neha

charges Student fine in rupees

Int(3) 300

Remark Fine remark Varchar(30) Lab breaking charges

Primary KeyRoll_no


SQL Codecreate table lab_charges(roll_cahr(10) references bt_labid,name varchar(25) references student_details,charges int(3),remark varchar(30),primary key(roll_no))

Graphical User Interface

The Interface was designed keeping the objective in consideration to make it user friendly and provide various functionality in his hands.

Interface include

A Home Page Four separate login pages(for different lab administrator)

Corresponding four different GUI.

of 106


Student and faculty have no need to login they can see the information without login.

8.8 Class Diagrams and ClassesCONCEPTUAL CLASS DAIGRAM OF ADMINISTRATORS AND LAB SECTION CLASS

of 106


8.9 Uses/InteractionsLab management system provide the administer valid id to login.

After valid login an administrator have all rights to take all the features of the corresponding lab sections.

Here the student and faculty can see the time table to give the lab name in the corresponding section. Students can see the attendance, lab marks, lab charges, computer allotment etc.

8.10 ResourcesHardware Requirements

Server Side:

Processor: Pentium 3.0 GHz or higher

RAM: 512 MB or more

Hard Drive: 10 GB or more

Client side:

Processor: Pentium III or 2.0 GHz or higher.

RAM: 256 Mb or more

of 106

ADMINSTRATORS LAB SECTION

COMPUTER ADMIN

MECHANICAL ADMIN

ELECTRONICS ADMIN

SCIENCE ADMIN

COMPUTER LAB

MECHANICAL LAB

ELECTRONICS LAB

SCIENCE LAB

HAVE


Software Requirements

Database/server: MySQL Server, Apache server.

Application: Mozilla Firefox, Google Chrome, Internet Explorer.

Manpower Requirements

6 students have complete this in 6 weeks

8.11 ProcessingIn the lab management system proper login id provided to each lab administrator through that id they can enter in the corresponding lab management system. If administrator have not valid id it give the message not valid to the administrator.

And on the student and faculty side processing there have separate interface for the student and faculty to take the corresponding faculty. Student just feed the roll no and see the lab attendance, lab marks, lab charges etc. processing is done in this sense.

Administrator processing can be described by the diagram

of 106


8.12 Interface/ExportsPhp is used to create the server side pages.

Javascript is used for the validation of the web pages.

Mysql is used to create and manage the database regarding lab management system.

Html is used to design the web pages.

of 106

PERSON/USER

ADMIN LOGINADMIN LOGIN

LAB MANAGEMENT (G.U.I)LAB MANAGEMENT (G.U.I)

LOGIN TERMINATED

LOGIN INCORRECT

P_ID, PASSWORD

LOGIN CORRECT

LOGIN ACCEPTED


Css is used to provide the design according to the need of the application interaction.

Phpide is used to create the server side web pages rapidly.

8.13 Detailed Subsystem DesignLab management system basically covers four main lab subsystems these are:-


Science lab section


Electronics lab section

COMPUTER LAB SECTION-

This lab section holds the information about all the computer lab of the college. And this lab section holds the computer allotment process of each student. L.M.S. contains all the data like requirement stock, reserve stock, complaint stock etc.






Science lab section hold the all science lab data it may physics or chemistry .

9. Source Code Details

S.No Filename SLOC

1. Labmain.php5 110

2. Comadmin_interface.php5 112

3. Electoadmin_interface.php5 130

4. Header.php5 35

5. Mechadmin_interface.php5 118

6. Science_interface.php5 125

7. Computer_lab1.php5 139

of 106


8. Fotter.php5 23

9. Comp_home.php5 95

10. Mech_home.php5 77

11. Electro_home.php5 88

12. Science_home.php5 76

13. Comp_adminconnect.php5 30

14. Logout.php5 12

15. Electroadmin_connect.php5 30

16. Mechadmin_connect.php5 35

17. Scienceadmin_connect.php5 32






23. Electro_lab1.php5 125



26. Mech_lab1.php5 127

27. Mech_lab2.php5 130

28. Science_lab1.php5 77

29. Science_lab2.php5 80

30. Comp_head.php5 129

31. Comp_lab1_info.ph5 43

32. Comp_lab1_req.php5 44

of 106


33. Comp_lab1_dumb.php5 42

34. Comp_lab1_maintain.php5 45

35. Comp_lab1_reserve.php5 44

36. Comp_lab1_marks.php5 45

37. Comp_lab1_incharge.php5 46

38. Comp_lab1_practical.php5 45

39. Comp_lab1_attendence.php5 46

40. Comp_lab1_timetable.php5 47

41. Comp_lab1_allotment.php5 48

42. Comphead2.php5 129
















of 106



























of 106





















102. Electrohead1.php5 113

103. electro_lab1_info.ph5 43

104. electro_lab1_req.php5 44

105. electro_lab1_dumb.php5 42

106. electro_lab1_maintain.php5 45

107. electro_lab1_reserve.php5 44

of 106


108. electro_lab1_marks.php5 45

109. electro_lab1_incharge.php5 46

110. electro_lab1_practical.php5 45

111. electro_lab1_attendence.php5 46

112. electro_lab1_timetable.php5 47





















of 106




135. Mechhead1.php5 125

136. mech_lab2_info.ph5 43

137. mech_lab2_req.php5 44

138. mech_lab2_dumb.php5 42

139. mech_lab2_maintain.php5 45

140. mech_lab2_reserve.php5 44

141. mech_lab2_marks.php5 45

142. mech_lab2_incharge.php5 46

143. mech_lab2_practical.php5 45

144. mech_lab2_attendence.php5 46

145. mech_lab2_timetable.php5 47

146. Mechhead2.php5 125

147. mech_lab1_info.ph5 43

148. mech_lab1_req.php5 44

149. mech_lab1_dumb.php5 42

150. mech_lab1_maintain.php5 45

151. mech_lab1_reserve.php5 44

152. mech_lab1_marks.php5 45

153. mech_lab1_incharge.php5 46

154. mech_lab1_practical.php5 45

155. mech_lab1_attendence.php5 46

156. mech_lab1_timetable.php5 47

157. Sciencehead1.php5 116

of 106


158. science_physics_info.ph5 43

159. science_physics_req.php5 44

160. science_physics_dumb.php5 42

161. science_physics_maintain.php5 45

162. science_physics_reserve.php5 44

163. science_physics_marks.php5 45

164. science_physics_incharge.php5 46

165. science_physics_practical.php5 45

166. science_physics_attendence.php5 46

167. science_physics_timetable.php5 47

168. Sciencehead2.php5 120

169. science_chem_info.ph5 43

170. science_chem_req.php5 44

171. science_chem_dumb.php5 42

172. science_chem_maintain.php5 45

173. science_chem_reserve.php5 44

174. science_chem_marks.php5 45

175. science_chem_incharge.php5 46

176. science_chem_practical.php5 45

177. science_chem_attendence.php5 46

178. science_chem_timetable.php5 47

of 106


Labmain.php5 (Home page)

<html>

<head>

<title>interface</title>

<style type="text/css">

.style1 {

font-family: Arial;

font-size: xx-small;

}

.style2 {

color: black;

}

.style3 {

text-decoration: none;

}

.style6 {

text-align: center;

}

.style7 {

font-family: "Arial Black";

font-size: xx-small;

}

</style>

of 106


</head>

<body bgcolor = "WHITE" >

<img src="pictures\LAB.png" width="100%" height="30%" >

<div id="help" style="width: 95%; height: 3%" class="style6">

<font face="arial" color="white" size="1" style="color: BLACK">

     </font> <span class="style7">

<font color="white" style="color: #FFFFFF">

<a target="_self" href="compadmin_interface.php5" class="style3">

<span class="style2">COMPUTER LAB SECTION </span></a> </font> </span>


    |     </font>

<span class="style7"><font color="white" style="color: BLACK">

<a target="_self" href="electroadmin_interface.php5" class="style3">

<span class="style2">ELECTRONICS LAB SECTION</span></a></font></span><font face="arial" color="white" size="1" style="color: #FFFFFF"><span class="style7"><font color="white" style="color: #FFFFFF"> </font>

</span><span class="style1">


    |     </font>


of 106


<a target="_self" href="mechadmin_interface.php5" class="style3">

<span class="style2">MECHANICAL LAB SECTION</span></a></font></span><font color="white" style="color: #FFFFFF"> </font>


    |     </font>


<a target="_self" href="scienceadmin_interface.php5" class="style3">

<span class="style2">SCIENCE LAB SECTION</span></a></font></span>


    |     </font>


<a target="_self" href="student_interface.php5" class="style3">

<span class="style2">STUDENT LAB SECTION</span></a></font></span>


    |     </font>


<a target="_self" href="student_interface.php5" class="style3">

<span class="style2">FACULTY LAB SECTION</span></a></font></span>

<br>

of 106


<br>

<br>

<br>

<br>

<br>

<br>

<img alt="sbit1" src="pictures\electro2.jpg" width="180" height="140" align="absmiddle" style="border-color: #FFFFFF" border="3">

<img alt="sbit2" src="pictures\lab1.jpg" width="180" height="140" align="absmiddle" border="3" style="border-color: #FFFFFF">

<img src="pictures\science5.jpg" width="180" height="140" align="absmiddle" border="3" style="border-color: #FFFFFF">

<img alt="neeraj1" src="pictures\electro4.jpg" width="180" height="140" align="absmiddle" border="3" style="border-color: #FFFFFF"><br>

</div>

<br/>

<br/>

<br/>

<br/>

<br/>

<br/>

<br/>

<br/>

<br/>

<img alt="" src="pictures\bottomline.png" width="100%" height="3%"><div align="center">

of 106


<a href="jjjjj" style="color: BLACK" class="style3">Contact us</a>

<span class="style2"> | </span> <a href="" class="style3"><span class="style2">Help</span></a>

<div align="center" class="style2">Copyright Â© 2009 Rohilla Group of company. All rights reserved.</div></div>

</body>

</html>

Compadmin_interface.php5 (computer section login page)

<html>

<head>

<title>interface</title>

<script type = "text/javascript" language = "JavaScript">

function check1()

{

if (document.getElementById("ai").value == "")

{

document.getElementById("val1").innerHTML = "<font color='red'>*FIELD REQUIRED</font>";

}

else

document.getElementById("val1").innerHTML = "";

}

function check2()

{

if (document.getElementById("ap").value == "")

{

document.getElementById("val2").innerHTML = "<font color='red'>*FIELD REQUIRED</font>";

of 106


}

else

document.getElementById("val2").innerHTML = "";

}

function home()

{

document.location="labmain.php5";

}

</script>


.style1 {

color: #FFCCCC;

}

.style2 {

color: #FFCCFF;

font-weight: bold;

}

.style3 {

color: #FFCCFF;

}

.style4 {

color: #FF9933;

}

.style5 {

color: #FF9933;

font-weight: bold;

}

.style6 {

text-align: right;

of 106


}

</style>

</head>

<body >

<?php

include_once "header.php5";

?>

<div id="help" align="right" style="width: 95%; height: 3%">

<font face="arial" color="white" size="1" style="color: #FFFFFF">

     </font> <span class="style1">

<font color="white" style="color: #FFFFFF">

<center>

<div align="right">

<input type="button" name="submit" value="HOME" onclick="home();">

</div>

<table cellpadding="0" height="50%" width="100%" color="skyblue">

<caption class="style6">

<br />

<br />

<img alt="sbit1" src="pictures\comp1.jpg" width="180" height="140" align="absmiddle" style="border-color: #FFFFFF" border="3">

<img alt="sbit2" src="pictures\comp3.jpg" width="180" height="140" align="absmiddle" border="3" style="border-color: #FFFFFF">

<img src="pictures\comp5.jpg" width="180" height="140" align="absmiddle" border="3" style="border-color: #FFFFFF">

<img alt="neeraj1" src="pictures\comp4.png" width="180" height="140" align="absmiddle" border="3" style="border-color: #FFFFFF"><br>

<tr>

<td align="right" style="color: #FFCCFF">

of 106


<font ><h2> <span class="style4">COMPUTER ADMIN LOGIN | INTERFACE</span></align></h2> </font></td>

<td bgcolor="white">

</td>

<td>

<table align="right" >

<tr><td colspan="5" align="center" ><font color="red"><?php if(isset($_GET['msg'])) echo $_GET['msg'];?></font></td></tr>

<tr><td>

<form name="Stud" id='Stud' action="compadmin_connect.php5" method="post">

<span class="style5">Admin Id</span><span class="style2"> </span><span class="style3">:&nbsp&nbsp&nbsp</span>&nbsp <input type="text" id = "ai" name = "ai" onblur="check1();" /> </td><td>

<div id="val1">

</div> </td></tr>

<tr><td> <span class="style5">Password :</span><span class="style1">&nbsp </span> <input type="password" id = "ap" name = "ap" onblur="check2();"/></td>

<td>

<div id="val2"></center></div></td></tr>

<tr><td>

<center><input type="submit" value="LOGIN" /></td></tr>

</center>

</form>

</table>

</td></tr></table>

</table>

<?php

include_once "fotter.php5";

of 106


?>

</body>

</html>

Compadmin_connect.php5 (computer section connectivity)

<?php

class login1

{

function insert()

{

$a=$_POST['ai'];

$b=$_POST['ap'] ;

$handle=mysql_connect('localhost','root','SBIT');

$db=mysql_select_db('lms',$handle);

$query="select * from a_login where a_id='$a' and a_pass=md5('$b') and d_id='1'";

$result=mysql_query($query,$handle);

if(mysql_num_rows($result)==1)

{

$row=mysql_fetch_row($result);

@session_start();

$_SESSION['adminname']=$row[2];

$_SESSION['adminid']=$row[0];

echo "<script>document.location='comp_home.php5';</script>";

}

else

{

header("Location: compadmin_interface.php5?msg=Not Valid");

}

}

}

$x=new login1();

of 106


$x->insert();

?>

Comp_home.php5 (computer section Home after valid login)

<?php

@session_start();

if(!isset($_SESSION['adminname']))

{

require_once "labmain.php5" ; exit(0);

}

else{

?>

<html>

<head>

<title>COMPUTER HOME</title>

<script type = "text/javascript" language = "JavaScript">

function lab1()

{

document.location="computer_lab1.php5";

}

function lab2()

{


}

function lab3()

{


}

of 106


<input type="submit" name="logout" value="LOGOUT" style="width: 79px" ></form></td>

</tr>

</table>

<br/>

<div class="style2">

<input type="button" name="li" id="li" value="LAB1" style="width: 122px" onclick="lab1();">

<input name="reqs" id="reqs" type="button" value="LAB2" style="width: 122px" onclick="lab2();">

<input name="dumb" type="button" value="LAB3" style="width: 122px" onclick="lab3();">

<input name="complain" type="button" value="LAB4" style="width: 122px" onclick="lab4();">

<input name="reserve" type="button" value="LAB5" style="width: 122px" onclick="lab5();">

<input name="Button1" type="button" value="LAB6" style="width: 122px" onclick="lab6();">

</div>

<br />

<br />

<br />

<br />





<img alt="neeraj1" src="pictures\comp4.png" width="180" height="140" align="absmiddle" border="3" style="border-color: #FFFFFF">

</div>

<?php

}

of 106



?>

</body>

</html>

Computer_lab1.php5 (click on lab1 in computer section after login)

<?php

@session_start();

if(!isset($_SESSION['adminname']))

{

require_once "labmain.php5" ; exit(0);

}

else{

?>

<html>

<head>

<title>COMPUTER LAB1</title>

<script type="text/javascript">

function home()

{

document.location="comp_home.php5";

}

function lab_info()

{

document.location="comp_lab1_info.php5";

}

function lab_require()

of 106


{

document.location="comp_lab1_req.php5";

}

function lab_dumb()

{

document.location="comp_lab1_dumb.php5";

}

function lab_maintain()

{

document.location="comp_lab1_maintain.php5";

}

function lab_reserve()

{

document.location="comp_lab1_reserve.php5";

}

function lab_incharge()

{

document.location="comp_lab1_incharge.php5";

}

function lab_practical()

{

of 106



.style2 {

text-align: center;

}

.style3 {

text-align: right;

font-size: smaller;

}

.style4 {

margin-left: 0px;

}

.style5 {

margin-left: 0px;

margin-right: 0px;

}

</style>

</head>

<body>

<?php


?>

<table style="width: 99%">

<tr>

<td style="width: 633px"><strong>WELCOME MR. <?php echo $_SESSION['adminname']; ?></strong></td>

<td class="style3"><form action="logout.php5" method="post">

of 106








<input type="submit" name="logout" value="LOGOUT" style="width: 129px" class="style4" >

<input name="back" type="button" value="BACK" style="width: 111px" onclick="home();">

<input name="netdaig" type="button" value="NETWORK DAIGRAM" style="width: 138px">

<input name="compallot" type="button" value="COMPUTER ALLOT" style="width: 131px" class="style5" onclick="lab_allotment();">    </form></td>

</tr>

</table>


<input type="button" name="li" id="li" value="LAB INFORMATION" style="width: 127px" onclick="lab_info();">

<input name="reqs" id="reqs" type="button" value="REQUIRE STOCK" style="width: 122px" onclick="lab_require();">

of 106


<input name="dumb" type="button" value="DUMB STOCK" style="width: 122px" onclick="lab_dumb();">

<input name="complain" type="button" value="COMPALIN STOCK" style="width: 125px" onclick="lab_maintain();">

<input name="reserve" type="button" value="RESERVE STOCK" style="width: 122px" onclick="lab_reserve();">

<input name="Button1" type="button" value="LAB INCHARGE" style="width: 122px" onclick="lab_incharge();">

<input name="practical" type="button" value="PRACTICAL DETAIL" style="width: 130px" onclick="lab_practical();">

<input name="marks" type="button" value="LAB MARKS" style="width: 113px" onclick="lab_marks();">

<input name="attendence" type="button" value="LAB ATTENDENCE" style="width: 138px" onclick="lab_attendence();">

<input name="time_table" type="button" value="TIME TABLE" style="width: 127px" onclick="lab_timetable();">

</div>

<br />

<br />

<br />

<br />





<img alt="neeraj1" src="pictures\comp4.png" width="180" height="140" align="absmiddle" border="3" style="border-color: #FFFFFF">

</div>

of 106


<?php

}


?>

</body>

</html>

logout.php5 (logout button coding)

<?php

if(isset($_POST['logout']))

{

@session_start();

$_SESSION['adminname']=null;

session_unregister('adminname');

session_unset();

session_destroy();

unset($_POST);

echo "<script>

document.location='labmain.php5';

</script>";

}

?>

10. Output

HOME PAGE

of 106


COMPUTER ADMIN LOGIN PAGE

of 106


AFTER VALID LOGIN

of 106


AFTER CLICK ON LAB1 BUTTON

of 106


AFTER CLICK ON LAB INFORMATION BUTTON

of 106


AFTER CLICK ON INSERT BUTTON

of 106


AFTER CLICK ON REQUIREMENT STOCK

of 106


AFTER CLICK ON COMPLAINT STOCK

of 106


AFTER CLICK ON LAB INCHAREGE BUTTON

of 106


AFTER CLICK ON LAB MARKS BUTTON

of 106


ELECRONICS ADMIN LOGIN PAGE

of 106


AFTER VALID LOGIN

of 106


AFTER CLICK ON LAB1 BUTTON

of 106



of 106


AFTER CLICK ON REQUIRMENT STOCK BUTTON

of 106


AFTER CLICK ON DUMB STOCK BUTTON

of 106


AFTER CLICK ON COMPAINT STOCK BUTTON

of 106


AFTER CLICK ON LAB INCHARGE BUTTON

of 106


AFTER CLICK ON LAB ATTENDENCE BUTTON

of 106


MECHANICAL ADMIN LOGIN PAGE

of 106


AFTER VALID LOGIN

of 106


AFTER CLICK ON MACHINE LAB BUTTON

of 106



of 106


AFTER CLICK ON REQUIRE STOCK BUTTON

of 106


SCIENCE ADMIN LOGIN PAGE

of 106


AFTER VALID LOGIN

of 106


AFTER CLICK ON PHYSICS LAB BUTTON

of 106


AFTER CLICK ON CHEMISTRY LAB BUTTON

of 106


AFTER CLICK ON LOGOUT BUTTON

of 106


AFTER CLICK ON STUDENT LAB SECTION LINK

of 106


AFTER CLICK ON STUDENT MARKS BUTTON

of 106


AFTER CLICK ON SUBMIT BUTTON

of 106


AFTER CLCIK ON STUDENT ATTENDECE BUTTON

of 106



of 106


AFTER CLICK ON FACULTY LAB SECTION LINK

of 106


AFTER CLICK ON PRACTICAL DETAILS BUTTON

of 106



of 106


AFTER CLICK ON TIME TABLE BUTTON

of 106



of 106


11. Glossary PHP: Hypertext Preprocessor is a popular general purpose server side scripting language.

It can be embedded into HTML to create a wide variety of mini application, but can also be used to build large scale complex application. A free scripting language that allows web authors to write dynamic web pages

MySQL : MySQL is an open source database s/w based on the SQL vocabulary which can be employed in combination with most server side language, but which is most commonly employed with PHP.SQL is a language that allows for interacting with different Database Management Systems by sending request /query to the system.

XHTML: Extensible Mark Up Language Combination of XML & HTML which provide developers with a language which uses a HTML specification within the constraint of the XML format. This language is more rigid and strict in its rule than HTML.

AJAX : Asynchronous Java and XHTML.In this technology a request can be send internally but the user can still work on it and when a response is obtained then partial updation of user page takes place.

HTML:Hypertext used to structure content on a website. Although the HTML certification contains the means to significantly impact the appearance of the page, HTML should be used exclusively for structure with CSS used to format the page.

JavaScript: Client side programming language which is use to create dynamic web pages. It allows the author to write code that can affect corrective many different aspects of a web page.

CSS: CSS stands for Cascading Style Sheets. This is a document format. This provides a set of style rules which can be incorporated in a XHTML or HTML document

12. BibliographyBooks Referred:

PHP5 power programming- Andi Gutmans, Stigs Saether Bakken,Derick Rethans.

HTML,XHTML,JavaScript By-Ivan Bayross

Internet Fundamentals By-Raymonds GreenLaw

Websites Referred:

http:/www.google.co.in/

http:/www.wikipedia.org/

http:/www.Phptr.com/

http:/www.Joedoson.com/

http:/www.W3Cschools.in/

http:/www.HowStuffWorks.com/

of 106

http://www.google.co.in/



http://www.google.com/



library management system sds

Documents