You are on page 1of 28

1.0 INTRODUCTION:Project Scheduler (projectscheduler.co.

in) is a total management and informative system,


which provides the up-to date information and management of all the records related to the
project of college students, institution and in the company. Project Scheduler helps the
company to overcome its difficulty in tracking the resources of the company by presenting the
customized reports, lab scheduling and is used to track the information related to project which
belongs to the particular college, Institution or Company, which helps in effectively and timely
manage the applications belongs to them.
Project Scheduler is a web-based application using the three-tier architecture. The ability to
handle the multi-user environment and maintaining the highest security for the access are some
of the features of this application.
Project Scheduler uses MySQL 5.5 as the back end for the database and uses all its features
offered in the web based technology for its transactions.

1.1 BACKGROUND:The Project Scheduler allows institutes to receive applications through the web and candidates
need not collect physical forms. Students are required to visit the registration of website in the
institute. All eligibility criteria, no. of seats, selection criteria etc are mentioned in the website.
Admin are required to fill in the online updating and submit it online. On successful submission
of the report to the student receives a unique form no. against which he / she is required to make
the payment of the application form. For institutes willing to receive the application fees online
we can also integrate the payment gateway. Merit list of eligible candidates are generated
through the application and published on the admission website. The Online Admission
Application System can also be programmed to electronically notify students about the outcome
of the detailed process.
Since the candidates information is entered by the student and that to once, this result in reduced
turnaround time for the entire admission process. This saves a lot of time and effort on the part of
the institute as well as for the candidates. Moreover, the merit list of admitted students is
generated automatically by the application, ruling out any chance of foul play. In this case only
the deserving candidates get management to the institute.
Project Scheduler has been accepted with widespread praise and as such several institutes have
approached us for implementing a similar system for them.

1.2 OBJECTIVES
The main objective of this application is to remove all possible drawback of computer less
requirement the basic goal of this application are:A. Print Forms :
Institute incurs expenditure on printing of admission forms, and in absence of any
reliable forecasting system on how much application it is going to receive it may
overspend by printing excessive application forms or may fall in crisis if there is
excess demand of application forms.
Once printed, changes to the application form are not only difficult but also incurs
additional cost.
B. Handle Queries & Distribute Forms :
Wastage of institute's resources as same information has to be imparted to
candidates / guardians individually.
Students / Guardians have to queue up numerous times i.e. to collect form, to
submit form, to view merit list, etc.
C. Collect Forms :
Chances of form misplacement are very high, because of huge number of
applications.
Wastage of institute's resources due to involvement of people / teachers in form
collection.
D. Sort List Candidates :
It is difficult to stop in-eligible candidates from applying.
It is a tedious and time consuming process to list out data of each candidate,
manually check them against documents submitted, resulting in delay and
wastage of valuable resources.
Multiple merit lists often leads to duplication of work for the institution, even candidates /
guardians have to visit again and again to check the latest merit list.

1.3 PURPOSE AND SCOPE


1.3.1 Purpose:
The present manual work at an educational institution like course registration, student
registration, Faculty registration, notes preparation, project training and college for students takes
too much time. Manual work can avail the above mentioned facilities only during the working
hours of the educational institution.
However, the Online Admission System remains all these drawbacks. Students can now avail all
these facilities round the clock. All this process now takes less time and any information can be
retrieved on time with minimum delay. This website will reduce the workload on part of the
administration.

1.3.2 Scope:
Projectscheduler.co.in portal will provide facilities like registration, upload document forms,
consulting, examination and certification of the project training report.
A. 24 x 7 Solution :
Minimizes time of processing - due to no time barrier, institutes admission
process time is reduced. Institutes can publish their merit list lot earlier than they
could have in case the same thing was required to be done manually following the
traditional way.
Maximizes Availability - allows candidates to fill application form at their
convenient time, our statistics from the past trend shows that almost 40% of the
application form are received during the non-office hours (i.e. 08:00 A.M. to
08:00 P.M.).
B. No Geographical Boundary :
Institutes don't need take the burden of posting the application form for outstation
candidates.
Candidates can fill application form from anywhere i.e. convenient place.
C. No Long Queues :
Students don't need to stand in long queues to get their queries answered.
Students don't need to queue up to get application form and submit the same.
Man Power Saving - Institutes don't need to assign additional security to manage
huge crowd.
D. Reduces Paper Work :
Institutes no longer require printing & storing forms.
Institutes no longer require collecting forms of all the candidates and filing them.
Institute can take the print of only candidates who are admitted to the college.

E.

F.

G.

H.

I.

Both these result in not only cost saving but also man power saving.
Only Eligible Candidate Apply :
Minimizes Data Redundancy - checks can be provided so that only eligible
candidates can apply. Moreover the candidate data is to be entered only once.
Reduces Human Involvement :
Releases institutes man power resources.
Institutes no longer require deputing personnel for addressing to candidates /
guardian's query.
Institutes no longer require deputing personnel to distribute and collect forms.
Institutes no longer require deputing personnel to file collected forms.
Enhance Productivity - as a result of this institute can utilize these man power
resources in other activities.
Accurate and Reliable :
In the traditional way human error might creep in due to fatigue and monotonous
nature of work involving numbers.
Very Accurate and Reliable - The process is very accurate and reliable due to
limited human involvement.
Dynamic and User Friendly :
The entire process is very dynamic - any changes can be reflected in real time &
will immediately reach the candidates.
The process is simple & user friendly - similar to filing a form manually, the
difference being use of keyboard instead of pen.
Customizable Real Time Reports :
Institutes can monitor the ongoing process.
Have day to day summary of progress of the admission.
Great Flexibility - Various types of reports can be generated in quick time with
minor changes in the design.

2.0 SURVEY OF TECHNOLOGIES:2.1 Front End Tool: PHP


PHP is an open source server side scripting language designed for web development by
generating dynamic web pages, created by Rasmus Lerdorf in June 1995.
PHP has the following properties:

Platform independent
Supports Object-orientated programming concepts
Loosely-typed programming language
Automatic memory management

2.1.1 WHY I AM USING FRONT END TOOL AS A PHP?


Windows means that you are still going to spend money. PHP was created by Sun Microsystems
as an extension to Java.
Despite having the same task, PHP and ASP achieves their tasks in different ways. ASP codes
are interpreted on the fly each time it is accessed while PHP pages can either be interpreted or
compiled into a servlet. This means that a PHP page actually takes a little bit longer to load
because it needs to be compiled first. But after it has loaded, it would actually perform faster just
as long as the code does not require any changes. Once the code changes, it needs to be
recompiled which takes longer PHP and ASP (Active Server Pages) are two of the commonly
used server side scripting languages that are used today in web development. ASP was created
by Microsoft as part of its IIS that provides the user with tools needed to create a web site on his
Windows computer. It can be considered as free as ASP itself does not cost money, but the fact
that you need. In cases where code changes happens very often to the point that the performance
deteriorates a lot, the coder can opt to have his pages interpreted on the fly just like ASP

With the more or less the same level of performance. PHP coders also have a choice of either
compiling into a Java servlet, which are still platform independent, or into the operating systems
native byte code.
As of today, most web developers are using either PHP or the improved version of ASP called
ASP.NET. For people who are using a web server thats running Microsoft Windows, using ASP
or ASP.NET is already a given. Those who use open source software like Linux can choose
between a few options that are either free or not. Most people use other open source software like
PHP while PHP stands a distant second.

2.1.2 Here is a list of reasons why PHP is better than ASP:

PHP and ASP are both server side scripting languages.


ASP costs money while PHP is free.
ASP code is interpreted while PHP code is compiled at run time.
PHP code can run faster than ASP if there are fewer changes.
Majority of Windows users use ASP while users of open source operating systems like
Linux use PHP among others.

2.1.3 Here is a list of reasons why PHP is better than PHP:

Anything you can do with PHP, you can do with PHP; the reverse is not true.

PHP is much more powerful, since it has access to all the Java libraries. PHP only has
access to PHP libraries.

PHP is Object-Oriented, so leads to cleaner code that's easier to debug, maintain, and
improve. (PHP also allows objects, but the object model is more primitive, and most
scripted pages ignore PHP objects and just use normal variables.)

The equivalent syntax in PHP is just as simple to learn, so you can get up and running
just as quickly -- that is, there's no extra startup cost in using Java, at least not a
significant one.

Java programmers (as opposed to 15-year-old hackers or HTML monkeys) appreciate the
importance of a clean language with complex OO data structures and strong typing.

With PHP, if the code inside a page gets too big, or if you want to use it elsewhere, you
can cut it out, make it into a Java class, and invoke it from anywhere in your application
(even not from a page). With PHP, you're stuck inside the HTML box.

PHP's concept of state management and persistence is more explicit and powerful than
PHP's. With PHP, you can specify whether a variable persists for the page, the request,
the session, or the application (or if it's just local to the function). The PHP engine
automatically does the right thing with cookies so you have access to the variable on later
requests. With PHP, you just have "global" and "not global", you don't have automatic

session management, and have to do your state thing manually with cookies or hidden
variables.

2.2 BACK END TOOL: MYSQL


MYSQL, the most popular Open Source SQL database management system, is developed,
distributed, and supported by MYSQL AB. MYSQL AB is a commercial company, founded by
the MYSQL developers. It is a second generation Open Source Company that unites Open
Source values and methodology with a successful business model.

MYSQL is a database management system.

MYSQL is a relational database management system.

MYSQL software is Open Source.

MYSQL Server works in client/server or embedded systems.

2.2.1 JAVA SERVER PAGES AND MYSQL


Java provides a JDBCODBC bridges that translate JDBC to ODBC this implementation alone
with native methods is very small and efficient.

3.0 REQUIREMENTS AND ANALYSIS:3.1 PROBLEM DEFINITION

It is difficult to stop in-eligible candidates from applying.


It is a tedious and time consuming process to list out data of each candidate, manually
check them against documents submitted, resulting in delay and wastage of valuable
resources.
Multiple merit lists often leads to duplication of work for the institution, even candidates
/ guardians have to visit again and again to check the latest merit list.
Wastage of institute's resources as same information has to be imparted to candidates /
guardians individually.
Students / Guardians have to queue up numerous times i.e. to collect form, to submit
form, to view merit list, etc.

3.2 REQUIREMENT SPECIFICATION:3.2.1 Identification of Needs


Identification of need mainly concern with requirements of the project how much time it would
be taken and how much cost it would require to complete. The hardware requirement of the
project also concern. The member of the project team also is decided in this phase.
Here we focus our point towards organizing needs i.e. to organize the things which are scattered
here and there. Need to gather information about various aspects like consumer information, bill
calculation & reports. Each & every level of entity that is involving in the management system
needs to communicate together with the help of the management system.

3.2.2 Problem faced in Existing System


In current system a lot of manpower is wastes in Chances of form misplacement are very high,
because of huge number of applications. Wastage of institute's resources due to involvement of
people / teachers in form collection. Institute incurs expenditure on printing of admission forms,
and in absence of any reliable forecasting system on how much application it is going to receive
it may overspend by printing excessive application forms or may fall in crisis if there is excess
demand of application forms. Once printed, changes to the application form are not only difficult
but also incurs additional cost.

3.3 SYSTEM ANLYSIS:System Planning is one of the important items to be considered before actually beginning the
project. Planning is performed on the issued like defining Life Cycle Model and an
organizational structure project, configuration management, quality and validation activities.
In the process of the System Planning various phase-dependent tools, techniques and
notations are determined. Preliminary cost estimates for the system development and
preliminary development schedules are established. Preliminary estimates of the computing
resources required to operate and maintain the system are developed, glossary of terms are
prepared.

3.3.1 Business Needs: Maintaining the information regarding all employees, components and
computers at single or multiple locations give raise to many problems like:
Difficulty in retrieval of data in desired manner.
Checking the uniqueness wherever it is required.
Availability of information in this manner is subjected to damage.
Providing security is also difficult.
One way to overcome all these difficulties is to store all the information into computer system.
The computerization helps the users a lot. The user can get information in desired manner. Data
retrieval is also easy and fast. This also restricts the users to enter invalid data and reduces the
burden on the user.
3.3.2 Objectives: The main objectives of this study are as follows: The main objective of Project Scheduler is to provide an automated system to maintain the
records of the company and college student.
To provide an user friendly and multi-user interface for handling the application.
To provide a user authentication and different interface depending upon the type of user
logged in
To provide maximum level of security for the data.
To provide the necessary reports to various users in time.

3.3.3 Benefits: A computer based information system is usually needed for the following
purposes.
Greater Processing Speed:
Using computers inherent ability to calculate, sort, retrieve data with greater speed than
that of the human doing we can get results in less time. Visual Basic guaranties for the faster
query processing thus we are satisfied with Visual Basic itself supporting in this direction.

Better Accuracy and Improved Consistency:


The computer carries out computing steps including arithmetic accurately and
consistently from which really human is escaped which yields more fatigue and boredom.
Cost Reduction:
Using computerization we can do the required operations with lower cost than any other
methods. Hence by computerization we can reduce the cost drastically.
3.3.4 Feasibility Study: An initial investigation culminates in a proposal that determines
whether an alternative system is feasible than the present candidate system. To do feasible study
we have to do the Economic, Technical, Behavioral feasible studies.
3.3.5 Economic Feasibility: -It is the most frequently used method for evaluating the
effectiveness of a system. It is also called as cost/benefit analysis.
In this project Computer Resource Management System, for the development of the candidate
system the cost that has to spend is the computer resources like the required software and
hardware that supports the software in an effective and efficient manner and the money to be
paid to the developers. As the company itself is a development center all the resources are in the
company itself and no extra cost is spent for Computer Resource Management System.
Hence our candidate system production is economically feasible.
3.3.6 Technical Feasibility: Technical feasibility centers around the existing computer system (software/hardware)
configuration and good software facilities in such a way that any new candidate system can be
implemented without a large alteration of the lab nut with slight modification of the existing
system.
Hence our candidate system production is technically feasible.
3.3.7 Behavioral Feasibility: People are inherently resistant to change. Our candidate system is developed in such a
way that it is very user friendly, easy to learn how to work with and there is also not much
resistant to this package from the staff side also. As the company is basically a development
center it will be very easy for the employees of the company to learn about the developed
candidate system.
Hence our candidate system production is behaviorally feasible.

3.4 SYSTEM DESIGN:SYSTEM DESIGN phase follows system analysis phase. Design is maintaining a record
proof design divisions and providing a blueprint for the implementation phase. Design is the
bridge between system analysis and system implementation.
The design is a solution, a how to approach to the creation a new system. This is
composed of several steps. It provides the understanding and procedural details necessary
for implementing the system recommended in the feasibility study. Design goes through
logical and physical stages of development, logical design reviews the present physical
system, prepare input and output specifications, detail the implementation plan, and prepares
a logical design walkthrough.
The database tables are designed by analyzing various functions involved in the system
and the format of the fields is also designed. The fields in the database table should define
their role in the system. Care is to be taken to encode the lengthy names. Then in the input
and the output screen design, the design should be made user friendly. The menu should be
precise and compact.

OBJECTIVES OF DESIGN
System design is like a blue print for a building, it specifies all the features that are to be
in the finished product. Design states how to accomplish objectives determined in the
analysis phase.

3.4.1 Software Process Model:The spiral model, originally proposed by Boehm , is an evolutionary software
process model that couples the iterative nature of prototyping with the controlled and
systematic aspects of the linear sequential model. It provides the potential for rapid
development of incremental versions of the software. Using the spiral model, software
is developed in a series of incremental releases.

During early iterations, the incremental release might be a paper model or prototype.
During later iterations, increasingly more complete versions of the engineered system are
produced.
A spiral model is divided into a number of framework activities, also called task
regions.6 Typically, there are between three and six task regions. A spiral model
that contains six task regions:
Customer communicationtasks required to establish effective communication
between developer and customer.

Planningtasks required to define resources, timelines, and other project related


information.

Risk analysistasks required to assess both technical and management risks.


Engineeringtasks required to build one or more representations of the application.
Construction and releasetasks required to construct, test, install, and provide user
support (e.g., documentation and training).
Customer evaluationtasks required to obtain customer feedback based on evaluation
of the software representations created during the engineering stage and implemented
during the installation stage.
Each of the regions is populated by a set of work tasks, called a task set, that are
adapted to the characteristics of the project to be undertaken. For small projects, the
number of work tasks and their formality is low. For larger, more critical projects,
each task region contains more work tasks that are defined to achieve a higher level
of formality
.

3.5 PROJECT PLANNING AND SCHEDULING:The objective of software project planning is to provide a framework that enables the manager to
make reasonable estimates of resources, cost, and schedule. These estimates are made within a
limited time frame at the beginning of a software project and should be updated regularly as the
project progresses. In addition, estimates should attempt to define best case and worst case
scenarios so that project outcomes can be bounded.
Software project scheduling is an activity that distributes estimated effort across the planned
project duration by allocating the effort to specific software engineering tasks. It is important to
note, however, that the schedule evolves over time. During early stages of project planning, a
macroscopic schedule is developed. This type of schedule identifies all major software
engineering activities and the product functions to which they are applied. As the project gets
under way, each entry on the macroscopic schedule is refined into a detailed schedule. Here,
specific software tasks (required to accomplish an activity) are identified and scheduled.
Two general scheduling techniques are Gantt charts and PERT Charts

GANTT CHART
Gantt charts (developed by Henry L. Gantt) are project control techniques that can be used for
several purposes, including scheduling, budgeting and resource planning. A Gantt chart is a bar
chart, with each bar representing an activity. The bars are drawn against a time line. The length
of each bar is proportional to the length of time planned for the activity. We estimated the
number of weeks required for each of the seven tasks as follows:
1. Analysis
3 Weeks
2. Design
4 Weeks
3. Coding
8 Weeks
4. Testing
4 Weeks
5. Write Manual
2 Weeks
6. Implementation
1 Week
7. Maintenance
2 Weeks
Gantt Chart for web application:-

PERT CHARTS
A PERT (Program Evaluation and Review Technology) chart is a network of boxes (or circles) and
arrows. There are different variations of PERT Charts, some use the boxes to represent the activities and
some use arrows to do so. We will use the first approach here. Each box thus represents an activity. The
arrows are used to show the dependencies of activities on one another. The activity at the head of an
arrow can not start until activity at the tail of the arrow is finished.
Pert Chart for web application:-

3.5 SOFTWARE AND HARDWARE REQUIREMENTS


3.5.1 Server side:
Hardware Requirements:
Processor
RAM
HDD
Monitor
Printer
Keyboard
Mouse

:
:
:
:
:
:
:

Pentium 4
512 MB.
80 GB.
17 SVGA Color
Dot-Matrix, Laser Printer
Microsoft standard 108 keys normal
Microsoft standard 3 button Optical

3.5.2 Software Requirements:


OS
Data Base
Frame work
Server
Browser

:
:
:
:
:

Windows 7 & Above


MySQL 5.5
JVM
Apache Tomcat 6.0
Any JAVA Enabled (IE, OPERA etc.)

3.5.3 Client side:


Hardware Requirements:
Processor
RAM
Hard disk
Monitor
Printer

:
:
:
:
:

Pentium 3 or Higher (500 M.B.)


128 MB
20 GB
SVGA Color
Dot-Matrix, Laser Printer

3.5.4 Software Requirements:


OS
Data Base
Frame work
Browser

:
:
:
:

Any Operating System


MySQL 5.5
JVM
Any Java Enabled (IE, OPERA etc.)

3.5.5 TOOLS / PLATEFORM

Operating System
Web Server
Server Side Language
Front-End GUI

:
:
:
:

IDEBack-endScripting Language-

:
:
:

Windows 7 & Above


Apache Tomcat5.5
JAVA SERVER PAGES
HTML, CSS, DHTML Menu
Designer, Photoshop, Flash.
Net Beans
MySQL 5.5
JAVA SCRIPT, AJAX

3.5 PRELIMINARY PRODUCT DESCRIPTION


Goals of proposed system:
Objectives of proposed system are as follows:

Manpower is reduced because user can test its skills in just one click.
Complete working is in computerized manner.
Cost effective, it avoids the extra cost wastes in collecting various books.
Report generation is easy, data handling is simple.
Reduce the effort in solve questionnaires.
Provide security of data, unauthorized access is denied.

Function and Operation of the system:


These are the following modules, the whole project is going to deal with which1. Registration:
It will register the students in the system so that they can process further & can
interact with project. Its sub-processes are Student- It will give register the student in the system. Student of any stream will
be added here.
Faculty- All the faculties, which are enrolled in the system will be registered
here.
2. Login:
It will permit the authorized users to enter in the system & will protect from the
unauthorized users. Its sub-modules are Student- It will provide the user all the facilities which a student needs.
Faculty- It will give the authorization in the faculty accessible mode.
Admin- It will give all the rites to the user so that he can interact with the project up
to any extent.

3. Admission:
It will give admission to a new student in the system. After being enrolled in the
system he will be able to process further.
4. Learning Technologists:
Supporting pedagogic innovation using technologies. Language Learning &
Technology is published three times per year (January and June). Back and
current issues of Language Learning & Technology are indexed in the Current
Contents/Social, Behavioral Sciences and Computer Science.
5. Study Material Distribution:
In this the lectures & assignments will be uploaded by the faculty in the system &
can be view & download by the student. These activities will be controlled by the
administrator.
6. Report:
It will generate report about the following criteria Student registered- it will let the user know the status about all the students
registered in the system.
College list- It will give the information about all the College in the system
Faculty list- It will give the information about all the faculties in the system.
Result analysis- It will give report about the result.
7. Notices:
It will generate all the relative notices of the system to all the users on the notice
board.
8. Feedback:
It will take feedback from user & will give to faculty & vice-versa for relative
solving problems.

3.6 Conceptual Model


3.6.1 DATAFLOW DAIGRAM

3.6.2 E-R Diagram:-

3.6.3 Entity Diagram

4.0 DATABASE DESIGN


Table 1: Student
Field name
Srollno
Sname
Father_name
Date_of_Birth
Address
State
Country
Contact_no
Semail

Data type
Varchar
Varchar
Varchar
Datetime
Varchar
Varchar
Varchar
Varchar
Varchar

Size
10
50
50

Constraint
Primary key
Not Null
Not Null

150
50
50
50
50

Not Null
Not Null
Not Null
Not Null
Not Null

Data type
Varchar
Varchar
Varchar
Varchar
Varchar
Varchar

Size
10
50
50
50
50
150

Table 2: Faculty
Field name
Faculty_id
Fname
Fqualification
Fcontactno
Femail
Faddress

Constraint
Primary key
Not Null
Not Null
Not Null
Not null
Not null

Table 3: Course_allotment
Field name
Course_code
Srollno
Opening_date
Closing_date

Data type
Varchar
Varchar
Datetime
Datetime

Size
10
50

Constraint
References course
Not null

Table 4: Project Course


Field name
Group_Code
Project_title
Duration
Semester

Data type
Varchar
Varchar
Varchar
Varchar

Size
10
50
50
50

Constraint
Primary key
Not Null
Not Null
Not Null

Table 5: Slogin
Field name
Semail
Spassword
Slogin_date
Slogout

Data type
Varchar
Varchar
Datetime
Datetime

Size
10
50

Constraint
References student
Not Null

Data type
Varchar
Varchar
Datetime
Datetime

Size
10
10

Constraint
References faculty
Not Null

Field name
College_id
Cpass
Login_Datetime
Logout_datetime

Data type
Varchar
Varchar
Datetime
Datetime

Size
10
10

Constraint
References faculty
Not Null

College_name

Varchar

40

Not Null

Table 6: Flogin
Field name
Faculty_id
Fpassword
Login_Datetime
Logout_datetime
Table 7: Clogin

6.0 FUTURE SCOPE


The project report entitled "Project Scheduler" has come to its final stage. The system has been developed
with much care that it is free of errors and at the same time it is efficient and less time consuming. The
entire system is secured.

My project is very flexible and easy to use, when requirement increases it is very easy to include
in the project. In this project we can add following to modules in the future: On line interview modules:-This is the first modules in future modules of my site in
which we take on-line examination if any person want to do jab then he send his profile
and after checking he give interview.
Online chatting module:- This is the second modules in future modules of my site in
which students can communicate with teachers through e-mail, telephone conversations
etc.
Online massaging module:-

7.0 REFERENCES
Here I would like to mention the name of the Authors, Books and URLs used for reference
while designing of the system:
1. Elias M. Ewad-System Analysis & Design-Galgotia Publication
2. Pankaj Jalote-An Integrated Approach to S/W Engineering-B.P.B. Publication
3. Roger S. Pressman-Software Engineering-Tata McGraw Hill Publication
4. Korth-Database System Concepts-Tata McGraw Hill Publication

5. www.javatpoint.com
6. www.roseindia.com

7. www.w3schools.com

You might also like