1.

INTRODUCTION
1.1 INTRODUCTION:

Management information system (MIS) is a branch in industrial engineering and

information management is now widely used around the world through database
management system, many subroots of MIS are derived and in different departments and
organization all around the world. Some among them which are widely used are:- 1)
Hospital database management system 2) Restaurant database management system 3)
Salary database management system 4) Whole shale database management system Thus
this project deals with a concept derived from MIS, it is a unique attempt to aid the
management of information of students in a university know as Student Database
Management System. What is student database management system? A student database
management system is automation of manual performance record management which
enables the user to assess necessary data at any place and any time through internet. The
student web portal contains a login page where after providing the login details the home
page is appeared for the user where it shows important notifications and activities in the
college like semester fee payment dates, exam registration, change in exam time table,
workshops or fests to be held, etc. the student can check his attendance a, semester marks
and mid-exam marks for every semester which enables them to improve his performance in
forthcoming semester. The faculty can also make changes in marks in case of any mistake
immediately which eliminate the time consuming activities like registering a complaint and
then faculty approving it then the administration making changes. The labs module also
mentions the list of equipment and list of experiments done in the labs. The library section
provides information about the availability of the books and journals in it. The admin
module allows admin to make changes in faculty and student academic and personal
details.

1
 2. LITERATURE SURVEY

2.1 A case analysis of knowledge sharing implementation and job searching in

Malaysia

The aim of this research is to consider an analysis through case studies on how knowledge
sharing may be successfully implemented. The study will clarify a conceptualisation that
provides a new understanding of the relationship between unemployed graduates and the
human capital concept. The cases adopted web documentation for the research technique,
and an interpretive approach was used as the research paradigm. Two online recruitment
agency sites were analysed through qualitative analysis. The connections show how
knowledge sharing can be used as a medium to help unemployed graduates to get jobs
through online recruitment agencies. High quality candidates must have good soft skills,
problem-solving skills and employable value added skills to get the best jobs. The findings
will be expressed as qualitative results from the two online recruitment agencies researched
as the case studies for the paper. From these case studies, the findings will contribute to the
ongoing study on how to implement knowledge sharing among undergraduates after they
finished their studies.

2.2 Stakeholder Expectations of Service Quality in a University Web Portal

Online service quality is a much-studied concept. There is considerable evidence that user
expectations and perceptions of self-service and online service quality differ in different
business domains. In addition, the nature of online services is continually changing and
universities have been at the forefront of this change, with university websites increasingly
acting as a portal for a wide range of online transactions for a wide range of stakeholders .
In this qualitative study, we conduct focus groups with a range of stakeholders in a
university web portal . Our study offers a number of insights into the changing nature of
the relationship between organisations and customers. New technologies are influencing
customer expectations. Customers increasingly expect organisations to have integrated

2
information systems, and to utilise new technologies such as SMS and web portals.
Organisations can be slow to adopt a customer-centric viewpoint, and persist in providing
interfaces that are inconsistent or require inside knowledge of organisational structures and
processes. This has a negative effect on customer perceptions.

2.3 Ontologies for enterprise knowledge management

Several challenges exist related to applying ontologies in real-world environments. The

author’s present integrated enterprise-knowledge management architecture, focusing on
how to support multiple ontologies and manage ontology evolution

2.4 Development of a Student Database Management System for a University

In this scholarly thesis pertinent to the setting up of a automated student performance

record management system which enables the users of a university like student and faculty
to access the important information with ease through a user friendly web application. This
proposed system aims at eliminating the practice of time consuming and vulnerable
tradition of manual maintenance of student information in paper at the very basic level. In a
university there are many departments all these departments provide various records
regarding student. Most of these track records need to maintain information about the
students. Thus by proposing a computerizes student record management system will enable
the users to access data at any time and any place. The student web portal enables huge
storage of data and easy retrieval. There are many departments in a college thus but
introducing a student web portal will centralize the administration and the entire system
will work as one single entity. The paper work would be reduced and number of workers in
each department staff also reduces as one single operator can run this web application.

3
 3. SYSTEM ANALYSIS

The Systems Development Life Cycle (SDLC), or Software Development Life Cycle in
systems engineering, information systems and software engineering, is the process of
creating or altering systems, and the models and methodologies that people use to develop
these systems. In software engineering the SDLC concept underpins many kinds of
software development methodologies.

Existing System:

In the existing system all the student information is added manually and the data is stored
in the records. Takes lot of time and physical effort in searching and adding the
information. In the existing system there is a possibility of losing data and no proper
maintenance of data.

Disadvantages

 It uses internet connection

Proposed System:
The proposed system provides student an easy and accurate data about projects and
academic percentages. Students can view all the information in just one click which saves
lot of time and effort. The proposed system maintains a database to store all the
information. In this system there is no chance of losing data. Adding and searching the
information is very easy which does not take much time and physical effort.

4
Advantages

 It helps in maintaining students records

 It helps teacher to get their assigned work

 Easy way of displaying notice

5
 4. IMPLEMENTATION
Modules:
Admin:
Admin can get login by entering valid username and password. Admin can view all the
details of the users and need to authorize them. Admin can upload projects by giving all the
details of the project. Admin can add all the details of student’s attendance and marks.
Admin can view added students and the progress in graph.

Student:
Student need to enter all the details in the registration form. Student should be authorized
by admin to get login into the application. Student can search projects based on title,
year and Guide name. Students can view all the details of his/her attendance and marks.
Students can view graph for his attendance and marks

4.1 Introduction of Technologies Used

Initially Java language was called as “oak” but it was renamed as “java” in 1995.The
primary motivation of this language was the need for a platform-independent i.e.
architecture neutral language that could be used to create software to be embedded in
various consumer electronic devices.

4.1.1Applications and applets

An application is a program that runs on our Computer under the operating system of that
computer. It is more or less like one creating using C or C++ .Java’s ability to create
Applets makes it important. An Applet I san application, designed to be transmitted over
the Internet and executed by a Java-compatible web browser. An applet I actually a tiny
Java program, dynamically downloaded across the network, just like an image. But the
difference is, it is an intelligent program, not just a media file. It can be react to the user
input and dynamically change.
6
4.1.2 Java Architecture

Java architecture provides a portable, robust, high performing environment for

development. Java provides portability by compiling the byte codes for the Java Virtual
Machine, which is then interpreted on each platform by the run-time environment. Java is a
dynamic system, able to load code when needed from a machine in the same room or
across the planet.

4.1.3 Compilation of code

When we compile the code, the Java compiler creates machine code called byte code for a
hypothetical machine called Java Virtual Machine (JVM). Compiling and interpreting java
source code.

Fig 4.1.3: Structure of compilation

During run-time the Java interpreter tricks the byte code file into thinking that it is running
on a Java Virtual Machine. In reality this could be an Intel Pentium windows 95 or sun
SPARCstation running Solaris or Apple Macintosh running system and all could receive
code from any computer through internet and run the Applets.

7
4.1.4 Simple

Java was designed to be easy for the Professional programmer to learn and to use
effectively. If you are an experienced C++ Programmer, learning Java will oriented
features of C++. Most of the confusing concepts from C++ are either left out of Java or
implemented in a cleaner, more approachable manner. In Java there are a small number of
clearly defined ways to accomplish a given task.

4.1.5 Object oriented

Java was not designed to be source-code compatible with any other language. This allowed
the Java team the freedom to design with a blank state. One outcome of this was a clean
usable, pragmatic approach to objects. The object model in Java is simple and easy to
extend, while simple types, such as integers, are kept as high-performance non-objects.

4.1.6 Robust

The multi-platform environment of the web places extraordinary demands on a program,

because the program must execute reliably in a variety of systems. The ability to create
robust programs was given a high priority in the design of Java. Java is strictly typed
language; it checks the code at compile time and runtime.
Java virtually eliminates the problems of memory management and deal location, which is
completely automatic. In a well-written Java program, all run-time errors can and should
be managed by your program.

8
 5. SOFTWARE REQUIREMENT SPECIFICATION

5.1 Requirements Specification:

Requirement Specification provides a high secure storage to the web server efficiently.
Software requirements deal with software and hardware resources that need to be installed
on a serve which provides optimal functioning for the application. These software and
hardware requirements need to be installed before the packages are installed. These are the
most common set of requirements defined by any operation system. These software and
hardware requirements provide a compatible support to the operation system in developing
an application.

5.1.1 HARDWARE REQUIREMENTS:

The hardware requirement specifies each interface of the software elements and the
hardware elements of the system. These hardware requirements include configuration
characteristics.
 System : Pentium IV 2.4 GHz.
 Hard Disk : 100 GB.
 Monitor : 15 VGA Color.
 Mouse : Logitech.
 RAM : 1 GB.

5.1.2 SOFTWARE REQUIREMENTS:

The software requirements specify the use of all required software products like data
management system. The required software product specifies the numbers and version.
Each interface specifies the purpose of the interfacing software as related to this software
product.

 Operating system : Windows XP/7/10

9
  Coding Language : Html, JavaScript, Java/J2EE (Jsp Servlet)
 Development Kit : JDK 1.7

 Database : MySQL

 IDE : Netbeans
 Server : Tomcat 7.0

5.2 FUNCTIONAL REQUIREMENTS:

The functional requirement refers to the system needs in an exceedingly computer

code engineering method.

The key goal of determinant “functional requirements” in an exceedingly product

style and implementation is to capture the desired behavior of a software package in
terms of practicality and also the technology implementation of the business
processes.
5.3 NON FUNCTIONAL REQUIREMENTS

All the other requirements which do not form a part of the above specification are
categorized as Non-Functional needs. A system perhaps needed to gift the user with a
show of the quantity of records during info. If the quantity must be updated in real
time, the system architects should make sure that the system is capable of change the
displayed record count at intervals associate tolerably short interval of the quantity of
records dynamic. Comfortable network information measure may additionally be a
non-functional requirement of a system.

The following are the features:

 Accessibility

 Availability

 Backup

 Certification

 Compliance
10
  Configuration Management

 Documentation

 Disaster Recovery

 Efficiency(resource consumption for given load)

 Interoperability

5.4 PERFORMANCE REQUIREMENTS

Performance is measured in terms of the output provided by the application. Requirement

specification plays an important part in the analysis of a system. Only when the
requirement specifications are properly given, it is possible to design a system, which will
fit into required environment. It rests largely with the users of the existing system to give
the requirement specifications because they are the people who finally use the system.
This is because the requirements have to be known during the initial stages so that the
system can be designed according to those requirements. It is very difficult to change the
system once it has been designed and on the other hand designing a system, which does not
cater to the requirements of the user, is of no use.
The requirement specification for any system can be broadly stated as given below:

 The system should be able to interface with the existing system

 The system should be accurate
 The system should be better than the existing system
The existing system is completely dependent on the user to perform all the duties.
5.5 Feasibility Study:

Preliminary investigation examines project feasibility; the likelihood the system will be
useful to the organization. The main objective of the feasibility study is to test the
Technical, Operational and Economical feasibility for adding new modules and debugging
old running system. All systems are feasible if they are given unlimited resources and
infinite time. There are aspects in the feasibility study portion of the preliminary
investigation:
11
  Technical Feasibility
 Operation Feasibility
Economical Feasibility

5.5.1 Technical Feasibility

The technical issue usually raised during the feasibility stage of the investigation includes
the following:
 Does the necessary technology exist to do what is suggested?
 Do the proposed equipments have the technical capacity to hold the data required to
use the new system?
 Will the proposed system provide adequate response to inquiries, regardless of the
number or location of users?
 Can the system be upgraded if developed?
Are there technical guarantees of accuracy, reliability, ease of access and data security?

5.5.2 Operational Feasibility

User-friendly
Customer will use the forms for their various transactions i.e. for adding new routes,
viewing the routes details. Also the Customer wants the reports to view the various
transactions based on the constraints. These forms and reports are generated as user-
friendly to the Client.
Reliability
The package wills pick-up current transactions on line. Regarding the old transactions,
User will enter them in to the system.
Security
The web server and database server should be protected from hacking, virus etc
Portability
The application will be developed using standard open source software (Except Oracle)
like Java, tomcat web server, Internet Explorer Browser etc these software will work both
12
on Windows and Linux o/s. Hence portability problems will not arise.
Availability
This software will be available always.
Maintainability
The system uses the 2-tier architecture. The 1st tier is the GUI, which is said to be front-
end and the 2nd tier is the database, which uses My-Sql, which is the back-end.
The front-end can be run on different systems (clients). The database will be running at the
server. Users access these forms by using the user-ids and the passwords.

5.5.3 Economic Feasibility

The computerized system takes care of the present existing system’s data flow and
procedures completely and should generate all the reports of the manual system besides a
host of other management reports.

It should be built as a web based application with separate web server and database server.
This is required as the activities are spread throughout the organization customer wants a
centralized database. Further some of the linked transactions take place in different
locations.

Open source software like TOMCAT, JAVA, Mysql and Linux is used to minimize the
cost for the Customer.

13
 6. Methodology

6.1 SDLC (Software Development Life Cycle) – Umbrella Model

Umbrella
DOCUMENT CONTROL
Activity

Business Requirement Umbrella

Documentation Activity

• Feasibility Study
• TEAM FORMATION
• Project Specification
Requirements PREPARATION ANALYSIS & ASSESSMENT
Gathering DESIGN CODE UNIT TEST

INTEGRATION ACCEPTANCE
& SYSTEM DELIVERY/INS TEST
TESTING TALLATION

Umbrella
TRAINING
Activity

Fig no. 6.1 Umbrella model

SDLC is nothing but Software Development Life Cycle. It is a standard which is used by
software industry to develop good software.

6.2 Requirements Gathering Stage

The requirements gathering process takes as its input the goals identified in the high-level
requirements section of the project plan. Each goal will be refined into a set of one or more
requirements. These requirements define the major functions of the intended application,
define operational data areas and reference data areas, and define the initial data entities.
Major functions include critical processes to be managed, as well as mission critical inputs,
outputs and reports. A user class hierarchy is developed and associated with these major
functions, data areas, and data entities. Each of these definitions is termed a Requirement.
14
Requirements are identified by unique requirement identifiers and, at minimum, contain a
requirement title and textual description.

Fig no. 6.2 Requirements Gathering stage

These requirements are fully described in the primary deliverables for this stage: the
Requirements Document and the Requirements Traceability Matrix (RTM). The
requirements document contains complete descriptions of each requirement, including
diagrams and references to external documents as necessary. Note that detailed listings of
database tables and fields are not included in the requirements document.

The title of each requirement is also placed into the first version of the RTM, along with
the title of each goal from the project plan. The purpose of the RTM is to show that the
product components developed during each stage of the software development lifecycle are
formally connected to the components developed in prior stages.

In the requirements stage, the RTM consists of a list of high-level requirements, or goals,
by title, with a listing of associated requirements for each goal, listed by requirement title.
In this hierarchical listing, the RTM shows that each requirement developed during this
stage is formally linked to a specific product goal. In this format, each requirement can be
traced to a specific product goal, hence the term requirements traceability.

15
The outputs of the requirements definition stage include the requirements document, the
RTM, and an updated project plan.

Feasibility study is all about identification of problems in a project, number of staff

required to handle a project is represented as Team Formation, in this case only modules
are individual tasks will be assigned to employees who are working for that project.
Project Specifications are all about representing of various possible inputs submitting to the
server and corresponding outputs along with reports maintained by administrator.

6.3 Analysis Stage

The planning stage establishes a bird's eye view of the intended software product, and uses
this to establish the basic project structure, evaluate feasibility and risks associated with the
project, and describe appropriate management and technical approaches.

Fig no. 6.3 Analysis stage

The most critical section of the project plan is a listing of high-level product requirements,
also referred to as goals. All of the software product requirements to be developed during
the requirements definition stage flow from one or more of these goals. The minimum

16
information for each goal consists of a title and textual description, although additional
information and references to external documents may be included. The outputs of the
project planning stage are the configuration management plan, the quality assurance plan,
and the project plan and schedule, with a detailed listing of scheduled activities for the
upcoming Requirements stage, and high level estimates of effort for the out stages.

6.4 Designing Stage

The design stage takes as its initial input the requirements identified in the approved
requirements document. For each requirement, a set of one or more design elements will be
produced as a result of interviews, workshops, and/or prototype efforts. Design elements
describe the desired software features in detail, and generally include functional hierarchy
diagrams, screen layout diagrams, tables of business rules, business process diagrams,
pseudo code, and a complete entity-relationship diagram with a full data dictionary. These
design elements are intended to describe the software in sufficient detail that skilled
programmers may develop the software with minimal additional input.

Fig no. 6.4 Designing stage

When the design document is finalized and accepted, the RTM is updated to show that
17
each design element is formally associated with a specific requirement. The outputs of the
design stage are the design document, an updated RTM, and an updated project plan.

6.5 Development (Coding) Stage

The development stage takes as its primary input the design elements described in the
approved design document. For each design element, a set of one or more software artifacts
will be produced. Software artifacts include but are not limited to menus, dialogs, data
management forms, data reporting formats, and specialized procedures and functions.
Appropriate test cases will be developed for each set of functionally related software
artifacts, and an online help system will be developed to guide users in their interactions
with the software.

Fig no. 6.5 Coding stage

18
6.6 Integration & Test Stage

During the integration and test stage, the software artifacts, online help, and test data are
migrated from the development environment to a separate test environment. At this point,
all test cases are run to verify the correctness and completeness of the software. Successful
execution of the test suite confirms a robust and complete migration capability. During this
stage, reference data is finalized for production use and production users are identified and
linked to their appropriate roles. The final reference data (or links to reference data source
files) and production user list are compiled into the Production Initiation Plan.

Fig no. 6.6 Integration and Testing Stage

19
6.7 Installation & Acceptance Test

During the installation and acceptance stage, the software artifacts, online help, and initial
production data are loaded onto the production server. At this point, all test cases are run to
verify the correctness and completeness of the software. Successful execution of the test
suite is a prerequisite to acceptance of the software by the customer.

After customer personnel have verified that the initial production data load is correct and
the test suite has been executed with satisfactory results, the customer formally accepts the
delivery of the software.

Fig no. 6.7 Installation

Maintenance

Outer rectangle represents maintenance of a project, Maintenance team will start with
requirement study, understanding of documentation later employees will be assigned work
and they will undergo training on that particular assigned category.

20
 7. System Design

7.1 SYSTEM ARCHITECTURE

The purpose of the design phase is to arrange an answer of the matter such as by the
necessity document. This part is that the opening moves in moving the matter domain to
the answer domain. The design phase satisfies the requirements of the system. The design
of a system is probably the foremost crucial issue warm heartedness the standard of the
software package. It’s a serious impact on the later part, notably testing and maintenance.
The output of this part is that the style of the document. This document is analogous to a
blueprint of answer and is employed later throughout implementation, testing and
maintenance. The design activity is commonly divided into 2 separate phases System
Design and Detailed Design.
System Design conjointly referred to as top-ranking style aims to spot the modules that
ought to be within the system, the specifications of those modules, and the way them
move with one another to supply the specified results.
At the top of the system style all the main knowledge structures, file formats, output
formats, and also the major modules within the system and their specifications square
measure set. System design is that the method or art of process the design, components,
modules, interfaces, and knowledge for a system to satisfy such as needs. Users will read
it because the application of systems theory to development.
Detailed Design, the inner logic of every of the modules laid out in system design is
determined. Throughout this part, the small print of the info of a module square measure
sometimes laid out in a high-level style description language that is freelance of the target
language within which the software package can eventually be enforced.
In system design the main target is on distinguishing the modules, whereas throughout
careful style the main target is on planning the logic for every of the modules.

21
 Figure 7.1: Architecture diagram

7.2 DATA FLOW DIAGRAMS

Data Flow Diagram can also be termed as bubble chart. It is a pictorial or graphical
form, which can be applied to represent the input data to a system and multiple functions
carried out on the data and the generated output by the system.
A graphical tool accustomed describe and analyze the instant of knowledge through
a system manual or automatic together with the method, stores of knowledge, and delays
within the system. The transformation of knowledge from input to output, through
processes, is also delineate logically and severally of the physical elements related to the
22
system. The DFD is also known as a data flow graph or a bubble chart.The BasicNotation
used to create a DFD’s are as follows:

 Dataflow:

 Process:
.


Source:


Data Store:


Rhombus: decision

7.3 UML DIAGRAMS

The Unified Modeling Language allows the software engineer to express an analysis model
using the modeling notation that is governed by a set of syntactic semantic and pragmatic
rules.
A UML system is represented using five different views that describe the system from
distinctly different perspective. Each view is defined by a set of diagram, which is as
follows.

User Model View

23
This view represents the system from the users perspective. The analysis representation
describes a usage scenario from the end-users perspective.

Structural Model view

In this model the data and functionality are arrived from inside the system. This model
view models the static structures.

Behavioral Model View

It represents the dynamic of behavioral as parts of the system, depicting the interactions of
collection between various structural elements described in the user model and structural
model view.

Implementation Model View

In this the structural and behavioral as parts of the system are represented as they are to be
built.

5.3.1 USE CASE DIAGRAM

A use case diagram at its simplest is a representation of a user's interaction with the
system and depicting the specifications of a use case. A use case diagram can portray the
different types of users of a system and the various ways that they interact with the system.
This type of diagram is typically used in conjunction with the textual use case and will
often be accompanied by other types of diagrams as well.

24
25
Figure 7.3.1 Use Case Diagram

26
5.3.2 CLASS DIAGRAM

The class diagram is the main building block of object oriented modeling. It is used both
for general conceptual modeling of the systematic of the application, and for detailed
modeling translating the models into programming code. Class diagrams can also be used
for data modeling. The classes in a class diagram represent both the main objects,
interactions in the application and the classes to be programmed. A class with three
sections, in the diagram, classes is represented with boxes which contain three parts:

The upper part holds the name of the class

The middle part contains the attributes of the class

The bottom part gives the methods or operations the class can take or undertake.

Figure 7.3.2: Class Diagram.

27
5.3.3 SEQUENCEDIAGRAM

A sequence diagram is a kind of interaction diagram that shows how processes

operate with one another and in what order. It is a construct of a Message Sequence Chart.
A sequence diagram shows object interactions arranged in time sequence. It depicts the
objects and classes involved in the scenario and the sequence of messages exchanged
between the objects needed to carry out the functionality of the scenario. Sequence
diagrams are typically associated with use case realizations in the Logical View of the
system under development. Sequence diagrams are sometimes called event diagrams, event
scenarios, and timing diagrams.

28
 Figure 7.3.3: Sequence diagram

5.3.4 ACTIVITY DIAGRAM

Activity diagrams are graphical representations of workflows of stepwise activities and

actions with support for choice, iteration and concurrency. In the Unified Modeling
Language, activity diagrams can be used to describe the business and operational step-by-
step workflows of components in a system. An activity diagram shows the overall flow of
control.

29
Figure 7.3.4: Activity Diagram

30
Component Diagram

31
Deployment Diagram

32
33
 8. TESTING

Testing is the process where the test data is prepared and is used for testing the modules
individually and later the validation given for the fields. Then the system testing takes place
which makes sure that all components of the system property functions as a unit. The test
data should be chosen such that it passed through all possible condition. The following is
the description of the testing strategies, which were carried out during the testing period.

8.1 SYSTEM TESTING

Testing has become an integral part of any system or project especially in the field of
information technology. The importance of testing is a method of justifying, if one is ready
to move further, be it to be check if one is capable to with stand the rigors of a particular
situation cannot be underplayed and that is why testing before development is so critical.
When the software is developed before it is given to user to user the software must be
tested whether it is solving the purpose for which it is developed. This testing involves
various types through which one can ensure the software is reliable. The program was
tested logically and pattern of execution of the program for a set of data are repeated. Thus
the code was exhaustively checked for all possible correct data and the outcomes were also
checked.

8.2 MODULE TESTING

To locate errors, each module is tested individually. This enables us to detect error and
correct it without affecting any other modules. Whenever the program is not satisfying the
required function, it must be corrected to get the required result. Thus all the modules are
individually tested from bottom up starting with the smallest and lowest modules and
proceeding to the next level. Each module in the system is tested separately. For example
the job classification module is tested separately. This module is tested with different job
and its approximate execution time and the result of the test is compared with the results
that are prepared manually. Each module in the system is tested separately. In this system
the resource classification and job scheduling modules are tested separately and their
corresponding results are obtained which reduces the process waiting time.
34
8.3 INTEGRATION TESTING

After the module testing, the integration testing is applied. When linking the modules there
may be chance for errors to occur, these errors are corrected by using this testing. In this
system all modules are connected and tested. The testing results are very correct. Thus the
mapping of jobs with resources is done correctly by the system

8.4 ACCEPTANCE TESTING

When that user fined no major problems with its accuracy, the system passers through a
final acceptance test. This test confirms that the system needs the original goals, objectives
and requirements established during analysis without actual execution which elimination
wastage of time and money acceptance tests on the shoulders of users and management, it
is finally acceptable and ready for the operation.

35
 8.5 TEST CASES:

Test Test Case Test Case Test Steps Test Test

Case Id Name Desc. Step Expected Actual Case Priority
Status
01 Upload the Verify If dataset is It cannot File is High High
tasks either file not display loaded
dataset is loaded uploaded the file which
or not loaded displays
message task
waiting
time
02 Upload Verify If dataset is It cannot It can low High
patients either not display display
dataset dataset uploaded dataset dataset
loaded or reading reading
not process process
completed completed
03 Preprocess Whether If not It cannot It can Medium High
ing preprocessi applied display display the
ng on the the necessary
dataset necessary data for
applied or data for further
not further process
process

36
04 Prediction Whether If not Random Random High High
Random Prediction applied tree is not tree is
Forest algorithm generated generated
applied on
the data or
not
05 Recomme Whether If not It cannot It can view High High
ndation predicted displayed view prediction
data is prediction containing
displayed containing patient data
or not patient
data
06 Noisy Whether If graph is It does not It shows Low Mediu
Records the graph not show the the m
Chart is displayed variations variations
displayed in in between
or not between clean and
clean and noisy
noisy records
records

TABLE 8.5.1 TESTCASES

37
 9. SCREEN SHOTS

Homepage

Admin login page

38
Admin home page

View student page

39
Upload project page

View project page

40
Add attendance page

Add marks page

41
Add placement page

Add event page

42
View applied page in admin

Graph page in admin

43
Attendance graph

Marks graph

44
Student registration page

Student home page

45
 10. CONCLUSION

. “Student Performance with Graph & Academic Project Work Reporting System”
project satisfies all the requirements of students in searching the projects and finding
details about his\her attendance and marks. This project also satisfies the requirement of
admin in adding all the details of the project and he can easily find the progress of
student’s attendance and marks.

Future Enhancements:

It is not possible to develop a system that makes all the requirements of the user. User
requirements keep changing as the system is being used. Some of the future enhancements
that can be done to this system are:

 As the technology emerges, it is possible to upgrade the system and can be

adaptable to desired environment.
 Based on the future security issues, security can be improved using emerging
technologies like single sign-on.

46
 11. REFERENCES

[1]. Gateways to portals research. International Journal of web portals, 1(1),

1–15.
[2]. Usability.gov. (n.d.).What does usability measure. Retrieved September
2, 2012, from: http://www.usability.gov/basics/index.html.
[3]. MarjanMansourvar, NorizanMohdYasin, (2010), Web portal as a
Knowledge Management System in the Universities, World Academy of
Science, Engineering and Technology
[4]. Sulaiman, N. & Burke, M. 2009. A case analysis of knowledge sharing
implementation and job searching in Malaysia. International Journal of
Information Management.
[5]. Tate, M., Evermann, J., Hope, B. & Barnes, S.2009. Stakeholder
Expectations of Service Quality in a University Web Portal. Self-Service in
the Internet Age, 1-21.
[6]. Telang, R. &Mukhopadhyay, T.2005. Drivers of Web portal use.
Electronic Commerce research and applications, 4, 49- 65.
[7]. Maedche, A., Motik, B., Stojanovic, L., Studer, R. &Volz, R. 2003.
Ontologies for enterprise knowledge management.IEEE Intelligent Systems,
26-33

BIBLIOGRAPHY

JAVA Technologies

JAVA Complete Reference

Java Script Programming by Yehuda Shiran

47
 Mastering JAVA Security

J2EE Professional by Shadab siddiqui

JAVA server pages by Larne Pekowsley

JAVA Server pages by Nick Todd

HTML

HTML Black Book by Holzner

JDBC

Java Database Programming with JDBC by Patel moss.

Software Engineering by Roger Pressman

SAMPLE CODE

/*
* To change this license header, choose License Headers in
Project Properties.
* To change this template file, choose Tools | Templates
* and open the template in the editor.
*/
package test;

import com.sun.org.apache.xerces.internal.impl.dv.util.Base64;
import java.io.BufferedReader;
import java.io.File;
import java.io.FileWriter;
import java.io.IOException;
import java.io.InputStream;
import java.io.InputStreamReader;
import java.io.PrintWriter;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
import java.util.Iterator;
import java.util.List;
import java.util.logging.Level;
import java.util.logging.Logger;
import javax.crypto.KeyGenerator;
import javax.crypto.SecretKey;
import javax.servlet.ServletException;
48
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import org.apache.commons.fileupload.FileItem;
import org.apache.commons.fileupload.FileItemFactory;
import org.apache.commons.fileupload.FileUploadException;
import org.apache.commons.fileupload.disk.DiskFileItemFactory;
import org.apache.commons.fileupload.servlet.ServletFileUpload;
import org.apache.poi.hwpf.HWPFDocument;
import org.apache.poi.xwpf.extractor.XWPFWordExtractor;
import org.apache.poi.xwpf.usermodel.XWPFDocument;

/**
*
* @author java2
*/
public class Upload extends HttpServlet {

private static java.sql.Date getCurrentDate() {

java.util.Date today = new java.util.Date();
return new java.sql.Date(today.getTime());
}

protected void processRequest(HttpServletRequest request,

HttpServletResponse response)
throws ServletException, IOException {
response.setContentType("text/html;charset=UTF-8");
try (PrintWriter out = response.getWriter()) {
/* TODO output your page here. You may use following
sample code. */
Connection con;
PreparedStatement pstm = null;
String title = "";
String studentname = "";
String year = "";
String guide = "";
String abstract1 = "";
// String a = (String)
request.getSession().getAttribute("user");
// System.out.println("User Name : " + a);
try {
boolean isMultipartContent =
ServletFileUpload.isMultipartContent(request);
if (!isMultipartContent) {
return;
}
FileItemFactory factory = new
DiskFileItemFactory();
ServletFileUpload upload = new
ServletFileUpload(factory);
try {
49
 List<FileItem> fields =
upload.parseRequest(request);
Iterator<FileItem> it = fields.iterator();
if (!it.hasNext()) {
return;
}
while (it.hasNext()) {
FileItem fileItem = it.next();
if
(fileItem.getFieldName().equals("title")) {
title = fileItem.getString();
System.out.println("File Name" +
title);

}
else if
(fileItem.getFieldName().equals("studentname")) {
studentname = fileItem.getString();
System.out.println("File Keyword" +
studentname);
}
else if
(fileItem.getFieldName().equals("year")) {
year = fileItem.getString();
System.out.println("File Keyword" +
year);
}
else if
(fileItem.getFieldName().equals("guide")) {
guide = fileItem.getString();
System.out.println("File Keyword" +
guide);
}
else if
(fileItem.getFieldName().equals("abstract1")) {
abstract1 = fileItem.getString();
System.out.println("File Keyword" +
abstract1);
}
else {

}
boolean isFormField =
fileItem.isFormField();
if (isFormField) {
} else {
try {

Connection connection = null;

Class.forName("com.mysql.jdbc.Driver");

50
 connection =
DriverManager.getConnection("jdbc:mysql://localhost:3306/studentpe
rformance","root","root");

pstm = connection.prepareStatement("insert
into file (file, title, studentname, year, guide, abstract1,
CDate, data)values(?,?,?,?,?,?,?,?)");
System.out.println("getD " +
fileItem.getName());
String str =
getStringFromInputStream(fileItem.getInputStream(),fileItem.getCon
tentType());

pstm.setBinaryStream(1,
fileItem.getInputStream());
pstm.setString(2, title);
pstm.setString(3, studentname);
pstm.setString(4, year);
pstm.setString(5, guide);
pstm.setString(6, abstract1);
pstm.setDate(7, getCurrentDate());
pstm.setString(8, str);

int i = pstm.executeUpdate();
if (i == 1) {

response.sendRedirect("upload.jsp?msg1=success");
} else {

response.sendRedirect("upload.jsp?msgg=failed");
}
connection.close();
} catch (Exception e) {

response.sendRedirect("upload.jsp?m3=Duplicate Data");
}
}
}
} catch (FileUploadException e) {
} catch (Exception ex) {

Logger.getLogger(Upload.class.getName()).log(Level.SEVERE, null,
ex);
}
} finally {
out.close();
}
}
}

51
 private static String getStringFromInputStream(InputStream
is,String fileType) {
String line = null;

if(fileType!=null){ //is a docx

try {
// fis = new FileInputStream(new File(fileName));
XWPFDocument doc = new XWPFDocument(is);
XWPFWordExtractor extract = new XWPFWordExtractor(doc);
System.out.println(extract.getText());
return extract.getText();

} catch (IOException e) {

e.printStackTrace();
}
}
else { //is not a docx
try {
HWPFDocument doc = new HWPFDocument(is);
// WordExtractor extractor = new WordExtractor(doc);
// System.out.println(extractor.getText());
} catch (IOException e) {
e.printStackTrace();
}
}
return line ;
}

// <editor-fold defaultstate="collapsed" desc="HttpServlet

methods. Click on the + sign on the left to edit the code.">

/**
* Handles the HTTP <code>GET</code> method.
*
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/
@Override
protected void doGet(HttpServletRequest request,
HttpServletResponse response)
throws ServletException, IOException {
processRequest(request, response);
}

/**
* Handles the HTTP <code>POST</code> method.
52
 *
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/
@Override
protected void doPost(HttpServletRequest request,
HttpServletResponse response)
throws ServletException, IOException {
processRequest(request, response);
}

/**
* Returns a short description of the servlet.
*
* @return a String containing servlet description
*/
@Override
public String getServletInfo() {
return "Short description";
}// </editor-fold>

53