Web-Based Instructional Information Management System
Content
Web-Based Instructional Information Management System (WIIMS)
PROJECT REPORT
SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE AWARD OF THE DEGREE MASTER OF COMPUTER APPLICATIONS
BY
John Xavier
Project Guides: Mr. Vinod. P Dr. Vineeth Kumar P
DEPARTMENT OF COMPUTER ENGINEERING
NATIONAL INSTITUTE OF TECHNOLOGY CALICUT
NIT CAMPUS P.O, KOZHIKODE 673601, KERALA
APRIL . 2005
National Institute of Technology Calicut
Department of Computer Engineering CERTIFICATE
This is to certify that the work reported in this project report entitled ‘Web-based Instructional Information Management System’ is a bonafide record of the work done by John Xavier(Y2M016), a student in the Department of Computer engineering, National Institute of Technology Calicut from December 2004 to April 2005 in partial fulfillment for the award of the degree of Master of Computer Applications of the National Institute of Technology Calicut.
Guides: Dr.Vineeth Kumar P Asst.Professor Dept. of Computer Engineering NIT, Calicut Mr.Vinod P Lecturer Dept. of Computer Engineering NIT, Calicut
Head of the Department: Dr. V.K Govindan Professor Dept. of Computer Engineering NIT, Calicut
ACKNOWLEDGEMENT
First of all I would like to thank my guide and our project co.ordinator, Dr.Vineeth Kumar P, Asst.Professor and guide Mr.Vinod P, Lecturer Department of Computer Engineering, National Institute of Technology, Calicut, for there guidance and support through out my project work.
I would also like to thank Dr. V.K Govindan, Head of the Department, Department of Computer Engineering, National Institute of Technology, Calicut, for all the help he has extended to me.
Last but not the least, I would like to sincerely thank all my friends especially Sandeep, for his moral support, valuable suggestions and help during the course of this work.
ABSTRACT
Web.based instructional information management system (WIIMS) is designed to easily manage course data online. WIIMS is a full.featured web.based software application. This web based instructional management software allows instructors to manage course related material, communication through short messages and performanc e in related to marks. It allows students to view their individual marks. Since every department and computer labs in NITC is connected by local area network it is easily implemented as a web.based software.
CONTENTS
1 2 INTRODUCTION ............................................. ................................................1 SYSTEM SPECIFICATION................................................................................2 2.1 Introduction.....................................................................................................2 2.2 Problem Specification.....................................................................................2 2.3 System Requirements......................................................................................2 2.3.1 Functional Requirements.................................................................... 2 2.3.2 Nonfunctional Requirements...............................................................3 2.3.3 External Interface Requirements..................................................…...4
3 SYSTEM DESIGN..................................................................................................5 3.1 Purpose and scope.................................................................................................. 5 3.2 Definition and acronyms........................................................................................ 5 3.3 Design overview.....................................................................................................5 3.3.1 System Overview.................................................................................................5 3.3.2 Assumptions and Dependencies..........................................................................7 3.3.3 Design issues....................................................................................................... 7 3.4 Detailed System Design...........................................................................................8 3.4.1Architecture Design.............................................................................................. 8 3.4.2 Object Oriented Design........................................................................................ 8 3.5 Data Base Design...........................................................................................10 4 IMPLEMENTATION.......................................................................................................15 4.1 Introduction..............................................................................................................15 4.2 Databases and Development tools used...................................................................15 4.3 Client side programming..........................................................................................16 4.4 Implementation Issues..............................................................................................18
5 SYSTEM TESTING..........................................................................................................19 5.1 Introduction.........................................................................................................…..19 5.2 Testing Methods........................................................................................................20
6 SECURITY PROCEDURES...........................................................................................22 7 CONCLUSION................................................................................................................23 APPENDIX A- Sequence Diagrams ..........……..................................................................24 A-1 Adding Course..........................................................................................24 A-2 Assigning Course to students...................................................................25 A-3 Entering marks and viewing grades..........................................................26 A-4 course material..........................................................................................27 APPENDIX B- Screen Shots...........................................................................................29 REFERENCES.....................................................................................…………...35
1. INTRODUCTION
Web.based instructional information management system (WIIMS) is a full.featured web.based software application. The term ‘Web.Based’ in the name clearly tells that this system works with web interfaces. We have chosen a web –interface because of one main reason.currently all the departments and computer labs in NITC are interconnected through local area network. The instructors can easily get access to this system from any computer provided in their department. The students can get access to this system from any of the computer labs.
The system has currently three modules, Administrator, Instructor and Students. The Administrator module contains the functionalities like adding course, adding instructor, adding student, assigning and de.assigning courses to instructor/student. The Instructor module contains the functionalities like Enter/Edit marks, sending messages, Posting course materials. The student module contains the functionalities like sending messages, viewing course materials, viewing marks. The next chapter gives a detailed description about System analysis done for this project. That gives a view about the various requirements for this project. Then comes system design. That gives a view about the design methods accepted for this project. The chapter implementation gives a view about the implementation techniques adopted for this project. Since we(myself and Ajesh Kumar P.G) have done this project as a group, we have divided this implementation into two parts.part 1 and part 2. I have done the part 2 and part 1 by Ajesh.[7].Part 1 is for implementing all the functionalities for instructor. Part 2 is for implementing the functionalities of student and administrator. Since this is a group project I am including part 1 also in this report. .
1
1
2 SYSTEM SPECIFICATION
2.1 Introduction
Analysis is a detailed study of the various operations performed by a system and their relationships within and outside the system. This section studies the system to be developed in detail. A proper analysis helps to design our problem properly with the functional requirements, input and output.
2.2 Problem Definition
Web.based Instructional Information Management System is designed to easily, and affordably manage course data online. WIIMS is a full.featured web.based software application. This web based instructional management software allows instructors to manage grades, instruction, assessment and student performance.
2.3 System Requirements
2.3.1 Functional Requirements
1. Administrator Input of the system to the administrator is the login form. There he can enter his login id and password .If the identification is correct, the administrator gains control over the system. He has the options to 1) Provide login to instructor. 2) Provide login to student. 3) Add course. 4) Assigning instructor to course. 5) Assigning student to course. 6) De.assigning instructor from course. 7) De.assigning student from course.
2
8) Remove course. 9) Remove instructor. 10) Remove student.
2.
Instructor Input of the system to the instructor is the login form. There he can enter his login id and password .If the identification is correct, the instructor gains control over the system. He has four options 1) Enter/Edit marks of the students for the course he is taking. 2) Sent and view messages. 3) Post course materials. 4) Take printout of mark.list.
3. Student Input of the system to the student is the login form. There he can enter his login id and password .If the identification is correct, the student gains control over the system. He has four options 1) Sent and view messages 2) View course materials. 3) View Marks and grade. .
2.3.2 Non.Functional Requirements
2.3.2.1 System.Related Non.Functional Requirements
1 Hardware requirements The minimum requirements will be as follows 128 MB RAM Processor with speed 500MHz 3
100 Mbps LAN connection. 2 Software requirements Web Server, database
3 Modifiability and extensibility Addition of further functionalities is possible. Since the software is delivered along with source code, it is easily modifiable. The system is accessible from any node, which is connected to the web server through network.
4
Portability The system will run on both Linux and Windows platforms.
5 Response time must be of maximum 1 minute.
2.3.2.2 Process.Related Non.Functional Requirements
Deliverable formats The system is delivered as Java Server Pages(JSP) .The needed classes are provided as JAR files and CLASS files. The java source code for the class files is also provided.
2.3.3 External Interface Requirements
1 User Interfaces All the interfaces are provided as web Pages. 2 Communication interfaces The communication protocol HTTP is required.
4
3 SYSTEM DESIGN
3.1 Purpose and scope of the document
This section outlines the expected contents of the system. The deliverable document from the System Design process will include a set of technical specifications that will be used to generate (build) and implement the new system. The System Design Document must be complete and in sufficient detail to allow a technical resource unfamiliar with the project to be able to construct the system based solely on this document and materials referenced herein.
3.2 Definitions and acronyms
WIIMS.Web.based Instructional Information Manageme nt System JSP. Java Server pages HTTP. Hyper Text Transfer Protocol. SQL.Structured Query Language GUI.Graphical User Interface.
3.3 Design Overview
3.3.1 System Overview Web.based Instructional Information Management System is designed to easily, and affordably manage course data online. WIIMS is a full.featured web.based software application. This web based instructional management software allows instructors to manage grades, instruction, assessment and student performance.
Users: Main users are Students and Instructors.
5
Instructors:
1.Course management Instructors can enter the marks for the students who have registered for a particular course. He can decide upon the name of evaluation conducted (assignment/quiz etc) and also upon the grades. Later he may also edit the previously entered marks.
2.Mailing option Instructors can send short messages to students who are registered for a particular course. He can either send messages to each student individually or as a whole class.
3.Post course materials Instructors can post course materials. These course materials are uploaded to the server as files. Any type of file extensions are permitted provided the files do not exceed the user quota provided.
Students:
1. View individual scores and statistics. Students can view their individual scores through this website. Also the student can view the course statistics i.e. number of students who got S grade, A grade etc
2.Mailing option Students can send short messages to the instructor who is teaching that particular course.
3.View Course Materials and messages Students can view the course materials and messages posted by the instructors. They can download the course materials by right.clicking the name of the material.
6
3.3.2 Assumptions and dependencies
1. The administrator has full control over the system. 2. The client system should have a web browser. It should have a network connection to the web.server and database server. 3. The system is going to be implemented only in a single department.
3.3.3 Design issues
1. We have given Administrator, Instructor and Student without any inheritance. So the class diagram we had to represent the same functionalities under different classes (Admin, Instructor and Student). 2. We have given the whole database as a single class. It reduced the readability of the class diagram. 3. Interaction of instructor with student. The interaction can be of two types.messages and course materials. The issue was on how to send these messages and course materials, whether it should be of the same format or not.
3.4 Detailed System Design
7
3.4.1 Architecture Design
Client
HTTP interaction Web server Application processing Database server Data management
Client
SQL query
Client
Client
Figure:1 A three tier client –server architecture for WIIMS
The use of three.tier architecture(Figure 1) in this case allows the information transfer between the web server and the database server to be optimized. The efficient middleware that supports database queries in SQL is used to handle information retrieval from the database.
3.4.2 Object Oriented Design Object Oriented Design is a design strategy where system designers think in terms of ‘things’ instead of operations or functions. It is a part of object.oriented development, where an object.oriented strategy is used throughout the development process.
8
Login_form Check_login()
checks
1 access 1..*
Student ID:String Passwd:String Name: String E.mail:String Sent_msg() View_msg() ViewCM() ViewMarks()
Course C_name:string C_ID:string C_inst:String
1 n manage
m Add/remove
has
Security_system Instructor Validate_login() Add_mark() Edit_mark() PostCM()
*
n
Course material C_ID:String C_Name:String Type :attachment
n
n
Administrator Add_User() Add_Course() Remove_User() Remove_Course() Assign_Inst_to course() Remove_Inst_from_course() Assign_stud_to Course() Remove_stud_from_course()
manages
Sent/View *
Message Msg_sent_to:ID Message:text
m
Figure 2: Class diagram for WIIMS CM =Course material Msg = message
Mark Mark1:float Weightage1:int Out of 1 :int ………… Mark8:float Weightage8:int Out of 8: int Grade :char Calculate_Tot_Mark()
9
3.5 Data base design
A good design of the database is the base for any application side project. The database is designed with RDBMS concepts. Special cares have been taken for not going for too much of normalization so as to make queries faster. Course
Course_ID Course_Name
INSTRUCTOR
Instr_ID
Instr_Name
STUDENT
Stud_ID
Stud_Name
MARKS M_1 M_2
M_3
…
…
M_7
Total
Grade
Stud_ID
Course_ID
Outof N_1 O_1 w_1
…
…
n_8
o_8
w_8
Course_I D
sms Course_ID
Student_id
Message
Type
Subject msgdate msgtime expdate
Figure 3:Relational database Schema Diagram for WIIMS
10
Abbreviations used
M_1 : Mark for first evaluation type. M_2 : Mark for second evaluation type. n_1 : name of first evaluation type. o_f : Out of mark for first evaluation type. w_1 : weightage for first evaluation type.
11
The tables used in WIIMS are as follows
1. Course table This table is used to store the details for each course conducted. It has the following structure
ATTRIBUTE c_name * c_id
DATA TYPE varchar(30) varchar(10)
COMMENTS Course name Course id
2. Student table This table is used to store the details for each student. It has the following structure ATTRIBUTE s_name *s_id s_pwd DATA TYPE varchar(25) varchar(10) varchar(10) COMMENTS Student name Student id Student password
3. Instructor table This table is used to store the details for each instructor. It has the following structure ATTRIBUTE i_name *i_id i_pwd DATA TYPE varchar(25) varchar(10) varchar(10) COMMENTS Instructor name Instructor id Instructor password
12
4. Course.Instructor table
ATTRIBUTE c_id i_id
DATA TYPE varchar(10) varchar(10)
COMMENTS Course id Instructor id
5. Course.Student table ATTRIBUTE c_id s_id DATA TYPE varchar(10) varchar(10) COMMENTS Course id Sudent id
6. Course material table ATTRIBUTE c_id i_id cm_name comment DATA TYPE varchar(10) varchar(10) varchar(20) text COMMENTS Course id Instructor id Course mat name Comments
7. Mark table
ATTRIBUTE m_1 m_2 m_3 m_4 m_5 m_6 m_7 Total *s_id *c_id Grade
DATA TYPE float float float float float float float float varchar(10) varchar(10) char(1)
COMMENTS Eval 1 marks Eval 2 marks Eval 3 marks Eval total marks Mid term 1 marks Mid term 2 marks Final marks Total marks Student id Course id Grade(S/A/B….)
13
8. Out.of table ATTRIBUTE n_1 o_1 w_1 n_2 o_2 w_2 ….. …... n_8 o_8 w_8 *c_id DATA TYPE varchar(10) int(3) int(3) varchar(10) int(3) int(3) COMMENTS Eval 1 name Out of marks Weightage Eval 1 Eval 2 name Out of marks Weightage Eval 2
varchar(10) int(3) int(3) varchar(10)
Total Out of(total) Weightage(total) Course ID
9. Short Message table
ATTRIBUTE c_id s_id message type subject msgdate msgtime expdate
DATA TYPE varchar(10) varchar(10) text varchar(10) varchar(15) date time date
COMMENTS Course id Student id Message Type(inst/stud) Subject Message date Message time Expiry Date
14
4. IMPLEMENTATION
4.1 Introduction
The implementation phase translates a detailed design representation of the problem into programming language realization. The following section describes the software used for development, coding standards and the practical issues involved in implementing the software.
4.2 Databases and Development Tools used
The application uses JSP as the front end and MySQL Database as the back end.
JSP
JSP is entirely based on java programming language. Internally, JSP pages are dynamically converted into java servlets, which are simply java classes. This means JSP enjoys all the capabilities that java programming supports. The first time that page is loaded off the server; it is compiled into a java servlet & loaded into memory. Each time a subsequent request is made to the page, the server just uses the already.compiled page that it has in memory to do its stuff. JSP is a great deal more efficient than many other scripting languages, such as CGI and ASP. Tags can be defined in tag libraries and then used within any JSP page. This makes for a better separation of page content from its code, which leads to less scattered code and hence, the site is easier to maintain. Java is platform and browser independent. Since Java is platform independent JSP pages can be run on any machine regardless of operating system without recompilation. There are other advantages as well, JSP allows you to keep much more of your code separate from the html than other html embedded languages, by using java beans.
15
MySQL
MySQL is a relational database management system that is a very fast, multi.threaded, multi.user and robust SQL (Struc tured Query Language) database server. MySQL is also Open Source, which means that it’s possible for everyone to use and modify its code. MySQL has a good feature set including: • • • • • • • Fully multi.threaded using kernel threads. This means it easily can use multiple CPUs if available. It works on many different platforms with C, C++, Eiffel, Java, Perl, JSP and Python . SQL functions are implemented through a highly.optimized class library. A privilege and password system which is very flexible and secure, and which allows host.based verification ODBC (Open.DataBase.Connectivity) support for Windows (with source). Handles large databases . tables with over a million rows can be created in MySQL with no problems. Full support for several different character sets.
4.3 Client side Programming
The most important phase of project from the point of view of an end user is nothing but interface design. Actually the application communicates with the user through the interfaces. This work also gives a special attention towards the interface design. A self explanatory GUI is adopted –Self explanatory in the sense if any one see a button he will get an idea about what is going to happened next if he or she press that button. Since we(myself and Ajesh Kumar P.G) have done this project as a group, we have divided this implementation into two parts.part 1 and part 2. I have done the part 2 and part 1 by Ajesh Kumar(y2m018) [7] ,a student in the Department of Computer engineering, Master of Computer Applications, National Institute of Technology Calicut, April 2005 Part 1 is for implementing all the functionalities for instructor. Part 2 is for implementing the functionalities of student and administrator. For the sake of completion of the report the first part is also included in the report.
16
Part 1:
Input of the system to the instructor is the instructor.login form. He logins to the system using the login.id and password pre.assigned to him by the administrator. If the login is valid then the course page loads automatically. This course page contains a list of courses that he teaches. On selection of any course the course home page loads automatically. From this page instructor can send messages and course materials to his students, view messages sent by students, enter/edit individual marks, take print outs of mark sheet and also can change his password.
Part 2:
Input of the system to the student is the student.login form. He logins to the system using the login.id and password pre.assigned to him by the administrator. If the login is valid then the course page loads automatically. This course page contains a list of courses for which he has registered. On selection of any course the course home page loads automatically. From this page student can send messages to his course instructor, view messages and course materials sent by his course instructor, view his/her individual marks and also can change his password.
Input of the system to the administrator is the admin.login form. The administrator has full control over the system. If the login is valid then the admin home page loads automatically. This page contains options like add ne w student, instructor and course, assigning and de.assigning course to instructors and students, removing instructor, student and course and change password.
17
4.4 Implementation Issues
1. Assigning courses to student/instructor.
This functionality is given only to administrator. So multiple assigning of students to multiple courses is possible. For easiness it is better to use a list box rather than pull down menus.
2. Mark Entry by Instructor.
Entering marks for multiple students at the same time was made possible. These marks can be edited in the same page itself.
3.
Sign out from admin/instructor/student page. Sign out guaranteed by expiring the session variables used. Any requests after a sign out
will result in reloading of the corresponding login page. These measures are undertaken to prevent unauthorized entries to any page in the server.
4. Storing name of Course Materials. Extracting the name of Course material published by the instructor and storing it in database.
5. The inheritance property provided in the class diagram has not been implemented. This is for providing security.
18
5. SYSTEM TESTING 5.1 Introduction
No program or system design is perfect. The number and nature of errors in a new design depends on such factors like the communication between the user and the designer, the programmer’s ability to generate a code that reflects exactly the system specifications and the time frame for the design. The purpose of system testing is to consider all the likely variations to which it will be subjected and to push the system to its limits. It is a tedious but necessary step in system development. Testing is vital to the success of the system. System testing makes the logical assumption that if all the parts of the system are correct, the goal will be successfully achieved. The system is to be tested to see whether the outputs are correct to a known specific input. The process of system testing can be classified into 1 Unit testing 2 Module testing 3 Sub.system testing 4 System testing 5 Acceptance testing Unit testing : Individual components are tested to ensure that they operate correctly. Each component is tested independently, without other component Module testing : A module is a collection of dependent components such as an object class, an abstract data type or some looser collection of procedures and functions. A module encapsulate related component so can be tested without other modules Sub.system testing : This phase involves testing collection of modules, which have been integrated into sub.systems. Sub.system may be independently designed and implemented. The most common problem, which arises in large software systems, is sub.system mismatches. The sub.system test process should therefore concentrate on the detection of interface errors by rigorously exercising these interfaces
19
System testing : The sub.system is integrated to make up the entire system. The testing process is concentrated with finding errors, which result from unanticipated interaction between sub.systems and system components. It is also concerned with validating that the system meets its functional and non.functional requirements. Acceptance testing : This is the final stage in the testing process before the system is accepted for operational use. The system is tested with data supplied by the system procurer rather than simulated test data. Acceptance testing may reveal errors and omission in the system requirements definition because the real data exercises the system in different ways from the test data. Acceptance testing may also reveal requirements problems where the system’s facilities do not really meets the users needs or the system performance is unacceptable.
5.2 Testing Methods Black Box Testing
Also known as functional testing. A software testing technique whereby the tester does not know the internal workings of the item being tested. For example, in a black box test on software design the tester only knows the inputs and what the expected outcomes should be and not how the program arrives at those outputs. The tester does not ever examine the pro code and does not need any further knowledge of the program other than its specifications. The advantages of this type of testing include:
•
The test is unbiased because the designer and the tester are independent of each other.
• • •
The tester does not need knowledge of any specific programming languages. The test is done from the point of view of the user, not the designer. Test cases can be designed as soon as the specifications are complete.
White Box Testing
20
Also known as glass box, structural, clear box and open box testing. A software testing technique whereby explicit knowledge of the internal workings of the item being tested are used to select the test data. Unlike black box testing, white box testing uses specific knowledge of programming code to examine outputs. The test is accurate only if the tester knows what the program is supposed to do. He or she can then see if the program diverges from its intended goal. White box testing does not account for errors caused by omission, and all visible code must also be readable.
Testing Method Used
We have adopted a testing method, which is a mix of both white box and black box testing. For the units we have adopted white box testing. Then we integrated the units into modules and further into the system. There we adopted black box testing for checking the correctness of the system
21
6. SECURITY PROCEDURES
1. No student is able to view the marks of other students. 2. A student can view only the course materials of the courses for which he has registered 3. The messages can only be viewed by destinies. 4. For security a sign out option is given to each user. Sign out is guaranteed by expiring the session variables used.
22
7. CONCLUSION
Web.based Instructional Information Management System (WIIMS) is a web.based software that allows students and instructors to interact each other in an efficient manner. This web based instructional management software allows instructors to manage course related materials, communication through short messages and performance in related to marks. It allows students to view their individual marks. Currently no such system exists. So we have been assigned to do this project in a product.oriented manner. Since every department and computer labs in NITC is connected by local area network we have easily implemented it as a web.based software. We have tested the performance of our system in local area network and were happy with the response time since it reflects what we have given in our requirements specification. Now our system has only the option to send short messages. This system can be extended to send attachments along with short messages.
23
APPENDIX-A
A:1 Sequence Diagram for Adding Course
Administrator
Department Record System checkIfExist(courseId)
Course
addCourse(courseId, courseName)
[ If course exists ] Return Unsuccessful
[ If course not exist ] Course(courseId,courseName) << create >>
addtoDB(course) Return Successful
Scenario Scenario 1: Course gets added successfully. Scenario 2: Adding the course fails because the course is already in the database.
24
A:2 Sequence Diagram for assigning courses to students
Department Record System
cou := getCourse() stu := getStudent() Administrator enroll(stuID, courseID) [ if stu != NULL and cou != NULL] addCourse(cou) Student
Return Successful Return Successful
Scenario Scenario 1: Student enrolls in the course successfully. Scenario 2: Enrolling fails because the student is already enrolled in the course.
25
A:3 Sequence Diagram for entering Marks and viewing grade
Instructor
Student
Department Record System
EnterMarks Total calculated and stored
EditMark
Return Successful
Get Marks/Grade View Marks/Grade
Scenario Scenario 1: Enter marks/Edit marks successfully. Scenario 2: Viewing Marks/grade.
26
A:4 Sequence diagram for Course.Material Department Record System
Instructor
Student
Sent_CM/Msg
AddtoDB ( )
View_CM/Msg
Sent Msg
addtoDB( )
View Msg
Abbrevations CM.Course Material Msg.messages
Scenario Scenario 1: Sending and viewing course material/messages by instructor. Scenario 2: Sending and viewing messages by student.
27
WIIMS Add_course Add_User
Assign cou_stud
Assign cou_inst
Administrator Enter_mark Edit_mark Send_msg
Post CM
Instructor
View_msg
View_msg Send_msg View_CM
View_Grade
Student
Use.case diagram for WIIMS
28
APPENDIX :B
ADMINISTRATOR
B:1 Assigning course to students form
Assigning course to students
29
B:2 Adding instructor form
30
INSTRUCTOR
B:3 Write message form for instructor
31
B: 4 View Marks form for instructor
32
STUDENT B:5 View Marks form for student
33
B:6 Sending message form for student
34
REFERENCE
[1]
Ian Somerville. “Software Engineering”. Sixth Edition, Pearson Education Ltd, 2002.
[2] Page Jones. “Fundamentals of Object Oriented design in UML”. Addison Wesley Longman Pvt Ltd.,2001 [3] Elamsri and Navathe. “Fundamentals of Database Systems”. Pearson Asia Edition, 2000 [4] [5] [6] [7] V.K Jain. ”Java Server Pages and Servlets”. Pearson Asia Edition ,2000. http://jdstiles.com/javamain.html http://www.jsptut.com/index.html Ajesh Kumar P.G. Project Report titled “Web-based Instructional Information Management System”,S6 MCA,NITC,April 2005
35
PROJECT REPORT
SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE AWARD OF THE DEGREE MASTER OF COMPUTER APPLICATIONS
BY
John Xavier
Project Guides: Mr. Vinod. P Dr. Vineeth Kumar P
DEPARTMENT OF COMPUTER ENGINEERING
NATIONAL INSTITUTE OF TECHNOLOGY CALICUT
NIT CAMPUS P.O, KOZHIKODE 673601, KERALA
APRIL . 2005
National Institute of Technology Calicut
Department of Computer Engineering CERTIFICATE
This is to certify that the work reported in this project report entitled ‘Web-based Instructional Information Management System’ is a bonafide record of the work done by John Xavier(Y2M016), a student in the Department of Computer engineering, National Institute of Technology Calicut from December 2004 to April 2005 in partial fulfillment for the award of the degree of Master of Computer Applications of the National Institute of Technology Calicut.
Guides: Dr.Vineeth Kumar P Asst.Professor Dept. of Computer Engineering NIT, Calicut Mr.Vinod P Lecturer Dept. of Computer Engineering NIT, Calicut
Head of the Department: Dr. V.K Govindan Professor Dept. of Computer Engineering NIT, Calicut
ACKNOWLEDGEMENT
First of all I would like to thank my guide and our project co.ordinator, Dr.Vineeth Kumar P, Asst.Professor and guide Mr.Vinod P, Lecturer Department of Computer Engineering, National Institute of Technology, Calicut, for there guidance and support through out my project work.
I would also like to thank Dr. V.K Govindan, Head of the Department, Department of Computer Engineering, National Institute of Technology, Calicut, for all the help he has extended to me.
Last but not the least, I would like to sincerely thank all my friends especially Sandeep, for his moral support, valuable suggestions and help during the course of this work.
ABSTRACT
Web.based instructional information management system (WIIMS) is designed to easily manage course data online. WIIMS is a full.featured web.based software application. This web based instructional management software allows instructors to manage course related material, communication through short messages and performanc e in related to marks. It allows students to view their individual marks. Since every department and computer labs in NITC is connected by local area network it is easily implemented as a web.based software.
CONTENTS
1 2 INTRODUCTION ............................................. ................................................1 SYSTEM SPECIFICATION................................................................................2 2.1 Introduction.....................................................................................................2 2.2 Problem Specification.....................................................................................2 2.3 System Requirements......................................................................................2 2.3.1 Functional Requirements.................................................................... 2 2.3.2 Nonfunctional Requirements...............................................................3 2.3.3 External Interface Requirements..................................................…...4
3 SYSTEM DESIGN..................................................................................................5 3.1 Purpose and scope.................................................................................................. 5 3.2 Definition and acronyms........................................................................................ 5 3.3 Design overview.....................................................................................................5 3.3.1 System Overview.................................................................................................5 3.3.2 Assumptions and Dependencies..........................................................................7 3.3.3 Design issues....................................................................................................... 7 3.4 Detailed System Design...........................................................................................8 3.4.1Architecture Design.............................................................................................. 8 3.4.2 Object Oriented Design........................................................................................ 8 3.5 Data Base Design...........................................................................................10 4 IMPLEMENTATION.......................................................................................................15 4.1 Introduction..............................................................................................................15 4.2 Databases and Development tools used...................................................................15 4.3 Client side programming..........................................................................................16 4.4 Implementation Issues..............................................................................................18
5 SYSTEM TESTING..........................................................................................................19 5.1 Introduction.........................................................................................................…..19 5.2 Testing Methods........................................................................................................20
6 SECURITY PROCEDURES...........................................................................................22 7 CONCLUSION................................................................................................................23 APPENDIX A- Sequence Diagrams ..........……..................................................................24 A-1 Adding Course..........................................................................................24 A-2 Assigning Course to students...................................................................25 A-3 Entering marks and viewing grades..........................................................26 A-4 course material..........................................................................................27 APPENDIX B- Screen Shots...........................................................................................29 REFERENCES.....................................................................................…………...35
1. INTRODUCTION
Web.based instructional information management system (WIIMS) is a full.featured web.based software application. The term ‘Web.Based’ in the name clearly tells that this system works with web interfaces. We have chosen a web –interface because of one main reason.currently all the departments and computer labs in NITC are interconnected through local area network. The instructors can easily get access to this system from any computer provided in their department. The students can get access to this system from any of the computer labs.
The system has currently three modules, Administrator, Instructor and Students. The Administrator module contains the functionalities like adding course, adding instructor, adding student, assigning and de.assigning courses to instructor/student. The Instructor module contains the functionalities like Enter/Edit marks, sending messages, Posting course materials. The student module contains the functionalities like sending messages, viewing course materials, viewing marks. The next chapter gives a detailed description about System analysis done for this project. That gives a view about the various requirements for this project. Then comes system design. That gives a view about the design methods accepted for this project. The chapter implementation gives a view about the implementation techniques adopted for this project. Since we(myself and Ajesh Kumar P.G) have done this project as a group, we have divided this implementation into two parts.part 1 and part 2. I have done the part 2 and part 1 by Ajesh.[7].Part 1 is for implementing all the functionalities for instructor. Part 2 is for implementing the functionalities of student and administrator. Since this is a group project I am including part 1 also in this report. .
1
1
2 SYSTEM SPECIFICATION
2.1 Introduction
Analysis is a detailed study of the various operations performed by a system and their relationships within and outside the system. This section studies the system to be developed in detail. A proper analysis helps to design our problem properly with the functional requirements, input and output.
2.2 Problem Definition
Web.based Instructional Information Management System is designed to easily, and affordably manage course data online. WIIMS is a full.featured web.based software application. This web based instructional management software allows instructors to manage grades, instruction, assessment and student performance.
2.3 System Requirements
2.3.1 Functional Requirements
1. Administrator Input of the system to the administrator is the login form. There he can enter his login id and password .If the identification is correct, the administrator gains control over the system. He has the options to 1) Provide login to instructor. 2) Provide login to student. 3) Add course. 4) Assigning instructor to course. 5) Assigning student to course. 6) De.assigning instructor from course. 7) De.assigning student from course.
2
8) Remove course. 9) Remove instructor. 10) Remove student.
2.
Instructor Input of the system to the instructor is the login form. There he can enter his login id and password .If the identification is correct, the instructor gains control over the system. He has four options 1) Enter/Edit marks of the students for the course he is taking. 2) Sent and view messages. 3) Post course materials. 4) Take printout of mark.list.
3. Student Input of the system to the student is the login form. There he can enter his login id and password .If the identification is correct, the student gains control over the system. He has four options 1) Sent and view messages 2) View course materials. 3) View Marks and grade. .
2.3.2 Non.Functional Requirements
2.3.2.1 System.Related Non.Functional Requirements
1 Hardware requirements The minimum requirements will be as follows 128 MB RAM Processor with speed 500MHz 3
100 Mbps LAN connection. 2 Software requirements Web Server, database
3 Modifiability and extensibility Addition of further functionalities is possible. Since the software is delivered along with source code, it is easily modifiable. The system is accessible from any node, which is connected to the web server through network.
4
Portability The system will run on both Linux and Windows platforms.
5 Response time must be of maximum 1 minute.
2.3.2.2 Process.Related Non.Functional Requirements
Deliverable formats The system is delivered as Java Server Pages(JSP) .The needed classes are provided as JAR files and CLASS files. The java source code for the class files is also provided.
2.3.3 External Interface Requirements
1 User Interfaces All the interfaces are provided as web Pages. 2 Communication interfaces The communication protocol HTTP is required.
4
3 SYSTEM DESIGN
3.1 Purpose and scope of the document
This section outlines the expected contents of the system. The deliverable document from the System Design process will include a set of technical specifications that will be used to generate (build) and implement the new system. The System Design Document must be complete and in sufficient detail to allow a technical resource unfamiliar with the project to be able to construct the system based solely on this document and materials referenced herein.
3.2 Definitions and acronyms
WIIMS.Web.based Instructional Information Manageme nt System JSP. Java Server pages HTTP. Hyper Text Transfer Protocol. SQL.Structured Query Language GUI.Graphical User Interface.
3.3 Design Overview
3.3.1 System Overview Web.based Instructional Information Management System is designed to easily, and affordably manage course data online. WIIMS is a full.featured web.based software application. This web based instructional management software allows instructors to manage grades, instruction, assessment and student performance.
Users: Main users are Students and Instructors.
5
Instructors:
1.Course management Instructors can enter the marks for the students who have registered for a particular course. He can decide upon the name of evaluation conducted (assignment/quiz etc) and also upon the grades. Later he may also edit the previously entered marks.
2.Mailing option Instructors can send short messages to students who are registered for a particular course. He can either send messages to each student individually or as a whole class.
3.Post course materials Instructors can post course materials. These course materials are uploaded to the server as files. Any type of file extensions are permitted provided the files do not exceed the user quota provided.
Students:
1. View individual scores and statistics. Students can view their individual scores through this website. Also the student can view the course statistics i.e. number of students who got S grade, A grade etc
2.Mailing option Students can send short messages to the instructor who is teaching that particular course.
3.View Course Materials and messages Students can view the course materials and messages posted by the instructors. They can download the course materials by right.clicking the name of the material.
6
3.3.2 Assumptions and dependencies
1. The administrator has full control over the system. 2. The client system should have a web browser. It should have a network connection to the web.server and database server. 3. The system is going to be implemented only in a single department.
3.3.3 Design issues
1. We have given Administrator, Instructor and Student without any inheritance. So the class diagram we had to represent the same functionalities under different classes (Admin, Instructor and Student). 2. We have given the whole database as a single class. It reduced the readability of the class diagram. 3. Interaction of instructor with student. The interaction can be of two types.messages and course materials. The issue was on how to send these messages and course materials, whether it should be of the same format or not.
3.4 Detailed System Design
7
3.4.1 Architecture Design
Client
HTTP interaction Web server Application processing Database server Data management
Client
SQL query
Client
Client
Figure:1 A three tier client –server architecture for WIIMS
The use of three.tier architecture(Figure 1) in this case allows the information transfer between the web server and the database server to be optimized. The efficient middleware that supports database queries in SQL is used to handle information retrieval from the database.
3.4.2 Object Oriented Design Object Oriented Design is a design strategy where system designers think in terms of ‘things’ instead of operations or functions. It is a part of object.oriented development, where an object.oriented strategy is used throughout the development process.
8
Login_form Check_login()
checks
1 access 1..*
Student ID:String Passwd:String Name: String E.mail:String Sent_msg() View_msg() ViewCM() ViewMarks()
Course C_name:string C_ID:string C_inst:String
1 n manage
m Add/remove
has
Security_system Instructor Validate_login() Add_mark() Edit_mark() PostCM()
*
n
Course material C_ID:String C_Name:String Type :attachment
n
n
Administrator Add_User() Add_Course() Remove_User() Remove_Course() Assign_Inst_to course() Remove_Inst_from_course() Assign_stud_to Course() Remove_stud_from_course()
manages
Sent/View *
Message Msg_sent_to:ID Message:text
m
Figure 2: Class diagram for WIIMS CM =Course material Msg = message
Mark Mark1:float Weightage1:int Out of 1 :int ………… Mark8:float Weightage8:int Out of 8: int Grade :char Calculate_Tot_Mark()
9
3.5 Data base design
A good design of the database is the base for any application side project. The database is designed with RDBMS concepts. Special cares have been taken for not going for too much of normalization so as to make queries faster. Course
Course_ID Course_Name
INSTRUCTOR
Instr_ID
Instr_Name
STUDENT
Stud_ID
Stud_Name
MARKS M_1 M_2
M_3
…
…
M_7
Total
Grade
Stud_ID
Course_ID
Outof N_1 O_1 w_1
…
…
n_8
o_8
w_8
Course_I D
sms Course_ID
Student_id
Message
Type
Subject msgdate msgtime expdate
Figure 3:Relational database Schema Diagram for WIIMS
10
Abbreviations used
M_1 : Mark for first evaluation type. M_2 : Mark for second evaluation type. n_1 : name of first evaluation type. o_f : Out of mark for first evaluation type. w_1 : weightage for first evaluation type.
11
The tables used in WIIMS are as follows
1. Course table This table is used to store the details for each course conducted. It has the following structure
ATTRIBUTE c_name * c_id
DATA TYPE varchar(30) varchar(10)
COMMENTS Course name Course id
2. Student table This table is used to store the details for each student. It has the following structure ATTRIBUTE s_name *s_id s_pwd DATA TYPE varchar(25) varchar(10) varchar(10) COMMENTS Student name Student id Student password
3. Instructor table This table is used to store the details for each instructor. It has the following structure ATTRIBUTE i_name *i_id i_pwd DATA TYPE varchar(25) varchar(10) varchar(10) COMMENTS Instructor name Instructor id Instructor password
12
4. Course.Instructor table
ATTRIBUTE c_id i_id
DATA TYPE varchar(10) varchar(10)
COMMENTS Course id Instructor id
5. Course.Student table ATTRIBUTE c_id s_id DATA TYPE varchar(10) varchar(10) COMMENTS Course id Sudent id
6. Course material table ATTRIBUTE c_id i_id cm_name comment DATA TYPE varchar(10) varchar(10) varchar(20) text COMMENTS Course id Instructor id Course mat name Comments
7. Mark table
ATTRIBUTE m_1 m_2 m_3 m_4 m_5 m_6 m_7 Total *s_id *c_id Grade
DATA TYPE float float float float float float float float varchar(10) varchar(10) char(1)
COMMENTS Eval 1 marks Eval 2 marks Eval 3 marks Eval total marks Mid term 1 marks Mid term 2 marks Final marks Total marks Student id Course id Grade(S/A/B….)
13
8. Out.of table ATTRIBUTE n_1 o_1 w_1 n_2 o_2 w_2 ….. …... n_8 o_8 w_8 *c_id DATA TYPE varchar(10) int(3) int(3) varchar(10) int(3) int(3) COMMENTS Eval 1 name Out of marks Weightage Eval 1 Eval 2 name Out of marks Weightage Eval 2
varchar(10) int(3) int(3) varchar(10)
Total Out of(total) Weightage(total) Course ID
9. Short Message table
ATTRIBUTE c_id s_id message type subject msgdate msgtime expdate
DATA TYPE varchar(10) varchar(10) text varchar(10) varchar(15) date time date
COMMENTS Course id Student id Message Type(inst/stud) Subject Message date Message time Expiry Date
14
4. IMPLEMENTATION
4.1 Introduction
The implementation phase translates a detailed design representation of the problem into programming language realization. The following section describes the software used for development, coding standards and the practical issues involved in implementing the software.
4.2 Databases and Development Tools used
The application uses JSP as the front end and MySQL Database as the back end.
JSP
JSP is entirely based on java programming language. Internally, JSP pages are dynamically converted into java servlets, which are simply java classes. This means JSP enjoys all the capabilities that java programming supports. The first time that page is loaded off the server; it is compiled into a java servlet & loaded into memory. Each time a subsequent request is made to the page, the server just uses the already.compiled page that it has in memory to do its stuff. JSP is a great deal more efficient than many other scripting languages, such as CGI and ASP. Tags can be defined in tag libraries and then used within any JSP page. This makes for a better separation of page content from its code, which leads to less scattered code and hence, the site is easier to maintain. Java is platform and browser independent. Since Java is platform independent JSP pages can be run on any machine regardless of operating system without recompilation. There are other advantages as well, JSP allows you to keep much more of your code separate from the html than other html embedded languages, by using java beans.
15
MySQL
MySQL is a relational database management system that is a very fast, multi.threaded, multi.user and robust SQL (Struc tured Query Language) database server. MySQL is also Open Source, which means that it’s possible for everyone to use and modify its code. MySQL has a good feature set including: • • • • • • • Fully multi.threaded using kernel threads. This means it easily can use multiple CPUs if available. It works on many different platforms with C, C++, Eiffel, Java, Perl, JSP and Python . SQL functions are implemented through a highly.optimized class library. A privilege and password system which is very flexible and secure, and which allows host.based verification ODBC (Open.DataBase.Connectivity) support for Windows (with source). Handles large databases . tables with over a million rows can be created in MySQL with no problems. Full support for several different character sets.
4.3 Client side Programming
The most important phase of project from the point of view of an end user is nothing but interface design. Actually the application communicates with the user through the interfaces. This work also gives a special attention towards the interface design. A self explanatory GUI is adopted –Self explanatory in the sense if any one see a button he will get an idea about what is going to happened next if he or she press that button. Since we(myself and Ajesh Kumar P.G) have done this project as a group, we have divided this implementation into two parts.part 1 and part 2. I have done the part 2 and part 1 by Ajesh Kumar(y2m018) [7] ,a student in the Department of Computer engineering, Master of Computer Applications, National Institute of Technology Calicut, April 2005 Part 1 is for implementing all the functionalities for instructor. Part 2 is for implementing the functionalities of student and administrator. For the sake of completion of the report the first part is also included in the report.
16
Part 1:
Input of the system to the instructor is the instructor.login form. He logins to the system using the login.id and password pre.assigned to him by the administrator. If the login is valid then the course page loads automatically. This course page contains a list of courses that he teaches. On selection of any course the course home page loads automatically. From this page instructor can send messages and course materials to his students, view messages sent by students, enter/edit individual marks, take print outs of mark sheet and also can change his password.
Part 2:
Input of the system to the student is the student.login form. He logins to the system using the login.id and password pre.assigned to him by the administrator. If the login is valid then the course page loads automatically. This course page contains a list of courses for which he has registered. On selection of any course the course home page loads automatically. From this page student can send messages to his course instructor, view messages and course materials sent by his course instructor, view his/her individual marks and also can change his password.
Input of the system to the administrator is the admin.login form. The administrator has full control over the system. If the login is valid then the admin home page loads automatically. This page contains options like add ne w student, instructor and course, assigning and de.assigning course to instructors and students, removing instructor, student and course and change password.
17
4.4 Implementation Issues
1. Assigning courses to student/instructor.
This functionality is given only to administrator. So multiple assigning of students to multiple courses is possible. For easiness it is better to use a list box rather than pull down menus.
2. Mark Entry by Instructor.
Entering marks for multiple students at the same time was made possible. These marks can be edited in the same page itself.
3.
Sign out from admin/instructor/student page. Sign out guaranteed by expiring the session variables used. Any requests after a sign out
will result in reloading of the corresponding login page. These measures are undertaken to prevent unauthorized entries to any page in the server.
4. Storing name of Course Materials. Extracting the name of Course material published by the instructor and storing it in database.
5. The inheritance property provided in the class diagram has not been implemented. This is for providing security.
18
5. SYSTEM TESTING 5.1 Introduction
No program or system design is perfect. The number and nature of errors in a new design depends on such factors like the communication between the user and the designer, the programmer’s ability to generate a code that reflects exactly the system specifications and the time frame for the design. The purpose of system testing is to consider all the likely variations to which it will be subjected and to push the system to its limits. It is a tedious but necessary step in system development. Testing is vital to the success of the system. System testing makes the logical assumption that if all the parts of the system are correct, the goal will be successfully achieved. The system is to be tested to see whether the outputs are correct to a known specific input. The process of system testing can be classified into 1 Unit testing 2 Module testing 3 Sub.system testing 4 System testing 5 Acceptance testing Unit testing : Individual components are tested to ensure that they operate correctly. Each component is tested independently, without other component Module testing : A module is a collection of dependent components such as an object class, an abstract data type or some looser collection of procedures and functions. A module encapsulate related component so can be tested without other modules Sub.system testing : This phase involves testing collection of modules, which have been integrated into sub.systems. Sub.system may be independently designed and implemented. The most common problem, which arises in large software systems, is sub.system mismatches. The sub.system test process should therefore concentrate on the detection of interface errors by rigorously exercising these interfaces
19
System testing : The sub.system is integrated to make up the entire system. The testing process is concentrated with finding errors, which result from unanticipated interaction between sub.systems and system components. It is also concerned with validating that the system meets its functional and non.functional requirements. Acceptance testing : This is the final stage in the testing process before the system is accepted for operational use. The system is tested with data supplied by the system procurer rather than simulated test data. Acceptance testing may reveal errors and omission in the system requirements definition because the real data exercises the system in different ways from the test data. Acceptance testing may also reveal requirements problems where the system’s facilities do not really meets the users needs or the system performance is unacceptable.
5.2 Testing Methods Black Box Testing
Also known as functional testing. A software testing technique whereby the tester does not know the internal workings of the item being tested. For example, in a black box test on software design the tester only knows the inputs and what the expected outcomes should be and not how the program arrives at those outputs. The tester does not ever examine the pro code and does not need any further knowledge of the program other than its specifications. The advantages of this type of testing include:
•
The test is unbiased because the designer and the tester are independent of each other.
• • •
The tester does not need knowledge of any specific programming languages. The test is done from the point of view of the user, not the designer. Test cases can be designed as soon as the specifications are complete.
White Box Testing
20
Also known as glass box, structural, clear box and open box testing. A software testing technique whereby explicit knowledge of the internal workings of the item being tested are used to select the test data. Unlike black box testing, white box testing uses specific knowledge of programming code to examine outputs. The test is accurate only if the tester knows what the program is supposed to do. He or she can then see if the program diverges from its intended goal. White box testing does not account for errors caused by omission, and all visible code must also be readable.
Testing Method Used
We have adopted a testing method, which is a mix of both white box and black box testing. For the units we have adopted white box testing. Then we integrated the units into modules and further into the system. There we adopted black box testing for checking the correctness of the system
21
6. SECURITY PROCEDURES
1. No student is able to view the marks of other students. 2. A student can view only the course materials of the courses for which he has registered 3. The messages can only be viewed by destinies. 4. For security a sign out option is given to each user. Sign out is guaranteed by expiring the session variables used.
22
7. CONCLUSION
Web.based Instructional Information Management System (WIIMS) is a web.based software that allows students and instructors to interact each other in an efficient manner. This web based instructional management software allows instructors to manage course related materials, communication through short messages and performance in related to marks. It allows students to view their individual marks. Currently no such system exists. So we have been assigned to do this project in a product.oriented manner. Since every department and computer labs in NITC is connected by local area network we have easily implemented it as a web.based software. We have tested the performance of our system in local area network and were happy with the response time since it reflects what we have given in our requirements specification. Now our system has only the option to send short messages. This system can be extended to send attachments along with short messages.
23
APPENDIX-A
A:1 Sequence Diagram for Adding Course
Administrator
Department Record System checkIfExist(courseId)
Course
addCourse(courseId, courseName)
[ If course exists ] Return Unsuccessful
[ If course not exist ] Course(courseId,courseName) << create >>
addtoDB(course) Return Successful
Scenario Scenario 1: Course gets added successfully. Scenario 2: Adding the course fails because the course is already in the database.
24
A:2 Sequence Diagram for assigning courses to students
Department Record System
cou := getCourse() stu := getStudent() Administrator enroll(stuID, courseID) [ if stu != NULL and cou != NULL] addCourse(cou) Student
Return Successful Return Successful
Scenario Scenario 1: Student enrolls in the course successfully. Scenario 2: Enrolling fails because the student is already enrolled in the course.
25
A:3 Sequence Diagram for entering Marks and viewing grade
Instructor
Student
Department Record System
EnterMarks Total calculated and stored
EditMark
Return Successful
Get Marks/Grade View Marks/Grade
Scenario Scenario 1: Enter marks/Edit marks successfully. Scenario 2: Viewing Marks/grade.
26
A:4 Sequence diagram for Course.Material Department Record System
Instructor
Student
Sent_CM/Msg
AddtoDB ( )
View_CM/Msg
Sent Msg
addtoDB( )
View Msg
Abbrevations CM.Course Material Msg.messages
Scenario Scenario 1: Sending and viewing course material/messages by instructor. Scenario 2: Sending and viewing messages by student.
27
WIIMS Add_course Add_User
Assign cou_stud
Assign cou_inst
Administrator Enter_mark Edit_mark Send_msg
Post CM
Instructor
View_msg
View_msg Send_msg View_CM
View_Grade
Student
Use.case diagram for WIIMS
28
APPENDIX :B
ADMINISTRATOR
B:1 Assigning course to students form
Assigning course to students
29
B:2 Adding instructor form
30
INSTRUCTOR
B:3 Write message form for instructor
31
B: 4 View Marks form for instructor
32
STUDENT B:5 View Marks form for student
33
B:6 Sending message form for student
34
REFERENCE
[1]
Ian Somerville. “Software Engineering”. Sixth Edition, Pearson Education Ltd, 2002.
[2] Page Jones. “Fundamentals of Object Oriented design in UML”. Addison Wesley Longman Pvt Ltd.,2001 [3] Elamsri and Navathe. “Fundamentals of Database Systems”. Pearson Asia Edition, 2000 [4] [5] [6] [7] V.K Jain. ”Java Server Pages and Servlets”. Pearson Asia Edition ,2000. http://jdstiles.com/javamain.html http://www.jsptut.com/index.html Ajesh Kumar P.G. Project Report titled “Web-based Instructional Information Management System”,S6 MCA,NITC,April 2005
35
