INDUSTRIAL TRAINING REPORT

TITLE OF THE PROJECT

VIRTUAL LEARNING

Submitted in partial fulfillment of the

Requirements for the award of

Degree of Bachelor of Technology in Information Technology

NNN

Submitted By

ANUDISH JAIN
1606413008

SUBMITTED TO:
Department of Information Technology
HINDUSTAN COLLEGE OF SCIENCE & TECHNOLOGY
FARAH, MATHURA, UTTAR PRADESH
 DECLARATION

I hereby declare that the Industrial Training Report entitled "Virtual Learning" is an authentic
record of my own work as requirements of Industrial Training during the period from10 June
2019 to 30 July 2019for the award of degree of B.Tech. (Information Technology),
Hindustan College of Science & Technology, Farah, Mathura, Uttar Pradesh under the
guidance of Somendra Singh Rathore.

Anudish Jain
1606413008
Date: 09/10/2019
 ACKNOWLEDGEMENT

We take this opportunity to express our gratitude and regards to our project guide Mr.
Somendra Singh Rathore for his exemplary guidance, monitoring and constant
encouragement throughout the course of this project.

We also take this opportunity to express a deep sense of gratitude to our friends for their
support and motivation which helped us in completing this task through its various stages.
I am obliged to the faculty members of the TechRefresh for the valuable information
provided by them in their respective fields. We are grateful for their cooperation during
the period of our training.

Lastly, we thank our parents for their constant encouragement without which this
assignment would not have been possible.
 CONTENTS

1. INTRODUCTION
1.1Company Profile
1.1.1Areas of Expertise
2.1.1 Work Environment
1.2 Project Profile
SYSTEM ANALYSIS
2.1Existing System
2.2Limitations of Existing System
2.3Proposed System
2.4Advantages of Proposed System
3. LITERATURE SURVEY
3.1 An Introduction to J2EE
3.2 J2EE Architecture
3.3 Distributed Multi Tiered Applications
3.4 J2EE Server Communications
4. FEASIBILITY STUDY
4.1 Technical Feasibility
Economical Feasibility
4.3Operational Feasibility
5. REQUIREMENT SPECIFICATION
5.1Hardware Requirements
5.2Software Requirements
6. SYSTEM DESIGN
6.1 Flowchart
6.2DFD (Data Flow Diagram)
6.3ERD (Entity Relationship Diagram)
7.TESTING
7.1Unit Testing
7.1.1Manual Testing
8.IMPLEMENTATION
9.MAINTENANCE
10.APPENDIX
14.1Sample Screen Shots
14.2Sample Weekly Reports
11.BIBLIOGRAPHY
 1. INTRODUCTION
1.1 Company Profile
Innovare Software Solutions (ISS) is an IT Solution Provider for a dynamic
environment where business and technology strategies converge. Its approach focuses on new
ways of business combining IT innovation and adoption while also leveraging an
organization's current IT assets. It work with large global corporations and new generation
technology companies - to build new products or services and to implement prudent business
and technology strategies in today's environment.
1.1.1 Areas of expertise
• Software Development Services
• Engineering Services
• Systems Integration
• Customer Relationship Management
• Supply Chain Management
• Product Development
• Electronic Commerce
• Consulting
• IT Outsourcing
1.1.2 Work environment
Innovare Software Solutions apply technology with innovation and responsibility to
achieve two broad objectives:
• Effectively address the business issues our customers face today.
• Generate new opportunities that will help them stay ahead in the future.
This approach rests on:
• A strategy where they Architect, Integrate and Manage technology services and
solutions — they call it AIM for success.
• A robust offshore development methodology and reduced demand on customer
resources.
• A focus on the use of reusable frameworks to provide cost and time benefits.
From time to time 360 degree feedbacks and discussions are conducted which help to
identify problem areas, improve development methods, chart out a course and create more
understanding between team members.
They offer customers the advantages of:
Speed:
They understand the importance of timing, of getting there before the competition. A
rich portfolio of reusable, modular frameworks helps jump start projects. Tried and tested
methodology ensures that they follow a predictable, low-risk path to achieve results. Their
track record is testimony to complex projects delivered within and even before schedule.
Expertise:
Their teams combine cutting edge technology skills with rich domain expertise.
What's equally important — They share a strong customer orientation that means they
actually start by listening to the customer. They are focused and coming up with solutions
that serve customer requirements today and anticipate future needs.
1.2 Project Profile
This project is developed for the electronic learning for the Training Institutions. This
project makes use of cheap communication media Internet. This product can be used for On-
Line Trainings and On-Line Seminars. It makes the institutions to provide quality of
education to the doorsteps. It makes Trainers available 24/7 if required. This incorporates the
global people under one umbrella and can share their knowledge by sitting at their desktop.

This system makes to share the Trainer’s Desktop Screen and Voice of Trainers; this
can be shared by any number of students. This system uses J2EE framework to build this
application, where this application is an enterprise application. Where the students and
trainers are remotely performing their activities. It makes use of Http-Protocol. This is a web
application where it is used to allow both trainers and students to register remotely to get the
services of application.

This System contains the following modules:

• Administration Module
• Middle- Tier
• Trainer Module
• Student Module

Administration Module:
It is responsible of configuration of the system and security concerns i.e. providing
the privileges for accessing the system. It allots course sessions to trainer and uploads course
material for trainers and students.

Middle-Tier:
The web application allows students and trainers to register if they want to interact
with each other with their software. This application acts as middle tier providing privileges
to both the users.

Trainer Module:
The Trainer side software module is used to prepare trainer side application. This
application is responsible to provide screen object to all students and share the voice to the
students. Online Chat facility further helps in bi-directional communication. The trainer can
also be approached through email.

Student Module:
The student side software module is used to prepare client side application. The
student can interact with the trainer application by using this application. This application is
used to grab the trainer desktop screen and hear the voice of the trainer. Any query can be
send through online chat facility. Email facility also helps in correspondence with trainer.
Students can download their study material and can also give online test.
 2. SYSTEM ANALYSIS

2.1 Existing System

The existing system is routine like. If the student wants to learn any thing they need to
attend the classes at their institutions. In case of any demo in the lab they can’t share the
trainer desktop and have to wait for their turn to see the desktop. The trainer conducts
such classes in several groups even within single batch. It leads to wastage of time and
resource. The audience is limited, and to conduct the classes the institutions need to
provide infrastructure and transport facilities for the students so these are little expensive
and overall wastage of the valuable time.

2.2 Limitations of Existing System

The limitations with the present system are as follows-:

• Limited accessibility of training

• Limited audience
• Infrastructure and transport facilities
• No global networking opportunities
• No timeliness of communication
• No online help available
2.3 Proposed System
A Virtual Learning Environment is a web-based education system, sometimes
referred to as an on-line class. In order to have access to the virtual classroom, the student
and the instructor would need an Internet provider, such as, Netscape Navigator or Microsoft
Internet Explorer. Most educational institutions have Internet access and computer labs
available for those students who do not have Internet access in their home. The virtual
classroom can include such technologies as the Internet, E-mail, chat rooms and virtual
desktop. Virtual classrooms can have centralized instruction, which involves the class having
a specific meeting time to come together in the course chat room, to very decentralized
instruction whereby students work through tutorials at their own pace and under their own
direction. Students normally communicate with one another and with the instructor via e-
mail and can send their assignments and offline query through e-mail.

2.4 Advantages of Proposed System

The proposed system has huge number of advantages over the existing system. The
advantages are: -
• Accessibility of training i.e., 24/7
• Audience size -- knowledge base
• Timeliness of communication
• Consistency of information
• Interactivity
• Shared sense of identity/unity
• Effective use of time and resources
• Quality of training
• Extend geographic connectivity (remote access over Internet)
• Improve security (using passwords and encryption of data)
• Reduce transit time and transportation costs for remote users
• Improve productivity
• Provide global networking opportunities
• Provide broadband networking compatibility
• Provide faster ROI (return on investment) than traditional WAN
• Uploading files
• Downloading files
 3. LITERATURE SURVEY

3.1 An Introduction to J2EE

The Java2 Enterprise Edition (J2EE) is a powerful collection of technologies that sit
on top of the Java2 Standard Edition (J2SE) environment. This base of Java2 provides a
stable and reliable application environment that runs on many different operating system
(OS) platforms. The cross-platform compatibility lifts both application and server
environments above the dependencies of specific OS and hardware platforms. The Enterprise
technologies that extend the Java2 environment are focused upon providing standard
interfaces, which J2EE application server vendors can implement while providing a robust
environment for server-based solutions; not only are J2EE Enterprise solutions free from OS
and hardware dependencies, but also achieve a high degree of portability between application
servers. It is precisely this standards-based approach that continues to attract Enterprise
systems development.

3.2 J2EE Architecture

The required relationships of architectural elements of the J2EE platform are shown in Figure
4.1. (next page). This figure shows the logical relationships of the elements; it is not meant to
imply a physical partitioning of the elements into separate machines, processes, address
spaces, or virtual machines. The Containers, denoted by the separate rectangles, are J2EE
runtime environments that provide required services to the application components
represented in the upper half of the rectangle. The boxes in the lower half of the rectangle
denote the services provided.
For example, the Application Client Container provides Java Messaging Service (JMS) APIs
to Application Clients, as well as the other services represented. The arrows represent
required access to other parts of the J2EE platform. The Application Client Container
provides Application Clients with direct access to the J2EE required Database through the
Java API for connectivity with database systems, the BCTM API. Similar access to
databases is provided to JSP pages and servlets by the Web Container, and to Enterprise
beans by the EJB Container. As indicated the APIs of the Java 2 Platform, Standard Edition
(J2SETM), are supported by J2SE runtime environments for each type of application
component.
3.3 Distributed Multi Tiered Applications
The J2EE platform uses a distributed multi tiered application model for Enterprise
applications. Application logic is divided into components according to function, and the
various application components that make up a J2EE application are installed on different
machines depending on the tier in the multi tiered. J2EE environment to which the
application component belongs. Figure 4.2 shows two multi tiered J2EE applications divided
into the tiers described in the following list.
• Client-tier components run on the client machine.
• Web-tier components run on the J2EE server.
• Business-tier components run on the J2EE server.
• Enterprise information system (EIS)-tier software runs on the EIS server.

Figure 4.2. Multitiered Applications

Although a J2EE application can consist of the three or four tiers shown in Figure 4.2, J2EE
multitiered applications are generally considered to be three-tiered applications because they
are distributed over three locations: client machines, the J2EE server machine, and the
database or legacy machines at the back end. Three-tiered applications that run in this way
extend the standard two-tiered client and server model by placing a multithreaded application
server between the client application and back-end storage.
3.4 J2EE Server Communications

Figure 4.3 shows the various elements that can make up the client tier. The client
communicates with the business tier running on the J2EE server either directly or, as in
the case of a client running in a browser, by going through JSP pages or servlets running
in the web tier.

Figure 4.3. Server Communications.

Your J2EE application uses a thin browser-based client or thick application client.
In deciding which one to use, you should be aware of the trade-offs between keeping
functionality on the client and close to the user (thick client) and offloading as much
functionality as possible to the server (thin client). The more functionality you off-load to the
server, the easier it is to distribute, deploy, and manage the application; however, keeping
more functionality on the client can make for a better perceived user experience.
 4. Feasibility Study

4.1 Technical Feasibility

As per the technology is considered it is advanced in terms of manpower, intelligence,
machine requirements, the company has Tomcat Server, Daffodil Database, Window XP
Professional operating system, J2EE as technology, hence the system is found to be
technically feasible.

4.2 Economical Feasibility

Regarding the cost and benefits, the application, which is to be developed and
implemented, will give large benefits to the company as it saves time and reduces efforts
of interaction between various users. Thus this project is considered economically
feasible.

4.3 Operational Feasibility

Operational feasibility is a consideration about the working of the application after the
product being installed on to any system. The company, which will use the product, can also
use the application to interact with its own people as well as its clients. This is meant to
increase productivity in the long run. Thus this project is considered operational feasible.
 5. REQUIREMENT SPECIFICATION

The hardware and software requirements specified are minimum and the system
would show an improved performance in advanced configured system.

5.1 Hardware Requirements

1. C.P.U -Pentium iii and above
2. Memory -64 MB RAM
3. Disk Drivers - 3 ½ floppy disk drive or CD-Drive
4. Monitor - SVGA color monitor
5. Keyboard - 104 Keys
6. Other I/O parts
• Mouse
• Speaker
• Microphone
7. Modem
5.2 Software Requirements
1. Operating System : Windows 2000 Professional and above
2. Platform : J2EE.
3. GUI : Swing/JFC
4. Web Technologies : Servlet, JSP
5. Web Server : Tomcat
6. Databases : Daffodil
 6. SYSTEM DESIGN

6.1 DFD (Data Flow Diagram)

Data Flow Diagrams are made of four types of symbols: -
Process: Process shows what systems do. Each process has one or more data inputs and
produce one or more data outputs. Processes are represented by circle in DFD. Each process
has a unique name and a fixed number of I/O data arrows.

Data Flow: A Data flow connects the output of an object or process to the input of another
object or process. It represents an intermediate data values within a computation. An arrow
between the producer and the consumer of the data value represents a data flow. The arrow is
labeled with a description of the data, usually its name or type.

Actor: An actor is an object that drives the data flow graph by producing or consuming
values. Actors are attached to the inputs and outputs of the data flows graph. Actors are
represented by rectangle in DFD.

Data Stores: A data store is a repository of data. Processes can enter data into a store or
retrieve data from the data store. Each data store is represented by an open-ended rectangle in
the DFD and each store has a unique name.
 6.2 Flowchart

Start

Login

Trainer Student

Administrator

Stop
 Zero Level DFD of Student Module (VLE)

USER DETAIL

Check Validity
TEST FILE

Login 1 Attend Test

STUDENT LOGIN
PROCESS
Receive from Trainer

Download
MESSAGE FILE

MATERIAL FILE
 First Level DFD of Student Module (VLE)

USER DETAIL

Check Validity

Invoke 2 Course Materials

Login
1 DOWN LOAD MATERIAL FILE
STUDENT LOGIN PROCESS
Logout PROCESS Invoke

Invoke
Invoke 4
3 Observe Virtual Desktop / Chat Msg SUBMIT
9 LOGIN QUERY
Online Paper 7 CLASS
PROCESS TEST
MESSAGE ROOM Query
PROCESS
Test Result Query Ans

Solved Paper MSG FILE

TEST FILE Msg Data
Msg Data
8
EVALUATE 6 5
TEST REPLY SEND
Test Ans
QUERY QUERY
Test Result

Offline Query / Assignment

RESULT FILE
Chat Msg

Test Result
Query
TRAINER
 Second Level DFD of Student Module (VLE)

TEST FILE
RESULT FILE
USER DETAIL
Test Ans
Online Paper
Test Result
Check Validity Submit
9 Solve Paper Send
8 Start Test 10 11
Invoke GET Test
Login TEST QUES ANS EVALUATE Result
1 PROCESS PAPER PAPER TEST
STUDENT LOGIN
Logout PROCESS
12
Test Result
Invoke
Invoke Invoke Observe
SENT TO
13 Virtual Chat Msg
CHECK 2 Login Desktop 5
4
MESSAGE 16 LOGIN 3 SUBMIT Test
ANALYZE
DOWN LOAD CLASS START CLASS QUERY Result
CLASS
PROCESS ROOM
Query
Emails Msg Data
Select Material
MSG FILE
14 Query Ans
PROCESS
MESSAGE 17 7 Msg Data
DOWN LOAD REPLY
MATERIAL QUERY 6
Assignment / Query SEND
QUERY
Download
Msg Data
15 Chat Msg
REPLY
MESSAGE
MATERIAL FILE

Messages/ Attachments

TRAINER
 6.3 ERD (Entity Relationship Diagram)

ER Diagram of System (VLE)

Pwd Address Name Email

Mid Mname SSid
SId
Date
Phone Downloads
m Cid
Uid m

STUDENT m
Register/ COURSE MATERIAL
Edit
m m
m m
EndDate
m Uid Manipulates
StartDate COURSE Manipulates /Upload
Pwd

Cname m 1 1 1
Takes
Manipulate 1 ADMINISTRATOR
Cid
/Allot
Contains 1 1

Checks Downloads

m m Register/
m Feedback Edit
Attends SSid DaysLeft m
SESSION
SSid SESSIONSTATUS
m
1
SSname

Cid Update
SSdate Request/
m
Takes
m m
1
m 1
TEST Conduct
m TRAINER
Uid
Tid
Result phone
pwd
Cid TDate Train_id
name address Email
 6.4 Table Design

The tables are organized so as to:

• Reduce redundancy
• Minimize addition, deletion and updating anomalies
• Simplify querying and retrieving data from database

The method of organizing or structuring data into table by eliminating anomalies is

known as Normalization. Normalization is required to minimize redundancy and to avoid
anomalies in database.

Following are the tables used in this Project (VLE):

Table : Login (Primary key is User_name)

This table maintains login detail of users.

Data Item Data Description Data Type Size

User_name User Varchar 25

Pwd Password Varchar 25

Type Type Varchar 15

Table : Batch (Primary key is Bid)
This table maintains Batches that are to be started.

Data Item Data Description Data Type Size

Bid Batch no unique number Int Default

Batch_name Name of the project Varchar 25

Batch_desc Description of the batch Varchar 70

Start_date Commencement date Date Default

End_date Batch completion date Date Default

Table : Course (Primary key is Cid)

This table maintains what all courses are available.

Data Item Data Description Data Type Size

Cid Course no Int Default

Course_name Course_name Varchar 25

Course_desc Course_desc Varchar 70

Table : Session (Primary key is Ssid)

This table maintains what all sessions in course are available to be allotted.

Data Item Data Description Data Type Size

Ssid Session id Int Default

Cid (FK) Course no Int Default

Session_name Session_name Varchar 25

Session_desc Session_desc Varchar 70

Table : Batch_course
This table contains all the courses allowed in the Batch.

Data Item Data Description Data Type Size

Bid (FK) Batch id Int Default

Cid (FK) Course id Int Default

Table : Trainer (Primary key is Tid)

This table maintains all the trainers who are registered.

Data Item Data Description Data Type Size

Tid Trainer id Int Default

Tname Trainer name Varchar 20

Taddress Address Varchar 60

Tphone Phone Numeric 20

Temail Email Varchar 35

 7. TESTING

7.1 Unit Testing

Unit test uses low-level design as the guide to test the control path within the boundary of the
module. Unit testing is also known as module testing. Since the proposed project has different
modules, the testing is done individually. Using the detailed design description as guide,
important control paths are tested to uncover errors within the boundary of the module.
This testing was carried out during the programming stage itself. In this testing step each
module is found to be working as regards to the expected output from the module. Typically
unit testing is done by programmers and not by testers, as it requires detailed knowledge of
the internal program design and code.

7.2 Manual Testing

Manual Testing is the type of testing in which we do the complete testing of our project
manually. After doing yhe complete Manual testing we found that our project is working
properly without any type of problem.
9.2 Sample Unit Test Cases

9.2.1 Unit Name: User Login Form

Success Cases

S. No Test Case Description Test Scripts/Actions Expected Result Pass/Fail

(P/F)

Field Validations

1 Validate User Id, Enter valid User ID Accepted and main P

Password, type fields form of different
and a valid Password
user is shown
(num, chars), maxlength
up to 25 chars

Error Cases

S. No Test Case Description Test Scripts/Actions Expected Result Pass/Fail

(P/F)

Field Validations

1 Validate User Id, Enter –ve num, wrong Should not be P

Password, type fields Password accepted, error
message is shown
9.2.2 Unit Name: Trainer Registration Form

Success Cases

S. No Test Case Description Test Scripts/Actions Expected Result Pass/Fail

(P/F)

Field Validations

1 Validate Enter alphanumeric Both password and P

Password/Retype start with chars, retype password
Password fields are matched
maxlength up to 25
chars

2 Validate Trainer Id Enter alphanumeric Accepted P

3 Validate name Enter only chars Accepted P

4 Validate Address Enter the Accepted P

alphanumeric

5 Validate Phone number Enter only Numeric Accepted P

and a sp. char,
hyphen

6 Validate E-mail Enter Alphanumeric Accepted P

address start with chars, sp.
chars @, _

Functionality Validation

1 Verify submit Click Submit Trainer details are P

accepted

2 Verify Reset Click Reset All fields are clear P

 Error Cases

S. No Test Case Description Test Scripts/Actions Expected Result Pass/Fail

(P/F)

Field Validations

1 Validate Enter special chars or Should not be P

Password/Retype password field is not accepted, Error
Password matched with retype message is shown
filed

2 Validate Trainer Id Enter the special Should not be P

chars or numeric accepted, Error
message is shown

3 Validate name Enter the special Error message is P

chars or numeric shown

4 Validate Address Enter the special Error message is P

chars or numeric shown

5 Validate Phone number Enter Alphanumeric Error message is P

shown

6 Validate E-mail Enter Alphanumeric Error message is P

address without@ shown

Functionality Validation
1 Verify submit Click Submit Should not be P
accepted, Error
( required field are
message is shown
blank)
9.2.3 Unit Name: Student Registration Form

Success Cases

S. No Test Case Description Test Scripts/Actions Expected Result Pass/Fail

(P/F)

Field Validations

1 Validate Enter alphanumeric Both password and P

Password/Retype start with chars, retype password
Password fields are matched
maxlength up to 25
chars

2 Validate User name Enter only chars Accepted P

3 Validate Course Enter alphanumeric Accepted P

4 Validate Batch Enter Valid batch Accepted P

5 Validate start date Enter valid date Accepted P

6 Validate End date Enter valid date Accepted P

7 Validate full name Enter only chars Accepted P

8 Validate Address Enter the Accepted P

alphanumeric

9 Validate Phone number Enter only Numeric Accepted P

and a sp. char,
hyphen

10 Validate E-mail Enter Alphanumeric Accepted P

address start with chars, sp.
 chars @, _

Functionality Validation

1 Verify submit Click Submit Students details are P

accepted

2 Verify Reset Click Reset All fields are clear P

Error Cases

S. No Test Case Description Test Scripts/Actions Expected Result Pass/Fail

(P/F)

Field Validations

1 Validate Enter special chars or Should not be P

Password/Retype password field is not accepted, Error
Password matched with retype message is shown
filed

2 Validate user name Enter the special Should not be P

chars or numeric accepted, Error
message is shown

3 Validate course Enter sp chars Error message is P

shown

4 Validate batch id Enter sp chars Error message is P

shown

5 Validate start date Enter invalid date Error message is P

shown

6 Validate end date Enter invalid date Error message is P

shown
7 Validate name Enter the special Error message is P
chars or numeric shown

8 Validate Address Enter the special Error message is P

chars or numeric shown

9 Validate Phone number Enter Alphanumeric Error message is P

shown

10 Validate E-mail Enter Alphanumeric Error message is P

address without@ shown

Functionality Validation

1 Verify submit Click Submit Should not be P

accepted, Error
( required field are
message is shown
blank)
 8. MAINTENANCE

The maintenance phase of the software life cycle is the time period in which a
software product performs useful work. Generally, it takes 5 times more time than
development time. The maintenance activities involve making enhancement to software.

This phase includes various activities; some of them are given below
• Providing new functional capabilities
• Improving user displays and modes of interaction, upgrading external documents and
internal documentation, or upgrading the performance characteristics of a system.
• Adaptation of s/w to a new environment may involve moving the s/w to a different
machine or for instance, modifying the software to accommodate a new environment
• Modifications and revalidation of software to correct errors.

Maintainability, like all high-level quality attribute, can be expressed in terms of

attributes that are built into the product. The primary product attributes that contribute to
software maintainability are clarity, modularity, and good internal documentation of the
source code, as well as appropriate supporting documents. VLE application contains code
comments to aid in debugging and maintenance.
 9. APPENDIX

9.1 Sample Screen Shots

This is the Login screen for the users, to get connected to the organization through VLE.
Administrator Registering the Students.
Students download study materials.
Trainer starts online class for a batch.
Students attending online class through virtual desktop and chat room.
Student’s mailbox for offline helps support.
Students online test page.
Student attending online test.
 9.2 Sample Weekly Reports

Weekly Report 1

Name : Sajid Akhtar.

Reg No : 1DA03MCA25.
Project : Virtual Learning Environment.
Mail ID: [email protected]
Phone no: 9886080641.

Plan for week no: 01 Date: 7th Feb to 10th Feb 2006.
Date: 7th Feb to 10th Feb 2006: Requirement analysis.

Execution

7th – 10th February 2006: According to the objectives of the customer the
requirements are gathered based on the environment,
finances and resources. Studying the present system in
detail and where improvements are required. “What” is
to be done is set here.
Weekly Report 2

Name : Sajid Akhtar.

Reg No : 1DA03MCA25.
Project : Virtual Learning Environment.
Mail ID: [email protected]
Phone no: 9886080641.

Plan for week no: 02 Date: 13th Feb to 17th Feb 2006.
Date: 13th Feb to 17th Feb 2006: Data Collection.

Execution

Date: 13th Feb to 17th Feb 2006: Data is collected based on the manual functionality of
the working system. Data is even collected using
questionnaires, on-site review, and observation and
interviewing the people working at different levels.
Weekly Report 3

Name : Sajid Akhtar.

Reg No : 1DA03MCA25.

Project : Virtual Learning Environment.

Mail ID: [email protected]

Phone no: 9886080641.

Plan for week no: 03 Date: 20th Feb to 24th Feb 2006.

Date: 20th Feb to 24th Feb 2006: Backend data processing.

Execution
Date: 20th Feb to 24th Feb 2006:

According to the data gathered, it is analyzed and

normalized to remove any duplication of data and to

remove any anomalies using normal forms.

 Weekly Report 4

Name : Sajid Akhtar.

Reg No : 1DA03MCA25.

Project : Virtual Learning Environment.

Mail ID: [email protected]

Phone no: 9886080641.

Plan for week no: 04 Date: 27 Th Feb - 3rd March 2006.

Date: 27 Th Feb - 3rd March 2006: Data Flow.

Execution
Date: 27 Th Feb - 3rd March 2006:

According to the data collected and functionality the

flow of the data is traced. According to the flow, the

different levels of Data Flow Diagrams are created that

gave a clear-cut idea of data flowing, storage and

processing of data.
 10. BIBLIOGRAPHY

[1] Technical and Functional Specification received from the company.

[2] Herbert Schildt, The Complete Reference Java 2 fifth edition, Tata
McGraw-Hill, 5 Edition, 2002.
[3] Khalid Mughal, Rolf Rasmussen, A Programmer's Guide to Java
Certification: A Comprehensive Primer.
[4] Pallavi Jain and Shadab Siddiqui with NIIT, J2EE Professional Projects.
[5] Elias M. Awad, System Analysis and Design, Second Edition.
[6] Henry F Korth, Database System Concepts, The McGraw-Hill Companies, 2 Edition
2002.
[7] Roger S. Pressman, Software Engineering (A Practitioner’s Approach),
The McGraw-Hill Companies, 5 Edition 2002

Web Sites:
[1] www.google.com
[2] www.jakarta.apache.org
[3] www.daffodildb.com