Department of M.C.

Loyola Academy pg. 1

Department of M.C.A

ABSTRACT

In a typical LAN managed by a system administrator there are some common problems faced
on day to day basis. These problems fall under two main categories.

One is to track the systems hardware and software configuration, allocation of system
resources to the user. Other is maintenance of complaint register, to track, identify and report
status on complaints received by users on system, LAN and other entities within the network.

The biggest challenge faced would be allocation of resource to a user. Consider a simple
college scenario where students need to be allotted systems for their practical work.

The general tendency would be to create a machine allocation chart which is nothing but a
schedule of student to a system. Since there allocations happen manually; its time
consuming.

Due to pressure and negligence there may be instances where these chart are not updated
which can lead to unhealthy arguments and baseless decision.

Loyola Academy pg. 2

Department of M.C.A

PROBLEM ANALYSIS

Loyola Academy pg. 3

Department of M.C.A

1. INTRODUCTION

Scope

The automated system provides facilities for student to access the slot allocation system services
to book the system and get a confirmation. Once the system is booked the machine allocation
chart will be updated and the system will be reserved for the user for a particular duration and
date. At any given point of time we can analyze the machine allocation chart to find out the
availability of the systems in the lab.

Overview

Overall description consists of background of the entire specific requirement. It also gives
explanation about actor and function which is used. It gives explanation about architecture
diagram and it also gives what we are assumed and dependencies. It also support specific
requirement and also it support functional requirement, supplementary requirement other than
actor which is used. It also gives index and appendices. It also gives explanation about any doubt
and queries.

Loyola Academy pg. 4

Department of M.C.A

2. ANALYSIS
2.1 EXISTING SYSTEM
Current system was analyzed to identify the potential drawbacks. The analysis was carried out in
an environment where systems were booked manually. The current system posed several
challenges with respect to entering the slots in the register, maintaining the allocation of slots.
When the number of students increased it became extremely difficult to maintain the registers as
they were more prone to manual data entry errors. To make the scene more worse, there are
situations where one slot is booked for more than one user which in turn can lead confusion.

Limitations in Existing System

 The Booking of the Slots is per hour basis. So if the user has to book the slots for
continuous two hours then he/she has to book twice each time booking 1hour.
 A Centralized view of the processes, resources and the services is being maintained
which may lead to single point failure.
 The system works well only if the necessary LAN connection is set up.

Advantages over Existing System

 The automated system resolves the conflicts in Booking of the Slots.

 The automated system also reduces time complexity as the time spent on the paper work
is reduced. In this era of global warming, this makes a lot of difference.
 Strict surveillance can be achieved which protects the integrity of the organization.
 Monitoring of the system resources and the tasks which the user is entitled to use enables
the administrator to keep track of the tasks the user is performing without actually going
to each user.
 The Maintenance and the Servicing activities enable the administrator to satisfy the needs
of the user.

Loyola Academy pg. 5

Department of M.C.A

2.2 PROPOSED SYSTEM

Each problem need not have a single well defined solution. There may be infinite number of
solutions pertaining to a single problem. To overcome the first problem of Allocation of System
Resources and Booking of Slots, the two proposed solutions are:

Online Booking:

The automated system provides facilities for student to access the slot allocation system
services to book the system and get a confirmation. Once the system is booked the machine
allocation chart will be updated and the system will be reserved for the user for a particular
duration and date. At any given point of time we can analyze the machine allocation chart to find
out the availability of the systems in the lab. To overcome the second problem of Allocation of
System Resources and Booking of Slots, the two proposed solutions are:

Surveillance Module:

The surveillance module in the slot allocation system traces such irregularities and illegal
accessing from users. A restriction can be imposed immediately so that such activities do not
repeat in the near future. The module retrieves the ID, configuration of the client and kills the
process. If the illegal accessing still prevails then remote shut down of the system takes place
based on the IP address of the system.

Loyola Academy pg. 6

Department of M.C.A

SOFTWARE

REQUIREMENT

SPECIFICATION

Loyola Academy pg. 7

Department of M.C.A

2.3 SYSTEM REQUIREMENTS

HARDWARE SPECIFICATIONS (minimum)

Processor : Pentium IV

Hard Disk : 40GB

RAM : 256MB

SOFTWARE SPECIFICATIONS

Operating System : Windows XP/2003

User Interface : HTML, CSS
Client-side Scripting : JavaScript
Programming Language : Java
Web Applications : JDBC/JNDI, Servlets , JSP
IDE/Workbench : MyEclipse8.6
Database : Oracle 10g
Server Deployment : tomcat

Loyola Academy pg. 8

Department of M.C.A

DESIGN

Loyola Academy pg. 9

Department of M.C.A

3. DESIGN
A graphical tool used to describe and analyze the moment of data through a system
manual or automated including the process, stores of data, and delays in the system. Data Flow
Diagrams are the central tool and the basis from which other components are developed. The
transformation of data from input to output, through processes, may be described logically and
independently of the physical components associated with the system. The DFD is also know as
a data flow graph or a bubble chart.

DFDs are the model of the proposed system. They clearly should show the requirements on
which the new system should be built. Later during design activity this is taken as the basis for
drawing the system’s structure charts. The Basic Notation used to create a DFD’s are as follows:

1. Dataflow: Data move in a specific direction from an origin to a destination.

2. Process: People, procedures, or devices that use or produce (Transform) Data. The physical
component is not identified.

Loyola Academy pg. 10

Department of M.C.A

3. Source: External sources or destination of data, which may be People, programs,

organizations or other entities.

4. Data Store: Here data are stored or referenced by a process in the System.

Loyola Academy pg. 11

Department of M.C.A

Fig 3.0 Level 0: Context Level Data Flow Diagram:

LEVEL 0

The Admin, Faculty, Student can perform the actions like they can login and they can check the
slots , holidays, complaints, time table, change password and the can logout at the end. All the
process is done each and every process is stored in the database.

Loyola Academy pg. 12

Department of M.C.A

Fig 3.1 Level 1: Admin Level Data Flow Diagram:

ADMIN LEVEL 1:

In the level 1 the admin can login and he can perform the actions like, he can add a slot, insert
time table, view time table, delete time table, add holidays, delete holidays, view holidays, he
can also add the faculty, view faculty and delete the faculty who are already registered and also
view the students who has registered and also how many student has booked the slot.

Loyola Academy pg. 13

Department of M.C.A

Fig 3.2 Level 1: Student Level Data Flow Diagram:

STUDENT LEVEL 1:

The student should login with an id and a password and then the student book the slot for a
particular day and he can also view the slots and can check how many slots are booked the
student can also delete the slot with a provided booking id. The student can also change the
password and can view the holidays also. If the student has any problem with the system he can
also give a complaint and the student can also check the service message sent from the admin.

Loyola Academy pg. 14

Department of M.C.A

Fig 3.3 Level 1: Faculty Level Data Flow Diagram:

FACULTY LEVEL 1:

The faculty has to login with the id and password and then the faculty can view the time table,
view the holidays, change the password and the logout.

Loyola Academy pg. 15

Department of M.C.A

Fig 3.4 E-R Diagram:

Loyola Academy pg. 16

Department of M.C.A

4. IMPLEMENTATION

1. Admin Module

Admin has higher privileges. He can do all the activities. He can add, modify, delete, view
all the activities. He can add event details.

2. Student Module

Student Allocate slot, view, delete, view holidays during the slot booking the slot details
also in the admin.

3. Faculty Module

a. View time table

b. View Holidays info

c. Change password

Loyola Academy pg. 17

Department of M.C.A

SAMPLE CODE

Loyola Academy pg. 18

Department of M.C.A

5. SAMPLE CODE
 ADMIN LOGIN
package com.dts.aoc.action;
import java.io.IOException;
import java.io.PrintWriter;
import java.util.HashMap;
import javax.servlet.RequestDispatcher;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.servlet.http.HttpSession;
import com.dts.dae.dao.SecurityDAO;
public class AdminLogin extends HttpServlet {
public void doGet(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
response.setContentType("text/html");
PrintWriter out = response.getWriter();
HttpSession session = request.getSession();
String fid = request.getParameter("txt1");
String pass = request.getParameter("txt2");
String path = "login.jsp";
HashMap hm = new SecurityDAO().checkAdminlogin(fid, pass);
if(!hm.isEmpty()){
String sname=(String)hm.get(1);
if (sname.equals("")) {
session.setAttribute("logmsg", "Please enter Correct UserID and Password");
}
Else
{

Loyola Academy pg. 19

Department of M.C.A

String role=(String)hm.get(2);
if(role.equalsIgnoreCase("A")){
path = "AHome.jsp";
}
if(role.equalsIgnoreCase("F")){
path = "FHome.jsp";
}
session.setAttribute("sid", fid);
session.setAttribute("sname", sname);
session.setAttribute("oldpass", pass);
}
}else{
session.setAttribute("logmsg", "Please enter Correct UserID and Password");
}
RequestDispatcher rd = request.getRequestDispatcher(path);
rd.forward(request,response);
out.flush();
out.close();
}
public void doPost(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
response.setContentType("text/html");
PrintWriter out = response.getWriter();
doGet(request, response);
out.flush();
out.close();
}}

Loyola Academy pg. 20

Department of M.C.A

 STUDENT LOGIN
package com.dts.aoc.action;
import java.io.IOException;
import java.io.PrintWriter;
import javax.servlet.RequestDispatcher;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.servlet.http.HttpSession;
import com.dts.dae.dao.SecurityDAO;
import com.dts.dae.dto.RegistrationBean;
public class SLogin extends HttpServlet {
public void doGet(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
HttpSession session = request.getSession();
response.setContentType("text/html");
PrintWriter out = response.getWriter();
String sid = request.getParameter("txt1");
String pass = request.getParameter("txt2");
String path = "slogin.jsp";
String sname = new SecurityDAO().loginCheck(sid, pass);
if (sname.equals("")) {
session.setAttribute("logmsg", "Please enter Correct Student ID and Password ");
}else{
path = "SHome.jsp";
session.setAttribute("sid", sid);
session.setAttribute("sname", sname);
session.setAttribute("op",pass);
}

Loyola Academy pg. 21

Department of M.C.A

RequestDispatcher rd = request.getRequestDispatcher(path);
rd.forward(request,response);
out.flush();
out.close();
}
public void doPost(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
response.setContentType("text/html");
PrintWriter out = response.getWriter();
doGet(request, response);
out.flush();
out.close();
}}

JSP CODE
<%@ page language="java" import="java.util.*" pageEncoding="ISO-8859-1"%>

<% String path = request.getContextPath();

String basePath = request.getScheme() + "://"

+ request.getServerName() + ":" + request.getServerPort() + path + "/";

%> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<html> <head> <base href="<%=basePath%>">

title>My JSP 'AdminMenu.jsp' starting page</title>

<meta http-equiv="pragma" content="no-cache">

<meta http-equiv="cache-control" content="no-cache">

<meta http-equiv="expires" content="0">

<meta http-equiv="keywords" content="keyword1,keyword2,keyword3">

Loyola Academy pg. 22

Department of M.C.A

<meta http-equiv="description" content="This is my page">

<link rel="stylesheet" type="text/css" href="css/menu.css" />

<link href="CSS/menu.css" rel="stylesheet" type="text/css" media="all" />

<script src="CSS/HoverMenu.js" type="text/javascript">

</script> </head><body> <ul id="nav"> <li class="top">

<a href="AHome.jsp" class="top_link"><span>Home</span> </a>

</li> <li class="top">

<a href="#" id="services" class="top_link"><span class="down">Information</span>

</a> <ul class="sub">

<li> <a href="ViewAllotedSlots.jsp" class="parent"><span>AllotedSlots</span>

</a> </li> <li>

<a href="ViewStudents.jsp" class="parent"><span>RegisterdStudents</span>

</a> </li> <li> <a href="ViewComplaint.jsp" class="parent"><span>Complaint</span>

</a> </li> </ul> </li> <li class="top"> <a href="#" id="services" class="top_link"><span
class="down">Time Table </span> </a> <ul class="sub">

<li> <a href="TimeTable.jsp" class="parent"><span>Insert Time Table</span>

</a> </li> <li> <a href="ViewTimeTable.jsp" class="parent"><span>View Time Table</span>

</a> </li> <li> <a href="DeleteTimeTable.jsp" class="parent"><span>Delete Time Table

</span> </a> </li> </ul> </li> <li class="top">

<a href="ViewHolidays.jsp" id="services" class="top_link"><span

class="down">Holidays</span> </a>

<ul class="sub"> <li> <a href="ViewHolidays.jsp" class="parent"><span>View

Loyola Academy pg. 23

Department of M.C.A

Holidays</span> </a> </li> <li>

<a href="AddHolidays.jsp" class="parent"><span>Add

Holidays </span> </a> </li> <li>

<a href="DeleteHolidays.jsp" class="parent">Delete Holidays</a>

</li> </ul> </li> <li class="top">

<a href="Facultyregister.jsp" id="services" class="top_link"><span

class="down">Faculty</span> </a> <ul class="sub"> <li>

<a href="Facultyregister.jsp" class="parent"><span>Faculty

Register</span> </a> </li> <li>

<a href="ViewRegFaculty.jsp" class="parent"> View Registered Faculty</a>

</li> <li> <a href="DeleteRegFaculty.jsp" class="parent"> Delete Registered Faculty</a>

</li> </ul> </li> <li class="top">

<a href="ChangePasswordAdmin.jsp" class="top_link"><span>Change

Password</span> </a> </li> <li class="top">

<a href="LogoutAction.jsp" class="top_link"><span>Logout</span>

</a> </li> </ul> </body>

<%@ page language="java" import="java.util.*" pageEncoding="ISO-8859-1"%>

<% String path = request.getContextPath();

String basePath = request.getScheme() + "://"

+ request.getServerName() + ":" + request.getServerPort()

+ path + "/"; %>

Loyola Academy pg. 24

Department of M.C.A

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<html> <head> <base href="<%=basePath%>">

<title>My JSP 'bookslot.jsp' starting page</title>

<meta http-equiv="pragma" content="no-cache">

<meta http-equiv="cache-control" content="no-cache">

<meta http-equiv="expires" content="0">

<meta http-equiv="keywords" content="keyword1,keyword2,keyword3">

<meta http-equiv="description" content="This is my page">

<link href="CSS/general.css" rel="stylesheet" type="text/css" />

<link href="CSS/controls.css" rel="stylesheet" type="text/css" />

<link href="CSS/buttons.css" rel="stylesheet" type="text/css" />

<link href="CSS/grids.css" rel="stylesheet" type="text/css" />

<link href="CSS/tabs.css" rel="stylesheet" type="text/css" />

<script language="JavaScript" type="text/javascript"

src="Scripts/Common/global.js">

</script> <script language="JavaScript" type="text/javascript"

src="Scripts/Common/common.js"> </script>

<script language="javascript" type="text/javascript"

src="Scripts/Individual/DMSHome.js">

</script> <script language="javascript" type="text/javascript">

var strPathInfo = ""; </script> <script language="JavaScript" type="text/javascript"

Loyola Academy pg. 25

Department of M.C.A

src="Scripts/ts_picker.js"> </script> </head> <body onload="setContentHeight();">

<center> <img src="images/networkingsecurity copy1.jpg">

</center> <div class="wrapper"> <table id="tblContent" width="100%">

<tr> <td class="content"> <div class="tabBar">

<div class="spacerLeft"> <jsp:include page="SMenu.jsp"></jsp:include>

</div></div> <div class="wrapper">

<table id="tblContent" width="100%" border="0" cellspacing="0" cellpadding="0">

<tr> <td class="content"> <div class="barCenter" style="padding: 15px 15px 15px 15px;">

<center> <div class="box" style="padding: 10px; width: 600px;">

<div class="controls"> <table border="0" cellspacing="0" cellpadding="0">

<tr> <td> <div> <form method='post' name="event1"

onsubmit="return validate()" action="./BookSlot">

<table style="font-size: xx-small;">

<tr> <td colspan="2" style="text-align: center; color: green;">

<font style="font-size: 45px;" face="Edwardian Script ITC">Book Slot </font>

</td> </tr> <tr> <td colspan="2" style="color: red; font-size: small;">

<%String msg=""; msg=(String)session.getAttribute("msgslot");

if(msg!=null){out.print(msg);session.setAttribute("msgslot"," ");} %>

</td> </tr> <tr> <td> Date </td> <td> <input type="text" name="eventdate" value=""
readonly="readonly" />

<a href="javascript:show_calendar('document.event1.eventdate',
document.event1.eventdate.value);">

Loyola Academy pg. 26

Department of M.C.A

<img src="images/cal.gif" alt="a" width="18" height="18" border="0" /> </a> </td> </tr> <tr>
<td> Lab Number </td> <td> <select name="ln" id="ln">

<OPTION value="" selected>

-labnumber-

</OPTION> <OPTION value="Lab1">

Lab1 </OPTION>

<OPTION value="Lab2">

Lab2 </OPTION>

<OPTION value="Lab3">

Lab3 </OPTION>

</select> </td> </tr> <tr> <td>

System Number

</td> <td> <select name="systemno" id="date">

<OPTION value="" selected>

-SystemNo-

</OPTION> <OPTION value="01">

01 </OPTION>

<OPTION value="02">

02 </OPTION>

<OPTION value="03">

03 </OPTION>

Loyola Academy pg. 27

Department of M.C.A

<OPTION value="04">

04 </OPTION>

<OPTION value="05">

05 </OPTION>

<OPTION value="06">

06 </OPTION>

</SELECT> </td> </tr> <tr> <td>

Lab Timing

</td> <td> <select name="lt" id="lt">

<OPTION value="" selected>

-labtimeing-

</OPTION> <OPTION value="9AM to 11AM">

9AM to 11AM

</OPTION> <OPTION value="11AM to 1PM">

11AM to 1PM

</OPTION> <OPTION value="2PM to 4PM">

2PM to 4PM

</OPTION> </select> </td> </tr> <tr> <td></td> <td>

<input type="submit" value="Book Slot">

</td> </tr> </table> </form> </div> </div> </td> </tr> </table> </div> </div> </center> </div>
</td> <td class="shadowR"> <img src="Images/spacer.gif" alt="1" width="5" height="5" />

Loyola Academy pg. 28

Department of M.C.A

</td> </tr> <tr> <td class="shadowB">

<img src="Images/spacer.gif" alt="1" width="5" height="5" /> </td> <td class="shadowBR">

<img src="Images/spacer.gif" alt="1" width="5" height="5" /> </td> </tr> </table> </div>

<div class="footer">Developed by ~</div> </td> </tr> </table> </div> </body> </html>

Loyola Academy pg. 29

Department of M.C.A

SCREEN SHOTS

Loyola Academy pg. 30

Department of M.C.A

26. SCREENSHOTS:
HOME PAGE:

6.1 Screenshot for Homepage

Homepage:
This is the home page for Computer Resources Allocation System. It contains Admin, Student
and the Faculty. The Admin, Student and the Faculty must register before login . Admin, Student
and the Faculty must login with a user Id and password.

Loyola Academy pg. 31

Department of M.C.A

STUDENT

Loyola Academy pg. 32

Department of M.C.A

Loyola Academy pg. 33

Department of M.C.A

Loyola Academy pg. 34

Department of M.C.A

6.2 Screenshot for Student

Student:
Student should login with user id and password and after the login the student can book the slot
and also the student can view how many lots are booked. If the student want to delete the slot
they can delete and the student can change the password. The students can view the holidays
before booking the slot and also the service messages provided by the admin.

Loyola Academy pg. 35

Department of M.C.A

ADMIN:

Loyola Academy pg. 36

Department of M.C.A

Loyola Academy pg. 37

Department of M.C.A

Loyola Academy pg. 38

Department of M.C.A

Loyola Academy pg. 39

Department of M.C.A

Loyola Academy pg. 40

Department of M.C.A

Loyola Academy pg. 41

Department of M.C.A

Loyola Academy pg. 42

Department of M.C.A

6.3 Screenshot for Admin:

ADMIN
The Admin has to login with the id and password. The Admin can view the information of the
Allotted Slots and Registered Students and the Complaints provided by the Student. The Amin
can also insert the Time Table, view the Time Table and also Delete the Time Table. The Admin
can view the Holidays and also insert a new Holidays and Delete the Holidays. He /She can view
how many Faculty are there and also the Amin can Register the Faculty and also Delete the
Faculty when the particular Faculty is not working. The Admin can provide a Service Message to
the Student for the Complaint given and the Admin can also change the password.

Loyola Academy pg. 43

Department of M.C.A

FACULTY

Loyola Academy pg. 44

Department of M.C.A

6.4 Screenshot for Faculty:

Faculty
The Faculty has to register to login with id and the password after the Faculty has login they can
check the Time Table provided so that the Faculty can know the classes and also they can view
the holidays and the Faculty can change the password also.

Loyola Academy pg. 45

Department of M.C.A

TESTING

Loyola Academy pg. 46

Department of M.C.A

7.TESTING

OVERVIEW OF TESTING

PURPOSE

 The process of executing a system with the intent of finding an error.

 Testing is defined as the process in which defects are identified, isolated, subjected for
rectification and ensured that product is defect free in order to produce the quality
product and hence customer satisfaction.
 Quality is defined as justification of the requirements
 Defect is nothing but deviation from the requirements
 Defect is nothing but bug.
 Testing --- The presence of bugs
 Testing can demonstrate the presence of bugs, but not their absence
 Debugging and Testing are not the same thing!
 Testing is a systematic attempt to break a program or the AUT
 Debugging is the art or method of uncovering why the script /program did not execute
properly.

Testing Methodologies:

 Black box Testing: is the testing process in which tester can perform testing on an
application without having any internal structural knowledge of application. Usually Test
Engineers are involved in the black box testing.
 White box Testing: is the testing process in which tester can perform testing on an
application with having internal structural knowledge. Usually The Developers are
involved in white box testing.
 Gray Box Testing: is the process in which the combination of black box and white box
tonics’ are used.

Loyola Academy pg. 47

Department of M.C.A

7.1 TYPES OF TESTING

 Smoke Testing: is the process of initial testing in which tester looks for the
availability of all the functionality of the application in order to perform detailed
testing on them. (Main check is for available forms)
 Sanity Testing: is a type of testing that is conducted on an application initially to
check for the proper behavior of an application that is to check all the functionality are
available before the detailed testing is conducted by on them.
 Regression Testing: is one of the best and important testing. Regression testing is the
process in which the functionality, which is already tested before, is once again tested
whenever some new change is added in order to check whether the existing
functionality remains same.
 Re-Testing: is the process in which testing is performed on some functionality which
is already tested before to make sure that the defects are reproducible and to rule out
the environments issues if at all any defects are there.
 Static Testing: is the testing, which is performed on an application when it is not been
executed. ex: GUI, Document Testing
 Dynamic Testing: is the testing which is performed on an application when it is being
executed. ex: Functional testing.
 Alpha Testing: it is a type of user acceptance testing, which is conducted on an
application when it is just before released to the customer.
 Beta-Testing: it is a type of UAT that is conducted on an application when it is
released to the customer, when deployed in to the real time environment and being
accessed by the real time users.
 Monkey Testing: is the process in which abnormal operations, beyond capacity
operations are done on the application to check the stability of it in spite of the users
abnormal behavior.

Loyola Academy pg. 48

Department of M.C.A

 Compatibility testing: it is the testing process in which usually the products are
tested on the environments with different combinations of databases (application
servers, browsers…etc) In order to check how far the product is compatible with all
these environments platform combination.
 Installation Testing: it is the process of testing in which the tester try to install or try
to deploy the module into the corresponding environment by following the guidelines
produced in the deployment document and check whether the installation is successful
or not.
 Adhoc Testing: Adhoc Testing is the process of testing in which unlike the formal
testing where in test case document is used, with out that test case document testing
can be done of an application, to cover that testing of the future which are not covered
in that test case document. Also it is intended to perform GUI testing which may
involve the cosmotic issues.

7.2 TEST CASES

 GUI Test Cases:

 Total no of features that need to be check
 Look & Feel
 Look for Default values if at all any (date & Time, if at all any require)
 Look for spell check
Example for Gui Test cases:

T.C.No Description Expected Actual value Result

value

Check for all the The screen

features in the screen must
1
contain all
the features

Loyola Academy pg. 49

Department of M.C.A

Check for the The

alignment of the alignment
2
objects as per the should be in
validations proper way

 Positive Test Cases:

 The positive flow of the functionality must be considered
 Valid inputs must be used for testing
 Must have the positive perception to verify whether the requirements are
justified.
Example for Positive Test cases:

T.C.No Description Expected value Actual value Result

1 Check for the date Time The date and The date and Success
Auto Display time of the time of the
system must be system must be
displayed displayed

2 Enter the valid doctorno It should accept It should accept Success

into the doctorno field

 Negative Test Cases:

 Must have negative perception.
 Invalid inputs must be used for test.

Loyola Academy pg. 50

Department of M.C.A

Example for Negative Test cases:

T.C.No Description Expected Actual value Result

value

1 Try to modify The Modification Modification failure

information in date should not be should not be
and time allow allow

2 Enter invalid data It should not It should not failure

in to the rewards accept invalid accept invalid
form, click on save data, save data, save
should not should not allow
allow

Loyola Academy pg. 51

Department of M.C.A

8. CONCLUSION

The “Computer Resources Allocation” was successfully designed and is tested for
accuracy and quality.

During this project we have accomplished all the objectives and this project meets the needs of
the organization. The developed will be used in searching, retrieving and generating information
for the concerned requests.

GOALS

 Reduced entry work

 Easy retrieval of information
 Reduced errors due to human intervention
 User friendly screens to enter the data
 Portable and flexible for further enhancement
 Web enabled.
 Fast finding of information requested
.9. FUTURE ENHANCEMENT
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.
 Because it is based on object-oriented design, any further changes can be easily
adaptable.
 Based on the future security issues, security can be improved using emerging
technologies.
 Attendance module can be added
 sub admin module can be added

Loyola Academy pg. 52

Department of M.C.A

10. REFERENCES:

 Java Complete Reference by Herbert Shield

 Database Programming with JDBC and Java by George Reese
 Java and XML By Brett McLaughlin
 Wikipedia, URL: http://www.wikipedia.org.
 Answers.com, Online Dictionary, Encyclopedia and much more, URL:
http://www.answers.com
 Google, URL: http://www.google.co.in
 Project Management URL: http://www.startwright.com/project.ht

Loyola Academy pg. 53