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)
Software Design Specification
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 Page 2 of 106
Software Design Specification
8.4 CONSTRAINTS...............................................................................................................19 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..........................................................................................36
8.9 USES/INTERACTIONS........................................................................................................37 8.10 RESOURCES...............................................................................................................37 8.11 PROCESSING...............................................................................................................38 8.12 INTERFACE/EXPORTS......................................................................................................39 8.13 DETAILED SUBSYSTEM DESIGN..........................................................................................40 9. SOURCE CODE DETAILS............................................................................40 10. OUTPUT.................................................................................................66 11. GLOSSARY...........................................................................................105 12. BIBLIOGRAPHY.....................................................................................106
Page 3 of 106
Software Design Specification
Revision History Version
Name
Reason For Changes
Date
1.0
Lab Management system
Initial Revision
11-11-2009
Page 4 of 106
Software Design Specification
3. Introduction It 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 Outline Lab 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
System Architecture o
Data Flow Diagrams
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
Page 5 of 106
Software Design Specification
o
Resources
o
Interface/exports
o
Detailed subsystem design
Glossary
Bibliography
3.2 Document Description 3.2.1 Introduction The 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 Manager The Project Manager is responsible for coordinating the efforts of those involved in the SRS development, review, and approval. Contract Manager The Contract Manager verifies that the SRS deliverable is provided, reviewed, and approved. Systems Engineer The Systems Engineer may provide input in developing the SRS. Quality Manager The Quality Manager verifies the quality of the SRS. Project Stakeholders The project stakeholders are involved in requirements gathering to allow the project team to document and verify their software requirements. Project Team The project team member(s) is responsible for assisting with gathering requirements and developing and reviewing the SRS.
Page 6 of 106
Software Design Specification
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.
Page 7 of 106
Software Design Specification
4. Design Considerations 4.1 Assumptions and Dependencies Some 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 Guidelines The 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 Methods The 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 Page 8 of 106
Software Design Specification
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.
Page 9 of 106
Software Design Specification
5. Architectural Strategies Level-0
LAB MANAGEMENT SYSTEM STUDENT /FACULTY (G.U.I) Only view
COMPUTER ALLOTEMEN T
LAB ATTENDENCE
LAB PRACTICALS LIST
LAB CHARGES
Lab_attendence Lab_charges
Comp_allotment Practical_details
TIME TABLE SHEDULE
Time_table
Page 10 of 106
Software Design Specification
PERSON/US ER LOGIN TERMINATED
LOGIN INCORRECT
P_ID, PASSWORD
LOGIN CORRECT
ADMIN LOGIN
LOGIN ACCEPTED
LAB MANAGEMENT (G.U.I)
Page 11 of 106
Software Design Specification
Level-1.0 LAB MANAGEMENT SYSTEM ADMIN (G.U.I) VIEW, UPDATE, DELETE, INSERT
After correct Admin’s Login
COMPUTER LABS SECTION
Page 12 of 106
SCIENCE LAB SECTION
ELECTRICAL & ELECTONICS LABS
MECHANICAL LAB SECTION
Software Design Specification
Level-1.1 LAB MANAGEMENT SYSTEM COMP ADMIN (G.U.I) VIEW, UPDATE, DELETE,
INSERT
Lab id details
Equipment id details
Bt_labid
Bt_equipid
lab details
Lab incharge details
Lab_info
Lab_incharg e
Stock requirement details
Maintenance stock details
Require_stock
Maintainance_sto ck
Dumb stock details
Computer allotment details
Dumb_stock
Comp_allotme nt
Network diagram
Lab charges details
Network_daig
Lab_charges
Page 13 of 106
Software Design Specification
Level-1.1 LAB MANAGEMENT SYSTEM MECHANICAL ADMIN (G.U.I) VIEW, UPDATE, DELETE,
INSERT
Lab id details
Equipment id details
Bt_labid
Bt_equipid
lab details
Lab incharge details
Lab_info
Lab_incharg e
Stock requirement details
Maintenance stock details
Require_stock
Maintainance_sto ck
Dumb stock details
Lab charges details
Dumb_stock
Page 14 of 106
Lab_charges
Software Design Specification
Level-1.1
Level-1. LAB MANAGEMENT SYSTEM SCIENCE ADMIN (G.U.I) VIEW, UPDATE, DELETE,
INSERT
Lab id details
Equipment id details
Bt_labid
Bt_equipid
lab details
Lab incharge details
lab
Lab_incharg e
La
Lab_info
Lab
B
Stock requirement details
Maintenance stock details
Require_stock
Maintainance_sto ck
Dumb stock details
Lab charges details
Du d
Lab_charges
Dum
Dumb_stock
Page 15 of 106
req d
Req
Software Design Specification
Level-1.1 LAB MANAGEMENT SYSTEM ELECTRICAL & ELECTRONICS ADMIN (G.U.I) VIEW, UPDATE, DELETE,
INSERT
Lab id details
Equipment id details
Bt_labid
Bt_equipid
lab details
Lab incharge details
Lab_info
Lab_incharg e
Stock requirement details
Maintenance stock details
Require_stock
Maintainance_sto ck
Dumb stock details
Lab charges details
Dumb_stock
Page 16 of 106
Lab_charges
Software Design Specification
6. System Architecture About System Architecture
6.1 Subsystem Architecture In the lab management systems have four subsystem or sub module these are:-
Computer lab section
Electronic lab section
Mechanical lab section
Science lab section
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 Classification Lab management system basically covers four main lab sections
Computer lab section
Page 17 of 106
Software Design Specification
Science lab section
Mechanical 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 Definition COMPUTER LAB SECTIONThis 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 SECTIONThis lab section hold the electronic lab data like electronic equipment description, practical list of labs, maintained stock, dump stock etc. MECHANICAL LAB SECTIONThis lab section holds the mechanical lab related data. equipment, machine uses, requirement stock etc.
It holds the information about the
SCIENCE LAB SECTIONScience lab section holds the all science lab data it may physics or chemistry. STUDENT/FACULTY INTERFACEStudent 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 Responsibilities Lab 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
Page 18 of 106
Software Design Specification
8.4 Constraints 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.
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 SECTIONThis 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. ELECTRONIC LAB SECTIONThis lab section hold the electronic lab data like electronic equipment description, practical list of labs, maintained stock, dump stock etc. MECHANICAL LAB SECTIONThis lab section holds the mechanical lab related data. equipment, machine uses, requirement stock etc.
It holds the information about the
SCIENCE LAB SECTIONScience lab section hold the all science lab data it may physics or chemistry. STUDENT/FACULTY INTERFACEStudent 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 Design The 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.
Page 19 of 106
Software Design Specification
E-R DIAGRAM FOR LAB MANAGEMENT SYSTEM
LAB MANAGEMENT SYSTEM HA S
Page 20 of 106
HA S
Reserve_stock
BT_Branch
A
K
BT_Department
B
L
Dump_stock
BT_labid
C
M
Practical_details
BT_equipid
D
N
Comp_allotment
BT_labincharge
E
O
Network_diag
A_login
F
P
Lab_attendence
Lab_info
G
Q
Lab_marks
Lab_incharge
H
R
Time_table
Require_stock
I
S
Lab_charges
Maintainance_stock
J
Software Design Specification
A_ID A_PASS
BR_ID BR_CODE
A
A_NAME
F
A_EMAIL
BR_NAME
A_CONTACT
BR_SEATS
D_ID (B) P_ID D_ID
B
D_NAME
LAB_ID(C) LAB_NAME(C) LAB_ID
C
LAB_NAME
G
EQUIP_NAME (D) QUANTITY
BR_ID(A) CONDITION
BR_NAME(A) USES
EQUIP_ID
D
EQUIP_NAME
INSTRUCT_ID
EQUIP_CODE
INSTUCT_NAME( E)
BR_NAME (A)
H
LAB_ID(C) LAB_NAME(C)
INSTUCT_ID
E
P_NAME
D_ID (B) D_NAME (B)
EQUIP_ID
I
EQUIP_NAME(D)
LAB_NAME(C)
INSTUCT_NAME INSTUCT_EMAIL
D_NAME (B)
INSTUCT_CONTA CT
REQUR_QUANTI TY
INSTUCT_ADDRE SS
REMARK
EQUIP_ID
J
EQUIP_NAME(D)
LAB_NAME(C) D_NAME (B) FAULT QUANTITY DATE OF FAULT
Page 21 of 106
Software Design Specification
LAB_NAME EQUIP_ID
O
DAI_PATH
EQUIP_NAME(D)
K
LAB_NAME(C) D_NAME (B)
ROLL_NO
QUANTITY
P
CONDITION
LAB_NAME NAME ATTENDENCE
EQUIP_ID EQUIP_NAME(D)
L
ROLL_NO
LAB_NAME(C)
Q
LAB_NAME
D_NAME (B)
NAME
QUANTITY
MARKS
REMARK LAB_NAME
R M
BR_NAME(A)
LAB_NAME(C)
SEMESTER
BR_NAME(A)
TIME_TABLE
SEMESTER PRACTICAL
ROLL_NO
S
NAME CHARGES REMARKS
ROOL_NO
N
LAB_NAME PC_IPADDRESS NAME
Page 22 of 106
Software Design Specification
Show Tables
Show Foreign key with reference (j) CO_ID (J)
Show Primary key Show Normal Attribute
Show connector
Page 23 of 106
Software Design Specification
8.7 Table schemas The main tables that were created in the database are:
Name of the table
BT_Branch
Description
Different Branch Description
Attribute
Description
Type
Br_ID
ID of branch
int(2)
Examples of values 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 Key
Br_ID
Foreign Keys SQL Code
create table bt_branch(br_id int(2) primary char(3),br_name varchar(15),br_seats int(3));
Name of the table
BT_Department
key,br_code
Description
Different Department Description
Attribute
Description
Type
D_ID
Id of department
Int(3)
Examples of values 1
D_Name
Name of department
Varchar(30)
computers
Primary Key
D_ID
Foreign Keys SQL Code
Page 24 of 106
create table varchar(30));
bt_department(d_id
int(3)
primary
key,d_name
Software Design Specification
Bt_labid
Name of the table Description
Different lab Description
Attribute
Description
Type
lab_ID
Id of lab
Int(3)
Examples of values 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
Lab_id
Primary Key
Br_id, Br_name references Bt_branch.
Foreign Keys
create 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
SQL Code
ranch);
Name of the table
Bt_equipid
Description
Different Equipment Description
Attribute
Description
Type
Equip_id
Id of equipment
Int(3)
Examples of values 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
Primary Key Foreign Keys SQL Code
equip_id Br_name references from bt_branch. create table bt_equipid(equip_id int(3) primary key,equip_name varchar(15),equip_code varchar(20),br_name varchar(15) references bt_branch );
Page 25 of 106
Software Design Specification
Bt_labincharge
Name of the table Description
Different lab incharge Description
Attribute
Description
Type
Instruct_id
Id of lab incharge
Int(3)
Examples of values 1
Dept_id
Id of department
Varchar(3)
1
Dept_name
Name of Depatment
Varchar(30)
computer
lab_ID
Id of lab
Int(3)
1
Instruct_name
Name of instructor
Char(25)
Rahul boss
Instruct_email
Email id of instructor
Varchar(30)
[email protected]
Instruct_contact
Contact number instructor
Varchar(10)
9813812489
Instruct_address
Address of instructor
Varchar(35)
Vikas puri-16 delhi.
of
Instruct_id
Primary Key
Dept_id, Dept_name references from bt_departement..
Foreign Keys
create table bt_labincharge(instruct_id int(3) primary key,dept_id varchar(3) references bt_department,dept_name varchar(30) references bt
SQL Code
_department,lab_id int(3),instruct_name char(25),instruct_email varchar(40),instruct_contact varchar(10),instruct_address varchar(50));
Name of the table Description
A_Login Administrator Login Information
Attribute
Description
Type
A_ID
Use to login admin panel
char(4)
A001,A002
A_Pass
Use to login admin panel
Varchar(20)
Abc123
Page 26 of 106
Examples of values
Software Design Specification
Md5(“”) 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 Key Foreign Keys SQL Code
A_ID D_ID references from Bt_department. create 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));
Name of the table
Lab_info
Description
Different lab information Description
Attribute
Description
Type
lab_ID
Id of lab
Int(3)
Examples of values 1
Lab_name
Name of lab
Varchar(15)
Data structure lab
Equip_name
name of equipment
varchar(25)
monitor
quantity
quantity equipment
of
Int(3)
45
Eq_condition
Condition equipment
of
char(10)
ok
uses
Uses of equipment in lab
Varchar(50)
For practical prupose
Page 27 of 106
Software Design Specification
Primary Key
Lab id +equip name
Foreign Keys
Lab_id, lab_name references from Bt_labid & Equip_name references from Bt_equipid
SQL Code
create 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 varchar(50));
int(3),eq_condition
varchar(10),uses
Name of the table
Require_stock
Description
Materials purchase/require stock.
Attribute
Description
Type
Equip_id
Id of equipment
Int(3)
Examples of values 1
Equip_name
name of equipment
varchar(25)
monitor
Lab_name
Name of lab
Varchar(15)
Data structure lab
Dept_name
Name of Depatment
Varchar(30)
computer
Reqr_quantity
Quantity required
Int(3)
200
Remark
Special Specification
Varchar(30)
L.G. company dvd
Primary Key
Equip_id
Foreign Keys
Equip_id, Equip_name references from Bt_equipid & lab_name references from BT_labid & Dept_name refrences from Bt_department
SQL Code
create 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) bt_department,req_quantity int(3),remark varchar(30));
Page 28 of 106
references
Software Design Specification
Name of the table
Maintainance_stock
Description
Complained stock descriptions.
Attribute
Description
Type
Equip_id
Id of equipment
Int(3)
Examples of values 1
Equip_name
name of equipment
varchar(25)
Monitor
Lab_name
Name of lab
Varchar(15)
Data structure lab
Dept_name
Name of Depatment
Varchar(30)
Computer
Fault
Fault description
Varchar(40)
Interface problem 8088
quantity
Quantity equipment
Int(3)
200
Date of fault
Date of fault
date
2009-09-09
Primary Key Foreign Keys
SQL Code
of
Equip_id Equip_id, Equip_name references from Bt_equipid & lab_name references from BT_labid & Dept_name refrences from Bt_department Create 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 table
Reserve_stock
Description
Reserved stock descriptions.
Attribute
Description
Type
Equip_id
Id of equipment
Int(3)
Examples of values 1
Equip_name
name of equipment
varchar(25)
Monitor
Page 29 of 106
Software Design Specification
Lab_name
Name of lab
Varchar(15)
Data structure lab
Dept_name
Name of Depatment
Varchar(30)
Computer
quantity
reserved Quantity
Int(3)
200
condition
Condition equipment
char(10)
Ok
Primary Key Foreign Keys
SQL Code
of
Equip_id+lab name Equip_id, Equip_name references from Bt_equipid & lab_name references from BT_labid & Dept_name refrences from Bt_department Create 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));
Name of the table
dumb_stock
Description
Dump stock descriptions.
Attribute
Description
Type
Equip_id
Id of equipment
Int(3)
Examples of values 1
Equip_name
name of equipment
varchar(25)
monitor
Lab_name
Name of lab
Varchar(15)
Data structure lab
Dept_name
Name of Depatment
Varchar(30)
computer
quantity
Quantity stock
Int(3)
200
Remark
Special Specification
Varchar(30)
L.G. company dvd
Page 30 of 106
of
dumb
Software Design Specification
Primary Key
Equip_id+lab name
Foreign Keys
Equip_id, Equip_name references from Bt_equipid & lab_name references from BT_labid & Dept_name refrences from Bt_department
SQL Code
create 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) bt_department,req_quantity int(3),remark varchar(30));
Name of the table
Practical_details
Description
Different practical descriptions
Attribute
Description
Type
Lab_name
Name of lab
Varchar(15)
Examples of values Data structure lab
Br_Name
Name of branch
Varchar(15)
Computer Science
semester
Semester name
Char(7)
Third
practical
Name practical
Varchar(150)
Study of 8086 micro kit.
Primary Key
of
references
No primary key need
Foreign Keys
Lab_name references from Bt_labid and Br_name references from Bt_branch
SQL Code
create table practical_details(lab_name varchar(15) bt_brid,semester char(7),br_name varchar(15) bt_branch,practical int(150));
Page 31 of 106
references references
Software Design Specification
Name of the table
Comp_allotment
Description
Computer allotment descriptions.
Attribute
Description
Type
Lab_name
Name of lab
Varchar(15)
Examples of values Data structure lab
Pc_IPaddress
Name computer
of
varchar(25)
198.163.01.11
Roll_no
Roll no student
of
Char(10)
CSE/06/001
Name
Name student
of
Varchar(25)
Neha
Primary Key
Roll_no + lab_name
Foreign Keys
Lab_name references from Bt_labid and roll_no, name references from student_details
SQL Code
create 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));
Name of the table
Network_daig
Description
Different lab network diagram descriptions.
Attribute
Description
Type
Lab_name
Name of lab
Varchar(15)
Examples of values Data structure lab
Diag_path
Diagram pathe
Varchar(40)
C:\mydocument\mydaigrma
Primary Key Foreign Keys SQL Code
Page 32 of 106
Lab_name Lab_name references from Bt_labid create table network_diag(lab_name varchar(15) references bt_labid(lab_name),diag_path varchar(40),primary key(lab_name));
Software Design Specification
Name of the table
Lab_attendence
Description
Student’s labs attendance descriptions.
Attribute
Description
Type
Lab_name
Name of lab
Varchar(15)
Examples of values Data structure lab
Roll_no
Roll no student
of
Char(10)
CSE/06/001
Name
Name student
of
Varchar(25)
Neha
attendance
Student attendance
Int(2)
24
Primary Key
Roll_no + lab_name
Foreign Keys
Lab_name references from Bt_labid and roll_no, name references from student_details
SQL Code
create 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 table
Lab_marks
Description
Student’s labs marks descriptions.
Attribute
Description
Type
Lab_name
Name of lab
Varchar(15)
Examples of values Data structure lab
Roll_no
Roll no student
of
Char(10)
CSE/06/001
Name
Name student
of
Varchar(25)
Neha
marks
Student marks
Int(2)
24
Page 33 of 106
Software Design Specification
Primary Key
Roll_no + lab_name
Foreign Keys
Lab_name references from Bt_labid and roll_no, name references from student_details
SQL Code
create 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 table
Time_table
Description
Different labs time table descriptions.
Attribute
Description
Type
Lab_name
Name of lab
Varchar(15)
Examples of values Data structure lab
Br_Name
Name of branch
Varchar(15)
Computer Science
semester
Semester name
Char(7)
Third
Time_table
Lab time table
Varchar(150)
In another module
Primary Key
Lab _name
Foreign Keys
Lab_name references from Bt_labid and Br_name references from Bt_branch
SQL Code
create 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 table
Lab_charges
Description
Student’s lab fine descriptions.
Attribute
Description
Roll_no
Roll no student
of
Char(10)
Examples of values CSE/06/001
Name
Name student
of
Varchar(25)
Neha
charges
Student fine in rupees
Int(3)
300
Page 34 of 106
Type
Software Design Specification
Remark
Fine remark
Primary Key
Varchar(30)
Lab breaking charges
Roll_no
Foreign Keys
Lab_name references from Bt_labid and roll_no, name references from student_details
SQL Code
create table lab_charges(roll_cahr(10) references varchar(25) references student_details,charges varchar(30),primary key(roll_no))
bt_labid,name int(3),remark
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. Student and faculty have no need to login they can see the information without login.
•
Page 35 of 106
Software Design Specification
8.8 Class Diagrams and Classes CONCEPTUAL CLASS DAIGRAM OF ADMINISTRATORS AND LAB SECTION CLASS
Page 36 of 106
Software Design Specification
ADMINSTRATORS
HAVE
LAB SECTION
COMPUTER ADMIN
COMPUTER LAB
MECHANICAL ADMIN
MECHANICAL LAB
ELECTRONICS ADMIN
ELECTRONICS LAB
SCIENCE ADMIN
SCIENCE LAB
8.9 Uses/Interactions Lab 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 Resources Hardware 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
Page 37 of 106
Software Design Specification
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 Processing In 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
Page 38 of 106
Software Design Specification
PERSON/U SER LOGIN TERMINATED
LOGIN INCORRECT
P_ID, PASSWORD
LOGIN CORRECT
ADMIN LOGIN
LOGIN ACCEPTED
LAB MANAGEMENT (G.U.I)
8.12 Interface/Exports Php 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.
Page 39 of 106
Software Design Specification
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 Design Lab management system basically covers four main lab subsystems these are:
Computer lab section
Science lab section
Mechanical lab section
Electronics lab section
COMPUTER LAB SECTIONThis 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 SECTIONThis lab section hold the electronic lab data like electronic equipment description, practical list of labs, maintained stock, dump stock etc. MECHANICAL LAB SECTIONThis lab section holds the mechanical lab related data. equipment, machine uses, requirement stock etc.
It holds the information about the
SCIENCE LAB SECTIONScience 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
8.
Fotter.php5
23
Page 40 of 106
Software Design Specification
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
18.
Computer_lab2.php5
139
19.
Computer_lab3.php5
140
20.
Computer_lab4.php5
133
21.
Computer_lab5.php5
140
22.
Computer_lab6.php5
138
23.
Electro_lab1.php5
125
24.
Electro_lab2.php5
130
25.
Electro_lab3.php5
126
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
33.
Comp_lab1_dumb.php5
42
34.
Comp_lab1_maintain.php5
45
Page 41 of 106
Software Design Specification
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
43.
Comp_lab2_info.ph5
43
44.
Comp_lab2_req.php5
44
45.
Comp_lab2_dumb.php5
42
46.
Comp_lab2_maintain.php5
45
47.
Comp_lab2_reserve.php5
44
48.
Comp_lab2_marks.php5
45
49.
Comp_lab2_incharge.php5
46
50.
Comp_lab2_practical.php5
45
51.
Comp_lab2_attendence.php5
46
52.
Comp_lab2_timetable.php5
47
53.
Comp_lab2_allotment.php5
48
54.
Comphead3.php5
130
55.
Comp_lab3_info.ph5
43
56.
Comp_lab3_req.php5
44
57.
Comp_lab3_dumb.php5
42
58.
Comp_lab3_maintain.php5
45
59.
Comp_lab3_reserve.php5
44
60.
Comp_lab3_marks.php5
45
Page 42 of 106
Software Design Specification
61.
Comp_lab3_incharge.php5
46
62.
Comp_lab3_practical.php5
45
63.
Comp_lab3_attendence.php5
46
64.
Comp_lab3_timetable.php5
47
65.
Comp_lab3_allotment.php5
48
66.
Comphead4.php5
130
67.
Comp_lab4_info.ph5
43
68.
Comp_lab4_req.php5
44
69.
Comp_lab4_dumb.php5
42
70.
Comp_lab4_maintain.php5
45
71.
Comp_lab4_reserve.php5
44
72.
Comp_lab4_marks.php5
45
73.
Comp_lab4_incharge.php5
46
74.
Comp_lab4_practical.php5
45
75.
Comp_lab4_attendence.php5
46
76.
Comp_lab4_timetable.php5
47
77.
Comp_lab4_allotment.php5
48
78.
Comphead5.php5
132
79.
Comp_lab5_info.ph5
43
80.
Comp_lab5_req.php5
44
81.
Comp_lab5_dumb.php5
42
82.
Comp_lab5_maintain.php5
45
83.
Comp_lab5_reserve.php5
44
84.
Comp_lab5_marks.php5
45
85.
Comp_lab5_incharge.php5
46
86.
Comp_lab5_practical.php5
45
Page 43 of 106
Software Design Specification
87.
Comp_lab5_attendence.php5
46
88.
Comp_lab5_timetable.php5
47
89.
Comp_lab5_allotment.php5
48
90.
Comphead6.php5
132
91.
Comp_lab6_info.ph5
43
92.
Comp_lab6_req.php5
44
93.
Comp_lab6_dumb.php5
42
94.
Comp_lab6_maintain.php5
45
95.
Comp_lab6_reserve.php5
44
96.
Comp_lab6_marks.php5
45
97.
Comp_lab6_incharge.php5
46
98.
Comp_lab6_practical.php5
45
99.
Comp_lab6_attendence.php5
46
100 .
Comp_lab6_timetable.php5
47
101 .
Comp_lab6_allotment.php5
48
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
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
Page 44 of 106
Software Design Specification
113 .
Electrohead2.php5
116
114 .
electro_lab2_info.ph5
43
115 .
electro_lab2_req.php5
44
116 .
electro_lab2_dumb.php5
42
117 .
electro_lab2_maintain.php5
45
118 .
electro_lab2_reserve.php5
44
119 .
electro_lab2_marks.php5
45
120 .
electro_lab2_incharge.php5
46
121 .
electro_lab2_practical.php5
45
122 .
electro_lab2_attendence.php5
46
123 .
electro_lab2_timetable.php5
47
124 .
Electrohead3.php5
120
125 .
electro_lab3_info.ph5
43
126 .
electro_lab3_req.php5
44
127 .
electro_lab3_dumb.php5
42
128 .
electro_lab3_maintain.php5
45
129 .
electro_lab3_reserve.php5
44
130 .
electro_lab3_marks.php5
45
131 .
electro_lab3_incharge.php5
46
132 .
electro_lab3_practical.php5
45
133 .
electro_lab3_attendence.php5
46
134 .
electro_lab3_timetable.php5
47
135 .
Mechhead1.php5
125
136 .
mech_lab2_info.ph5
43
137 .
mech_lab2_req.php5
44
138 .
mech_lab2_dumb.php5
42
Page 45 of 106
Software Design Specification
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
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
Page 46 of 106
Software Design Specification
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
Labmain.php5 (Home page) interface .style1 { font-family: Arial; Page 47 of 106
Software Design Specification
font-size: xx-small; } .style2 { color: black; } .style3 { text-decoration: none; } .style6 { text-align: center; } .style7 { font-family: "Arial Black"; font-size: xx-small; }
Page 48 of 106
Software Design Specification
COMPUTER LAB SECTION
|
ELECTRONICS LAB SECTION
|
MECHANICAL LAB SECTION
|
Page 49 of 106
Software Design Specification
SCIENCE LAB SECTION
|
STUDENT LAB SECTION
|
FACULTY LAB SECTION
Page 50 of 106
Software Design Specification
Contact us | Help Copyright © 2009 Rohilla Group of company. All rights reserved. Page 51 of 106
Software Design Specification
Compadmin_interface.php5 (computer section login page)
interface function check1() { if (document.getElementById("ai").value == "") { document.getElementById("val1").innerHTML = "*FIELD REQUIRED"; } else document.getElementById("val1").innerHTML = ""; } function check2() { if (document.getElementById("ap").value == "") { document.getElementById("val2").innerHTML = "*FIELD REQUIRED"; } else document.getElementById("val2").innerHTML = ""; } function home() { document.location="labmain.php5"; Page 52 of 106
Software Design Specification
}
.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; }
COMPUTER ADMIN LOGIN INTERFACE
Page 54 of 106
|
Software Design Specification
Admin Id :
Password :
Compadmin_connect.php5 (computer section connectivity)
