INTERNSHIP REPORT ON

EZYMANAGE
BACHELOR OF TECHNOLOGY (Computer Science & Engineering) (2009-2013)

AMITY SCHOOL OF ENGINEERING AND TECHNOLOGY

INDUSTRY GIUDE: MR. ANGAD PAUL APPIN TECHNOLOGY LAB

FACULTY GUIDE MS. NIDHI SHARMA ASET AMITY UNVERSITY

SUBMITTED BY:NAME MOHAK MAHAJAN ENROLL. NO - A2305209225 ROLL NO 2225

CERTIFICATE
This is to certify that the project entitled EZYMANAGE is a bona fide record of the industrial training project done by MOHAK MAHAJAN (Enrollment No. A2305209225) under my supervision and guidance, in partial fulfillment of the requirements for the award of Degree of Bachelor of Technology in Computer Science & Engineering from Amity School of Engineering and Technology, Sec125, Noida , Uttar Pradesh.

Faculty Guide: Ms Nidhi Sharma CSE Dept., ASET, Amity University

PLACE: DATE:

ACKNOWLEDGEMENTS

This project came to us as an excellent learning opportunity and gave us such an exposure. We would like to thank the authorities of AMITY UNIVERSITY for giving us this opportunity to work in this esteemed organization under the guidance of highly knowledgeable and experienced faculty and industry guide. First of all I would like to thanks our DG ASET Dr. Balwinder Shukla and our Head of the Department Dr. Abhay Bansal, for their ongoing support throughout the project. Secondly, I would like to thanks my project guide MS. ANGAD PAUL under whose guideline I was able to complete my project. I am wholeheartedly thankful to him for giving me his valuable time & attention & for providing me a systematic way for completing my project in time. Last but not the least; I would like to thank Ms. Nidhi Sharma, my Project Guide. Without whom this project would have been a distant reality.

MOHAK MAHAJAN Computer Science & Engineering A2305209225 B.TECH CSE (2009-2013) Amity University

TABLE OF CONTENTS

1. Title of the project. 2. Introduction and objectives of the Project. 3. Project category. 4. Analysis (DFD, ER Diagrams, Class Diagrams etc.) 5. Brief Description of the modules including the data structures. 6. Tools / Platform, Hardware and Software Requirement specification. 7. Security Mechanism. 8. Future scope and further enhancements.

ABSTRACT

EzyManage is an intranet based Java application that automates the working of a professional institute that imparts professional training in the field of IT, Management, Accounting etc. this application is created as a product and can be customized according the specific needs of the client. All such professional institutions have same kind of problems to solve such as they run professional courses for which queries are received, students are enrolled, classes are conducted, batches are scheduled, dues are to be collected, record of batches, students and study materials is to maintained, various type of reports are generated, etc. EzyManage provides solution of all these problems in the form of easy to configure and use application by automating all these functionality. Its major modules are: Enquiry Management Query Management Registration Batch Scheduling Fee and Recovery Management Attendance Management Student Management (Transfer, Break, Resume & Backup) Study Material Management Result & Certification

MODULES
Brief Description of the modules: Enquiry Management: An Enquiry represents the query of a prospective customer about various courses offered by the institution. An enquiry can be made in the following three ways- In Person, by Phone, by Internet. This module is responsible for storing the information of all enquiries into the system so that it can be retrieved later to generate various reports, to follow up non-converted enquires etc. An Enquiry that is stored into the system is either converted or becomes dead. Query Management: This module deals with the replying of queries of existing students. Once students are enrolled, they request various type of information from time to time such as current topic of a specific batch, schedule of batches of a specific consultant etc. This module mainly fetches required information stored in the system and presents it in easy to understand manner. Registration: The Bread and Butter of all such institution depends on the no. of students that enroll themselves into the courses. This module is responsible for capturing and submitting the details of all the enrolled students into the system. This information is later retrieved to generate various reports. This module receives input from Enquiry Module and its output acts as input to the Fee and Recovery Module. Batch Scheduling: An Institution that offers various courses and has various consultants needs a mechanism for proper scheduling of the batches. This module provides an interface to its user to insert the details of courses and consultants as well as to plan and view schedules. Fee and Recovery Management: This module is responsible for entering fee details of the registered students into the system,

generating due fee reports, collected fee reports, arrears and dead arrears. It also has the provision of factoring service tax into the collected fee, inclusively or exclusively as desired by the client.

Attendance Management: This module provides an interface to mark attendance of students, and generates batch wise, course wise daily, weekly and monthly attendance and absentee summary reports. Student Management: Registering in one batch and then seeking transfer to another batch, discontinuing one batch and resuming another batch is a common phenomenon in all such institutions. This module deals with keeping track of all such transfers, breaks and resumption. It provides an interface to facilitate registering all transfers, breaks or resumptions into the system and generates student wise, course wise, consultant wise reports of breaks, transfers and resumptions. Study Material Management: Mostly all such institutions provide study material in the form of books, printed notes and CDs to their students. This module deals with keeping track of course wise, batch wise distribution of study material. It provides an interface to submit the details of all available study materials into the system, details of all distribution into the system, and generates course wise, batch wise distribution reports as well as study material availability reports. Result & Certification: All the professional institutions have the provision of awarding certificates after successful completion of the courses for this, in house examinations are conducted. This module provides an interface to submit results of examination as well as details of awarding certificates into the system. It generates course wise, month wise certificate distribution report as well as facilitate query of students results.

SOFTWARE REQUIRED: The product is implemented as a collection of Java web applications that extensively use Struts 2.0 framework, Hibernate 3.2 framework, Jasper Reports for Reporting and Oracle10g as RDBMS package. Software required for the development and execution of the project are j2sdk1.5 or above and any operating system having Java Virtual Machine, tomcat 5.5 or above web server Apache and Jasper Reports, Struts2 and JPA (Hibernate 3.0 APIs). HARDWARE REQUIRED: As the product is a portal that needs web server and database servers, its hardware requirements are nontrivial. For reasonable performance a dedicated web server and database server are required.

TOOLS AND PLATFORM: FRONT END

BACK END PLATFORM USED HIGHER Web Server/application server glassfish,tomcat,weblogic10 MINIMUM HARDWARE REQUIREMENTS: PROCESSOR PENTIUM 4 RAM 1 GB HARD DISK 40 GB

J2EE,JPA with Hibernate, Struts ORACLE WINDOWS XP AND

Introduction and Objective:

EzyManage is an intranet based Java application that automates the working of a professional institute that imparts professional training in the field of IT, Management, Accounting etc. this application is created as a product and can be customized according the specific needs of the client. All such professional institutions have same kind of problems to solve such as they run professional courses for which queries are received, students are enrolled, classes are conducted, batches are scheduled, dues are to be collected, record of batches, students and study materials is to maintained, various type of reports are generated, etc. EzyManage provides solution of all these problems in the form of easy to configure and use application by automating all these functionality. Its major modules are: Enquiry Management Query Management Registration Batch Scheduling Fee and Recovery Management Attendance Management Student Management (Transfer, Break, Resume & Backup) Study Material Management Result & Certification

Project Category:
The product is a web application that is to be implemented on local Intranet. The advantage of developing the product as web application is that it need not be installed on individual machines of clients. A web application is installed on the server and client access it using a browser. The product comes under the category of MIS as it captures information related to different operations of an educational institution and generates various reports which help the management in decision making.

Analysis: Context Level DFD of EzyManage

Consultants

Mark Attendance Query Status

Submit Follow up Remarks Details Enter Enquiry Details Enter Registration Details

Counselors

Mark Brakes, Resumption, & transfer View Batch Details Update Batch Status

Submit Query Criteria.

EzyManage
View Query Result View Follow up Reports

Adds courses & Users

View Reports

Generates Reports

Enter, view and update Fee Details

Managers

Accountant

Brief Description of the modules:

Enquiry Management: An Enquiry represents the query of a prospective customer about various courses offered by the institution. An enquiry can be made in the following three ways- In Person, by Phone, by Internet. This module is responsible for storing the information of all enquiries into the system so that it can be retrieved later to generate various reports, to follow up non-converted enquires etc. An Enquiry that is stored into the system is either converted or becomes dead. Query Management: This module deals with the replying of queries of existing students. Once students are enrolled, they request various type of information from time to time such as current topic of a specific batch, schedule of batches of a specific consultant etc. This module mainly fetches required information stored in the system and presents it in easy to understand manner. Registration: The Bread and Butter of all such institution depends on the no. of students that enroll themselves into the courses. This module is responsible for capturing and submitting the details of all the enrolled students into the system. This information is later retrieved to generate various reports. This module receives input from Enquiry Module and its output acts as input to the Fee and Recovery Module. Batch Scheduling: An Institution that offers various courses and has various consultants needs a mechanism for proper scheduling of the batches. This module provides an interface to its user to insert the details of courses and consultants as well as to plan and view schedules. Fee and Recovery Management: This module is responsible for entering fee details of the registered students into the system, generating due fee reports, collected fee reports, arrears and dead

arrears. It also has the provision of factoring service tax into the collected fee, inclusively or exclusively as desired by the client.

Attendance Management: This module provides an interface to mark attendance of students, and generates batch wise, course wise daily, weekly and monthly attendance and absentee summary reports. Student Management: Registering in one batch and then seeking transfer to another batch, discontinuing one batch and resuming another batch is a common phenomenon in all such institutions. This module deals with keeping track of all such transfers, breaks and resumption. It provides an interface to facilitate registering all transfers, breaks or resumptions into the system and generates student wise, course wise, consultant wise reports of breaks, transfers and resumptions. Study Material Management: Mostly all such institutions provide study material in the form of books, printed notes and CDs to their students. This module deals with keeping track of course wise, batch wise distribution of study material. It provides an interface to submit the details of all available study materials into the system, details of all distribution into the system, and generates course wise, batch wise distribution reports as well as study material availability reports. Result & Certification: All the professional institutions have the provision of awarding certificates after successful completion of the courses for this, in house examinations are conducted. This module provides an interface to submit results of examination as well as details of awarding certificates into the system. It generates course wise, month wise certificate distribution report as well as facilitate query of students results.

Data Structures
(1) User: This table shall store general information of the users. It contains following fields.

Field name userId name address mobileNo mailId designation

Data type Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2

Constraint/Description Primary key Not Null Not Null Not Null Not Null Not Null

(2)

LoginDetails: This table shall store user information to be used at the time of login. It contains following fields.

Field name userId loginId password role

Data type Varchar2 Varchar2 Varchar2 Varchar2

Constraint/Description Foreign key (User) Login Id of the user, Unique Not Null Not Null, (manager, accountant, consultant etc.)

(3)

Enquiry: This table shall store enquiry information. It contains following fields. Data type Constraint/Description

Field name

enquiryId name mailId phoneNo mobileNo enquiryDate mode status attendantId courseName comment followupDate

Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Date Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 date

Primary key Not Null

Not Null Not Null, (In Person, Mail, telephonic) (To be Attended, converted, on hold, dead) Foreign key (userId of userDetails ) Not Null (Friend, News Paper Ad, etc.) Any comment marked by attendant. Date on which enquiry is to be followed up.

awernessSource Varchar2

(4)

EnquiryFollowup: This table shall store enquiry follow-up information. It contains following fields.

Field name enquiryId

Data type Varchar2

Constraint/Description Primary key Not Null, Date on which enquiry is followed-up. Not Null, (In Person, Mail, telephonic) Foreign key (userId of userDetails ) Any comment marked by attendant at the time of follow-up.

followupDate Date mode attendantId comment Varchar2 Varchar2 Varchar2

(5)

Student: This table shall store general information of students. It contains following fields.

Field name registrationId name address phoneNo mobileNo mailId qualification boardUniv college branch (6)

Data type Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2

Constraint/Description Foreign key (Registration)

Not Null Not Null Not Null Name of study Center in case of correspondence. IT, CS etc.

Registration: This table shall store information regarding registration of students in a batch. It contains following fields. Data type Varchar2 Date Varchar2 Number Number Number Varchar2 Varchar2 Specific timing or consultant etc. Foreign key (Enquiry) Constraint/Description Primary key Not Null, Registration Date Foreign key (Batch) Not Null Not Null

Field name registrationId regDate batchId regAmount totalFee discount comment enquiryId

modules (7)

Varchar2

Not Null. (Modules to be covered.)

FeeSchedule: This table shall store information about fee schedule of students. It contains following fields. Data type Varchar2 Varchar2 Varchar2 Varchar2 d a te Varchar2 Varchar2 Constraint/Description Primary key Foreign key (Registration) Not Null, (Amount to be collected.) Not Null, (First/second Installment etc) Not Null Not Null, (due, collected, arrear, dead)

Field name scheduleId registrationId amount description expectedDate status comment (8)

collectionDetails: This table shall store information about fee collection. It contains following fields. Data type Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Number Number Not Null (amount serviceTax) Not Null Constraint/Description Primary Key Foreign key (Fee Schedule) Not Null, (Amount collected.) Not Null Not Null (cash, check, credit card etc.)

Field name collectionId scheduleId amount mode comment fee serviceTax

collectionDate date

(9)

CheckDetails: This table shall store check details. It contains following fields. Data type Varchar2 Varchar2 Varchar2 d a te Varchar2 Varchar2 Constraint/Description Foreign Key (Collection Details) Not Null Not Null Not Null Not Null Not Null (Received, In Clearing, Bounced etc.)

Field name collectionId bankName checkNo checkDate clearingDate status

(10) RecoveryFollowup: This table shall store recovery follow-up information. It contains following fields. Field name scheduleId followupDate mode coordinator comment Data type Varchar2 Date Varchar2 Varchar2 Varchar2 Constraint/Description Foreign Key (Fee Schedule) Not Null Not Null, (Phone, SMS, In person) Foreign key, userId (User) Not Null

(11) Batch: This table shall store general information about batches. It contains following fields. Field name batchId course Data type Varchar2 Varchar2 Constraint/Description Primary Key Not Null

consultant coordinator mode batchDuration classDuration time startDate status

Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Date Varchar2

Not Null Foreign key, userId (User) Not Null, (WD, WE, MWF,TTS) Not Null (Six Weeks, Four Moths, Six Months, etc. Not Null (1 hr, 2 hr, 3 hr etc.) Not Null Not Null (Expected in case status is Planned) Not Null (Planned, Running, On Break, Completed.) (Expected in case status is not Completed) (Expected in case status is Planned)

completionDate Varchar2 Strength Number

(12) BatchProgressDetail: This table shall store information about current and next topics of batches. It contains following fields. Field name batchId currentTopic startedOn nextTopic expDate updationDate comment Data type Varchar2 Varchar2 Date Varchar2 Date Date Varchar2 Constraint/Description Primary Key Not Null Not Null Not Null Not Null. Not Null

(13) BatchSchedule: This table shall represent schedule of the batches on a day. It contains following fields. Field name batchId Data type Varchar2 Constraint/Description Foreign Key (Batch)

roomNo scheduleDate status

Varchar2 Date Varchar2

Not Null Not Null (Tentative, Permanent)

(14) Attendance: This table shall store summary of attendance in a batch on a day. It contains following fields. Field name attendanceId batchId date strength topicCovered Data type Varchar2 Varchar2 date Varchar2 Varchar2 Constraint/Description Primary Key Foreign Key (Batch) Not Null Not Null, (No. of Students Present) Not Null

(15) AttendanceDetails: This table shall store details of attendance in a batch on a day. It contains following fields. Field name attendanceId registrationId Data type Varchar2 Varchar2 Constraint/Description Foreign Key (Attendance) Foreign Key (Registration)

(16) BreakDetails: This table shall store details of students on break. It contains following fields. Field name registrationId batchId startDate endDate Topic authorisedBy comment Data type Varchar2 Varchar2 Date Date Varchar2 Varchar2 Varchar2 Constraint/Description Foreign key (Registration) Not Null (Identifies Batch form which break is taken.) Not Null Not Null Not Null Foreign Key (userId (User)) Not Null

(17) TransferDetails: This table shall store details of transfer of students from one batch to another. It contains following fields. Field name registrationId toBatch fromBatch transferDate authorisedBy comment Data type Varchar2 Varchar2 Varchar2 Date Varchar2 Varchar2 Constraint/Description Foreign key (Registration) Not Null Not Null Not Null Foreign Key (userId (User)) Not Null

(18) DailyCollection: This table shall store summary of fee collected on a given day. It contains following fields. Field name dcId Date Cash Check Other Data type Varchar2 Date Number Number Number Constraint/Description Primary Key Not Null Not Null Not Null Not Null

(19) DCDetails: This table shall store batch wise details of fee collected on a given day. It contains following fields. Field name dcId batchId Amount Data type Varchar2 Varchar2 Number Constraint/Description Foreign Key (DailyCollection) Foreign Key (Batch) Not Null (Total amount collected from a batch on a day)

(20) MonthlyCollection: This table shall store summary of fee collected in a month. It contains following fields. Field name mcId Month Year Cash check Other Data type Varchar2 Varchar2 Varchar2 Number Number Number Constraint/Description Primary Key Not Null Not Null Not Null Not Null Not Null

(21) MCDetails: This table shall store batch wise details of fee collected in a given month. It contains following fields. Field name mcId batchId Amount Data type Varchar2 Varchar2 Number Constraint/Description Foreign Key (MonthlyCollection) Foreign Key (Batch) Not Null (Total amount collected from a batch in a month)

(22) QCollection: This table shall store summary of fee collected in a Quarter. It contains following fields. Field name qcId Quarter Year Cash Check Other Data type Varchar2 Varchar2 Varchar2 Number Number Number Constraint/Description Primary Key Not Null Not Null Not Null Not Null Not Null

(23) QCDetails: This table shall store batch wise details of fee collected in a given quarter. It contains following fields. Field name qcId batchId Amount Data type Varchar2 Varchar2 Number Constraint/Description Foreign Key (QCollection) Foreign Key (Batch) Not Null (Total amount collected from a batch in a Quarter)

(24) AnnualCollection: This table shall store summary of fee collected in a given year. It contains following fields. Field name acId Year Cash Check Other Data type Varchar2 Varchar2 Number Number Number Constraint/Description Primary Key Not Null Not Null Not Null Not Null

(25) ACDetails: This table shall store batch wise details of fee collected in a given year. It contains following fields. Field name acId batchId Amount Data type Varchar2 Varchar2 Number Constraint/Description Foreign Key (AnnualCollection) Foreign Key (Batch) Not Null (Total amount collected from a batch in a year)

(26) Distribution: This table shall store batch wise summary of study material distribution. It contains following fields. Field name distId batchId Date booksCount cdCount description Data type Varchar2 Varchar2 d a te Number Number Varchar2 Constraint/Description Primary Key Foreign Key (Batch) Not Null Not Null (Count of distributed books.) Not Null (Count of distributed CDs.) Not Null (Description of distributed books and CDs)

(27) DistributionDetails: This table shall store details of study material distribution. It contains following fields. Field name distId registrationId Data type Varchar2 Varchar2 Constraint/Description Foreign Key (Distribution) Foreign Key (Registration)

(28) Test: This table shall store summary of tests conducted for awarding grades. It contains following fields. Field name testId Date studentsCount coordinator Data type Varchar2 d a te Number Varchar2 Constraint/Description Primary Key Not Null Not Null (Count of students.) Foreign key (userId (User))

(29) TestDetails: This table shall store student wise details of tests. It contains following fields. Field name testId registrationId grade Data type Varchar2 Varchar2 Varchar2 Constraint/Description Foreign Key (Test) Foreign Key (Registration) Not Null

(30) CertificateDetails: This table shall store student wise details of certificates. It contains following fields. Field name certId Data type Varchar2 Constraint/Description Primary Key

registrationId grade date courseDesc

Varchar2 Varchar2 Date Varchar2

Foreign Key (Registration) Not Null Date on which certificate is distributed. Not Null (Desc. Of the Course & Modules mentioned in the Certificate.) Foreign Key (userId (User))

verifiedBy

Varchar2

Requirement Specification:
Software Required: The product is implemented as Java web application that extensively uses JSP, Java Beans, JDBC, and Jasper Reports. Software required for the development and execution of the project are j2sdk1.4 or above and any operating system having Java Virtual Machine, a web server or application server and API of Jasper Reports. Hardware Required: As the product is a web application that needs application server and database servers, its hardware requirements are nontrivial. For reasonable performance a System with Pentium P4 or above processor, 512 MB RAM, 40GB Hard Disk, a LAN Card, and a CDROM or USB support is required.

Security Mechanism:
Security means different things to different people depending upon their perspective. In the context of our product it means only valid users can login into the system and each user can only access the functionality authorized to the user. To prevent unauthenticated access, form based authentication implemented through Front Controller is to be used. To prevent unauthorized access, different roles are to be created by the administrator and access to features is to be controlled through these roles.

Future Scope and Further Enhancement:

Any product despite of its meticulous design and features needs enhancement with time. EzyManage being no exception needs active enhancement of features and functionality. Following features are proposed to be implemented in future to make the product more feature rich. Intranet Messaging: In each organization, there is always a need of efficient paperless, secure, and private communication medium that has the retention capabilities. We are proposing to add Intranet messaging facility to fill this requirement as an independent module in future release. Template Based Look & Feel: Being a product, it is proposed to be implemented at the site of different clients. Each client has different set of preferences for look and feel of the application. To minimize the customization process, look and feel of the application is proposed to be based on templates in future releases.